GroupChat Server is not syncing in changes to Chat Room membership, via Distribution List
This issue could happen, if the changes to the Distribution list are not completely synced in from the DC. In certain scenarios, we have a number of ports on the GroupChat Server in TIME_WAIT state when talking to the GC.
The following log entry in ChannelServer log, may be used to determine such a state:
276799 Microsoft.Rtc.Chat.MgcCommon.Exceptions.MgcActiveDirectoryException: Error accessing active directory. ---> System.Runtime.InteropServices.COMException (0x8007203A): The server is not operational.
Multiple instances of:
262061 DEBUG |20100917-14:04:53.126| 14: |ActiveDirectoryConne.ConnectToAD | connecting to AD host <… >
Considering lowering the value of TcpTimedWaitDelay. The default is fairly high.
Consider increasing the number of available ports.
After making the above changes (which do require a reboot) monitor the ChannelServer logs for instances of the traces mentioned in the Cause Section.
I was asked if this registry needs to be applied to GroupChat Server ? the answer is YES.
What value do I set for the above registry keys ? It depends on the customer scenario, and their AD setup which will determine, how many ports they are currently using and are in TIME_WAIT state. You can begin by setting the values as follows and monitor the behavior. There are no magic numbers that I can come up with to work for all customers.
The value of TcpTimedWaitDelay lowered to 30s.
Number of available ports increased to 10000.
This is a temporary workaround.
The fix is to apply the next Cumulative update for Group Chat Server, when it is available through KB 2437381 later.
We are currently not planning on releasing KB 2437381. It will be available through Microsoft Support, via download available from Hotfix site (hosted internally at Microsoft). If you believe you can benefit from this hotfix, please contact Microsoft Support and state the KB 2437381, for the hotfix.