The Channel service stops when a user signs in to a Group Chat client in Lync Server 2010, Group Chat

Article ID: 2666342 - View products that this article applies to.
Expand all | Collapse all

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:

Time:     Time
ID:       6394
Level:    Information
Source: LS MGC SERVER
Machine:  Computer name
Message:  Server 1 successfully handled subscribe from peer 2, <2> <PeerService> <ChannelServer>. [Active servers list
            - This Server: <1> <PeerService> <LookupServer>  
             - Peer Server 1: <3> <PeerService> <LookupServer> (99dfeb35-d450-407d-bfb2-e43f887b999b), 
             - Peer Server 2: <4> <PeerService> <ChannelServer> (6801ad05-fe0f-4c95-b3fc-106d7fbc6ddd), 
             - Peer Server 3: <2> <PeerService> <ChannelServer> (0babf208-4a74-4e07-b544-5f736d27934c)]

Time: Time
ID: 6384
Level: Error
Source: LS MGC SERVER
Machine: Computer name
Message: Channel server encountered a fatal error Fatal Error processing internal quit command message: Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Messaging.QuitCommandMessage, Reason: Operation failure while processing command QuitCommandMessage. Processing will NOT continue. Stack trace
at Microsoft.Rtc.Internal.Chat.Server.Channel.MessageProcessors.QuitCommandProcessor.CreateExceptionReply(ITransportMessage message, String reason, Exception ex)
at Microsoft.Rtc.Internal.Chat.Server.Channel.MessageProcessors.MessageProcessor`2.Microsoft.Rtc.Internal.Chat.Server.Channel.MessageProcessors.IMessageProcessor.ProcessInSafeMode(ITransportMessage transportMessage, ProcessStatus status)
at Microsoft.Rtc.Internal.Chat.Server.Channel.MessageProcessors.RoutingProcessor.Process(ITransportMessage message, ProcessStatus status)
at Microsoft.Rtc.Internal.Chat.Server.Channel.MessageProcessors.RoutingProcessor.Process(ITransportMessage message)
at Microsoft.Rtc.Internal.Chat.Server.Channel.Server.ChannelServer.ProcessWithNoMessageLock(ITransportMessage inboundMessage).


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

Properties

Article ID: 2666342 - Last Review: March 1, 2012 - Revision: 1.0
APPLIES TO
  • Microsoft Lync Server 2010, Group Chat
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix KB2666342

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com