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.

Event ID 31128 when RGS can't synchronize an Agent Group member's SIP address in Lync Server 2013


View products that this article applies to.

Symptoms

Assume that a member of a distribution list is also a member of a Response Group service (RGS) agent group in a Microsoft Lync Server 2013 environment. When the member's SIP address is changed, all related changes are blocked from synchronizing from Active Directory to the RGS database. Also, event ID 31128 is logged as follows:


Additionally, users who were recently added to the RGS agent group experience the following issues:
  • Newly added users don't receive the 'You were added as an agent' notification.
  • Calls that are made to the RGS workflow aren't routed to the newly added RGS agent.

↑ Back to the top


Cause

This issue occurs because the SIP address change prevents RGS from referencing the agent. However, the RGS database indexes agents by using their SIP addresses.

↑ Back to the top


Resolution

To fix this issue, apply the April 2016 cumulative update 5.0.8308.956 for the Lync Server 2013, Response Group Service.

↑ Back to the top


Keywords: kbfix, kbqfe, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3148256
Revision : 1
Created on : 1/7/2017
Published on : 5/20/2016
Exists online : False
Views : 266