I booted up my server this afternoon and tried to deploy a SharePoint solution package. I ran a deployment script which called stsadm commands to install and deploy several wsp files. The install script looks something like:
SET stsadm ="%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\12\BIN\STSADM.EXE"
%stsadm% -o addsolution -filename "MySolutionPackage.wsp"
%stsadm% -o execadmsvcjobs
%stsadm% -o deploysolution -name "MySolutionPackage.wsp" -allowgacdeployment -allcontenturls -immediate –force
%stsadm% -o execadmsvcjobs
Nothing special is happening here. After both the addsolution and deploysolution commands I get the following error:
The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled. If the timer job is scheduled to run at a later time, you can run the jobs all at once using stsadm.exe -o execadmsvcjobs. To avoid this problem in the future, enable the Windows SharePoint Services administrative service, or run your operation through the STSADM.exe command line utility.
I checked the services and found out that the Windows SharePoint Services Administration service wasn't running. After starting the service the errors weren't reproduced.
Please note: My install script included the command execadmsvcjobs which runs all jobs that are waiting to be run instead of waiting for the service to pick it up. If you deploy a solution via Central Administration you should run STSADM –O execadmsvcjobs or start the Windows SharePoint Services Administration service.
Just need to find out now why the service didn't start automatically .... TBC