Microsoft Lync (2011) on Sierra: Nope

This may well be related to how my organisation uses an antiquated version of Exchange, and the fact that I'm using Lync 2011, however, it will not work on macOS Sierra -- starts up, tries to authenticate, then just ceases.


In looking at tcpdump and Console (I like the new Console.app!) there's not a lot of clues given, but, I have the feeling it is related to ATS and the various TLS requirements. Even though I've trusted all the right certificates and whatnot, it won't log in.


Just posting this to make other people's lives easier...

Lync 14.3.3 seems to work for me.

Though it seems to have a problem stating people's status. Everyone is listed as "presence unknown", unless I search for a contact, then it lists their proper status. Have not tried any other functions.

Microsoft Lync wants to use the "OC_KeyContainer_email@.com" keyhain. Please enter the keychain password.


Will not take the password. Cancelling bypassess and Lync works, just happens upon Lync Logon.


Any thoughts or suggestions?

OneDrive was giving me the same error...open Keychain Access and find any saved password with Lync in it and delete it, then try again.


For OneDrive I had to remove the entry called OneDrive Cached Credential

I actually had to go into the Keychains folder under the Library subfolder to remove the OC_KeyContain... file. Then Lync started up with no difficulties

So, here's my Lync update:


Using the same version of Lync on a MacPro and an iMac, both running macOS Sierra DP 4:


1) It works fine on the iMac

2) It hangs HARD on the MacPro, requring a Force Quit


The primary symptom is that the applicaiton launches fine, but, as soon as I type my password and click on Sign In, the button sort of greys out and the application (and entire system) grind to a halt.


.spin and .hang files are created in the DiagnosticReports (sending to Apple, just in case), and I have to Force Quit to recover the system.


From one of the .spin files:

Command: Microsoft Lync

Path: /Applications/Microsoft Lync.app/Contents/MacOS/Microsoft Lync

Version: 14.4.1 (14.4.1)

Build Version: 0

Source Version: 160608


Fllowed by a lot of detail in the stacks:


Heaviest stack for the main thread of the target process:

100 ??? (Microsoft Lync + 8261) [0xf9045]

100 ??? (Microsoft Lync + 8363) [0xf90ab]

100 NSApplicationMain + 1368 (AppKit + 26913) [0x9255f921]

100 -[NSApplication run] + 1018 (AppKit + 235385) [0x92592779]

100 ??? (Microsoft Lync + 32085189) [0x1f904c5]

100 -[NSApplication(NSEvent) sendEvent:] + 3627 (AppKit + 7607875) [0x92c9a643]

100 -[NSWindow(NSEventRouting) sendEvent:] + 547 (AppKit + 9018721) [0x92df2d61]

100 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 5876 (AppKit + 9025491) [0x92df47d3]

100 -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 5864 (AppKit + 9034991) [0x92df6cef]

100 -[NSControl mouseDown:] + 686 (AppKit + 2674492) [0x927e5f3c]

100 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 783 (AppKit + 2948010) [0x92828baa]

100 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 287 (AppKit + 2678054) [0x927e6d26]

100 -[NSCell _MSMessengerTrackMouse:inRect:ofView:untilMouseUp:] + 2000 (AppKit + 4920367) [0x92a0a42f]

100 -[NSButtonCell _sendActionFrom:] + 105 (AppKit + 2948708) [0x92828e64]

100 -[NSCell _sendActionFrom:] + 120 (AppKit + 2685803) [0x927e8b6b]

100 _os_activity_initiate + 79 (libsystem_trace.dylib + 23232) [0x9f989ac0]

100 __26-[NSCell _sendActionFrom:]_block_invoke + 151 (AppKit + 2685992) [0x927e8c28]

100 -[NSControl sendAction:to:] + 85 (AppKit + 2686226) [0x927e8d12]

100 -[NSApplication(NSResponder) sendAction:to:from:] + 584 (AppKit + 7618302) [0x92c9cefe]

100 _os_activity_initiate + 79 (libsystem_trace.dylib + 23232) [0x9f989ac0]

100 __49-[NSApplication(NSResponder) sendAction:to:from:]_block_invoke + 35 (AppKit + 7618430) [0x92c9cf7e]

100 -[NSObject performSelector:withObject:] + 59 (libobjc.A.dylib + 35994) [0x9ef0bc9a]

100 ??? (Microsoft Lync + 32854624) [0x204c260]

100 ??? (Microsoft Lync + 32797470) [0x203e31e]

100 ??? (Microsoft Lync + 33578712) [0x20fced8]

100 ??? (Microsoft Lync + 34144538) [0x218711a]

100 ??? (Microsoft Lync + 34144079) [0x2186f4f]

100 ??? (Microsoft Lync + 21046575) [0x150952f]

