Tuesday, September 4, 2012

Issues


Issue-1
I recently came to an issue where I tried deploying web part in WSP to production. I used “STSADM –o addsolution” command and my WSP got added. Then, I deployed WSP and it got deployed too but with Timer service successfully created warning. So, I tried executing this timer service with “STSADM –o execadmsvcjobs” command and it took 1 hrs to execute (and sometime 2 hrs).  Doing research I got to know that it’s because other existing WSP deployment is pending and that WSP got in pending state during deployment.

Resolution
 We need to cancel existing WSP which is in error state.

Step-by-step approach to Cancel WSP deployment
1.       Search for all WSP which are about to deployed but are in Pending state.
2.       You can see all WSP under <deployment> tags.
3.       Get Job ID of WSP which is in Pending state and cancel that WSP deployment.
4.       stsadm –o canceldeployment –id “XXXX-XXX…..”

Issue-2
Also you might face issue related to retracting solution and during retracting; solution execution takes endless time.

Resolution
You might need to delete solution directly without retracting it. Run command stsadm –o deletesolution –name “WSP-Name”. Now, add a solution and deploy solution.