Event ID 5059 — IIS Application Pool Availability
Applies To: Windows Server 2008 R2 SharePoint 2010

Web sites and Web applications depend on the availability of
Internet Information Services (IIS) application pools. IIS application
pools in turn depend on the Windows Process Activation Service (WAS). If
WAS is not running or errors occur during the startup or shutdown of an
application pool, Web sites and Web applications may not be available.
Event Details
Product:
|
Internet Information Services |
ID:
|
5059 |
Source:
|
Microsoft-Windows-WAS |
Version:
|
7.0 |
Symbolic Name:
|
WAS_EVENT_RAPID_FAIL_PROTECTION_REGARDLESS |
Message:
|
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. |
In our environment we harden all of our Servers and upon the hardening procedures we noticed that the IIS Application Pool wouldn't start. After a couple restarts and undoing some of the lock downs we had to make an exception to one of the lock down procedures.
Verify
In the Active Directory Group Policy for our SharePoint Servers we had to add the "Sharepoint Farm account" to the "Log on as Batch Job" entry. Per our lock down this setting requires us to leave it blank, with no entry. If the SharePoint Farm account is part of the Administrators group then the Administrators group would need to be added to that entry instead. Once we did that we rebooted the SharePoint servers all the sites and Central Administrator console came up fine.
No comments:
Post a Comment