Microsoft KB Archive/832998

= The Inbox Manager component generates high CPU-utilization on an SMS site server =

Article ID: 832998

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition

-



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
Your Microsoft Systems Management Server (SMS) 2.0 site may process data slowly, and this may cause a backlog of files on the site server computer. In this scenario, Performance Monitor may indicate that the SMS_Executive service is generating high CPU-utilization. Specifically, the Inbox Manager component continuously logs entries to the Inboxmgr.log file, and this indicates that it is analyzing various Inboxes -- for example, the Offerinf.box and the Pkginfo.box folders. Additionally, Replication Manager may process incoming files from the Despooler much more slowly than expected.

In addition to these issues, Inbox Manager may continuously add new entries to the following registry key:

When this issue occurs, the size of the registry continues to grow, and this may cause quota errors in the registry.



CAUSE
These issues may occur when more than one client access point (CAP) exists on the same server. The first CAP is located in the CAP_ folder, where   is the SMS site code. Additional CAPs may have been created on a network share on the existing CAP computer.



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 problem, follow these steps:  In the SMS Administrator Console, expand Site Hierarchy\SMS\Site Settings. Click Site Systems to review the CAPs that are installed for your site. Right-click each CAP where the Type column contains &quot;Windows NT Share,&quot; and then click Delete. Click Yes when you are prompted to confirm the deletion of the object. After you have finished, make sure that there is only one CAP listed. Wait several minutes to give SMS a chance to process the changes. Click Start, point to Programs, point to Administrative Tools, and then click Services. Stop all SMS services.</li> Click Start, point to Run, and then type regedit.

Note Type regedt32 if you are running Microsoft Windows NT 4.0.</li> Expand the following registry key:

 

</li> Delete each subkey where the NAL Path entry value contains the network share location for the CAP shares that you deleted in step 3.</li> Restart the SMS services.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
There must be only one CAP on any particular server computer. Multiple CAPs on the same computer do not provide any additional benefit. In a typical SMS 2.0 installation, an SMS 2.0 CAP computer will have only 50 to 70 registry subkeys in the  subkey.

When another CAP is created on a computer that contains an existing CAP, duplicate subkeys are created that point to the same Inbox folders. Each subkey contains a Location Type entry with a value of 3. When the Inbox Manager component cycle starts, each Inbox folder is reviewed; when many additional Inboxes are added to the registry, the Inbox Manager enumerates the registry subkeys and therefore runs continuously.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

Additional query words: threads Replication Inventory Dataloader Sender Discovery Data

Keywords: kbcap kbinboxmgr kbclientserver kbusage kbperformance kbnofix kbbug KB832998

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.