Last Friday, I encountered a problem where the application deployed on IIS 7 could not be accessed. When I browsed the WCF Service, I reported HTTP ERROR 503. Check and find that the Application Pool is stopped. After you manually start up, go back to the page and report error 503. Then, check the Application Pool and find that it is stopped automatically. At first, I thought it would be good to restart IIS, but it was useless.
Why? I haven't done anything recently? In addition to changing the password. Oh! The problem lies here.
Application Pool Identity I use a windows Account in the domain instead of the default AppPoolIdentity. Because the domain user's password needs to be modified regularly, after the modification, the password stored in the IIS configuration file is no longer valid, which is why the Application Pool will always stop automatically.
Reset your account and browse again.