SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are tring to run an update script. As part of this script we use stsadm command retractsolution and then deletesolution to remove the wsp packages.

Our problem is that on the last run several of our packages are stuck in the retracting state.

Anyone know what causes this and how to fix it?

share|improve this question
up vote 2 down vote accepted

Are you always deploying solutions from the same WFE always? You should!

execadmsvcjobs only flushes the jobs running on current WFE. Hence if you have stalled jobs on other WFE you can get inconsistent behaviour and jobs tend to get stuck.

Gary Lapointes gl-execadmsvcjobs have helped me out before in situations like that before, since it executes across WFE.

share|improve this answer

Does your script run stsadm with -o execadmsvcjobs after the retract command?

share|improve this answer
Yes, we run it after each retract sloution and delete solution – Shiraz Bhaiji Aug 25 '10 at 12:20
You could try manually executing the retract step, going into Central Admin to manually execute the timer job and seeing the results. Also, are there any clues in the ULS or Event Logs? – James Love Aug 25 '10 at 12:23

First thing I'd check is make sure the Timer Service is actually running on all front-end servers :-)

share|improve this answer
@Paul, yes we checked, it is running on all servers – Shiraz Bhaiji Sep 2 '10 at 7:26

It will may help to restart the Timer Service.

share|improve this answer

do a restart.. it worked for us

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.