Service Start Operations

Applies To: Windows Server 2008 R2

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

Events

Event ID Source Message

7000

Service Control Manager

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

7001

Service Control Manager

The %1 service depends on the %2 service which failed to start because of the following error:
%3

7002

Service Control Manager

The %1 service depends on the %2 group and no member of this group started.

7003

Service Control Manager

The %1 service depends on the following nonexistent service: %2

7017

Service Control Manager

Detected circular dependencies demand starting %1.

7019

Service Control Manager

Circular dependency: The %1 service depends on a service in a group which starts later.

7020

Service Control Manager

Circular dependency: The %1 service depends on a group which starts later.

7022

Service Control Manager

The %1 service hung on starting.

7038

Service Control Manager

The %1 service was unable to log on as %2 with the currently configured password due to the following error:
%3

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

7039

Service Control Manager

A service process other than the one launched by the Service Control Manager connected when starting the %1 service. The Service Control Manager launched process %2 and process %3 connected instead.

Note that if this service is configured to start under a debugger, this behavior is expected.

7041

Service Control Manager

The %1 service was unable to log on as %2 with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.

Service: %1
Domain and account: %2

This service account does not have the necessary user right "Log on as a service."

User Action

Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.

If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.

Service Events Logging

Core Operating System