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 having a weird issue. None of our WSPs (MOSS 2007 and 2010) work first time they are deployed. We noticed that upgrading solution (after deploying) works.

Our WSPs normally replace user controls in layouts folder. Any ideas why this is happening?

share|improve this question
When you say "work", does this mean you get an error or changed code isn't updating? – Alex Angas May 2 '11 at 5:16
No Error nothing. The resule via stsadm is "Operation completed successfully" but files wont be replaced. Then we run upgrade immediately and files get updated. – Shoban May 2 '11 at 5:46
try deploying the solutiosn using stsadm with the -local parameter. Otherwise the actual deployment is done by the timer job in the background and you will not see any errors (unless you check the ULS logs) – Wictor Wilen MCA MCM MVP May 2 '11 at 5:57
Thanks Wictor. Let me try. – Shoban May 2 '11 at 6:45
As wictor say: operation completet successfully refers only to the timer job. In 2010 you can check the status for a given solution in PowerShell using: Get-SPSolution | select DisplayName, LastOperationResult – Anders Rask May 2 '11 at 9:35
up vote 1 down vote accepted

Maybe adding "stsadm -o execadmsvcjobs" as your last step in the initial deployment will fix the issue. It will execute the administrator timer jobs immediately.

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.