Consider the following scenario:

• You import a management pack to monitor certain network devices in a Microsoft System Center Operations Manager 2007 Service Pack 1 environment or in a Microsoft System Center Essentials 2007 Service Pack 1 environment.
• You perform a network device discovery by using Simple Network Management Protocol (SNMP).

In this scenario, you may receive one or both of the following error messages: In this scenario, the OpsMgr Health Service is still running correctly. However, the Root Management Server (RMS) becomes unhealthy or unusable.

Additionally, the following event is logged in the Operations Manager log on the server on which you perform the network device discovery:

Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 4000
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
A monitoring host is unresponsive or has crashed. The status code for the host
failure was 2164195371.

Problem signature:
Problem Event Name: APPCRASH
Application Name: MonitoringHost.exe
Application Version: 6.0.6278.0
Application Timestamp: 47b71437
Fault Module Name: HealthServiceRuntime.dll
Fault Module Version: 6.0.6278.0
Fault Module Timestamp: 47b71433
Exception Code: c0000005
Exception Offset: 00003d9d
OS Version: 6.0.6001.2.1.0.16.7
Locale ID: 1033

This problem occurs because a defect in the SNMP networking module causes the HealthService service to become unstable or to crash. Therefore, the Root Management Server becomes unstable or unusable.

Update Information

This fix is contained within the Microsoft System Center Operations Manager 2007 Service Pack 1 update. To see a list of issues are fixed and how to obtain the cumulative rollup, refer to this article in the Microsoft Knowledge Base:

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 this specific problem. 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 Web site: 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 have System Center Operations Manager 2007 Service Pack 1 or System Center Essentials 2007 Service Pack 1 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

However, the hotfix installation process automatically restarts the services that are related to Operations Manager 2007 or Essentials 2007.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Hotfix installation instructions

You must apply this hotfix on each computer that hosts an Operations Manager 2007 Management Server role. To apply this hotfix, follow these steps:

1. Copy the following file to a local folder or to a shared folder, and then run the file:
   SystemCenterOperationsManager2007-SP1-KB951526-X86-X64-ENU.msi
   Note You can run this file either in Windows Explorer or at a command prompt. The hotfix installation process automatically restarts the services that are related to Operations Manager 2007.
2. On the computer that is running the Management Server role, click Start, point to All Programs, point to System Center Operations Manager 2007, and then click Operations Console.
3. Select the Administration view, expand Administration, expand Device Management, and then click Pending Management.
4. In the Pending Management folder, select all agent computers that are listed, and then click Reject in the Actions pane.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

System Center Operations Manager 2007 Service Pack 1 or System Center Essentials 2007 Service Pack 1, x86-based version

System Center Operations Manager 2007 Service Pack 1 or System Center Essentials 2007 Service Pack 1, x64-based version

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft System Center Operations Manager 2007 R2.

For a list of issues that are fixed in Microsoft System Center Operations Manager 2007 R2, refer to the following article in the Microsoft Knowledge base:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: