Dreaded 503 After SP2010 Installation

after a 'successful installation of SP2010' application pool for 'Central Administration v4.0 is stopping due to WAS error: 5059, this happen when a domain group policy is implemented. There are tons of solutions you can easily found by googling this error and probably would suggest editing of applicationhost.config or even adding of service account in 'login as batch', however these might or might not solve your issue.

Specially when you don't have the privileged to edit the GPO or even the local policy is locked because the 'Domain Group Policy' supersede the local policy.

Note: I used my standard domain account that has full privileged to both SQL Server and Local Server.

Changing Application Pool Identity to Network Service will run OK but will encounter Database connection failure, even if you give the identity dbcreator or sysadmin server role.

To make the story short:

Solution that works for me is to use local account in the SP configuration(I wouldn't advice this unless for testing purposes only). Yeah I was aware that local account is for stand alone only and SP GUI wouldn't allow local account to be used as Database Access, but there is a clever workaround here.

POWERSHELL is you friend!

After installing SharePoint 2010 do not run the Config wizard yet. make sure that there are no created SharePoint Admin and Config database, if so just delete it and application pools as well.

Note:

Run the "SharePoint 2010 Management Shell" by using Administrator rights. Click the Icon and select 'run as administrator', otherwise you'll encounter registry write error. Don't make me say I told you so! :P

Type and execute the command below:

PS> C:\Users\ New-SPConfigurationDatabase

cmdlet New-SPConfigurationDatabase at command pipeline position 1
Supply value for the following parameters:
DatabaseName: SharePoint_Config
DatabaseServer:
FarmCredentials
Passphrase:
-

after a successful creations of SharePoint Admin and Config databases. Run the SharePoint Confguration GUI wizard again and connect the created databases.


Update: 4/29/2011

THIS WILL WORK ONLY IF YOU'LL USE LOCAL ACCOUNTS (Farm and Complete installations)

For real solutions is to add ISS_IUSRS in 'logon as batch' when
global policy is implemented.

For reference: