The following table covers the common HTTP 503 substatus codes, along with their possible causes and troubleshooting advice: Status Code If needed, share the detailed error message recorded in the event log. If you see such errors or warnings, notify your application developers, and ask them to fix the exception. The following screenshot shows a typical error logged in the application log that occurred due to an unhandled exception:Ĭhecking the application log to identify the cause of application pool failure In that case, the application log can give you some useful insights. If the application pool stops repeatedly but there is no application pool identity-related error in the system log, the issue is likely due to some fatal error or unhandled exception in the code. If possible, set the password to never expire for that user. If a custom username is used, make sure its password is not expired. If you get an application pool identity-related error or warning, make sure the username and password for the identity are correct. Fixing HTTP Error 503Ī simple resolution for HTTP Error 503 is to start the application pool corresponding to your website. Once rapid-fail protection is disabled, the web server won't disable the faulting application pool, and visitors will no longer see HTTP Error 503. Anyway, disabling it sometimes comes in handy if developers are taking longer to fix the bug meanwhile, you want to keep the web application up and running. Instead, fixing the underlying cause (or bug causing the behavior) in the application code is really important. Remember that the rapid-fail protection feature is there for the safety of the web server, so disabling it shouldn't be considered a solution to the problem. Viewing and disabling the rapid fail protection for an application pool with PowerShell Set-WebConfigurationProperty -Name rapidFailProtection -Value $False You could even disable this feature by using the following PowerShell command: (Get-IISAppPool ).failure.rapidFailProtection As discussed above, when a worker process experiences five fatal errors or exceptions within five minutes, rapid-fail protection kicks in and automatically disables the faulting application pool.īased on event logs, if you conclude that the reason for application pool failure is a bug in the application code, but you still want to keep the application pool running until your developer fixes it, you could temporarily adjust the behavior of rapid-fail protection, either by increasing the Maximum Failures or the Failure Interval to a higher value. If you couldn't find anything in the System log, take a look in the Application log since the ASP.Net-related exceptions are logged there. Checking the system log to identify the cause of application pool failure
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |