Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 920703 - Last Review: February 12, 2007 - Revision: 2.0
When you try to install an SMS Service Pack 1 reporting point on a remote Windows Server 2003 Service Pack 1-based secondary site server, the installation is unsuccessful
When you try to install a Microsoft Systems Management Server (SMS) Service Pack 1 (SP1) reporting point on a remote Microsoft Windows Server 2003 SP1-based secondary site server, the installation is unsuccessful.
Additionally, the SMS\Logs\Srvboot.log file contains log entries that resemble the following:
SMS_SERVER_BOOTSTRAP_secondary site started.
Microsoft Systems Management Server v2.50 (Build 3174)
Copyright (C) 2004 Microsoft Corp.
Command line: "SMS_SERVER_BOOTSTRAP_secondary site LBN D:\SMS /install \\primary site\D$\SMS\bin\i386\rpregset.exe".
Set current directory to D:\SMS\bin\i386.
Site server: secondary site code.
Added machine account secondary site to the local administrator group.
Converting Path from \\primary site\D$\SMS\bin\i386\rpregset.exe to D:\SMS\bin\i386\rpregset.exe.
Created child process for D:\SMS\bin\i386\rpregset.exe, PID = 2380, command line arguments = "\\primary site\D$\SMS\bin\i386\rpregset.exe /install /siteserver:secondary site ".
Child process exited, exit code = 103.
Bootstrap operation failed: Child process exited with non-zero code 103.
Disconnecting from Site Server.
SMS_SERVER_BOOTSTRAP_secondary site stopped.
At least one file required for installation is missing, from server
Status message is 4952.
Similar entries may also be logged in the SMS\Logs\sitecomp.log file.
This problem occurs because the Rpregset.exe program cannot connect to one of the following registry subkeys on the site server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SQL Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Identification
This connection failure is indicated by error code 103.
The computer account on the secondary site (the reporting point site) may be unable to access the primary site server registry because the SMS_SiteSystemToSiteServerConnection_
sitecode local group on the site server does not have the required permissions.
To resolve this problem, make sure that the SMS_SiteSystemToSiteServerConnection_
sitecode group has Full Control permissions for the registry subkeys that are listed in the "Cause" section.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To confirm that you are experiencing the problem that is discussed in the "Cause" section, follow these steps:
- On the secondary site server, click Start, click Run, type cmd.exe, and then click OK.
- At the command prompt, type AT Current time + two minutes /interactive cmd.exe, and then press ENTER.
For example, if the current time is 1:46 P.M., type AT 1348 /interactive cmd.exe.
- A new command prompt will open after two minutes. At the new command prompt, type the following commands. Press ENTER after each command.
REG QUERY \\primary site server name\HKLM\SOFTWARE\\Microsoft\\SMS\\SQL Server
REG QUERY \\primary site server name\HKLM\SOFTWARE\\Microsoft\\SMS\\Setup
REG QUERY \\primary site server name\HKLM\SOFTWARE\\Microsoft\\SMS\\Identification
If you receive an "access denied" error from any of the REG QUERY commands, you are experiencing the problem that is discussed in this article.
Note If the SMS_SiteSystemToSiteServerConnection_
sitecode group has Full Control permissions, the problem may be that there are no "Allowed Paths" defined in the
winreg
registry key.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
153183Â
(http://kbalertz.com/Feedback.aspx?kbNumber=153183/
)
How to restrict access to the registry from a remote computer
APPLIES TO
- Microsoft Systems Management Server 2003 Service Pack 1
| kbfix kbbug kbsmsreporting kbprb KB920703 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate