Applies To

Windows Server 2008

(This wiki page is part of a pilot program to remove topics such as this one from the TechNet and MSDN libraries and move them to the wiki.We plan to do a better job of helping customers than the repeated instructions to go to the forums seen in the thread history at the end of this article.)

Service Control Manager (SCM) starts services and driver services. It also reports when services fail to start or hang while starting.

Event Details

Resolve

Review the error information

To resolve this issue, first review the error code that the Service Control Manager encountered when trying to start the service, and then review the Event logs for other events that have been logged by the Service Control Manager (SCM) Eventlog Provider.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Review the error code

To review the error code:

1. Click the Start button, Run, then type cmd to open a command prompt.
2. Type sc query service_name (where service_name is the name of the service) at the command prompt to display the Windows WIN32_EXIT_CODE error code text that the Service Control Manager encountered when trying to start the service.

   Note: If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first.

3. For descriptions of the Windows error codes, either see http://go.microsoft.com/fwlink/?LinkID=83027, or type net helpmsg exit_code (where exit_code is the 4 digit number of the error code) at the command prompt to display the meaning of the WIN32_EXIT_CODE. For more information about the net helpmsg command, see http://go.microsoft.com/fwlink/?LinkId=105087. For more information about the sc command, see SC Command Reference Help (http://go.microsoft.com/fwlink/?LinkID=84961).

Review the related events logged by the SCM

To review the related events logged by the SCM:

1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

   Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

2. Click Event Viewer (Local), then Windows Logs and System.
3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.

The error message text and related events for this service should help you to further troubleshoot and resolve the issue. Some examples are provided below:

• If event ID 7011 is also logged for this service, then extending the service timeout period to resolve event ID 7011 would also resolve this error.
• If event ID 7034 is also logged for this service, then restoring the service default settings to resolve event ID 7034 would also resolve this error.

If the issue remains unresolved, contact Microsoft support and provide the error information. For information about how to contact Microsoft support, see Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=89446).

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that a service has started:

1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

   Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

2. In the details pane of the Services snap-in, locate the name of the service and verify that the Status column shows a status of Started.

Related Management Information

Service Start Operations (TechNet Library)

Core Operating System (TechNet Library)