I had to add batch logon rights in AD. It was grayed out locally.
Main Topics
Browse All TopicsI am installing MOSS 2007 Ent on a Hyper-V virtual machine running Windows Server 2008 Std. Database is on a separate physical machine (SQL 2008/Windows Server 2008).
For installation I use a domain account with local admin rights on the MOSS machine and db_creator and db_security rights on the SQL machine. I also use another account with same rights as an account for SQL connectivity and application pool.
When installation and initial farm configuration is finished I get the "HTTP Error 503. The service is unavailable." when trying to go to Central Administration Website. Under ISS logs I have the following 2 warnings and an error:
--------------------------
Log Name: System
Source: Microsoft-Windows-WAS
Date: 12/9/2008 5:31:21 PM
Event ID: 5021
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
The identity of application pool SharePoint Central Administration v3 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.
--------------------------
Log Name: System
Source: Microsoft-Windows-WAS
Date: 12/9/2008 5:31:21 PM
Event ID: 5057
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
Application pool SharePoint Central Administration v3 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: 12/9/2008 5:31:21 PM
Event ID: 5059
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
Application pool SharePoint Central Administration v3 has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.
--------------------------
Any ideas what am I doing wrong?
Thanks...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
On the Server go to Administrative Tools - Local Security Policy - Local Policies - User Rights Assignment - Log on as batch job and add the Application Pool Identity User account to this setting If this is grayed out then there is a GPO from Active Directory with No Override (Enforced) that is making this setting. Go to AD and find the GPO and then add the Application Pool Identity User account to this setting. Perform gpupdate /force from the server command prompt, check the local policy again to ensure the new setting has taken place. Then start the Application Pool
Business Accounts
Answer for Membership
by: mass2612Posted on 2008-12-09 at 18:58:32ID: 23135929
Hi,
I know this might sounds silly but have you tried re-entering the password for the account under the application pooly properties? I had similar issues on MOSS with Windows 2003 when I enabled the Central Admin site on the second WFE server for HA.
Have you also confirmed the account has rights to logon as a server and batch logon rights etc?