Environment:
SharePoint 2010 Enterprise RTM
Windows Server 2008 R2 Domain
Description:
I chose not to use the Farm Configuration Wizard, but instead create my web applications manually.
1. Created a new Web Application.
2. Added a new managed service account.
3. Created a new application pool for this web app.
4. Created a Site Collection for this web app.
Error Messages:
The following error occurs when trying to launch the newly created Site Collection:
HTTP Error 503. The service in unavailable.
The application pool is shutdown and the Event Viewer indicates:
Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 4/24/2010 4:58:28 PM
Event ID: 1500
Task Category: None
Level: Error
Keywords:
User: GUERILLA\spapppool
Computer: SPS2010RTM.guerilla.local
Description:
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, and that your network is functioning correctly.
DETAIL – Unspecified error
Observations:
Seems like the application pool was having trouble loading the user profile for the service account. Since I had never logged on locally with the service account before, it was unable to find a user profile for it (C:\Users\).
Resolutions:
Option 1 – Log on locally with the service account once to create a local profile for it.
Option 2 – Modify the application pool by going into IIS > Application Pools > Right-Click offending app pool > Advanced Settings > Set “Load User Profile” to False.
Side Effects?
Haven’t seen any yet… Not sure if SharePoint service accounts need to have local user profiles for anything in particular.
The SharePoint Swiss Army Knife 
Seems like the “Option 2” should be already set as default. Why would a service account need to load user profile? Great post!
Just want to say what a great blog you got here!
I’ve been around for quite a lot of time, but finally decided to show my appreciation of your work!
Thumbs up, and keep it going!
Cheers
Christian, iwspo.net
a service account should not need to load user profile i think
I come accross this situation three times and i solved it every is running as before, so this is my experiece:
First Case#1: Interface IP configuration problem.
Look your local driver E:\Windows\System32\drivers\etc\host
If you see any entry like this:
fe80::9069:9334:813e:868 ComputerName # Added by Office SharePoint Server Search (6/8/2010 4:45 AM). It means office sharepoint server is removing your ip 4 entry.
Then you have problem of IP 4 & 6 conflicts so to solve it disactivate the IP V6 of your interface and remove the entry and run IISRESET. The problem has gone.
Second case #2: Exchange server version 2003 problem.
Administrative tools->IIS->Default website->properties->ASP.Net choose asp.net version 2.0.
Run IIS RESET and the problem is gone.
Case #3: Exchange server version 2007 problem.
isapifiler for exchange when bad request arrives. change precondition to 32 or 64
IIS configuration sections
I hope this will solve your problem.
Excellent post, it is truly a great read!
I had a similiar problem however it turns out that there was a domain security that specified the accounts that could run as a batch job and as a service. It was not until i added the account to this allowed list that the application pool would start and i could access the central admin site.
Really a lifesaver…..
I spent a couple of Hours Trying to Understand what was happening with my Dev box without any Luck…
Great Post….
This worked for several of us:
http://patricklamber.blogspot.com/2010/11/sharepoint-2010-returns-503-service.html
My profile load was already set to “False” by default, but still the 503 error. This is a MICROSOFT ISSUE! Why would this FAIL to start, right after the install! Ridiculous!
Maybe the IPV6 or the ‘logon as a service’ issues might be part of it. Right now, I am rebooting, since I had not yet rebooted. FYI, the app pools WERE STOPPED after I finished the SharePoint install, so I had to manually start those; I did not have any credentials issues.
The service accounts I am using are local admins on the server and are domain users.
I also will check out the “patricklamber” link mentioned above.
Follow below link that will work for you hopefully
http://www.fewlines4biju.com/2011/01/http-error-503-service-is-unavailable.html
This post is exactly what I needed! Extremely helpful!
banker neilsen hula Azra orlin enamored myr skedaddle caxton
Option 2 helped. Thanks!
This update resolved the above issue.
http://support.microsoft.com/kb/2682616.
I think you might mean http://support.microsoft.com/kb/947215 Sandeep 😉 (Andy Talbot – we we’ve spent the last couple of days talking about this together!!!!). Guys, watch out for issues with ForeFront Protection for SharePoint after this (#Justsaying !!!)
Woops I mean http://support.microsoft.com/kb/2682616 not the above KB I mentioned!!! Copy and paste issue! My bad?! Yes I can confirm that this resolves the issue. I would advise with extreme caution about using ‘work around’ such as preventing local profile load overides in IIS, and also logging on with the service account – you could be in for a whole load of pain upon doing so, as what happens if/when the profile is removed and or you have a server refresh, or add another server to your farm, and don’t test that it works ok on other farms (let’s say if you didn’t document your ‘workaround’)?
Option 2 worked great. I remember the same problem/solution has croped up before.
It is possibly because the configuration wizard was run while logged into the machine as a different account to the original SharePoint creator (farm admin) account.
It was only the central admin app pool account that had this issue, making me believe that it may have been this reason.
>> 503 Service Unavailable, App Pool Shutdown
Hi!
Had this problem on Server 2010 after SP1 installed. Retype Your passwords for
– App Pools (inetmgr.exe-> app pools)
– and Services(services.msc)
By example if You had on ‘Log On’ tab something like DOMAIN\Administrator – retype all this passwords on Sharepoint and SQL services
Way cool! Some extremely valid points! I appreciate you
penning this post and also the rest of the site
is very good.
When someone writes an post he/she retains the image of
a user in his/her mind that how a user can be
aware of it. Therefore that’s why this post is great. Thanks!
Other than Password expiry and Application Pool in Stopped status, There are few more reasons for Service Unavailable: HTTP Error 503. The service is unavailable in SharePoint
Found this checklist to resolve this error in SharePointDiary.com – http://www.sharepointdiary.com/2011/04/http-error-503-service-is-unavailable.html#ixzz2aWTwKAIM