SMS 2003 Status: Some or all of the Management Point Component Managers could not be started

SMS_2003_Status__Some_or_all_of_the_Management_Point_Component_Managers_could_not_be_started_9_Rule (Rule)

Knowledge Base article:

Summary

SMS status message 5434 was detected. To investigate this status message:

Causes

Refer to the documentation for SMS status message 5434 for more information about the cause of this issue.

Resolutions

Refer to the documentation for SMS status message 5434 for more information about the resolution of this issue.

External

For more information about status messages, see SMS 2003 Status Messages at the Systems Management Server 2003 Product Documentation Web page.

For more information about troubleshooting Management Point Component Managers, seeTroubleshooting Flowcharts at the Systems Management Server 2003 Product Documentation Web page

For more assistance, a list of additional support options is available in the support section of the SMS Web site at Support for Systems Management Server.

Additional

This alert is best handled by SMS administrators.

Element properties:

TargetMicrosoft.SMS.2003.Microsoft_SMS_2003_Site_Database_Servers_Installation
CategoryEventCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityLow
RemotableTrue
Alert Message
SMS 2003 状态: 无法启动部分或全部管理点组件管理器

$Data/Params/Param[1]$ - SMS 2003 状态: 无法启动部分或全部管理点组件管理器。


$Data/EventDescription$


状态消息中包含消息属性

计算机名称: $Data/Params/Param[1]$

模块名称: $Data/Params/Param[2]$

组件: $Data/Params/Param[3]$

消息 ID: $Data/Params/Param[4]$

Win32 错误: $Data/Params/Param[5]$

顶级站点代码: $Data/Params/Param[6]$

数据库记录 ID: $Data/Params/Param[7]$
CommentMom2005ID='{C99E8ECF-B553-4333-94BC-F00859593655}';MOM2005ComputerGroupID={6E07E901-5EEF-4D43-ABC9-5A73BC9B072D}

Member Modules:

ID Module Type TypeId RunAs 
_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_ DataSource System.Mom.BackwardCompatibility.FilteredEvent.DataProvider Default
GenerateAlert WriteAction System.Mom.BackwardCompatibility.AlertResponse Default

Source Code:

<Rule ID="SMS_2003_Status__Some_or_all_of_the_Management_Point_Component_Managers_could_not_be_started_9_Rule" Target="Microsoft.SMS.2003.Microsoft_SMS_2003_Site_Database_Servers_Installation" Enabled="true" ConfirmDelivery="false" Comment="Mom2005ID='{C99E8ECF-B553-4333-94BC-F00859593655}';MOM2005ComputerGroupID={6E07E901-5EEF-4D43-ABC9-5A73BC9B072D}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_" Comment="{F320DA51-13BF-11D3-B2CD-00A0C92A28B4}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.FilteredEvent.DataProvider">
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>5434</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>SMS 2003 Monitor SMS Status Messages</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.AlertResponse">
<AlertGeneration>
<GenerateAlert>true</GenerateAlert>
<Owner/>
<Description>
$Data/Params/Param[1]$
- SMS 2003 Status: Some or all of the Management Point Component Managers could not be started.


$Data/EventDescription$


The status message contains message properties

Machine Name:
$Data/Params/Param[1]$

Module Name:
$Data/Params/Param[2]$

Component:
$Data/Params/Param[3]$

Message ID:
$Data/Params/Param[4]$

Win32 Error:
$Data/Params/Param[5]$

Top Level Site Code:
$Data/Params/Param[6]$

Database Record ID:
$Data/Params/Param[7]$
</Description>
<AlertLevel>40</AlertLevel>
<ResolutionState/>
<Source>
$Data/PublisherName$
</Source>
<Name>SMS 2003 Status: Some or all of the Management Point Component Managers could not be started</Name>
</AlertGeneration>
<InvokerType>0</InvokerType>
</WriteAction>
</WriteActions>
</Rule>