Learn how to fix Event ID 5059 and resolve IIS Application Pool errors. Our IIS Support team is here to help you with your questions and concerns.

How to Fix Event ID 5059: Resolving IIS Application Pool Errors

Have trouble with your IIS website’s “HTTP 503 – Service Unavailable” error?

According to our experts, it’s likely due to application pool configuration or permission issues that cause the application pool to stop unexpectedly. In fact, this error is commonly associated with Event ID 5059, which indicates that the application pool has been disabled.

The error message usually looks like this:

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.

An Overview:

• Troubleshooting Tips
• Alternate Solution
• Impact of Disabled Application Pools
• How to Automate Application Pool Monitoring

Troubleshooting Tips

The HTTP 503 status code and Event ID 5059 usually point to issues related to account permissions or misconfigurations in IIS. Here are the main causes and a step-by-step checklist to help us fix the error:

• Ensure that the account used as the application pool identity is not locked.
• Reset the account’s password if it has expired.
• If using a built-in account, consider switching to a domain account.
• Use a different domain account as the application pool identity if needed.
• Grant “Full Control” to the application pool identity account on shared data and configuration folders. Then, assign the “Log on as Batch Job” permission to the account. Also, add the application pool identity account to the IIS_USRS group.
• Furthermore, inspect the applicationHost.config file for any potential typos or misconfigurations.
• Ensure that the correct encryption provider (IISWASOnlyCngProvider or IISCngProvider) is used. Also, verify that the IISWASKey is the same if using shared configuration in IIS.
• If the error still occurs, recreate the application pool, websites, or shared configuration to ensure no misconfigurations.
• We can also, switch the process model from LogonBatch to LogonService to ensure the application pool starts properly.

Alternate Solution

If the application pool has been disabled, we may need to debug the associated application and restart the pool:

1. First, identify and correct any issues in the application running within the worker process.
2. Then, test and retest the application to ensure stability.
3. Now, go to Control Panel > Administrative Tools > Internet Information Services (IIS) Manager.
4. At this point, run IIS Manager as an administrator. Then, go to the Connections pane and expand the server node. Now, go to Application Pools.
5. Then, select the application pool to restart, right-click, and choose Start.

In order to verify the application pool is running, follow these steps:

1. Open IIS Manager as an administrator.
2. In the Connections pane, go to Application Pools.
3. Then, check the Status column to ensure that it shows Started.

Here are some additional tips from our Experts to avoid this error:

• Regularly review account permissions and configurations to prevent future errors.
• Furthermore, enable detailed logging in IIS to diagnose issues more effectively.

Impact of Disabled Application Pools

• When an application pool is disabled, all websites or services tied to it become inaccessible, leading to potential downtime.
• Even if the application pool temporarily restarts, there can be lingering performance issues like slow page loads, incomplete transactions, or interrupted sessions.
• Applications relying on the pool may encounter errors that result in corrupted data or lost transactions, particularly for database-driven apps.
• An unstable or disabled application pool can expose vulnerabilities if attackers exploit service interruptions.

How to Automate Application Pool Monitoring

• Use PowerShell Scripts for Automation:

  We can create PowerShell scripts to monitor the status of application pools regularly, triggering alerts when issues are detected. These scripts can also be set to restart the application pool automatically, minimizing downtime.
• Integrate with Monitoring Tools:

  Alternatively, use tools like SolarWinds, PRTG, or Nagios to monitor IIS performance and application pool status. Set up alerts to notify admins of any issues, including disabled application pools or performance drops.
• Event Viewer Integration:

  Additionally, we can configure triggers within Windows Event Viewer to send alerts or run scripts whenever Event ID 5059 or similar errors appear.
• Scheduled Maintenance Checks:

  Finally, set up routine checks to verify application pool health, clear logs, and refresh system resources.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

By implementing these solutions, you can fix the “HTTP 503 – Service Unavailable” error due to disabled application pools in IIS.

In brief, our Support Experts demonstrated how to fix Event ID 5059 and resolve IIS Application Pool errors.