Tag Archives: Central Administration

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

SharePoint-2013

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.

How to Identify the Version and Service Packs installed on a SharePoint 2013 Server

In many cases, we may not be bothered about the Version, Service Packs installed on our Server when we do the development. It is obvious that, when we get the requirement, immediately we will start analysis the requirement.

But recently there was a situation that one of our client wants to move on to the new Service Pack which released on this April. In that case, we may also have to analyze the impact of the new Service Pack. Before knowing that, I just wanted to know, what are the things installed on our Dev environment first. Then on top of it, what needs to be installed and what would be the impact after installation.

To answer all these questions, First we need to know what is the version installed on our Farm. Use the following command to get the Version of the product installed using PowerShell script.(Get-SPFarm).Products.

First Run ISE as below :

Run_ISE_as_Administrator

Then after selecting the Commands of “Add.PSSnapin” output of the above command will be something like,Get-SPFarm_Products

By seeing the GUID, we will be able to identify the Product. These GUIDs will not change. On all the environments, and all the machines, the GUIDs will remain same.

Here are all of the product GUIDs:

GUID : 35466B1A-B17B-4DFB-A703-F74E2A1F5F5E Product : Project Server 2013

GUID : BC7BAF08-4D97-462C-8411-341052402E71 Product : Project Server 2013 Preview

GUID : C5D855EE-F32B-4A1C-97A8-F0A28CE02F9C Product : SharePoint Server 2013

GUID : CBF97833-C73A-4BAF-9ED3-D47B3CFF51BE Product : SharePoint Server 2013 Preview

GUID : B7D84C2B-0754-49E4-B7BE-7EE321DCE0A9 Product : SharePoint Server 2013 Enterprise

GUID : 298A586A-E3C1-42F0-AFE0-4BCFDC2E7CD0 Product : SharePoint Server 2013 Enterprise Preview

GUID : D6B57A0D-AE69-4A3E-B031-1F993EE52EDC Product : Microsoft Office Web Apps Server 2013

GUID : 9FF54EBC-8C12-47D7-854F-3865D4BE8118 Product : SharePoint Foundation 2013

And to know about the Service Packs, there is no need of any PowerShell Commands. That we can directly go to the Central Administration and find.

Go to Central Administration.image1

Click on “Upgrade and Migration” on the Quick Links. image2

Click on “Check Product and Patch Installation Status”image3

This will tell us the current Patches Installation. By seeing the Version column we can identify. On the screen shot above shared, there is no SP installed.