'DefaultAppPool' failed to respond to a ping.

Question

0.00/5 (No votes)

See more:

Hey all,

We have below warning in the event viewer that is thrown

A process serving application pool 'DefaultAppPool' failed to respond to a ping. The process id was 'XXXX'.

We have put the option of recycling the Application pool on hold has this contains many application in it . Meanwhile i would like to know what could be root cause for this issue also how do we aviod this .

Posted 24-Mar-11 22:32pm

Aravind Ravindranath Gopi

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rutvik Dave · Answer 1 · 2011-03-25T10:28:00

First of all you should not be using same AppPool for all your web applications/websites. If one web application crashes, it will recycle the app pool which will make all the other application to restart, so users will lose their session information on the server.

Now if any fault occurs IIS will restart the AppPool to recover from it. now if you have disabled it, it will not come out of the fault.

Also this is a very generic error, there is no specific cause for this. so you need to debug the cause using IIS Debug Diagnostics Tool[^]. this tool will generate detail log file, which will help you to identify the problem.

or you can create seperate app pool for each application and then assign to it, and see which one is not working, that application is causing the problem.