Sometimes, after provisioning a new machine, or making some configuration changes, you may find that your IIS server has gone completely missing without so much as leaving you a note. As you desperately try to bring up your site, your browser connection times out with “server not found” or, slightly better, you get the plain 503 “service unavailable” error.
In these cases, a lot of the instrumentation you typically have at your disposal with application failures is not available to help you fix the problem. But, not to worry - the solution is usually only a few steps away. The step-by-step instructions below should help you figure out what’s wrong in minutes.