If it is too far away you may exceed this timeout and your users will be unable to login. So… It turns out that Desktop Director should be pointed at a data collector that sits closest to the database. Procmon shows lots of database communication and our two ZDC’s 303 and 304 are in Edmonton and the database resides in Calgary communication round-trip makes those ZDC’s exceed 10 seconds. Why was it taking so long? It turns out that the ZDC is forced to contact the database with that command as opposed to utilize the LHC (local host cache). I then tried it against 303 and 304 and the command completed in…. With powershell remoting I connected to the ZDC 301 and 302 and ran the command and it completed within a second. Is this because something was wrong with our ZDC? To test this I used Remote-XAPSSession to test the command above in the log (Get-XAServer -OnlineOnly -ZoneName A,B,C). It appears there is a timeout and the XenAppCommands is not completing in time. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client." This may be because the service is still processing the operation or because the service was unable to send a reply message. The time allotted to this operation may have been a portion of a longer timeout. "15:13:37.2515 : TimeoutException caught: This request operation sent to net.tcp://:2513/Citrix/XenAppCommands did not receive a reply within the configured timeout (00:00:10).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |