Agent Health tips and fixes for System Center Operations Manager 2007

Article translations Article translations
Article ID: 2616936 - View products that this article applies to.
Expand all | Collapse all

Summary

This article discusses tips on fixes and changes for Microsoft System Center Operations Manager 2007 (OpsMgr) Agent Health. This article discusses hotfixes and registry keys. Be aware that these hotfixes and registry keys may not be noticed in your environment directly but might be causing issues of which you are not aware.

This article is for Operations Manager 2007 SP1 and Operations Manager 2007 R2. For Operations Manager 2012, Operations Manager 2012 SP1, and Operations Manager 2012 R2 see the following article:

http://support.microsoft.com/kb/2843219
If you have an issue that affects agents that are in a gray state, these tips and fixes may help. However, if they do not help, the following article may be helpful:

http://support.microsoft.com/kb/2288515

More information

Hotfixes

  1. Make sure that your agents, management servers, and gateways are running the latest Cumulative Update (CU). At the time that this article was written, the latest CU version was CU6. To download Cumulative Update 6 for System Center Operations Manager 2007 R2 (KB 2626076), go to the following Microsoft website:

    http://www.microsoft.com/download/en/details.aspx?id=29850
  2. All agents, management servers, and gateways should be running the latest version of the JET EDB hotfix for Windows.

    For Windows 2008 R2 and for Windows 7

    The latest version of the JET EDB hotfix for Windows is included in Service Pack 1 (SP) for these operating systems.

    For Windows 2008 and for Windows Vista

    Install the hotfix rollup that is mentioned in the following Microsoft Knowledge Base article:

    http://support.microsoft.com/kb/2553708

    For Windows Server 2003

    Install the hotfix that is mentioned in the following Microsoft Knowledge Base article:

    http://support.microsoft.com/kb/981263
  3. There is an Avg. Disk Sec/Transfer issue that returns a very large value that is incorrect. For more information, see the following articles, as appropriate for your operating system:

    For Windows 2008 R2 or for Windows 7

    http://support.microsoft.com/kb/2470949
    For Windows Server 2008 or for Windows Vista

    http://support.microsoft.com/kb/2495300
  4. You do not receive event notifications after you back up and then clear event logs in Windows Server 2008 or in Windows Vista. Therefore, OpsMgr is prevented from providing a warning for events after the event logs are cleared.

    For Windows 2008 or for Windows Vista
    http://support.microsoft.com/kb/2458331

    Note This issue does not occur in Windows Server 2008 R2 or in Windows 7.
  5. The "Win32_Service" WMI class leaks memory in Windows Server 2008 R2 and in Windows 7:

    http://support.microsoft.com/kb/981314

    Note This issue is resolved in Windows Server 2008 R2 SP1 and in Windows 7 SP1.
  6. A hotfix is available that improves the stability of the Windows Management Instrumentation repository in Windows Server 2003:

    http://support.microsoft.com/kb/933061
  7. WSH binaries are overwritten by Windows File Protection after you install Windows Script 5.7 on a computer that is running Windows Server 2003 or Windows XP:

    http://support.microsoft.com/kb/955360
    For Operations Manager, this may be the cause of high CPU utilization.
  8. A managed application has a high number of thread handles and of event handles in the Microsoft .NET Framework 2.0:

    http://support.microsoft.com/kb/968760
    For Operations Manager, this causes a high number of handles
  9. The CPU usage of an application or a service that uses MSXML 6.0 to handle XML requests reaches 100% in Windows Server 2008, Windows Vista, Windows XP Service Pack 3, or other systems that have MSXML 6.0 installed:

    http://support.microsoft.com/kb/968967
    For Operations Manager, this behavior causes high CPU usage for the Monitoringhost.exe process.
  10. New AFD connections fail when software that uses TDI drivers is installed on a Windows Server 2008 or Windows Vista SP1 system that is running on a computer that has multiple processors:

    http://support.microsoft.com/kb/961775
  11. FIX: You receive a "Provider Load Failure" error message or the Wmiprvse.exe process stops responding when you use a SQL Server WMI provider to obtain information about SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 services:

    http://support.microsoft.com/kb/980142
  12. Extended Protection for Authentication: This feature enhances the protection and handling of credentials when authenticating network connections by using Integrated Windows Authentication (IWA). In Operations Manager, there may be some errors doing a client push. In this case, a network trace would contain the following:

    Server Error, (91) Invalid user identifier
    For more information, view the following article in the Microsoft Knowledge Base:

    http://support.microsoft.com/kb/968389
  13. Description of the rollup update for the .NET Framework 3.5 Service Pack 1 on Windows XP and on Windows Server 2003 (976765, 980773 and 976769): June 8, 2010:

    http://support.microsoft.com/kb/982168
  14. Description of the rollup update for the .NET Framework 3.5 Service Pack 1 and the .NET Framework 2.0 Service Pack 2 on Windows XP and on Windows Server 2003 (976765 and 980773): June 8, 2010:

    http://support.microsoft.com/kb/982167
  15. A rollup hotfix package for Windows Server 2008 Failover Clustering WMI provider:

    http://support.microsoft.com/kb/968936
  16. There is a memory leak in IIS when stress-testing our IIS discovery. This QFE is important for whoever uses OpsMgr with the IIS MP, and even more important when the APM feature is used in OM12. For more information, see "FIX: Memory leak in Rhs.exe after you configure the IIS 7.5 W3SVC service in a Windows Server 2008 R2 SP1 failover cluster":

    http://support.microsoft.com/kb/2618982
  17. The WMI service and the WMI providers stop responding when you use WMI performance classes to monitor performance on a computer that is running Windows 7 or Windows Server 2008 R2:

    http://support.microsoft.com/kb/2547244
  18. High CPU usage or a lengthy startup process occurs during WMI repository verification when a large WMI repository exists in Windows 7 or in Windows Server 2008 R2:

    http://support.microsoft.com/kb/2505348
  19. Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7:

    http://support.microsoft.com/kb/2617858
  20. "0x80041001" error when the Win32_Environment WMI class is queried by multiple requestors in Windows 7 or in Windows Server 2008 R2:

    http://support.microsoft.com/kb/2692929
  21. FIX: The host process of the application crashes when the CounterExists method or the Exists method is called on a multiprocessor computer in IIS 6.0

    http://support.microsoft.com/kb/960718
  22. Only the first character appears for some strings in the event messages when you query the DFS Replication event log on a computer that is running Windows Server 2008

    http://support.microsoft.com/kb/973275

