Applies to: Lync 2013 Lync Server 2013
Nov 20, 2014 Microsoft Skype for Business aspires to close the gap between large enterprises using Lync for corporate communications, and consumers and small businesses using Skype since Microsoft’s acquisition of the video service in 2011. Now, both large and small businesses will have access to the UC features- in addition to the security and control - that Lync offered, rolled into the familiar. Solution: In the Lync for Mac sign-in window, check your user ID and password for typos. If you’re using Office 365, use the same user ID and password that you use to sign in to Office 365, for example, aprilr@contoso.onmicrosoft.com. Passwords are case-sensitive.
There are several required steps when you install a managed application on Microsoft Lync Server 2013. This article describes those steps and the errors Lync Server 2013 may return when the installation is not done correctly.
Lync Server 2013
A managed code application that references the Lync Server API.
Membership in the local computer RTC Server Applications group on the computer where the application is installed.
Registering an application requires use of the management shell, and PowerShell cmdlets. Also, it is useful to be familiar with the Lync Server API, and the tools for managing Lync Server.
Table 1. Core concepts for registering a managed application
Article title | Description |
---|---|
Familiarity with the Lync Server API. | |
Familiarity with Lync Server administrative tools. | |
Use of the Lync Server Management Shell. |
Use the Lync Server SDK to create server applications that extend and customize Lync Server features. For example, features to add might include forwarding messages to different targets, managing message content, or modifying message headers.
There are two types of server applications created with the Lync Server SDK: script applications and managed code applications. Server applications are often deployed on an application server. In simple topologies server applications can be deployed to the Lync Front End server. To run a managed or script application on Lync Server you must register it, which includes configuring and deploying the application on a computer in the Lync Server domain.
For typical coding patterns in Lync Server applications, see the samples listed in Lync developer sample applications.
The tasks listed here are required to register a managed server application.
Compile the application and the application manifest, configured as a 64-bit application.
Copy the application executable and manifest files to the server.
Log in to the server as a member of the local computer RTC Server Applications group.
Use the cmdlet New-CsServerApplication to create the server application.
Ensure that the URI in the manifest file is identical to the URI used in the New-CsServerApplication cmdlet.
Start the application executable. Using administrator privileges to start the executable is recommended.
The following list contains some common errors seen when registering an application and the steps commonly used to fix the error.
Error text | Try this |
---|---|
Is not a valid Win32 application | Rebuild the application, and ensure the build is configured for a 64-bit application. |
Registration time-out | Use the cmdlet Get-CsServerApplication to verify that the application exists on the server. Verify that the URI listed on the server application is identical to the URI in the manifest. |
Queue could not be opened | Make sure you are logged on as a member of the local computer RTC Server Applications group. Then, log off, log back in, and try again. |
Server application failed to start | Make sure that the URI listed on the server application is identical to the URI in the manifest. |
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.
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 Update for Lync for Mac 2011.
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:
Kerberos authentication:Leave this option cleared. Office 365 uses the Microsoft Azure AD authentication system for authentication.
The following table describes error messages that may occur when users sign in or use Lync for Mac with Skype for Business Online.
Error | Cause | Type | Resolution |
---|---|---|---|
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. | Client | To troubleshoot this issue, see the Make sure that users follow the correct steps when they sign in to Skype for Business Online section. |
Lync was unable to sign in. Please verify your logon credentials and try again. If the problem continues, please contact your support team. | Various causes. | Client | To troubleshoot this issue, see the Users may be unable to sign in unless they first use an incorrect sign-in address section. |
The user name, password, or domain appears to be incorrect. Ensure that you entered them correctly. If the problem continues, please contact your support team. | This issue may occur in scenarios in which a federated user tries to sign in, and this user has a password that's longer than 16 characters. | User Account | To troubleshoot this issue, see the Federated users synchronized from on-premises Active Directory Domain Services can't sign in by using a password that's longer than 16 characters section. |
EXC_BAD_ACCESS | This issue may occur if Lync for Mac tries to integrate or schedule meetings with an Exchange mailbox that isn't hosted in Exchange Online. | Client | To troubleshoot this issue, see the Lync for Mac crashes and the user receives an EXC_BAD_ACCESS error or Clear cached data and corrupted certificates in Lync sections. |
Use one or more of the following methods, as appropriate for your situation.
Try to sign in to Skype for Business Online by using an incorrect sign-in address. That is, a sign-in address that you know won't work. For example, EmailAddress @contoso.com.
Note
When you do this, sign-in will fail. This is expected behavior.
After the sign-in fails, sign in by using the correct sign-in address. For example, EmailAddress@contoso.com.
To flush the DNS cache, do one of the following, depending on the version of Mac OS that you're running:
First, delete the following folders:
Then, delete any corrupted or cached certificates. To do this, follow these steps:
2020-3-19 Outlook 15.26.1 for Mac Search not working Hi there, I have recently updated to Outlook for Mac 15.26.1, and since my update, my searches in the top right hand box are only giving me partial results from over a week ago. Outlook for Mac 2011 does not work with macOS 10.15 Catalina. Sending meeting updates with REST calendar sharing feature in Outlook for Mac. Categories no longer appear in the sidebar of individual calendars. Known issues syncing Google accounts to the.
Open the Keychain Access certificate management utility. To do this, in Finder, click Applications, click Utilities, and then click Keychain Access. Or, search for Keychain Access by using Spotlight.
In the left pane, click login, and then click Certificates.
In the right pane, find a certificate that's named Unknown or Communications Server, select it, and then delete it.
Note You may have to unlock your keychain by using your password.
Close Keychain Access.
Restart Lync for Mac.
Sep 01, 2019 Step 3: Scan for and remove VIRUS ALERT FROM MICROSOFT. Files from your MacWhen you are facing problems on your Mac as a result of unwanted scripts and programs such as VIRUS ALERT FROM MICROSOFT, the recommended way of eliminating the threat is by using an anti-malware program. Microsoft virus alert on mac. 'VIRUS ALERT FROM MICROSOFT' is virtually identical to Firefox Requires A Manual Update, CRITICAL ALERT FROM MICROSOFT, Windows Firewall Warning Alert, and many others. All state that the system is damaged/corrupted, however, these claims are merely attempts to. Nov 15, 2018 Fake pop-up like “Virus Alert from Microsoft.This computer is BLOCKED” is a fake warning that aims to mislead computer users either to download recommended program or call technical support numbers. It is important to note that fake “Virus Alert from Microsoft” usually pop-ups upon visiting malicious websites that was made solely to present the bogus alert in an attempt to mislead. If you are experiencing problems while trying to remove microsoft warning alert virus from your computer, please ask for assistance in our malware support forum. Post a comment: If you have additional information on microsoft warning alert virus or it's removal. Aug 29, 2017 It doesn't even fit the definition of a virus or malware so it's a whole new world. Unfortunately, many people post here that they did fall for it and among having to change passwords, cancel credit cards, etc, reloading Windows is the best way.
Important
Before you perform the next step, try reproduce the issue by using a new test user account. If the issue doesn't repeat in the new account, then follow these steps:
Open Keychain Access Preferences, and then click Reset My Default Keychain.
Open Finder, locate the following folders, and then delete them:
/Users/Home Folder/Documents/Microsoft User Data/Microsoft Lync Data
/Users/Home Folder/Documents/Microsoft User Data/Microsoft Lync History
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.
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:
DocumentsMicrosoft User DataMicrosoft 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.
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:
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:
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//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.
If the steps in this article don't resolve the issue, try to do a clean uninstallation of Lync for Mac 2011, and then reinstall the application. For more information about how to do a clean uninstallation of Lync for Mac 2011, see How to do a clean uninstallation 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.
Still need help? Go to Microsoft Community.