Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Thursday, August 9, 2012 8:05 AM
Dear Sir, Recently in one of my website gives error as follows: HTTP Error 503. Service Unavailable. And in IIS 7 application pool is stop automatically for the website. I have restart the pool but when I run the website it goes to stop. I googled it, follow the below steps but could not solve the problem. 1.Custom account issue.To change username and password for application pool in IIS 7. -There is no such username or password for my website. 2.In application pool,Advanced setting--Rapid Fail Protection --Maximum Failures 50 - No change in Error. 3.Change of application pool, I have created new application pool and run website using that pool but the same error. Please guide me useful steps to resolve this issue. -Programmer
Tuesday, August 14, 2012 3:25 AM ✅Answered
Have you checked event viewer to see if there's any related events logged? If nothing logged in event viewer, please check http.sys logs(located at %windir%\system32\logfiles\httperr) for detailed reason. Here's a great article that elaborates the general steps for troubleshooting 503 service unavailable:
Where did my IIS7 server go? Troubleshooting 503 "service unavailable" errors
http://mvolo.com/where-did-my-iis7-server-go-troubleshooting-503-quotservice-unavailablequot-errors/
Thanks.
Thursday, August 9, 2012 9:12 AM
Hi,
The system event log will provide insight as to why the app pool is stopping. If you are using a custom user account for the app pool identity make sure that user account has permissions on the root folder for the site and is added to the IIS_WPG user group.
Here is more information about setting app pool identities.
http://learn.iis.net/page.aspx/624/application-pool-identities/
Monday, November 11, 2013 3:00 PM
This was because the password was changed recently for the Identity under which the application pool was trying to run. Fix was to go to the IIS Manager-> Application Pool -> Advanced Settings -> Process Model -> Identity and set the password to the new one.