Troubleshooting Solution (.wsp) Deployment
This article help you troubleshoot issue while deploying solution package and successfully complete the solution deployment:
Once you have got your solution (.wsp) package for deployment, you will have to add the solution to the solution store using the command:
stsadm -o addsolution -filename <solution file name>
Once the solution is added to configuration database, you have to deploy it to the individual front-end Web servers in the farm. You have a choice to either deploy from the GUI of Central Administration page or from the command line.
If you are going to deploy from command line, use the following command:
stsadm -o deploysolution -name <solution name> [-url] <virtual server URL>
[-allcontenturls] [-time] <time to deploy> [-immediate] [-local]
[-allowgacdeployment] [-allowcaspolicies] [-lcid] <language> [-force]
If you are facing issue like the status is showing as “deploying” then you will need would like to know where is it stuck? Enable verbose logging for all or for the following categories : Timer and Topology. Most likely it would be timer service stuck or waiting for a job to complete.
Try using the command : stsadm – o execadmsvcjobs
If the solution is still hung state, you can cancel the deployment of the solutions by using the following commands:
1. stsadm -o enumdeployments
It will list out the Windows SharePoint Services Solution Package (*.wsp) and Web Part packages located in the solution store of the farm. along with the deployment IDs.
2. stsadm -o canceldeployment -id <ID>
This will retract the solution package deployment.
3. stsadm -o deletesolution -name <solution name>
Hope this will help you!