Microsoft KB Archive/886015

= The SMS Executive service stops after you upgrade a Systems Management Server 2.0 SP5 site to SMS 2003 SP1 =

PSS ID Number: 886015

Article Last Modified on 10/27/2004

-

The information in this article applies to:


 * Microsoft Systems Management Server 2003 SP1

-





SYMPTOMS
After you successfully upgrade a site server that is running Microsoft Systems Management Server (SMS) 2.0 Service Pack 5 (SP5) to SMS 2003 Service Pack 1 (SP1), you notice the following symptoms:  The SMS Executive service has stopped. You can restart the SMS Executive service. However, it stops soon after you restart it. Entries that are similar to the following are logged in the :\Sms\Logs\Smsexec.log file:

ERROR: Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_EXECUTIVE\Threads\SMS_INVENTORY_DATA_LOADER is corrupt. $$< >

Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_EXECUTIVE\Threads\SMS_INVENTORY_DATA_LOADER ignored. $$< >< >





CAUSE
This problem occurs if the server that you upgrade has a local policy that prevents SMS 2003 SP1 from accessing objects in the Microsoft Windows registry.



RESOLUTION
To resolve this problem, modify the local policy on the server that you upgrade. To do this, follow these steps:  Click Start, click Run, type MMC in the Open box, and then click OK.</li> Click File, and then click Add/Remove Snap-in.</li> In the Add/Remove Snap-in dialog box, click Add.</li> In Standalone Snap-in, click Group Policy Object Editor, and then click Add.</li> On the Welcome to the Group Policy page, verify that Local Computer appears in the Group Policy Object box, click Finish, click Close, and then click OK.</li> Expand Local Computer Policy, expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then click Security Options.</li> In the left pane, right-click Network Access: Remotely accessible registry paths and sub-paths, and then click Properties.</li> In the Network Access: Remotely accessible registry paths and sub-paths box, add the following registry path, and then click OK:

Software\Microsoft\SMS

</li> In the left pane, right-click System Objects: Default owner for objects created by members of the Administrators group, and then click Properties.</li> In the Default owner for objects created by members of the Administrators group box, click Administrators group, and then click OK.</li> Restart the server.</li> When the server has restarted, log on, and then run a site reset. To run a site reset, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, point to All Programs, point to Systems Management Server, and then click SMS Setup.</li> Click Next two times.</li> On the Setup Options page of the Systems Management Server Setup Wizard, click Modify or reset the current installation, and then click Next.</li> Follow the instructions in the wizard to reset the site.</li></ol> </li></ol>

After you have completed these steps, the SMS Executive service will not stop when you have restarted it, and the SMS 2003 SP1 site will be fully functional.

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

Keywords: kbtshoot kbwinservperf kbSMS2003bug kbMgmtServices kbprb KB886015

Technology: kbSMS2003 kbSMS2003Search kbSMS2003SP1 kbSMSSearch

-

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

© Microsoft Corporation. All rights reserved.