Service Misconfigured Alert

Summary

This alert is generated when any one of the following Service Control Manager events occur:

• 7017 Detected circular dependencies demand starting.

• 7018 Detected circular dependencies auto-starting services.

• 7019 Circular dependency: The service depends on a service in a group that starts later.

• 7020 Circular dependency: The service depends on a group that starts later.

Each of these events indicates that a service’s configuration is incorrect and that the service might not be able to start up appropriately.

Causes

Each of these events indicates that a service has either been configured to start before the service’s dependent services; service groups have started; or that a circular list of service dependencies has been configured. More specific descriptions of the cause of each event are shown below:

The specified service is dependent on a chain of other services. One of the other services is dependent on another service that appears earlier in the chain.

An auto-start service is dependent on a chain of other services. One of the services in that chain is dependent on another service that appears earlier in the chain.

The service depends on a service in a group that starts later.

The service specified depends on another service that is in a group which is configured to start later than the specified service.

The specified service depends on a group that is configured to start later than that service.

• 7017 Detected circular dependencies demand starting. The specified service is dependent on a chain of other services. One of the other services is dependent on another service that appears earlier in the chain.

• 7018 Detected circular dependencies auto-starting services. An auto-start service is dependent on a chain of other services. One of the services in that chain is dependent on another service that appears earlier in the chain.

• 7019 Circular dependency: The service depends on a service in a group that starts later. The service specified depends on another service that is in a group which is configured to start later than the specified service.

• 7020 Circular dependency: The service depends on a group that starts later. The specified service depends on a group that is configured to start later than that service.

Resolutions

To resolve this issue, follow the steps below:

Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

SCSI miniport

port

Primary disk

SCSI class

SCSI CDROM class

filter

…

To adjust the load order for a ServiceGroup, move the relevant ServiceGroup further down the list so that the dependent service starts before the service that has generated the alert does.

CAUTION: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. To do this, open Registry Editor and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder registry key. The ServiceGroupOrder registry key contains a registry value named “List,” and the data in this registry value enumerate the group names in the order in which they will be loaded. Here is a portion of the “List” registry value data: SCSI miniportportPrimary diskSCSI classSCSI CDROM classfilter… To adjust the load order for a ServiceGroup, move the relevant ServiceGroup further down the list so that the dependent service starts before the service that has generated the alert does.

• For alerts generated by event 7017 or 7018, remove the dependency that loops back. To remove this dependency, use the config command of the command-line tool, Sc.exe. This tool is included with the Microsoft® Windows® 2000 Resource Kit. For Microsoft® Windows® Windows 10 and above, the tool is part of the operating system.

• For alerts generated by events 7019 or 7020, modify the ServiceGroupOrder list in the registry to adjust the service group load order. CAUTION: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

• To do this, open Registry Editor and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder registry key. The ServiceGroupOrder registry key contains a registry value named “List,” and the data in this registry value enumerate the group names in the order in which they will be loaded. Here is a portion of the “List” registry value data: SCSI miniportportPrimary diskSCSI classSCSI CDROM classfilter… To adjust the load order for a ServiceGroup, move the relevant ServiceGroup further down the list so that the dependent service starts before the service that has generated the alert does.

• For alerts generated by events 7019 or 7020, modify the ServiceGroupOrder list in the registry to adjust the service group load order. CAUTION: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. To do this, open Registry Editor and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder registry key. The ServiceGroupOrder registry key contains a registry value named “List,” and the data in this registry value enumerate the group names in the order in which they will be loaded. Here is a portion of the “List” registry value data: SCSI miniportportPrimary diskSCSI classSCSI CDROM classfilter… To adjust the load order for a ServiceGroup, move the relevant ServiceGroup further down the list so that the dependent service starts before the service that has generated the alert does.