This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to 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
When the Microsoft Systems Management Server (SMS) Executive service is restarted in Microsoft SMS 2003, some SMS-related registry keys and registry values may appear in incorrect locations in the registry.
For example, after the Backup SMS Site Server task has finished or after the SMS site server has been restarted, the
subkey appear in the following incorrect locations in the registry:
Additionally, error messages that are similar to the following may be logged in the applicable logs in the SMS Executive service components:
Warning: found invalid inbox key:
SoftwareWarning: found invalid inbox rule key:
SoftwareWarning: found invalid inbox def key: Software
Note Registry keys and registry values that appear in incorrect locations in the registry may not affect the operation of the SMS site server. However, in some scenarios, this problem may cause the SMS Executive service or the components used by the SMS Executive service to stop responding.
In addition to the errors noted, the SMS Inbox Manager component may stop replicating data from drive letter:\SMS\Inboxes to the Client Access Point (CAP) servers. This may occur for all or some of the inboxes that exist on the CAP. No specific errors appear in the Inboxmgr.log file, the inbox is just not referenced. For example, Offermgr.box Pkginfo.boxwill not be be replicated to the CAP servers.
This problem occurs because SMS creates a new registry key or new registry value in an incorrect registry location instead of opening an existing registry key or registry value. This problem only occurs when multiple threads read from the registry at the same time by a multithreaded application such as the SMS Executive service.
Service pack information
To resolve this problem, obtain the latest service pack for Systems Management Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
885643 How To obtain the latest Systems Management Server 2003 service pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must install SMS 2003 Service Pack 1 (SP1) to apply this hotfix. This hotfix applies only to the SMS site server role.
You do not have to restart the computer after you apply this software update.
Hotfix replacement information
This hotfix does not replace any other software updates.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------------------------------- 25-Oct-2004 12:45 2.50.3174.1146 643,072 Baseutil.dll 26-May-2005 23:14 2.50.3174.1146 535,272 Sms2003-sp1-kb896602-x86-enu.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Systems Management Server 2003 Service Pack 2.
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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
The hotfix mentioned in this article does not delete any existing registry keys or registry values that appear in incorrect locations. This hotfix only prevents new registry keys and registry values from being created in incorrect locations in the registry.
Before you install this hotfix, manually remove any existing registry keys or registry values that appear in incorrect locations. To do this, follow these steps:
Click Start, click Run, type regedit, and then click OK to open Registry Editor.
Locate and right-click the incorrect registry keys or registry values, and then click Delete.
Warning Carefully evaluate each registry key and its values before you delete the key.
Quit Registry Editor.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates