Article ID: 930055
Article Last Modified on 1/9/2007
APPLIES TO
- Microsoft Systems Management Server 2003
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
You experience the following symptoms on a Microsoft Systems Management Server (SMS) 2003 Service Pack 2 (SP2) site server:
- Message ID 3707 and Message ID 3701 are logged in the SMS Status Message Viewer.
- The following error information is logged in the SMS_CCM\Logs\CCMexec.log file:
Request failed: 503 Service Unavailable CcmExec <date> <time> 2360 (0x0938)
- The following error information is logged in the %windir%\System32\LogFiles\HTTPERR\Httperr1318.log file:
<date> <time> <IP address> <port> <IP address> 80 HTTP/1.1 CCM_POST /ccm_system/request 503 1 QueueFull
- The following error information is logged in the SMS\Logs\Statmrg.log file:
CStatusManagerPerfObject::Initialize(): ERROR: Could not initialize the "Computer <ComputerName>" instance of the "SMS Status Messages" performance object. SMS_STATUS_MANAGER <date> <time> 2856 (0x0B28)
CAUSE
This issue occurs if the SMS 2003 Status Manager component exceeds the maximum number of performance instances that are available for a performance object. This issue does not indicate that a problem exists with SMS 2003.
The SMS performance counter library is a new feature in SMS 2003 SP2. By default, this component has 256 kilobytes (KB) available from which to create instances of SMS performance objects. However, because SMS performance object instances are created per computer, this limit may be exceeded.
Note The block of memory that is used for the SMS performance counter library is shared by the SMSEXEC process and other processes that monitor performance counters, such as the Perfmon.exe counter.
WORKAROUND
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To work around this issue, increase the RAM that is available for use by the SMS performance counter library. To do this, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS Performance Data Provider
- In the details pane, right-click Kilobytes of Virtual Memory to Reserve for SMS Performance Counter Data (min 16 KB, max 65536 KB), and then click Modify.
- In the Edit DWORD Value dialog box, click Decimal, and then type a value in the Value data box.
Note The Status Manager component creates a performance instance for every computer that generates a status message. The Status Manager creates these performance instances when it receives a status message and not when it starts. Therefore, you may have to try different values for this registry entry and then test the results to determine whether the issue is resolved. We recommend that you start with a small value, such as 2,048 decimal (2 megabytes), and then increase this value until the error messages are no longer generated. For example, depending on your environment, you may have to increase this value to 32,768 decimal. - Click OK, and then exit Registry Editor.
- Restart the SMS Status Manager thread.
Keywords: kbtshoot kbprb KB930055
