Q. A Window Server 2003 service does not start and the Application event logs records events 7000 and 7011?

Jerold Schulman

July 23, 2006

1 Min Read
ITPro Today logo in a gray background | ITPro Today

When your Windows Server 2003 starts, a service fails to start and logs the following in the Application event log:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: DD.MM.YYYY
Time: HH:MM:SS
User: N/A
Computer:
Description: The service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011
Description: Timeout (30000 milliseconds) waiting for a transaction response from the service.

You need to increase the default 30 seconds that the SCM uses, to 60 or more seconds, allowing time for the dependent services to start.

To set the ServicesPipeTimeout default to 60 seconds:

1. Open a CMD.EXE window.

2. Type the following command and press Enter::

SvcTimeOut.bat 60000


Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like