Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool

Tags:

asp.net

iis

iis-7

IIS 7 Application Pool stops when browsing to http://localhost/

In Event Viewer -> System Log I see:

Application pool ASP.NET v4.0 has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

Are there other troubleshooting steps I can take to see a more detailed messages of why this is happening?

like image 267
dev.e.loper Avatar asked May 07 '12 14:05

dev.e.loper


People also ask

Was application pool has been disabled?

Event ID 5059 clearly shows the reason behind the 503 error: “Application pool has been disabled”. The identity of application pool %1 is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights.

Why does an IIS app pool crash?

The reason IIS keep crashing caused by unhandled exception is because the default policy for an unhandled exception has changed in the . Net framework 2.0 and later version. The behavior of this policy is to end the worker process.

How do I reinstall Windows Process Activation Service?

In the left navigation pane, right-click Features, and then click Add Features. On the Select Features pane, scroll down to Windows Process Activation Service. Select the check boxes for Process Model. Click Next from the Select Features pane, and then click Install at the Confirm Installations Selections pane.


2 Answers

If your application pool is running under a specific identity, an expired password could be the cause for your problem.

I had similar problems, see http://blog.janjonas.net/2012-07-14/iis_75-fix-application-pool-disabled-windows-process-activation-service-failure-worker-process-event-id-5059

like image 117
janjonas Avatar answered Oct 02 '22 22:10

janjonas


In IIS, go to Application Pools, and check the Identity of your Application Pool.

Is the App Pool using a custom account? Does it need to be?

Try changing the Identify to a Built-in account like ApplicationPoolIndentity. To do this, go to Advanced Settings, Process Model, Identity. Remember to restart the App Pool after making your changes.

IIS Custom App Pool Identity

enter image description here

like image 31
James Lawruk Avatar answered Oct 02 '22 23:10

James Lawruk