I'm having a issue with installing a secondary site server. The funny thing is I have installed quite a few servers so far as secondaries and this is the first time I have experienced this issue. The server is a brand new windows 2003 build so there is no software on it as far as I'm aware that could cause the install to fail. When I kick off the secondary install process via the console on the primary, the bootstrap files download successfully onto the secondary server. It then starts the install process and the temporary folder is created and the files I can see are being decompressed into it. Then, all of a sudden it fails and all files are deleted from the server and the sms_bootstrap.log file is left behind. The errors within this file is specified below. If anyone has experience this issue, help would be greatly appreciated. All permissions have been correctly set on the secondary so the primary has access to it and visa versa. The highlighted part is the actually error: Decompressing d:\SMS_BOOTSTRAP.pkg... $$<SMS_BOOTSTRAP><Fri Apr 18 17:08:30 2008><thread=10D8>Decompression successful. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>Elapsed time since startup: 0 days, 00 hours, 01 minutes, 56 seconds. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>Running SMS Setup... $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>Successfully parsed d:\ic515m12.TMP\SMSSETUP\install.map. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>d:\ic515m12.TMP\SMSSETUP\install.map build number "5931" is correct. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>Started "d:\ic515m12.TMP\SMSSETUP\bin\i386\setup.exe /script d:\SMS_BOOTSTRAP.ini /nouserinput" as PID 3068. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>Waiting for PID 3068 to terminate... $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:19 2008><thread=10D8>PID 3068 exited with code 1. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted! $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deinstalling myself... $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deleted temp directory d:\ic515m12.TMP. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deleted d:\SMS_BOOTSTRAP.pkg. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deleted d:\SMS_BOOTSTRAP.ini. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deleted d:\SMS_BOOTSTRAP.EXE. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deinstalled the SMS_BOOTSTRAP service. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Deinstallation complete. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Bootstrap procedure unsuccessful. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>Stopping SMS_BOOTSTRAP... $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>SMS_BOOTSTRAP stopped. $$<SMS_BOOTSTRAP><Fri Apr 18 17:10:29 2008><thread=10D8>

Setup itselffailed for some reason.Setup is started as a process and terminating with return code 1 (error). Please review the log file 'ConfigMgrSetup.log' located on the root for the setup failure information. Since setup fails right away, I suspect you may have designated an invalid drive in your installation path.

Actually, designating an invalid drive will not cause this problem. The files are being delivered ok, and setup is launched but fails for some reason. In any case, the ConfigMgrSetup.log should indicate why.

I had the same problem. In my case I tried to Install it direct on D:\ without subdir... The log says: "Error You cannot use the root of a drive as the sole directory path" So you have to define a subfolder!