Hinweis: Dieser Artikel wurde ursprünglich veröffentlicht in 2013. Einige Schritte, Befehle oder Softwareversionen haben sich möglicherweise geändert. Überprüfen Sie die aktuelle Dokumentation von Sharepoint 2013 für die neuesten Informationen.

Voraussetzungen

Bevor Sie beginnen, stellen Sie sicher, dass Sie Folgendes haben:

  • SharePoint Server 2013 or later
  • Farm administrator or site collection admin access
  • PowerShell with SharePoint snap-in

How to: Enable (http://sharepoint.microsoft.com “Microsoft SharePoint”) 2013 Central Administration when it displays “(http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol “Hypertext Transfer Protocol”) (http://www.iana.org/assignments/http-status-codes “List of HTTP status codes”). 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 (http://www.iis.net/ “Internet Information Services”) 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!

  1. Open the “Local Sicherheit Policy” however you can ((http://www.microsoft.com/en-us/server-cloud/windows-server/default.aspx “Windows Server 2012”) you can just hit the Windows key and type that or for older versions go to: (http://en.wikipedia.org/wiki/Control_Panel_%28Windows%29 “Control Panel (Windows)”) >> Administrative Tools >> Local Sicherheit Policy)
  2. Go to Sicherheit Settings
  3. Then Local Policies
  4. Finally User Rights Assignment
  5. 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 (http://sharepoint.microsoft.com “Microsoft SharePoint”) as well and the steps to resolve it are the same.

(http://img.zemanta.com/zemified_h.png?x-id=77b2f548-ec61-48ff-a00c-f558f5507fbf)](http://www.zemanta.com/?px “Enhanced by Zemanta”)

Zusammenfassung

Verwandte Artikel