Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What's a valid way to test IIS7's OrphanWorkerProcess settings are working? I have a script and all the settings in the configuration for my application pool. However, it seems just simply recycling the application pool does not do the trick. I've even validated that the script is never attempted to load by using ProcessMon.

I'm basically trying to do something similar to this:

Here's the IIS 7 reference page:

I think the problem I'm having may be I was simply expecting the process to be orphaned when I recycled the application pool, but that doesn't work. The reference says:

"Specifies whether to assign a worker process to an orphan state instead of terminating it when an application pool fails."

So maybe the real question is possibly:

  • How do I invoke a failure to see if the script I have set for the orphanActionExe is working?
share|improve this question

Use Process Explorer from SysInternals. It has a feature to suspend a process allowing it to pause communication with WAS.

share|improve this answer

You need to make it fail communication with WAS somehow. If pinging is enabled, you could try attaching a debugger and pausing the process; haven't tried it.

It doesn't happen on regular recycles, just when a reactive recycling event is encountered.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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