Performance Problems for Agents with Debug Logging Turned On (296009)
The information in this article applies to:
- Microsoft Operations Manager 2000
This article was previously published under Q296009 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 Microsoft Operations Manager (MOM), MOM configures logging on agents to level 0 debug.
On inactive servers, the logging can produce over 1 million bytes of logged data within 30 minutes after the agent is installed. Furthermore, an additional 5 million bytes of logging may be written each day. This load can result in a significant performance impact on the agent computer. In addition, important logs that are used to track MOM activity may be overwritten.
WORKAROUNDWARNING: 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 work around this behavior by disabling debug logging on an agent computer, follow these steps:
- Start Registry Editor (Regedt32.exe).
- Locate the TraceLevel value under the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Mission Critical Software
- On the Edit menu, click DWORD, type FFFFFFFF, and then click OK.
- Quit Registry Editor.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
|---|
| Keywords: | kbbug kbenv KB296009 |
|---|
|