Starting the app pools in AppFabric fails

Question

Hello,

Please help with any experience with this issue. I see similar posts, e.g. http://social.msdn.microsoft.com/Forums/sk/dublin/thread/708bb63a-aef1-48cc-bf6f-7dc297d71b1c but no resolutions.

My services were working properly till last Sunday and yesterday - on Monday all of a sudden I could not bring them up. Starting the app pools always logs the eventd Id-s: 2281, 2276 and several 2302:

The worker process failed to initialize communication with the W3SVC and therefore could not be started.  The data is the error.

The worker process failed to initialize correctly and therefore could not be started.  The data is the error.

There was an error during processing of the managed application service auto-start for configuration path: 'MACHINE/WEBROOT/APPHOST/Default Web Site/SubscriptionManagerService'. The error message returned is: ''.  The worker process will be marked unhealthy and be shutdown.  The data field contains the error code.

They all contain data fields referring to errors 800700E7 (error pipe busy) and 80070005 (Access Denied). Does anyone have any ideas (I already tried the suggestions in the post above and also some old suggestions from Microsoft about bypass traverse checking rights).

Thank you!

Val

---

Thanks Val

Answer 1

This is apparently a timing issue based on the other thread. I am wondering if it would be possible to sort of reset the timing problem. I am not sure how to do a clean reset. Have you tried restarting the box and/or restarting the WAS/AppFabric services, etc?

Since the other thread is a little old I would try contacting Microsoft Support for an updated status on the fix. I will also reach out to my Microsoft support contacts to see if this issue was officially closed yet or if an fix has not yet been released. My contacts get back to me informally as a low priority so if you need something ASAP, open a ticket with Microsoft Support. The other thread had the ticket number so they should be able to lookup this fix very quickly.

-- Update

I sent the email to Microsoft support, will let you know when I hear anything.

Thanks,

---

If this answers your question, please use the "Answer" button to say so | Ben Cline

Answer 2

While I have not fixed my issue, I am pretty sure that there is something that I misconfigured or maybe a bug in the service host factory - I rolled back my latest (small?!) changes and all works again. Whatever it is, we deserve a better diagnostic and tools here... I am working to figure out what went wrong and if I find a suspect I'll definitely post it here.

Val

---

Thanks Val

Answer 3

I heard back from my Microsoft Support contacts and they recommended the following workarounds:

1. Disable the application pool recycling:

  a. Open IIS
  b. Expand the computer name and click Application Pools
  c. Right-click the application pool and click Recycling.
  d. Uncheck any Recycling Conditions that are checked.

The application pool may need retarted after making this change.

2. Use application warm-up to ensure that the application pool is always running. This may help: http://www.iis.net/download/ApplicationInitialization.

3. Configure a scheduled task to recycle the application pool less frequently, like every 10-15 days or every night at 10 pm; something like that. This should reduce the amount of recycles.

Thanks Microsoft!

---

If this answers your question, please use the "Answer" button to say so | Ben Cline