Access Violation in PerfMgr Thread (305981)


The information in this article applies to:

  • Microsoft Operations Manager 2000
This article was previously published under Q305981

SYMPTOMS

The Microsoft Operations Manager (MOM) OnePointService stop working because there is an access violation in the Performance Manager (PerfMgr) thread on MOM agents. The service attempts to restart but it may or may not succeed. The following two events are typically logged in the Application event log if you experience this problem:
Event ID: 9015 Event Type: Error Event Source: OnePoint Operations Description: The Microsoft Operations Manager 2000 service (OnePointService.exe) received an unexpected exception. Thread Name: PerfMgr Exception code: 0xc0000005 Exception description: Access Violation Exception address: 77DF7D88
Event ID: 9014 Event Type: Error Event Source: OnePoint Operations User: NT AUTHORITY\SYSTEM Description: The Microsoft Operations Manager 2000 service (OnePointService.exe) terminated due to an unhandled exception. It will attempt to restart itself.
If the "Thread Name", "Exception code", and the "Exception address" match these errors, you are most likely affected by this issue. Also, the OnePointService log file may log entries that are similar to the following entries:
``12015```0`3044`39`1`PerfMgr`PerformanceManager::execute`236775672`29425836``Event logging is disabled (this is normal for GUIs). Suppressed logging of event 9015(Error) args = "0xbe4" "0x00000000c0000005" "Access Violation" "77DF7D88" "0x0" "PerfMgr" ``12016```0`3044`39`1`PerfMgr`PerformanceManager::execute`236775672`29425836``Event logging is disabled (this is normal for GUIs). Suppressed logging of event 9014(Error) args = ``12017```0`3044`39`0`PerfMgr`PerformanceManager::execute`236931925`29425836``}PerformanceManager::execute: exiting. ``12018```0`3044`39`0`PerfMgr``239275720`29425836``VERIFY FAILURE:T:\Dev\EEM\V3\Ship\Providers\PerfProvider\PerformanceManager.cpp(51): Destroying mutex locked at this location!
After you receive these errors, the OnePointService service may appear to be running when it stops responding (hangs). To recover from this, you must restart the computer.

CAUSE

This problem occurs because there is a timeout issue when the PerfMgr thread requests performance data from the computer.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Microsoft Operations Manager 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

814529How to Obtain the Latest Microsoft Operations Manager 2000 Service Pack

The English-language version of this fix should have the following file attributes or later: 

   Date        Time    File version  Size       File name     
   ---------------------------------------------------------
   08/22/2001  06:59p  4.0.1.66      2,037,840  Mcscmn04.dll


Installation

This hotfix must be applied to each computer that meets the following criteria:
  • Hosts a Microsoft Operations Manager Consolidator (CAM).
  • Hosts a manually installed MOM agent.
To apply this hotfix, you must first copy the Q305981.exe file to either a local folder or to an accessible network shared folder and then run Q305981.exe locally on each applicable computer that meets the predefined criteria. You can run Q305981.exe from either Windows Explorer or from a command prompt.

NOTE: When you run the Q305981.exe file while the MOM Administrator console is open, you must restart the CAM server. It is therefore recommended that you shut down the MOM Administrator console before you install this hotfix.

When you install this hotfix on a CAM server, the installation engine starts an agent update to all currently managed servers. This process involves the following steps:
  • At the next scheduled Managed Computer scan, the list of agent computers that need to be updated is displayed in the Pending Installation folder in the Configuration snap-in. If necessary, you can start the Managed Computer scan immediately by using the following steps:
    1. In the MOM Administrator console, click Configuration, and then click Agent Managers.
    2. In the right pane, right-click the Agent Manager.
    3. Click Scan Managed Computers Now.
  • On the CAM computer, the deployment of the updated agents must be approved by locating the agents under Configuration\Pending Installation in the MOM explorer tree. After you do this, right-click an agent computer, and then click Approve. The deployment of the updated agent occurs for each managed node only after it has been approved in the Pending Installation folder. You can approve all pending operations if you right-click Pending Installation, and then click Approve All Pending Actions. If you want the installation to occur as soon as possible, right-click Configuration\Pending Installation, and then click Process All Approved Actions.

WORKAROUND

To work around this problem, manually restart the OnePointService service if it does not automatically restart after the access violation occurs.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Operations Manager 2000 Service Pack 1.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbOpMan2000SP1Fix kbbug kbenv kberrmsg kbfix KB305981
©2004 Microsoft Corporation. All rights reserved.