When deploying C # related items in the normal procedure IIS application pool and the program after the success of the new site, and then through the browser to initiate a request services, report found 503 errors. Thinking reported 503 errors, more of a problem with the server, so the earlier thinking lookup on IIS problem, you can see the application pool use is off, you re-initiate the request, 503 error still occurs, then go to the application pool is still closed. Why such a mistake happen?
So the problem of Baidu, told me this is closely related to the application pool used by right - process model - identify, select the built-in account -ApplicationPoolIdentity.
After setting the application pool identity, the application pool should be no longer automatically shut down the state.