Which stsadm command does and doesn't recycle the application pool?

I am trying to figure out if deploying / updating solutions and activating features recycle the application pool or interrupt / slow down user actions in some way. I need to know if these steps can be done while uploading to the server, or if deployment after work is best.

The specific commands I use are upgradeesolution or displayolution, addolution, installfeature and activfeature, but for completeness, it would be nice to have an exhaustive list.

+2


source to share


2 answers


As a rule of thumb, always improve features / solutions outside of the watch. You never know how a change will affect a running application.

  • upgradeesolution - yes
  • addolution - yes
  • installfeature - yes
  • activatefeature - no


The reason for activfeature is not because you are executing the commands contained in this function, for example. events and schemes. Everyone else is registering assets to use sharepoint, so a restart is required.

+5


source


For reference: Updesolution seems to be running a full IISReset, not just an application pool utility. This is an important distinction if you are using more than one site in your farm. To work around this, it seems you can pass the -local parameter and then recycle the application pool instead of IISReset. The downside to this is that you need to run the command on each server. It all depends on your situation, but it's good to know.



+4


source







All Articles