In most of the cases, we have a 503.0, Application pool unavailable and when we check the corresponding application pool, it shows “ Stopped”.īelieve it or not, that is actually a feature in IIS acting: the Rapid-Fail Protection. If we’re looking at the reference list of responses that IIS could send, an HTTP response status 503 means Service Unavailable. In many cases, it may be needed to collect memory dumps to study the exceptions causing the crash: see article at. Evidence of what causes the w3wp.exe to crash may be found in Windows Events, in the Application log: second-chance crashing exceptions with w3wp.exe.Ĭollecting the IIS basic troubleshooting info helps expedite investigation for the root cause of application crashes.Evidence of repeated w3wp.exe crashes and Rapid-Fail Protection may be found in Windows Events, in the System log with Source=WAS.
It helps prevent consuming valuable system resources creating a worker process that crashes anyway, soon after spawning. This is a feature of IIS, at Application Pool level, called Rapid-Fail Protection. Since the w3wp.exe worker process, created by IIS to execute a web application, is crashing frequently, the respective IIS application pool is turned off.
The 503 response from the IIS machine, Service Unavailable, is the result of repeated application crashes.
0 kommentar(er)
