How to: Enable SharePoint 2013 Central Administration when it displays “HTTP Error 503. The service is unavailable.”

So this issue threw me off at the beginning as I had just freshly installed a SharePoint 2013 server and who would possibly expect that right out of the box the thing won’t work. Regardless, after doing some digging in the event logs and on IIS it turns out the SharePoint application pools were stopped as the domain user I had provided for some reason didn’t have enough permissions to run as a service / batch job. As you can imagine, all you need to do at this point is give that user the right permissions and you are good to go. Be sure to check you have the right username/password and that the account is not locked too!

• Open the “Local Security Policy” however you can (Windows 2012 you can just hit the Windows key and type that or for older versions go to: Control Panel >> Administrative Tools >> Local Security Policy)
• Go to Security Settings
• Then Local Policies
• Finally User Rights Assignment
• There you will find “Log on as a batch job”. Go in there and add the user you set up on your SharePoint 2013 installation!

Rumor has it this issue appears on SharePoint 2010 as well and the steps to resolve it are the same.

SharePoint 2010: Error 7043

SharePoint 2010: Error 7043 “Load control template file /_controltemplates/TaxonomyPicker.ascx failed”

SUMMARY

You install Microsoft Sharepoint 2010 RTM on Windows 2008 R2, you receive the following error message multiple times in the application event log:
Event Type: Error
Event Source: SharePoint Foundation
Event Category: None
Event ID: 7043
Computer: SERVERNAME
Description: Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type ‘Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker’ from assembly ‘Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.

CAUSE
The ULS log is created in a code path where all control templates are loaded into the web application. This is a one time process which happens just before showing any UI to the user after an IISReset.
The source of the problem looks like a stale control template in the control templates folder while the control itself has been removed from the code base.

RESOLUTION
This is not causing any issues except for a wrong ULS log message a single time in a web application process life time, the exception is caught and that template file is skipped. This message should be treated as log noise and can be ignored.
To change this behavior:

1. Navigate to /14/TEMPLATE/ControlTemplates/TaxonomyPicker.ascx user control
2. Open the user control in a text editor and locate the first line
3. Find the character string , and replace with a comma ‘,’ (without quotes).
4. Save the user control