After an unexpected reboot of one of our Exchange 2010 CAS/Hub servers...the DefaultAppPool will not start using the ApplicationPoolIdentity that is assigned by default.
I get the following 3 error/warnings in the system event logs:
Log Name: System
Source: Microsoft-Windows-WAS
Date: 11/17/2011 5:56:37 PM
Event ID: 5021
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: cas.server.com
Description:
The identity of application pool DefaultAppPool 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. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number <31050780>
Log Name: System
Source: Microsoft-Windows-WAS
Date: 11/17/2011 5:56:37 PM
Event ID: 5057
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: cas.server.com
Description:
Application pool DefaultAppPool 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.
Log Name: System
Source: Microsoft-Windows-WAS
Date: 11/17/2011 5:56:37 PM
Event ID: 5059
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: cas.server.com
Description:
Application pool DefaultAppPool has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.
I can get the DefaultAppPool to start as NetworkService, but activesync still has issues. I have checked the permissions for the DefaultAppPool and they have log on as batch and log on as a service. Group Policy is not overiding the local security. I've compared to the other CAS servers in the environment, and there is no discernable difference.
Users who are experiencing the activesync issues can go get to the same servers OWA splashscreen, but they cannot actually log in. I can log in to that same url and get into my email.
Any ideas?