This article contains information about how to troubleshoot Lync for Mac issues in Skype for Business Online (formerly Lync Online). It also discusses how to sign in to Skype for Business Online by using Lync for Mac and how to collect log files and system information for Lync for Mac issues.
Before you troubleshoot
First, make sure that users follow the correct steps when they sign in to Skype for Business Online. If users are signing in to Skype for Business Online correctly and the issue persists, use one or more of the other methods later in this article to troubleshoot the issue, as appropriate for your situation.
Note To connect Lync for Mac 2011 to Skype for Business Online in Office 365, you must have Lync for Mac version 14.0.6 or a later version installed. If you use a version that's earlier than version 14.0.6, you may have problems when you sign in to Skype for Business Online because earlier versions have issues that prevent authentication to Skype for Business Online. You can find the latest update at the following Microsoft website:
Make sure that users follow the correct steps when they sign in to Skype for Business Online
To sign in to Skype for Business Online by using Lync for Mac, users should follow these steps:
Start Lync for Mac.
Enter your email address, user ID, and password.
Next to Sign in as, select the presence status that you want to display after you sign in.
If you want to save your credentials, click to select the Remember my password check box. Your credentials will be saved in the Mac OS Keychain and will work until the next time that your password changes or expires.
To configure additional options for connecting to Skype for Business Online, click Advanced. You can configure the following options:
Automatic Configuration: In most cases, this is the correct setting. If the necessary DNS records are present and automatic configuration isn't working, try Manual Configuration.
Manual Configuration: Select this option if automatic configuration is failing, and specify the following values:
Internal server name: sipdir.online.lync.com:443
External server name: sipdir.online.lync.com:443
Kerberos authentication: Leave this option cleared. Office 365 uses the Microsoft Azure AD authentication system for authentication.
If you still aren't able to sign in
The following table describes error messages that may occur when users sign in or use Lync for Mac with Skype for Business Online.
The service might not be available, or you might not be connected to the Internet. Make sure the server is available. Also, make sure your network connection cable is securely connected.
This issue may occur if Lync can’t detect a suitable Lync Server.
Federated users synchronized from on-premises Active Directory Domain Services can't sign in by using a password that's longer than 16 characters
Organizations that have on-premises customer password policies may allow for passwords to exceed 16 characters. By default, the password policy in Office 365 restricts passwords to 16 characters or less. Because of the Windows Challenge/Response (NTLM) authentication mechanism in the Mac OS, passwords that are longer than 16 characters aren't recognized correctly, and this causes sign-in to fail.
To work around this issue, the user should change his or her password to be 16 characters or less. Back to top
Lync for Mac crashes, and the user receives an "EXC_BAD_ACCESS" error
This error message usually occurs when Lync for Mac tries to integrate or schedule meetings with an Exchange mailbox that isn't hosted in Exchange Online. This scenario isn't supported in Skype for Business Online. For the best experience, you should use both Skype for Business Online and Exchange Online. However, if that isn't an option, follow these steps as a potential workaround:
Open Finder, locate the following folder, and then delete it:
Documents\Microsoft User Data\Microsoft Lync Data
Start Lync for Mac, and then sign in to Skype for Business Online.
On the Lync for Mac menu, click Preferences, click Account, and then clear the Use Microsoft Exchange for managing personal information check box.
Note You must perform step 3 quickly after you sign in.
Collect log files and system information for Lync for Mac issues
To collect log files and system information for Lync for Mac issues, follow these steps:
Verify the version of the operating system that's used.
Verify the error message that's returned.
Turn on logging for troubleshooting in Lync for Mac. To do this, follow these steps:
On the Lync menu, click Preferences, and then click General.
Under Logging, click to select the Turn on logging for troubleshooting check box.
Exit Lync for Mac, and then restart Lync for Mac to create a log file.
Reproduce the issue.
Turn off logging for troubleshooting. To do this, follow these steps:
On the Lync menu, click Preferences, and then click General.
Under Logging, clear the Turn on logging for troubleshooting check box.
Collect the log files for Lync for Mac. To do this, follow these steps:
On the menu bar in Finder, click Go, and then click Go to Folder.
In the Go to the folder box, type the path of the logs folder. For example, type /user/<Useraccountfolder>/library/logs. Then, click Go.
Note <Useraccountfolder> is usually the same as the user name that the user uses to log on the computer. The user name can also be found next to the House icon at the top of the Finder window.
In the Logs folder, collect the log files.
Uninstall and reinstall Lync for Mac 2011
If the steps in this article don't resolve the issue, try performing a clean uninstall of Lync for Mac 2011, and then reinstall the application. For more information about how to perform a clean uninstall of Lync for Mac 2011, click the following article number to view the article in the Microsoft Knowledge Base:
2691870 How to perform a clean uninstall of Lync for Mac 2011
If you’re using third-party virtualization software for the Mac, it can coincide with various performance-related issues including but not limited to slow desktop sharing, unexpected poor media quality, possible sign-in and Exchange integration issues. In order to continue, Microsoft technical support may have to confirm that the issue occurs on a computer where the third-party virtualization software isn’t present.
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.