Symptoms

Consider the following scenario:

  • You set up a Group Chat server pool that contains several Group Chat servers in a Microsoft Lync Server 2010 environment.

  • You configure the log level for the Channel service to Debug or Trace.

  • A user signs in to a Group Chat client.

In this scenario, the Channel service on the last started Group Chat Server in the Group Chat server pool stops. Additionally, the following events are logged in the Application log:

Cause

This issue occurs because an object reference in a Group Chat function is set to a NULL when the function tries to determine whether the client is local or remote. This causes the Channel service to stop when the logging is set to a DEBUG level or a higher level.

Resolution

To resolve this issue, install the following cumulative update:

2670342 Description of the cumulative update for Lync Server 2010, Group Chat: February 2012

Workaround

To work around this issue, set the log level of the Channel service to INFO level on all Group Chat servers in the pool.

More Information

For more information about how to set log levels for the Channel service, Lookup service, or Web service, visit the following Microsoft website:

How to set log levels for the Channel service, Lookup service, or Web service

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×