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:
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.
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:
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.
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:
976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
To apply this hotfix, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Windows Server 2008 R2
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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: