Microsoft KB Archive/922918

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

Article ID: 922918

Article Last Modified on 2/9/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
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 1

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7000

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 2

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.



WORKAROUND
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 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:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 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:  On the Edit menu, point to New, and then click DWORD Value. Type ServicesPipeTimeout, and then press ENTER. </li> Right-click ServicesPipeTimeout, and then click Modify.</li> Click Decimal, type 60000, and then click OK.

This value represents the time in milliseconds before a service times out.</li> Restart the computer.</li></ol>

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.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
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:

839803 The Windows Trace Session Manager service does not start and Event ID 7000 occurs

Keywords: kbqfe kberrmsg kbprb kbexpertiseinter KB922918

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.