When trying to Edit or Create a Persistent Chat Room in Lync 2013 you may encounter a problem opening the Persistent Chat Room management web site.
Error : “Server Could not process your request. Please try again later”
While this error does not give you a clear indication what is wrong we can check other things on the server.
- Check the Persistent Chat Server state
- Check the Application log for ASP.NET Errors
- Use OCSLogger.exe and find problems related to Persistent Chat
The state of the Persistent Chat service is normal
We find an ASP.NET error but without any clear indication what is wrong
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/17/2013 1:22:39 PM
Event time (UTC): 4/17/2013 11:22:39 AM
Event ID: d66e27a7a4ee4b81a7a95c97c3a48b92
Event sequence: 11
Event occurrence: 5
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/34578/ROOT/PersistentChat/RM/Handler-7-130106607609071496
Trust level: Full
Application Virtual Path: /PersistentChat/RM/Handler
Application Path: C:\Program Files\Microsoft Lync Server 2013\Web Components\PersistentChat\Ext\RM\Handler\
Machine name: SERVER
Process information:
Process ID: 11644
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: FailureResponseException
Exception message: A 504 (Server time-out) response was received from the network and the operation failed. See the exception details for more information.
at Microsoft.Rtc.Collaboration.PersistentChat.Internal.AsyncResultNoResult.EndInvoke(Int32 millisecondsTimeout)
at Microsoft.Rtc.Collaboration.PersistentChat.Internal.MessageRouter.EndCommand(GenericAsyncResult`1 asyncCommand)
Request information:
Request URL: https://externalurl.domain.com:4443/PersistentChat/RM/Handler/ManagementHandler.ashx
Request path: /PersistentChat/RM/Handler/ManagementHandler.ashx
User host address: 192.168.0.1
User: user@domain.com
Is authenticated: True
Authentication Type: WebTicketAssertions
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 62
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at Microsoft.Rtc.Collaboration.PersistentChat.Internal.AsyncResultNoResult.EndInvoke(Int32 millisecondsTimeout)
at Microsoft.Rtc.Collaboration.PersistentChat.Internal.MessageRouter.EndCommand(GenericAsyncResult`1 asyncCommand)
Even using OCSLogger does not help us really
TL_INFO(TF_COMPONENT) [3]2D7C.10B4::04/17/2013-11:30:01.298.0000065d (ChatRoomManagement,Default.Page_Load:834.idx(63))(0000000000E11E04)Loading Room Management default page.
TL_INFO(TF_COMPONENT) [3]2D7C.10B4::04/17/2013-11:30:01.298.0000065e (ChatRoomManagement,Default.get_ValidRoomRequestFormat:834.idx(144))(0000000000E11E04)QueryString contains no 'id'.
TL_INFO(TF_COMPONENT) [3]2D7C.10B4::04/17/2013-11:30:01.298.0000065f (ChatRoomManagement,Default.get_ValidRoomRequestFormat:834.idx(144))(0000000000E11E04)QueryString contains no 'id'.
TL_INFO(TF_COMPONENT) [3]2D7C.10B4::04/17/2013-11:30:01.300.00000660 (ChatRoomManagement,Default.FoundClientSpecifiedLanguage:834.idx(336))(0000000000E11E04)Trying to find the resource for client requested language en-US
TL_INFO(TF_COMPONENT) [0]2D7C.10B4::04/17/2013-11:30:01.301.00000661 (ChatRoomManagement,Default.FoundClientSpecifiedLanguage:834.idx(343))(0000000000E11E04)Resource en-US matches the client requested language en-US
TL_INFO(TF_COMPONENT) [0]2D7C.10B4::04/17/2013-11:30:01.301.00000662 (ChatRoomManagement,Default.FoundClientSpecifiedLanguage:834.idx(336))(0000000000E11E04)Trying to find the resource for client requested language en-US
TL_INFO(TF_COMPONENT) [0]2D7C.10B4::04/17/2013-11:30:01.301.00000663 (ChatRoomManagement,Default.FoundClientSpecifiedLanguage:834.idx(343))(0000000000E11E04)Resource en-US matches the client requested language en-US
TL_INFO(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:09.764.00000664 (ChatRoomManagement,ManagementHandler.BeginProcessRequest:2092.idx(372))(0000000002F5F5AF)BeginProcessRequest: Trying to figure the exact request from client side
TL_INFO(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:09.764.00000665 (ChatRoomManagement,ManagementHandler.BeginProcessRequest:2092.idx(390))(0000000002F5F5AF)BeginProcessRequest: About to process landing page request.
TL_INFO(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:09.765.00000666 (ChatRoomManagement,ManagementBase.constructor:1199.idx(50))Trying to get the identity of the sip-authenticated user.
TL_INFO(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:09.767.00000667 (ChatRoomManagement,ManagementBase.GetNewConnection:1199.idx(84))(000000000218BE67)Primary home server: server.domain.com
TL_INFO(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:09.767.00000668 (ChatRoomManagement,ManagementBase.ConnectPersistentChatServer:1199.idx(178))(000000000218BE67)About to get provisioning data for userEndpoint
TL_INFO(TF_COMPONENT) [0]2D7C.3714::04/17/2013-11:30:09.824.00000669 (ChatRoomManagement,ManagementBase.ConnectPersistentChatServer:1199.idx(216))(000000000218BE67)About to establish Persistent chat endpoint to sip:GC-1-PersistentChatService-17@domain.be
TL_INFO(TF_COMPONENT) [2]3330.1B6C::04/17/2013-11:30:09.870.0000066a (ChatServer,UcmaTransport.HandleSignaling_SessionReceived:1732.idx(399))(0000000001A5B562)Session invite from <sip:server.domain.com:5041;grid>. Details=Federated: False, UserAgent: RTCC/5.0.0.0 rmweb/5.0.0.0, ClientVersion: 0.0.0.0/Current
TL_INFO(TF_COMPONENT) [1]3330.1B6C::04/17/2013-11:30:09.874.0000066b (ChatServer,ChannelServer.ShouldAcceptIncomingSession:663.idx(1379))(00000000012719D7)IncomingUser: <sip:user@domain.com:ebd59c1c-7f4c-4ac6-ae57-96bce934a6aa>, Federated: <False>, Result: <Allowed>, ActiveEndpoints: <4>, ActiveUsers: <3>, Principal: <[10]sip:user@domain.com> fetch took <00:00:00.0000573>.
TL_ERROR(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:10.058.0000066c (ChatRoomManagement,ManagementBase.ConnectPersistentChatServer:1199.idx(230))(000000000218BE67)Failed to establish Persistent chat endpoint to sip:GC-1-PersistentChatService-17@domain.be because of Command failed - see inner exception for details.
TL_ERROR(TF_COMPONENT) [1]2D7C.3714::04/17/2013-11:30:10.083.0000066d (ChatRoomManagement,ManagementHandler.BeginProcessRequest:2092.idx(555))(0000000002F5F5AF)Exception on BeginProcessRequest: Microsoft.Rtc.Collaboration.PersistentChat.CommandFailedException: Command failed - see inner exception for details. ---> Microsoft.Rtc.Signaling.FailureResponseException: A 504 (Server time-out) response was received from the network and the operation failed. See the exception details for more information.
at Microsoft.Rtc.Collaboration.PersistentChat.Internal.AsyncResultNoResult.EndInvoke(Int32 millisecondsTimeout)
at Microsoft.Rtc.Collaboration.PersistentChat.Internal.MessageRouter.EndCommand(GenericAsyncResult`1 asyncCommand)
--- End of inner exception stack trace ---
at Microsoft.Rtc.Collaboration.PersistentChat.Internal.AsyncResultNoResult.EndInvoke(Int32 millisecondsTimeout)
at Microsoft.Rtc.Collaboration.PersistentChat.PersistentChatEndpoint.EndEstablish(IAsyncResult asyncResult)
at Microsoft.Rtc.Internal.RMWebHandler.ManagementBase.ConnectPersistentChatServer(UserEndpoint userEndpoint)
at Microsoft.Rtc.Internal.RMWebHandler.ManagementBase.GetNewConnection(CollaborationPlatform collabPlatform, String sSipUri)
at Microsoft.Rtc.Internal.RMWebHandler.ManagementLanding..ctor(CollaborationPlatform collabPlatform, HttpContext cntx, String localRegistrarFqdn)
at Microsoft.Rtc.Internal.RMWebHandler.ManagementHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)!
RESOLUTION:
While all of these logs and messages don’t say anything I decided to move my user which was currently hosted on the SBA in a branch office to the Front-End Server in the Datacenter and surprisingly this fixed the Persistent Chat Room website issues.
So I guess this must still be a big in Lync 2013