100 ??? (Microsoft Lync + 31792355) [0x1f48ce3]

100 ??? (Microsoft Lync + 31784399) [0x1f46dcf]

94 ??? (Microsoft Lync + 31783962) [0x1f46c1a]

94 SecKeychainCopyDefault + 44 (Security + 1822622) [0x994cdf9e]

52 Security::KeychainCore::StorageManager::defaultKeychain() + 124 (Security + 1888170) [0x994ddfaa]

47 Security::KeychainCore::StorageManager::keychain(Security::DLDbIdentifier const&) + 104 (Security + 90932) [0x99327334]

47 stat$INODE64 + 10 (libsystem_kernel.dylib + 119174) [0x9f891186]

*47 hndl_unix_scall + 216 (kernel + 699448) [0xffffff80002aac38]

*47 unix_syscall + 519 (kernel + 6457223) [0xffffff8000828787]

*47 stat64 + 58 (kernel + 3365354) [0xffffff80005359ea]

*41 ??? (kernel + 3363127) [0xffffff8000535137]

*41 nameiat + 128 (kernel + 3341152) [0xffffff800052fb60]

*41 namei + 2001 (kernel + 3245313) [0xffffff8000518501]

*41 lookup + 484 (kernel + 3248692) [0xffffff8000519234]

*41 kauth_authorize_action + 84 (kernel + 5541508) [0xffffff8000748e84]

*41 ??? (kernel + 3298162) [0xffffff8000525372]

*41 vnode_getattr + 286 (kernel + 3478222) [0xffffff80005512ce]

*38 ??? (kernel + 3479864) [0xffffff8000551938]

*38 vn_getxattr + 1289 (kernel + 3438921) [0xffffff8000547949]

*38 hfs_vnop_getxattr + 254 (HFS + 111723) [0xffffff7f8227b46b]

*22 hfs_getxattr_internal + 1479 (HFS + 113950) [0xffffff7f8227bd1e]

*21 hfs_systemfile_lock + 423 (HFS + 317126) [0xffffff7f822ad6c6]

*21 hfs_lock + 91 (HFS + 276721) [0xffffff7f822a38f1]

*21 lck_rw_lock_exclusive_gen + 576 (kernel + 2104096) [0xffffff8000401b20]

*20 thread_block_reason + 222 (kernel + 1112974) [0xffffff800030fb8e]

*20 ??? (kernel + 1117547) [0xffffff8000310d6b]

*12 machine_switch_context + 206 (kernel + 2118990) [0xffffff800040554e] (runnable)


And so on. It may well be there's something in the Keychain causing this (but I've looked at the advice in this thread and it's not provided any clues). It's just peculiar that it's this one system, and not both.


Interestingly: The old Communicator works just fine.

I realize this doesn't solve the problem and is more of a workaround, but the Skype for Business preview works great.


https://www.skypepreview.com

Lync 14.4.1 (160608) works fine.

This solved my problem as well.


1) Quit Lync 2011

2) rm /Users/<USERNAME>/Library/Keychains/OC_KeyContainer__*

3) Launch Lync, where the above file gets recreated.


Voila.

I had the same issues and finally got it resolved. I had valid certs on my local machine but removing them and importing new ones from my Lync server resolved the issue. Lync was working with no issue proir to updating to 10.12.


1. Delete the OC_KeyContainer from your keychain and any certs you may have installed for Lync.

2. Export new certs from your Lync server

- open ISS on your Lync server, navigate to server > server cerficiates

- open each cert, go to the details tab, and select the copy to file option.

- export them with default values (DER X.509) and copy them to your local Mac

3. Double click each cert to import them, import as login and system certs. Be sure to open each cert afterwards and select "always trust" in the top dropdown menu. Input your password to confirm changes.

We are usin lync connected to office 365 , I have descover that lync works just fine when connected to the internet, but not when connected to VPN or the office LAN.


Still looking for answere but i hope the above provides some one with a hint


regards


Julian

My proble were fixed when i checked my certificates. seems instaling macOS Sierra several of them to not trusted. You can also set what to trust them for.


regards


Julian

Fixed my issue, thanks!

Here is how to solve this problem :

  1. ask your IT to download from the Lync Server the corresponding certificate and give it to you ;
  2. open that certificate (*.cer file) on your mac (runnin macOS Sierra) ;
  3. this will open the keychain and add that certificate in it : open that newly added certificate (double-click), and change the settings to "Always approve" ;


Then try again to log in.

This solved my problem while I was facing the same issue.


I hope it helped.

That was my case. After installing the new version of OS some of the company's certificates were not trusted again and I needed to change their status back to trusted.


It would be good to have some logs or info from Microsoft Lync to diagnose the problem.

Microsoft Lync (2011) on Sierra: Nope
 
 
Q