IIS convention should check WWW service is running

[PaulStovell]

Customer was getting errors trying to deploy an IIS site:

10:42:29 Info | Application pool "Internal" does not exist, creating... 
10:42:30 Error | new-item : Destination element already exists, please use "force" parameter to
10:42:30 Error | override. 

Looked strange - first we can't find the app pool, then we get told it exists. Luckily they found the problem:

I did some digging. Seems the check for the app pool is failing. The app pool already exists but it is stopped. Furthermore the World Wide Web Publishing Service is stopped which is actually the problem. After restarting WWW Publishing I again stopped the Internal app pool. This time, even though the pool was stopped, the script found that the app pool was there and left it alone.

Perhaps adding a check to see if WWW publishing is running so you could return a better exception would be a good user experience: “WWW Publishing service is stopped so Octopus cannot update your app pool.”

[PaulStovell]

To be honest, this has only come up once and doing the checks might cause more problems - going to just leave this one as something to resolve via a KB.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.