Resolution: The MED-V Server service fails to start with Error 1053
When you attempt to start the MED-V Server service on Windows Server 2008 or Windows Server 2008 R2, you may get the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.
Additionally, the system event log indicates this timeout failure by a log entry that is similar to the following:
Source : Service Control Manager
Event ID : 7000
This can occur if the service control manager encounters a timeout. To work around this problem, increase the default timeout value for the service control manager in the registry. This will require you to adjust the ServicePipeTimeout registry value.
Warning: Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To increase the timeout value in the registry, follow these steps:
1. Start Registry Editor (Regedit.exe).
2. To change the value data for the ServicesPipeTimeout DWORD value to 60000 in the Control key, follow these steps:
3. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
4. Click the Control subkey
5. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
6. Click Decimal.
7. Type 60000, and then click OK.
If the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 60000 in the Control key. To do so, follow these steps:
1. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
2. Click the Control subkey.
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type ServicesPipeTimeout, and then press ENTER.
5. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
6. Click Decimal.
7. Type a value of 60000, and then click OK.
The value is 60000 milliseconds and is equivalent to 60 seconds or one minute.
Note: This change does not take effect until the computer is restarted.
Steve Thomas | Senior Support Escalation Engineer
Comments
Anonymous
January 01, 2003
Thanks, Steve. This got us through our issues yesterday.Anonymous
May 17, 2012
This resolved my issue. Thanks