Article ID: 267258 - View products that this article applies to.
This article was previously published under Q267258
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(https://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you attempt to install a Systems Management Server (SMS) hotfix on a secondary site, the hotfix may seem to be installed correctly, or may not be installed. If the hotfix is not installed, you may see the following text in the Qnnnnnn.log file that is generated when you install a hotfix:
Installation aborted. This system is not running SMS version number 2.00.1239.1000. Instead, the version reported is 000.
However, the server is in fact running SMS 2.0 or SMS 2.0 SP1.
Installation aborted. This system is not running SMS version number 2.00.1380.1000. Instead, the version reported is 000.
The Qnnnnnn.log file is located in the SMS\Logs folder on the site server on which you installed the hotfix. The nnnnnn portion of the file name represents the number of the hotfix you installed.
This behavior can occur if you either installed or upgraded an SMS 2.0 secondary site directly from the SMS Administrator console at the primary site. This issue does not occur on sites that you installed or upgraded by using the CD-ROM.
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 issue, manually create or update the required registry value. To create or update this value on secondary sites:
Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.