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. High CPU usage after you publish a changed topology in Lync Server 2013 that has the Response Group Service run

High CPU usage after you publish a changed topology in Lync Server 2013 that has the Response Group Service run

View products that this article applies to.

Symptoms

This issue occurs when you make a major change to a Lync topology (for example, adding or removing a server) and then you publish the topology in a Microsoft Lync Server 2013 environment that has the Response Group Service run.

When this issue occurs, the LyncIntFeature or the LyncExtFeature application pool on the Lync Server 2013 front-end server consumes large amounts of CPU resources.

↑ Back to the top

Cause

This issue occurs because the topology snapshot was recomputed multiple times by the Response Group Service.

↑ Back to the top

Resolution

To resolve this issue, install the September 2015 cumulative update 5.0.8308.933 for the Lync Server 2013 Response Group service.

Note This update redesigns and optimizes the computation of the topology snapshot.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbfix, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3083355
Revision : 3
Created on : 4/23/2018
Published on : 4/23/2018
Exists online : False
Views : 195