Thanks for that workaround information and I assume you mean SBS 2003 since SBS 2008 comes only with WSS 3.0 and you don’t add it to WSS 2.0.

As an asside, I for one appreciate all the important work you do there at Dunlap keeping everything zipped. From this day forward and every time I put on a pair of pants and they don’t let the horses out, I’ll be reminded of this conversation. You are the DU-IT citizen of the day.

1. I changed where ’stsadm’ was referenced in the script to the explicit path to the command. On my server it was ‘c:\”Program Files”\”common files”\”microsoft shared”\”web server

extensions”\12\bin\stsadm.exe’. It appeared to be grabbing the stsadm.exe associated with WSS 2.0 (the default on a small business server). The clue was when running ’stsadm -help’ there was no ‘addsolution’ option.

2. For whatever reason, the Windows SharePoint Services Administration was not started. When I first ran the script, I received a ‘The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled.” error. After I restarted the service and ran a series of ’stsadm-o enumdeployments’ to get the job id’s of the failed jobs and then ’stsadm-o canceldeployment-id “GUID jobId” ‘ to cancel them, I was able to re-run the batch file and everything loaded beautifully.