Share via

Event ID 7000: Service Start Failure

  • Article

Applies to: Windows Server 2008 R2

Event Details

Product:

Windows Operating System

ID:

7000

Source:

Service Control Manager

Version:

6.1

Symbolic Name:

EVENT_SERVICE_START_FAILED

Message:

The %1 service failed to start due to the following error:
%2

 

Troubleshooting

Examine the Error Code

Examine the error code that the Service Control Manager (SCM) generated when attempting to start the service and then review the Event logs for any related events that have been logged by the SCM.

To review the error code:

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

  1. For descriptions of the Windows error codes 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.

Review related events logged by the SCM

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

  1. Click Event Viewer (Local), then Windows Logs and System.
  2. In the details pane, click 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.

  • 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.