Troubleshoot IIS - Service Not Available 503 Issue
Table of Contents
Introduction
When working with IIS, you may encounter the "Service Unavailable 503" error. This usually occurs when the application pool stops automatically. The following is a collection of useful resources for troubleshooting this issue.
Useful Resources
-
http://www.codeproject.com/Questions/674073/Csharp-Code-to-Start-and-stop-perticular-applicati
-
http://stackoverflow.com/questions/14359983/asp-net-mvc-site-has-stopped-working-in-iis7
-
http://stackoverflow.com/questions/18016353/why-does-the-application-pool-automatically-stop
-
http://weblogs.asp.net/scottgu/auto-start-asp-net-applications-vs-2010-and-net-4-0-series
-
http://stackoverflow.com/questions/23615050/random-crashes-in-asp-net-mvc-how-to-debug
-
http://forums.asp.net/t/2065560.aspx?Thread+Abort+in+ASP+NET+app+causes+w3wp+exe+to+crash
-
http://w3stack.org/question/why-c-wrapper-of-c-crash-crashes-web-app-but-runs-fine-as-console-app/
-
https://msdn.microsoft.com/en-us/library/system.appdomain.unhandledexception(v=VS.90).aspx
-
http://stackoverflow.com/questions/2481047/executing-code-on-application-crash
-
https://blog.kowalczyk.info/article/c4qb/How-to-make-software-crash-less.html
-
http://www.codeproject.com/Questions/283255/Application-Pool-Stops-automatically
-
http://stackoverflow.com/questions/18016353/why-does-the-application-pool-automatically-stop
Conclusion
The IIS 503 Service Unavailable error is commonly caused by an application pool that has stopped. The resources above cover various scenarios including automatic pool stopping, unhandled exceptions crashing the worker process, and strategies for keeping ASP.NET applications running reliably.