Does anyone know of the best way to log all work process requests that are currently running when an IIS recycle happens.

If you go to IIS > Worker Processes > Select an app pool > View Current Requests you get a list of requests.

We have occasional recycles. If we are able to see the RAM on the server for w3wp.exe going up quickly, and we check the list of requests, we are often able to pinpoint the source of the issue (the URL gives us enough info to go on).

We have logEventOnRecycle set to log the event, and this works, but the details are useless.

In a perfect world the list of requests would go into the details of the event log.

In an even more perfect world, our team would get the requests emailed to us on a recycle.

Anyone else ever walk down this path?


Try DebugDiag tool, it's by far the easiest one to use that's free from MS. It's easy to setup to catch crash/hang and gives you a decent way to review the contents of it's dump files. It's pointed us right to the source in the code several times.

Here is a quick setup article, Steps to Catch a Simple “Crash Dump” of a Crashing Process from an MS blogger.

It's worth a try to see if you can catch what's causing your recycles.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.