A service has been detected as misconfigured.
Each of these events indicates that a service’s configuration is incorrect and that the service might not be able to start up appropriately. This alert is generated when any one of the following Service Control Manager events occur:
7015: a boot-start or system-start driver service has a dependency on other individual services to start. (Boot-start and system-start driver services cannot depend on another service, but can depend on a service group.)
7017: This issue occurs because the manually started services have a circular dependency chain, for example, service A depends on service B which depends on service C which depends on service A.
7018: This issue occurs because the auto started services have a circular dependency chain, for example, service A depends on service B which depends on service C which depends on service A.
7019: This issue occurs because the manually started services have a circular dependency chain, for example, service A depends on service B which depends on service C which depends on service A.
7020: This issue occurs because the manually started services have a circular dependency chain, for example, service A depends on service B which depends on service C which depends on service A.
The Service Control Manager has generated an event indicating that a service failed to start due to the service having an invalid configuration, such as the service having a circular dependency with another service.
To resolve this issue, follow the steps below:
7015: To resolve this issue, change the dependency of the boot-start or system-start driver service indicated in the event message text. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To list the dependent services for a service and modify the dependencies:
At a command prompt, type sc qc service_name to view the other services on which service_name is dependent.
Type sc config service_name depend= +group_name (where group_name is the name of any dependent service group) to remove dependencies on individual services.
Note: If the service has no dependent service groups, enter a null value for the depend parameter.
7017: To resolve this issue, remove the circular dependency. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To list the dependent services or service groups for a service and remove the circular dependencies:
At a command prompt, type sc qc service_name to view the other services and service groups on which service_name is dependent.
Type sc config service_name depend= service_name/+group_name (where service_name is the name of any noncircular dependent service and group_name is the name of any noncircular dependent service group) to remove dependencies on individual circular services or service groups.
7018: To resolve this issue, remove the circular dependency. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To list the dependent services for a service and remove the circular dependencies:
At a command prompt, type sc qc service_name to view the other services on which service_name is dependent.
Type sc config service_name depend= service_name/+group_name (where service_name is the name of any noncircular dependent service and group_name is the name of any noncircular dependent service group) to remove dependencies on individual circular services or service groups.
Note: If the service has no dependent services or service groups, enter a null value for the depend parameter.
7019: To resolve this issue, remove the circular dependency. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To list the dependent services or service groups for a service and remove the circular dependencies:
At a command prompt, type sc qc service_name to view the other services on which service_name is dependent.
Type sc config service_name depend= service_name/+group_name (where service_name is the name of any noncircular dependent service and group_name is the name of any noncircular dependent service group) to remove dependencies on individual circular services or service groups.
Note: If the service has no dependent service groups, enter a null value for the depend parameter.
7020: To resolve this issue, remove the circular dependency. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To list the dependent services or service groups for a service and remove the circular dependencies:
At a command prompt, type sc qc service_name to view the other services and service groups on which service_name is dependent.
Type sc config service_name depend= service_name/+group_name (where service_name is the name of any noncircular dependent service and group_name is the name of any noncircular dependent service group) to remove dependencies on individual circular services or service groups.
Note: If the service has no dependent services or service groups, enter a null value for the depend parameter.
Target | Microsoft.Windows.Server.10.0.OperatingSystem | ||
Category | EventCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | System |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
EventDS | DataSource | Microsoft.Windows.EventProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Windows.Server.10.0.OperatingSystem.ServiceMisconfigured.Alert" Enabled="true" Target="ServervNext!Microsoft.Windows.Server.10.0.OperatingSystem" ConfirmDelivery="true">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventSourceName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Service Control Manager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>7015</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>7017</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>7018</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>7019</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>7020</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.10.0.OperatingSystem.ServiceMisconfigured.Alert.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>