Microsoft KB Archive/942866

= A computer agent unexpectedly generates heartbeat alerts after you put it into Maintenance mode in System Center Operations Manager 2007 =

Article ID: 942866

Article Last Modified on 10/10/2007

-

APPLIES TO


 * Microsoft System Center Operations Manager 2007

-



SYMPTOMS
Consider the following scenario. In Microsoft System Center Operations Manager 2007, you put a computer agent into Maintenance mode. Then, the following information appears in the Maintenance Mode Settings dialog box:

These features are temporarily suspended for objects in Maintenance mode:
 * Rules and monitors
 * Notifications
 * Automatic responses
 * State changes
 * New alerts

However, the computer that is running the agent unexpectedly continues to generate heartbeat alerts.

Note For more information about how to put an agent into Maintenance mode, see the &quot;Steps to reproduce the behavior&quot; section.



CAUSE
This behavior occurs if you do not put the following features into Maintenance mode:
 * Health Service
 * Health Service Watcher

By design, System Center Operations Manager 2007 verifies that the agent is functioning correctly even if the computer is not being monitored. If the Health Service feature and the Health Service Watcher feature for the particular agent are not in Maintenance mode, you experience the behavior that is mentioned in the &quot;Symptoms&quot; section.



RESOLUTION
To resolve this behavior by putting the Health Service feature and the Health Service Watcher feature into Maintenance mode, follow these steps:
 * 1) Start the Operations Console if it is not already running.
 * 2) Click Monitoring, expand the Monitoring node, and then click Computers.
 * 3) Select the computer that you want to put into Maintenance mode, and then click Start Maintenance Mode in the Actions pane.
 * 4) In the Maintenance Mode Settings dialog box, click OK.
 * 5) Under the Monitoring node, click Discovered Inventory.
 * 6) In the Actions pane, click Change target type.
 * 7) In the Select a Target Type dialog box, click Health Service, and then click OK.
 * 8) Click the agent for which you want to put the Health Service into Maintenance mode, and then click Start Maintenance Mode in the Actions pane.
 * 9) In the Maintenance Mode Settings dialog box, click OK.
 * 10) In the Discovered Inventory view, click Change target type in the Action pane.
 * 11) In the Select a Target Type dialog box, click View all targets, click Health Service Watcher, and then click OK.
 * 12) Click the agent for which you want to put the Health Service Watcher into Maintenance mode, and then click Start Maintenance Mode in the Actions pane.
 * 13) In the Maintenance Mode Settings dialog box, click OK.



STATUS
This behavior is by design.



MORE INFORMATION
Administrators may want to make sure that the agent is functioning even if the computer is not being monitored. If the agent is not being monitored, hidden agent-related errors may occur that affect the overall monitoring of the computer when the computer is no longer in Maintenance mode. Therefore, when a computer is put into Maintenance mode, the OpsMgr Health Service is not also put into Maintenance mode.

Steps to reproduce the behavior

 * 1) Start the Operations Console.
 * 2) Click Monitoring, expand the Monitoring node, and then click Computers.
 * 3) In the Computers pane, click an agent, and then click Start Maintenance Mode.
 * 4) In the Maintenance Mode Settings dialog box, click Selected objects and all their contained objects.

Note The following entries appear under These features are temporarily suspended for objects in Maintenance Mode:
 * 1) * Rules and monitors
 * 2) * Notifications
 * 3) * Automatic responses
 * 4) * State changes
 * 5) * New alerts
 * 6) Click OK.
 * 7) On the agent, stop the OpsMgr Health Service.

Notice that in approximately three minutes (if you use the default heartbeat settings), you receive a Health Service Heartbeat Failure alert for this agent in the Active Alerts view. Additionally, the following event is logged in the Operations Manager log: Event Source: OpsMgr Connector

Event Category: None

Event ID: 20022

Date:

Time:

Type: Error

User: N/A

Computer:

Description: The health service { } running on host  and serving management group   with id { } is not heartbeating.

Keywords: kbeventlog kbtshoot kbprb KB942866

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.