HTTP Error 503. The service is unavailable. App pool stops on accessing website

Solution 1:

One possible reason this might happen is that the Application Pool in IIS is configured to run under some custom account and this account either doesn't exist or a wrong password has been provided, or the password has been changed. Look at the advanced properties of the Application Pool in IIS for which account it uses.

Also the Event Log might contain more information as to why the Application Pool is stopping immediately on the first request.

Solution 2:

Ok, I have another solution for one specific case: if you use WINDOWS 10, and you updated it recently (with Anniversary Update package) you need to follow the steps below:

1. Check your Windows Event Viewer - press Win+R and type: eventvwr, then press ENTER.
2. On the left side of Windows Event Viewer click on Windows Logs -> Application.
3. Now you need to find some ERRORS for source IIS-W3SVC-WP in middle window.
4. Probably you will see message like:

The Module DLL >>path-to-DLL<< failed to load. The data is the error.

5. You have to go to Control Panel -> Program and Features and depending on which dll cannot be load you need to repair another module:
   • for rewrite.dll - find IIS URL Rewrite Module 2 and click Change->Repair
   • for aspnetcore.dll - find Microsoft .NET Core 1.0.0 - VS 2015 Tooling ... and click Change->Repair.
6. Restart your computer.

Solution 3:

For my situation is that my login password changed, while the application pool still uses the old one. So just click the "Advanced Settings" of your application pool and reset your "Identity".

Solution 4:

I was facing the same problem, and debugged it using the event logs. First it said that : "The description for Event ID 5059 from source Microsoft-Windows-WAS cannot be found".

I then turned on WAS using turn windows features on/off. Then i saw this in eventvwr "Microsoft-Windows-DistributedCOM cannot be found".

Finally I gave up and deleted the App Pool (that used to stop on accessing the website) and created it again, as it is. This resolved the problem.

Solution 5:

Most of Time, it was occured due to AppPool Setting.

Check the following to resolve this

1. Check Apppool service is running.
2. Check Identity of AppPool.
3. Enter the new password if it has changed for that identity.

The following Images show these setting in IIS