This alert is triggered when the Windows Service Control Manager generates event ID 7022. The service failed to indicate that it is making progress within the time period indicated in its last status message. This message is not specific to Configuration Manager. This condition does not repair itself and must be resolved before Configuration Manager can resume some of its core functions.
This is due to a critical problem with the service or one of its dependent components or services.
This alert is best handled by Configuration Manager administrators.
For more assistance, see a list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager.
Sample Events:
The %1 service stopped responding after starting.
Target | Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Servers_Installation |
Category | EventCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
Event Log | System |
Comment | Mom2005ID='{0D2309BB-1CF1-4D22-84B6-6649C7478880}';MOM2005ComputerGroupID={D0741372-F3F6-43EB-8B8B-965F937BCC65} |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
_907D4578_146C_11D3_AB21_00A0C98620CE_ | DataSource | Microsoft.Windows.EventProvider | Default |
CollectEventData | WriteAction | Microsoft.SystemCenter.CollectEvent | Default |
CollectEventDataWarehouse | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
GenerateAlert | WriteAction | System.Mom.BackwardCompatibility.AlertResponse | Default |
<Rule ID="SMSv4_service_failure__SMS_SITE_VSS_WRITER_hung_on_starting_19_Rule" Target="Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Servers_Installation" Enabled="true" ConfirmDelivery="true" Comment="Mom2005ID='{0D2309BB-1CF1-4D22-84B6-6649C7478880}';MOM2005ComputerGroupID={D0741372-F3F6-43EB-8B8B-965F937BCC65}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_907D4578_146C_11D3_AB21_00A0C98620CE_" Comment="{907D4578-146C-11D3-AB21-00A0C98620CE}" TypeID="WindowsLibrary!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Service Control Manager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[1]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>SMS_SITE_VSS_WRITER</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>7022</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="System.Mom.BackwardCompatibility.AlertResponse">
<GenerateAlert>true</GenerateAlert>
<Owner/>
<Description>
$Data/LoggingComputer$
- ConfigMgr 2007 service failure: SMS_SITE_VSS_WRITER hung on starting.
The SMS_SITE_VSS_WRITER service running on
$Data/LoggingComputer$
was detected as stopped at
$Data/@time$
.</Description>
<AlertLevel>70</AlertLevel>
<ResolutionState/>
<Source>
$Data/PublisherName$
</Source>
<Name>ConfigMgr 2007 service failure: SMS_SITE_VSS_WRITER hung on starting</Name>
<InvokerType>0</InvokerType>
</WriteAction>
<WriteAction ID="CollectEventData" TypeID="SystemCenterLibrary!Microsoft.SystemCenter.CollectEvent"/>
<WriteAction ID="CollectEventDataWarehouse" TypeID="DataWarehouseLibrary!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>