I just had a customer who’s SharePoint application pool keep stopping.
We had the following output in the event log on the server:
|
1 |
The identity of application pool [AppPoolID] 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. |
There can be 2 resolutions to this error, the following needs to be done.
- Incorrect application pool credentials, one needs to update the credentials:
- Open “IIS”.
- Navigate to “Application Pools”.
- Find the stopped application pool, right click it and choose “Advanced Settings”.
- Under “Process Model”, find “Identity” then click on the “…” next to it.
- Apply the updated credentials information, like [Domain]\[Username] and your new password.
- The service account is not member of “Logon as a batch” policy:
- Open “gpedit.msc” in cmd on the local machine, or open the Domain GPO on your administrative machine.
- Navigate to “Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> Logon as a batch job”.
- Add your service account here.
If you had a default domain policy, now run the following in a cmd.exe prompt:
|
1 |
gpupdate /force |
This should update the local policy on the machine.