OS: Windows Server 2012 R2 Standard

Usage: Application Server, FTP

Hardware: Virtual Server running on VMWare ESXi 5.5 U2

Issue: Every now and then we have been receiving this error on our server which we are unable to narrow down as what could be causing this issue.

Action Take so far: After going through few blogs we have disabled the Printer mappings from local GPO level and also disabled the Smart Card Service as well since we are not using smart card authentication in our organization. Servers is fully patched and there is no issues from the Application side. its only this service which has been timing out and they dont follow any pattern as such. we have atleast 3 to 4 alerts in a week. Server also has the latest version of VM Tools and VM HW version.

Log Name:      System
Source:        Service Control Manager
Date:          8/24/2015 8:12:35 AM
Event ID:      7011
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      servername.mydomain.com
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

Any advice on how to fix this error message?

UmRdpService service allows the redirection of Printers/Drives/Ports for RDP connections. One of the reason of timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service is Remote Desktop Services UserMode Port Redirector service is not running. Pls. check this service and ensure that it is up and running.
Roger

thanks, but i couldn't understand what you are trying to say.

Yes, that's the service which is timing out and when we login to the server it was already UP and running. There are no logs to say that it crashed and stopped or started.

i just got another error from the same server of similar nature but for a different service (iphlpsvc) this time :(

Log Name:      System
Source:        Service Control Manager
Date:          9/2/2015 1:05:05 PM
Event ID:      7011
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      servername.mydomain.com
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.

Hi Sicasankar,

According to the article, we could use the Registry Editor to change the default timeout value for all services.

Remember to backup before modifying the registry.

Here is the detailed guide:
Event ID 7011: Service Timeout:
http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx

Best Regards,

thanks for your reply Leo, however increasing the timeout value only hides the actual issue of service getting crashed. is there a way to find out the cause as why this is happening and how we can fix it?

Hi Sivasankar,

We could modify the registry and observe the server. If everything is working properly, then I suppose we don't need to worry about it.

To fix the error, we need to find out why the specific service is not responding. When the error appears, check if the service is running.

Best Regards,

Leo