Blog Post

IIS Support Blog
2 MIN READ

Event ID 5059 (Application pool has been disabled)

Nedim's avatar
Nedim
Former Employee
Dec 20, 2018

An IIS website may display “HTTP 503 – Service Unavailable” error when the application pools don’t have correct configuration or permissions which causes them to unexpectedly stop. Event ID 5059 clearly shows the reason behind the 503 error: “Application pool has been disabled”.

 

You may also see 5021 (The identity of application pool %1 is invalid) and 5057 (Application pool %1 has been disabled) in Event Viewer. Here are the detailed error messages:

 

Event ID 5021

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.

Source

 

Event ID 5057

Application pool %1 has been disabled. Windows Process Activation Service (WAS) did not create a worker process to serve the application pool because the application pool identity is invalid.

Source

 

Event ID 5059

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

Source

 

Checklist to solve “Application pool has been disabled” error

HTTP 503 status code and 5059 event ID may indicate issues related to account permissions or IIS configuration. Here is a list of things to try. You may need to restart IIS or machine after each change.

 

  1. The account used as application pool identity shouldn’t be locked
  2. Reset the password of the application pool identity account in case it is expired
  3. Switch from built-in account to domain account for application pool identity
  4. Use another domain account as application pool identity
  5. Give “Full Control” to application pool identity account on shared data and configuration folders
  6. Give “Log on as Batch Job” permission to the application pool identity account
  7. Add the application pool identity account to IIS_USRS group
  8. Check account information in applicationHost.config for possible typos
  9. Recreate application pools, websites, and shared configuration (if used)
  10. Make sure to use the same encryption provider (IISWASOnlyCngProvider or IISCngProvider) in applicationHost.config
  11. Change application pool process model from LogonBatch to LogonService
  12. If it is a shared configuration setup in IIS, use the same IISWASKey
Updated Dec 20, 2018
Version 2.0

3 Comments

  • kollodziej's avatar
    kollodziej
    Copper Contributor
    Jun 04, 2024

    I have checked all points that you have mentioned and my some of my app pools still fails to start after computer restart. Does anyone maybe have the same problem? 

     

    I have my applicationPoolDefaults -> startMode se to "AlwaysRunning"

     

    If I start pools that fails after computer restart manually it works.

  • AmitBarkai's avatar
    AmitBarkai
    Copper Contributor
    May 02, 2021

    thanks for the post , but i still fail to understand what would make a working application suddenly crush this way.

    and how we can prevent it from happening in the first place?

    let say the applicaiton pool is working with the ApplicationPoolIdentity why would this "user" expaire ?

    is there any possibility that a windows update could affect it ?

    is there any option and AWS machine could load with an invalid state ?

  • BWMerlin's avatar
    BWMerlin
    Copper Contributor
    Jun 10, 2019

    Thanks, for me the logon as batch was the final part.  I also needed to reset all of the password used by the different sharepoint services as well.