Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

You receive the following message in a Microsoft Lync client in a Lync Server 2013 Enterprise Edition environment:

Limited functionality is available due to an outage
NoteWhen this issue occurs, there is no information that indicates a front-end server is in the Queue Full state in the Event Logs or the Performance Monitor counters. To determine whether the "Queue Full" issue has occurred, you must enable the Lync Server 2013 logging for UserServices. If FailureCode:9 is in the log, the Queue Full issue has occurred. The More Information section describes the simplest method to determine whether the front-end server is in the Queue Full state by using the Centralized Logging Service (CLS).

Cause

This issue occurs because the replication queue between the Primary and the Secondary becomes full. Therefore, the Lync client user receives the message.

Workaround

To work around this issue, you must restart the Lync Server 2013, Server components in the Enterprise Edition pool.

Resolution

To resolve this issue, install the following cumulative update:

2967486 August 2014 Cumulative Update 5.0.8308.738 for Lync Server 2013

More Information

To look for "FailureCode: 9" by using the Centralized Logging Service (CLS), follow these steps:

  1. Start Lync Server Management Shell, and then run the following command:Start-CsClsLogging -Scenario AlwaysOn

  2. Starts CLS Logging for the following Providers:

    • UserServices

    • PowerShell

    • BackupService

    • RtcDbSyncAgent

    To do this, run the following command:Start-CsClsLogging -Scenario HADR -Duration 0:10:0

  3. Wait for 10 minutes, then run the following command:Start-Sleep -Seconds 600

  4. Search and retrieve the logs. To do this, run the following command:Search-CsClsLogging -LogLevel Verbose -OutputFilePath " $env:USERPROFILE\Documents\hadr.txt" –Components UserServices –Verbose

  5. Determine whether the logs contain FailureCode:9. To do this, run the following command:Get-Content " $env:USERPROFILE\Documents\hadr.txt " | Select-String "FailureCode:9" Or, you can open the file (hadr,txt), and then search for FailureCode:9.

For more information about the Centralized Logging Service, go to the following Microsoft website:

General information about the Centralized Logging Service

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×