This rule generates alerts when the root management server is not reachable from this management server's Data Access service.
Either the root management server is down or the root management server's Health service is not available.
This can be caused by:
The root management server is offline.
The Health service on the root management server is not running.
An administrative restart of the Health service on the root management server.
The Data Warehouse Write Account has expired.
If these alerts are generated during or shortly after installation of the Data Warehouse or reporting components, the likely cause is due to the flow of alerts and state transitions to the Data Warehouse, however, the corresponding data structures are not there yet. Deployment happens within approximately 30 minutes of installation.
While deployment is not yet done, data will be retained by alert and state sync workflows to be written later to the Data Warehouse. Thus, these workflows do not put data back to data sources and that in turn generates the alerts in question. After deployment is complete, data is written and alerts clear up automatically.
If alerts do not auto-resolve within 120 minutes of Data Warehouse installation, then another problem exists.
Check the availability of the root management server or start up the Health service on the root management server.
Also, check the status of the Data Warehouse Write Account.
The below table explains the possible reason codes in the alert description:
Reason Code | Description |
17 | The Health Service windows service is paused. |
25 | The Health Service Action Account is misconfigured or has invalid credentials. |
41 | The Health Service failed to parse the new configuration. |
42 | The Health Service failed to load the new configuration. |
43 | A System Rule failed to load. |
49 | Collection of Object State Change Events is stalled. |
50 | Collection of Monitor State Change Events is stalled. |
51 | Collection of Alerts is stalled. |
97 | The Health Service is unable to register with the Event Log Service. The Health Service cannot log additional Heartbeat and Connector events. |
98 | The Health Service is unable to parse configuration XML. |
Target | Microsoft.SystemCenter.ManagementServer | ||
Category | Alert | ||
Enabled | True | ||
Event_ID | 271828 | ||
Event Source | Health Service Watcher | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | Operations Manager | ||
Comment | Rule used by Data Access service to generate alerts from each Management Server when the RHS is down |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
EventDS | DataSource | Microsoft.Windows.EventProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.SystemCenter.SDKService.PrincipleManagementServerDown.Alert" Comment="Rule used by Data Access service to generate alerts from each Management Server when the RHS is down" Enabled="true" Target="SCLibrary!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="High" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Operations Manager</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Health Service Watcher</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>271828</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertName/>
<AlertDescription/>
<AlertMessageId>$MPElement[Name='Microsoft.SystemCenter.SDKService.PrincipleManagementServerDown.Alert.AlertMessage']$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>