A - OBJECTIVE: to describe a high-level objective.
B - PROBLEMS :
Using stsadm to deploy a solution, a timer job for deployment is created but its state is always “pending”
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o enumdeployments
<Deployments Count=”1″>
<Deployment JobId=”7547c94e-5b2a-4619-88a4-93306319ec6d”>
<Title>Windows SharePoint Services Solution Deployment for “samplesolution.wsp”</Title>
<Type>Deployment</Type>
<State>Pending</State>
<Schedule>3/15/2013 12:14 PM</Schedule>
<File>sharepointboost.licensecentersetup12.3.wsp</File>
<ServerType>Front-end Web server</ServerType>
<Target>http://feowss01/</Target>
</Deployment>
</Deployments>
Troubleshooting:
– Ensure that the deployment lock is released at all server by stsadm:
stsadm -o removesolutiondeploymentlock
C - SOLUTION:
– In my case, there was a server which had been removed out of the farm. Hence, deployment for the whole farm (including all servers) will surely encounter the above problem.
– The expected stsadm command is to use “local” parameter for one current server at a time
stsadm -o deploysolution -name “timerjobmanager.wsp” -url “http://testsite” -local -allowgacdeployment -force
