'HTTP Error 503. The service is unavailable' message in IIS7 – Application Pools

One of my IIS7 virtual directories wigged out today and started to give me the following error screen.

Error Screen

Service Unavailable – HTTP Error 503. The service is unavailable.

I found a post from Rich Strahl that pointed me in the right direction. When I brought up my Internet Information Services Manager and clicked on Application Pools, my DefaultAppPool was stopped.

app pools

Unfortunately, my application pools were already set to auto-start and restarting the application pool didn’t solve my problem. As soon as I tried to bring up my website, the application pool would immediately stop again and give me the same error screen. After spending the next 10 minutes or so restarting Windows 7 and starting and re-staring my application pools to no avail, I decided to re-install my IIS7 and Windows Process Activation Service features.

After re-installing these windows features, everything was back in order. Unfortunately, I did have to add ALL of my virtual directories again, but I expected as much. You can re-install these features from the Programs and Features screen by clicking on Turn Windows features on or off.

Programs and Features

On the Windows Features screen, you can uninstall any feature by removing the check next to it and then clicking OK. You can then return to this screen after restarting windows to reinstall them.

Windows Features Windows Features 2

Hope this helps someone. If anyone knows how to correct this without reinstalling the features, please comment!

2 comments :: 'HTTP Error 503. The service is unavailable' message in IIS7 – Application Pools

  1. Hey man, I have this same error and I did exactly what you did and it still doesn't work. I can't find anything on the internet that points me to the right directionm what fo you think could it be?

    Anonymous

    8:26 PM

  2. If uninstalling and reinstalling IIS7 and Windows Process Activation Service didn't fix the problem for you, I'm not sure what else could be causing it.

    It might be something specific to the web application or virtual directory that you have running on the application pool. You might want to create a new application pool to test with to rule out issues with just the Default pool.

    Sorry, I wish I could be of more help.