Registry subkeys

Subkey 1

Subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HealthService\Parameters

Type: REG_DWORD
Name: Persistence Version Store Maximum
Value: Number of 16-kilobyte pages
Base: Decimal

The default size of the version store depends on the Operations Manager role and is defined as the number of 16-kilobyte pages to allocate in memory. The default values are as follows:
Collapse this tableExpand this table
Agent (workstation operating systems): 640 (10 megabytes)
Agent (server operating systems): 1920 (30 megabytes)
Management Server: 5120 (80 megabytes)
If you experience a problem with the configuration of this registry value, you see the following event:

Event Type: Error
Event Source: ESE
Event Category: Transaction Manager
Event ID: 623
Description: HealthService (<PID>) The version store for instance <instance> ("<name>") has reached its maximum size of <value>Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Possible long-running transaction:
SessionId: <value>
Session-context: <value>
Session-context ThreadId: <value>.
Cleanup:<value>


Note This event may report the issue with other Operations Manager processes, depending on the affected role.

We recommend that you set the version store size to double its default size. For example, if you set the version store size on a computer that hosts a Management Server role, set the registry value to 10240 (decimal).

Subkey 2

Subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HealthService\Parameters\Management Groups\<MGNAME>

Type: REG_DWORD
Name: MaxItemSizeBytes
Value: 52428800
Base: Decimal

If you experience an issue with this registry value, you see the following event:

Event Source: HealthService
Event Category: Health Service
Event ID: 2015
User: N/A
Description:
A workflow in the Health Service has generated a message which exceeds the size limit, and has been discarded.


Note An increase in the limit can adversely affect the Management group performance. This is because this increase causes lots of discovery data to be collected by the Management server and by the Root Management server.

Properties

Article ID: 2616936 - Last Review: December 21, 2013 - Revision: 9.1
Applies to
  • Microsoft System Center Operations Manager 2007
  • Microsoft System Center Operations Manager 2007 R2
  • Microsoft System Center Operations Manager 2007 Service Pack 1
Keywords: 
KB2616936

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com