Help Sharepoint 2013 - HTTP 503 Site is unavailable

I'm looking for some assistance with SharePoint 2013. I've had the site up and running for the past year with no issues.

After installing windows updates this weekend, suddenly sharepoint is  inaccessible.  All the appears is a message stating

Service unavailable.

HTTP Error 503.  The service is unavailable.

The event logs is full of errors for sharepoint.  121, 6482, 6398 Primarily, although, these errors showed up prior to this month's install of windows updates so that may not be relevant to the situation.

I found several articles that indicated to look at the application pool in IIS.   this was setup with a specific user created just for sharepoint tasks in AD.  

SharePoint-80 starts, but stops every time I try to load a site.

ff5698066fa040ba9bcc9a997ebe0fc5 starts but also appears to stop when I try to load a site.

I've tried changing the user on both of these application pools and when I change it to domain admin, I get a message stating you don't have permission to access the sharepoint site instead of HTTP ERROR 503.

The underlying server OS is Windows 2012

The database is SQL Express 2012

Any sharepoint experts have any advice?   We had other issues with several IIS sites and application pools on other web servers.  Those have all been resolved by changing the user on the application pool, but at this point we haven't been able to get sharepoint working.



June 17th, 2015 1:35pm

Have you tried running SP2013 configuration wizard already?
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 2:25pm

Just tried running the config wizard, and it doesn't seem to have done any good.  Went ahead and tried creating a new site collection, and can't view that new page either.

June 17th, 2015 2:52pm

update.  I just set all the sharepoint services to use a domain admin account and it's working.  

Why?   There's no reason why sharepoint should need to run under a domain admin account.  What am I missing here?

Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 4:32pm

Most of my 503 errors before were due to bad user account in the app pool.  Can you verify:

  1. the service account used is not locked?
  2. WWW publishing is on?
  3. Pull all the critical errors in ULS and IIS, and trace for error using ULS log viewer after restarting IIS?
  4. Try a different alternative access mapping?

June 17th, 2015 4:33pm

service account is not locked, verified by logging into a spare workstation with the account that the password being used is correct.

I'm able to use central administration from the same server.   My sharepoint implementation is very small, it is a single server.

After doing a bit more testing, it doesn't seem the domain admin was the trick that did it, but rather group policy "logon as batch"   Researching why a web app needs logon as batch.

I'm still baffled, this has been working fine for over a year and never needed logon as batch.  Why now?

Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 5:13pm

HI,this issue could be of many reasons like the service account,pwd change for account...Please check the link below that explains more in detail about the solution of the issue.

http://expertsharepoint.blogspot.de/2013/11/error-application-pool-keeps-stopping.html

June 18th, 2015 2:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics