oos alert issue

Question

I recieved alert below

Alert: Application Pool disabled due to worker process failure

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

I verifed event logs from OOS server, Please find the error from event logs in the attached text16687-ooserror.txt

what could be the cause of this error and what needs to be done. Please help

Answer 1

Hi @sns ,

From the event log you provided, it means w3wp.exe file crashes. And IIS uses worker processes (w3wp.exe file in Windows) to handle client requests. So you get the Alert: Application Pool disabled due to worker process failure. You could refer to this article: w3wp.exe crash

For your issuse, it's the Exception code: 0xe0434352

Exception code 0xe0434352: This is a generic CLR exception code. It is thrown when there is an internal issue in the application. In most cases, it is either System.NullReferenceException or System.ArgumentException
There is no straightforward way to solve these kind of issues. I would recommend debugging the application in Visual Studio to get more details. In case you don’t have access to the source code, you can use DebugDiag or WinDbg for further troubleshooting.

Answer 2

This is the IIS feature Rapid-Fail Protection. By default an App Pool is configured to become disabled if a worker in the pool crashes 5 times within a 5 minute span. Please refer to this post: application-pool-defaultapppool-is-being-automatically-disabled-due-to-a-serie

You could try to restart the application pool:

Go to your IIS, select the Application pool 'HostingService'. Right click the application pool, select Start.

Answer 3

Hi Michael Han,

Did you have a chance to look in to above thread?

Answer 4

Hi sns1,

It's not the "hosting service" app pool crash. It's the w3wp.exe crashes, so the app pool would be disabled automatically due to w3wp.exe failures.

The default values are "5 failures" in "5 minutes" for app pools.

By changing this, it would change the Rapid-Fail Protection feature. You would not get the alert again. But this error would still exist in the event log.

Since there is no straightforward way to solve these kind of issues. It you want to find the cause of this issue, I would suggest open a ticket with Microsoft to have a dedicated Technical Professional to support you from there.