Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "Limited functionality is available due to outage" in Lync client when Lync Server 2013 replication queue is full

"Limited functionality is available due to outage" in Lync client when Lync Server 2013 replication queue is full

View products that this article applies to.

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).

↑ Back to the top

Cause

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

↑ Back to the top

Workaround

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

↑ Back to the top

Resolution

To resolve this issue, install the following cumulative update:
2967486 August 2014 Cumulative Update 5.0.8308.738 for Lync Server 2013

↑ Back to the top

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

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2983199
Revision : 1
Created on : 1/7/2017
Published on : 8/7/2014
Exists online : False
Views : 191