SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

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

I'm trying to figure out a wierd problem, maybe yous guys can help.

I'm deploying a web part using powershell (Update-SPSolution) in a build definition.

The deploy works, but every time one application pool is stopped, and to make this more wierd this web app does not use the web part.

I've been reading the logs trying to find something to sugest a problem, but I cant find anything useful.

Unlike this question my web part is in one single project and it deploys "quickly" (~ 1min)

Thanks for any insight

UPDATE: I've manage to find a workaround, defining the solution setting "Reset Web Server Mode on Update" to Recycle.

But I'm still troubled on why the problem exists in the first place, and if it's allways going to append on each new solution.

share|improve this question

Check in Central Administration site-> System Settings > Farm Solution > Your solution

the solution you are updating would have been deployed to the web application for which app pool is recycled.

share|improve this answer
I just checked and no, it's deployed to another application, and that one does not stop. – Ricardo Gomes Feb 15 '12 at 14:50

If the Solution is Web-scoped, it will restart the Application Pool it is deployed to. If it is Farm-scoped, it will recycle all Application Pools on the server.

share|improve this answer
The solution only has one feature and the scope is Site. – Ricardo Gomes Feb 15 '12 at 14:52

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.