Solving SharePoint Server 2010 - 503. The service is unavailable, After installation

Question

Installed: SharePoint Server 2010 for Internet Enterprise Beta (x64) On: Windows Server 2008 Standard (x64) on 64 bit hardware

Attempts to access the Central Administration console led to IIS returning 503. The service is unavailable

And this error was found in the Application log

The Module DLL 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\isapi\owssvr.dll' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture.

After much ado, the solution turned out to be:

1) Ensure that the enable32BitAppOnWin64 seeting for the "SharePoint Central Administration" app pool is set to False, and the same for the "SharePoint Web Services Root" app pool

2) Edit applicationHost.config:

Change:

  <globalModules>
 ...
 ...
 <add name="SharePoint14Module" image="C:\Program Files\Common
 Files\Microsoft Shared\Web Server
 Extensions\14\isapi\owssvr.dll"
 preCondition="appPoolName=SharePoint
 Central Administration v4" />
 </globalModules>

To:

    <add name="SharePoint14Module" image="C:\Program Files\Common Files\Microsoft
 Shared\Web Server Extensions\14\isapi\owssvr.dll" preCondition=
"appPoolName=SharePoint Central Administration v4,bitness64" />

I hope this helps somebody :-)

bitness64 being the magic word here

Solution 1

1) Ensure that the enable32BitAppOnWin64 setting for the "SharePoint Central Administration" app pool is set to False, and the same for the "SharePoint Web Services Root" app pool

2) Edit applicationHost.config:

bitness64 being the magic word here

Solution 2

I got a 503 error because the Application Pools weren't started in IIS for some reason.

Solution 3

I agree with Beytan Kurt.

I had 503 thrown for both the Central Admin site as well as the SharePoint landing page. In both cases the Passwords were expired.

After resetting the password in the AD, and refreshing the Identity, CA worked but the SharePoint landing page threw a 500 error.

It turned out that the .Net Framework Version was set to V4.0. I changed it to V2.0 and it worked.

Remember after each change you need to recycle the appropriate app pool.

Solution 4

Can You Please try this : Check the web site properties in IIS. Under home directory tab, check the application pool value Verify that all SharePoint services are started. If the application is not started do the following: I think this error might occur because of changing the service account password. You may need to change the new password to application pool
1)Click the stopped application pool 2)click advanced settings 3)Identity ->click the user to retype the user 4) Application Pool Identity dialog 5)click set -> manually type the user name and password. Then restart the server.

Solution 5

It can also happen if your password policy or something else have changed your password in case your appPools are using the the user with changed password.

So, you should update the user password from the advanced settings of your appPool throught "Identity" property.

The reference is here

View more solutions