Sorry to post yet another like this, but I've been through the similar posts with no joy. SharePoint Server 2010 gives me a 503 error the first time I try and get into the Central Admin Site after running the Configuration Wizard during install.
I'm building a Team Foundation Server 2010 system for our Dev group, using SharePoint Server 2010 in support of TFS. All components (IIS, SQL Server, Reporting Server, SharePoint Server, and TFS) are going on one machine. Not the best design,
but we don't have spare servers to spread the load, and we're a small group and don't need screaming performance.
The domain controllers are Windows 2008 R2 Std. Ed. x64 SP1. The SharePoint machine is Windows 2008 R2 Std. Ed. x64 SP1, fully patched. IIS installed, no problems. SQL Server 2008 R2 Std. Ed. installed, with Reporting Services. Applied
SP2 to SQL Server. Configured Reporting Services, no problem. I let Reporting Services use port 80, and installed it in Native Mode. (I tried 'SharePoint Integrated Mode' in an earlier test, SharePoint Central Admin threw a 503 error then,
as well.)
Reporting Services looks good, its web sites come up with no problem.
Based on prior experience, I then go into RegEdit on the SharePoint server and change ownership of the AppID key for the IIS WAMReg Admin service from 'TrustedInstaller' to the local administrators group, and then give the local administrators group Full
Control on that key.
Now I'm ready to start installing SharePoint Server 2010. Since the Prerequisites installer always gives errors, I first manually install the Windows Identity Foundation, reboot the server, and manually start the Microsoft .NET Framework NGEN v2.0.50727
services (both the _x86 and _x64 versions). After that, the Prerequisites installer will install everything correctly.
(I am logged in to this server as an account that is both a Domain Admin and a SQL Admin, with the SysAdmin role and 'db_owner' user mapping on everything in SQL Server. The passwords on all of the applicable accounts have not been changed in over
six months, before this server was built.)
I have a 'SharePoint Farm Admin' account created, at the domain level. It is a member of the 'Domain Users' group only. Its password has also been stable since before this server was built.
I install SharePoint Server 2010, choosing 'Server Farm' and 'Complete' during installation. Installation gives no problems, and I start the Configuration Wizard.
For the Database Settings, I give it the server name of this server (since I'm using the SQL Server that was installed on this same machine), and the Instance Name of the SQL Installation - 'Mimas\TFS2010'. I take the default database name, 'Sharepoint_Config'.
I give it the SharePoint Farm Admin account, '<domain name>\SPFarmAdmin' and its password.
I provide a passphrase and confirm it.
For the Central Admin web app, I have tried using the 'standard' port, 17012, and gotten the 503 error. This time, I take the default port it provides, 27850. I tell it to use NTLM authentication.
SharePoint goes through its configuration, tasks 1 through 10, and apparently completes successfully. I click 'Finish', and I should go into the Central Admin site. I get a 503 error.
I check the web, and look at the usual suspects. IPv6 is turned off on all the NICs in the server.
There are no 'empty .NET 2.0 folders' under %WinDir%\Microsoft.NET\Framework or Framework64.
There have been no recent password changes.
There are no SQL 1346 errors in the logs.
There are no failed logins in the Security Log.
There is a local profile on the server for the SPFarmAdmin account.
SPFarmAdmin has 'log on as a service' and 'log on as a batch job' rights on the server.
The Reporting Services web sites still come up OK.
When I look at the applications pools in IIS 7 manager, the app pool for SharePoint Central Administration v4 is stopped. Its identity is <domain name>\SPFarmAdmin. I can start it normally, and it starts. It stays running.
When I try and launch the Central Admin site, it gives a 503 error, and that app pool stops again.
My logs on the server then show a string of Event ID 2276 errors in the Application Log - 'IIS-W3SVC-WP The worker process failed to initialize correctly and therefore could not be started.' The qualifier given is 49152, for what that's worth.
The System Log also shows a string of Event ID 5009 errors, 'A process serving application pool 'SharePoint Central Administration v4' terminated unexpectedly. The process exit code was '0xfffffffe''.
Searching for solutions to these errors has not yielded any results so far.