[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1532
  • Last Modified:

IIS application pool crashes

event log events

Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '4072'. The process exit code was '0xc0000005'.

A process serving application pool 'DefaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '5352'. The data field contains the error number.
1 Solution
If you have an idea of which application is causing this problem, you can go into IIS and set that application up in a different pool. You can also force the pool to restart itself.
Basically your code has caused some error in an app/website and caused the whole application pool to error.

First step as twol says is to isolate the application to a unique pool.

Then look at the IIS logs of that site for any 500 errors or long running requests.

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now