A service does not start, and events 7000 and 7011 are logged in Windows Server 2003

When you start a computer that is running Microsoft Windows Server 2003, a service does not start, and the following error events appear in the Application log :

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000

The ServiceName 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 ServiceName service.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this problem, modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry.
   
   Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
   1. On the Edit menu, point to New, and then click DWORD Value.
   2. Type ServicesPipeTimeout, and then press ENTER.
4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 60000, and then click OK.
   
   This value represents the time in milliseconds before a service times out.
6. Restart the computer.

Note This workaround may resolve the problem where the service does not start. However, we recommend that you research this problem to determine whether it is a symptom of another problem.

The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000 or 7011. Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start. For more information, click the following article number to view the article in the Microsoft Knowledge Base: