Installing MOM Agent on Existing Operations Manager Agent Pushes CPU Utilization to 100 Percent (300322)


The information in this article applies to:

  • Microsoft Operations Manager 2000
This article was previously published under Q300322
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you install a Microsoft Operations Manager (MOM) agent on a computer that currently has the Operations Manager 3.3 agent installed on it, CPU utilization may reach 100 percent.

CAUSE

This behavior can occur if the default logging level on the agent has been modified.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this behavior, set the logging level to the default value of zero (0):
  1. Start Registry Editor (Regedt32.exe).
  2. Locate the TraceLevel value under the following key in the registry:

    HKEY_LOCAL_MACHINE\Software\Mission Critical Software

  3. On the Edit menu, click DWORD, type 0, and then click OK.
  4. Quit Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbbug kbenv kbsetup KB300322
©2004 Microsoft Corporation. All rights reserved.