Microsoft KB Archive/834617

= You receive error messages and scheduled updates do not occur when you start SMS Service Manager in SMS 2003 =

Article ID: 834617

Article Last Modified on 10/25/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-



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
You may experience any one or all the following symptoms on your Microsoft Systems Management Server (SMS) 2003 site server:   When you start the SMS Service Manager tool in the SMS Administrator Console, you receive the following error:

Error Communicating with the specified SMS Site Server

You also find entries that are similar to the following in the Compmgrprov.log file: *** ERROR *** CCompMgrProv::PopulateComponentArray: Could not read the Site Control File. Return code: 0

Additionally, the Sitecomp.log file contains the following entries: Waiting for the &quot;Site Control Manager (Master Site Control File)&quot; inbox to be defined. Sleeping for 60 seconds.  In certain low memory conditions, various components (threads) of the SMS Executive service overwrite data that is stored in the Registry subkey. This Registry subkey is reserved for the Site Control Manager component of the SMS Executive service and is written only during a site installation or a site reset. If the Registry subkey is changed, you experience all the following conditions:  SMS does not process Discovery Data Record (DDR) files. Scheduled updates to collections do not occur. Offer Manager does not detect any new or changed advertisements. </li>  The following entry appears in the Ddm.log file or the Colleval.log file, but also appears in other component logs: <pre class="fixed_text">Createded Inbox Definition 0 Note In this message, the word &quot;Createded&quot; is a misspelling for the word &quot;Created.&quot; </li></ul>
 * ERROR *** CCompMgrProv::CreateInstanceEnumAsync: PopulateComponentArray returned false.

<div class="cause_section">

CAUSE
These problems may occur when the SMS site server computer is in a low memory condition. Low system resources may occur when you use SMS Active Directory discovery methods.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

836145 Active Directory discovery methods cause low resources on Systems Management Server 2003

<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.

<div class="workaround_section">

WORKAROUND
To work around this problem, Microsoft recommends that you apply the hotfix from Knowledge Base article 836145. You must manually correct the registry values in the following registry subkey:

To do this, follow these steps.

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. <ol> Click Start, point to Administrative Tools, and then click Services.</li> Stop all SMS services.</li> Click Start, click Run, type regedit in the Open box, and then click OK.</li> Locate the following registry subkey:

HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Inbox Source\Inbox Definitions\0

The Value data for Inbox Name, Relative Path, and Service Rights will be incorrect.</li> Double-click Inbox Name, type Site Control Manager (Master Site Control File), and then click OK.</li> Double-click Relative Path, type inboxes\sitectrl.box, and then click OK.</li> Double-click Service Rights, type 1, and then click OK.</li> In some circumstances, the the Inbox Name and Relative Path value entries under the following registry subkey may be incorrect also:

HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Inbox Source\Inbox Instances\0

Verify that Inbox Name is set to Site Control Manager (Master Site Control File) and that Relative Path is set to inboxes\sitectrl.box .</li> Quit Registry Editor, and then restart the SMS services.</li></ol>

Note The   registry key is not site specific and can be imported from a working site. The   registry key is site specific. If this key is imported from another site, the UNC Path value must be modified to make sure that the value entry points to the correct location on the site server that is being corrected. Alternatively, these keys can be restored from a known good backup of the site server's registry. If either the  key or the   key is modified, Microsoft recommends that you run the ACLReset.exe utility to make sure that the correct registry permissions exist. The SMS 2003 version of this utility is available on the site server, under \SMS\bin\i386\, where  indicates the language setting for your computer. The utility is installed by the SMS 2003 Repair Wizard.

Keywords: kbactivedirectory kbserver kbregistry kbsmsutil kbsmsadmin kberrmsg kbsmstopazfix kbperformance kbdiscovery kbnofix kbbug KB834617

-

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

© Microsoft Corporation. All rights reserved.