Installing a SMS 2003 secondary site installation hangs

[mginsberg]

I am attempting to install a SMS 2003 secondary site using the admin console of the primary site server. After a couple of days the site installation status lists as pending. The SQL database resides on a dedication SQL box which does not act as the SMS Primary site server. I have removed and resinstalled the secondayr site a number of times. Unfortunately, the secondary site never appears to complete isntallation. Does anyone have any advice on troubleshotting this problem?

Thanks,

Mitchell Ginsberg

Mitchell Ginsberg
Technical Analyst

 

[clong72]

did you get a resolution for this ?

 

[cthulhu4u]

I too have this problem. There are a few of things you can do to troubleshoot:

There should be a bootstrap package on the secondary site. If it is not there, there is a problem.

There is a log file on the C drive called smsinstall.log I think. Review this and it will give you a good idea as to what is going on.

There is also a utility that I use review the SMS logs called SMS Trace. It in SMS Tools. I usually point it to the parent site sender.log in \sms\logs. Look for boot, the hostname for the server you are pushing to, or the SMS site code.

All this in mind, I still can't get my package through. It just hangs and I cannot find a thing about in any of the above places.

 

[cthulhu4u]

Also check out thread22-469449. It has a bunch of info on this problem.

 

[tbrennans]

I know a few ppl that had to write the source files (installation files) to the secondary HD and install from there instead of doing the whole thing over the wire

Tbey too were not able to install until they copied the files over, then it worked fine.

HTH

 

[crobin1]

I ran into this problem back in January. We were setting up two secondary sites. The servers to handle the sites were not identical hardware, but were identical in OS/software. One site installed fine through the admin console, the other site never would install. As tbrennans said, we copied the installation files to the hard drive and ran the setup from there. It then worked fine. We never did figure it out.