There is another thread open under the "General" section. I was asked to post it here. I have left the other thread open because I believe this is not just applicable to the Remote Desktop Services Role. (http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/94b0d7f7-6a26-4795-8c1f-ffee1ac309aa/)
Hey everyone,
I have now seen this issue happen on multiple Windows Server 2008 Terminal server setups. The services that time out are not exactly the same across all the servers, but a number of them are the same on all of them.
Here are the lists of services that timed out on one of these servers, along with the time it happened.
- 80237AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndpointBuilder service.
- 80307AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
- 80237AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
- 80407AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.
- 80437AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.
- 80507AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
- 80537AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service.
- 80607AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
- 80637AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the seclogon service.
- 80707AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
- 80737AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
- 80807AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxSms service.
- 80837AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinVNC4 service.
- 80851AM - The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.
- 80907AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.
- 80938AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the wuauserv service.
- 81008AM - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
In the end, the server has to be restarted for us to access it and for users to connect to it.
Doing some research, I cam across this KB article (http://support.microsoft.com/kb/972596/), but not sure if it applies to this situation. I have seen other people post about this issue, but haven't come across anything that states the cause and resolution.
Has anyone else faced this or is facing it at the moment?
Any tips or suggestions would be great!
Thanks a lot!
Warm regards,
Sri