OpsMgr 2012 or OpsMgr 2007 R2 generates a "Heartbeat Failure" message and then goes into a greyed out state in Windows Server 2008 R2 SP1

Symptoms

Assume that one of the following conditions is true for each server in a Windows Server 2008 R2 Service Pack 1 (SP1) environment:
  • System Center Operations Manager 2007 (OpsMgr 2007) or System Center 2012 Operations Manager (OpsMgr 2012) RTM, Service Pack 1, or R2 is installed on the server.
  • An Operations Manager server role that uses the Health Service is installed on the server. More specifically, the server is running as an Operations Manager management server, an Operations Manager gateway server or an Operations Manager agent.
When the servers manage network devices, the servers generate a warning message similar to the following:

Heartbeat Failure

The servers then enter a grayed out state, thus all devices that are managed by the servers enter a grayed out or a "Not Monitored" state. 

Note You may experience this issue after you install the update KB2775511  on the servers. For more information about how to identify this issue, go to the "More Information" section.

Cause

This issue occurs because a deadlock was introduced to the Advapi32.dll file in a previous system change. OpsMgr 2007 and OpSMgr 2012 are both affected by this deadlock.

Note The following are the affected versions of the Advapi32.dll file:
  • 6.1.7600.21271
  • 6.1.7601.22056
  • 6.1.7601.22119
  • 6.1.7601.22137

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

If one of the following events is logged on a management server when the Monitoringhost.exe process consumes zero CPU resources, and when there is low activity in the OperationsManager database, you may experience the issue that is described in this article:
  • Event ID 2115
  • Event ID 8000
  • Event ID 10000
  • Event ID 22402
  • Event ID 31042
  • Event ID 10451
  • Event ID 26017
When the Monitoringhost.exe process consumes zero CPU resources and there is low activity in the OperationsManager database on an Operations Manager agent, you may experience the issue that is described in this article.

For more information about how this issue may present itself, go to the following Microsoft website:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information
Vlastnosti

ID článku: 2878378 - Poslední kontrola: 17. 4. 2014 - Revize: 1

Váš názor