Sharepoint http error 503 the service is unavailable - Исправление ошибок и поиск оптимальных решений проблем

From last few days, lots of people have come across error «503 Service Unavailable». Mostly people come up with a plan to update passwords to resolve the issue. 90% of the time Update Password in IIS and Central Admin does the trick but if you come across a
scenario where you are still stuck with “503 Service Unavailable” try below. Verify that all SharePoint services are started, this error mostly occurs because of changing the service account password.

Issue: Error 503. The service is unavailable

Here is screenshot of error how it looks

0076

Error you might see in Log file.

Exception: System.ServiceModel.ServiceActivationException: The service ‘/SecurityTokenServiceApplication/securitytoken.svc’ cannot be activated due to an exception during compilation. The exception message is: Exception has been thrown by the target of an
invocation.. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —>

What is “503 Service Unavailable” error?
Http 503 errors are generated by the IIS and it happens when web server sends data stream back to the web site.

First, make sure the steps below are followed to update the password:

Open IIS on SharePoint server > Expand Server > Expand Website.
Check the web site properties in IIS > under home directory tab, check the application pool value and then open that application pool from the application pools (separate node in the IIS tree).
Click the identity tab and see who the pool is assigned to. For the sake of testing, you can select «Predefined» and select local service from the drop down.
Restart IIS and see if things work out for you.
You may need to change the new password to SharePoint timer service in services.msc console.

Here are the Advanced troubleshooting steps to resolve this issue:

Incorrect Authentication Settings: Please ensure that the authentication settings for the SecureTokenServiceApplication are correctly configured by completing the following steps: Open IIS Manager
Expand “Sites”
Expand “SharePoint Web Services”
Select “SecurityTokenServiceApplication”
From the “Features” pane, double click on “Authentication” under “IIS”
Right click “Forms Authentication” and select “Disable”

The authentication settings page should only have Windows and Anonymous access enable for the security token service to issue tokens properly (and for claims authentication to work properly)

Incorrect data in the configuration file: Please review the web.config file of the secure token service application and compare it to a web.config file from a «working» secure token service application or secure token
service application on a different machine. Lots of people eventually copy web.config from a working machine which resolves the issue. Here is a copy of my web.config for security token:

———————- Security Token Service Application web.config————Start ——————

<?xml
version="1.0"
encoding="utf-8"
?>

<configuration>

<system.serviceModel>

<behaviors>

<serviceBehaviors>

<behavior
name="SecurityTokenServiceBehavior"
>

<!-- The serviceMetadata behavior allows one to enable metadata (endpoints, bindings, services) publishing.

This configuration enables publishing of such data over HTTP GET.

This does not include metadata about the STS itself such as Claim Types, Keys and other elements to establish a trust.

-->

<serviceMetadata
httpGetEnabled="true"
/>

<serviceThrottling
maxConcurrentCalls="65536"
maxConcurrentSessions="65536"
maxConcurrentInstances="65536"
/>

</behavior>

<behavior
name="ApplicationSecurityTokenServiceBehavior"
>

<serviceMetadata
httpGetEnabled="false"
httpsGetEnabled="false"
/>

<serviceThrottling
maxConcurrentCalls="65536"
maxConcurrentSessions="65536"
maxConcurrentInstances="65536"
/>

</behavior>

</serviceBehaviors>

</behaviors>

<services>

<service
name="Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceContract"

behaviorConfiguration="SecurityTokenServiceBehavior"
>

<endpoint

address=""

binding="customBinding"

bindingConfiguration="spStsBinding"

contract="Microsoft.IdentityModel.Protocols.WSTrust.IWSTrust13SyncContract"
/>

<endpoint

name
="ActAs"

address="actas"

binding="customBinding"

bindingConfiguration="spStsActAsBinding"

contract="Microsoft.IdentityModel.Protocols.WSTrust.IWSTrust13SyncContract"
/>

<endpoint
address="mex"

binding="mexHttpBinding"

contract="IMetadataExchange"
/>

</service>

<service

name="Microsoft.SharePoint.IdentityModel.ApplicationSecurityTokenService"

behaviorConfiguration="ApplicationSecurityTokenServiceBehavior">

<endpoint

name="app"

address=""

binding="customBinding"

bindingConfiguration="spStsApplicationBinding"
contract="Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract"
/>

</service>

<servicename="Microsoft.SharePoint.Administration.Claims.SPWindowsTokenCacheService">

<endpoint
address=""

binding="customBinding"

bindingConfiguration="SPWindowsTokenCacheServiceHttpsBinding"
contract="Microsoft.SharePoint.Administration.Claims.ISPWindowsTokenCacheServiceContract"
/>

</service>

</services>

<bindings>

<customBinding>

<binding

name="spStsBinding">

<binaryMessageEncoding>

<readerQuotas

maxStringContentLength="1048576"

maxArrayLength="2097152"/>

</binaryMessageEncoding>

<httpTransport

maxReceivedMessageSize="2162688"

authenticationScheme="Negotiate"

useDefaultWebProxy="false"
/>

</binding>

<binding

name="spStsActAsBinding">

<security

authenticationMode="SspiNegotiatedOverTransport"

allowInsecureTransport="true"

defaultAlgorithmSuite="Basic256Sha256"
messageSecurityVersion="WSSecurity11WSTrust13WSSecureConversation13WSSecurityPolicy12"
/>

<binaryMessageEncoding>

<readerQuotas

maxStringContentLength="1048576"

maxArrayLength="2097152"/>

</binaryMessageEncoding>

<httpTransport

maxReceivedMessageSize="2162688"

authenticationScheme="Negotiate"

useDefaultWebProxy="false"/>

</binding>

<binding

name="spStsApplicationBinding">

<binaryMessageEncoding>

<readerQuotas

maxStringContentLength="1048576"

maxArrayLength="2097152"
/>

</binaryMessageEncoding>

<namedPipeTransport

maxPendingAccepts="250"

maxPendingConnections="250"

maxReceivedMessageSize="2162688">

<connectionPoolSettings

idleTimeout="00:30:00"

maxOutboundConnectionsPerEndpoint="250"/>

</namedPipeTransport>

</binding>

<binding
name="SPWindowsTokenCacheServiceHttpsBinding">

<security

authenticationMode="IssuedTokenOverTransport"

defaultAlgorithmSuite="Basic256Sha256"
/>

<textMessageEncoding>

<readerQuotas
maxStringContentLength="1048576"
maxArrayLength="2097152"/>

</textMessageEncoding>

<httpsTransport
maxReceivedMessageSize="2162688"
authenticationScheme="Anonymous"
useDefaultWebProxy="false"
/>

</binding>

</customBinding>

</bindings>

</system.serviceModel>

<system.webServer>

<security>

<authentication>

<anonymousAuthentication
enabled="true"
/>

<windowsAuthentication
enabled="true">

<providers>

<clear
/>

<add
value="Negotiate"
/>

<add
value="NTLM"
/>

</providers>

</windowsAuthentication>

</authentication>

</security>

<modules>

<add
name="WindowsAuthenticationModule"
/>

</modules>

</system.webServer>

<system.net>

<connectionManagement>

<clear
/>

<add
address="*"
maxconnection="10000"
/>

</connectionManagement>

</system.net>

</configuration>

———————- Security Token Service Application web.config————End ——————

SecureTokenServiceApplication not provisioned: Use the following PowerShell commands to provision the secure token service application:

$sts = Get-SPServiceApplication | ?{$_ -match "Security"}

$sts.Status

$sts.Provision()

$farm = [Microsoft.SharePoint.Administration.SPFarm]::Local

$webServiceCollection = new-object Microsoft.SharePoint.Administration.SPWebServiceCollection($farm)

foreach ($service in $webServiceCollection)

After running above command we see this error:
Exception calling «SecurityTokenForContext» with «1» argument(s): «The requested service,’http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas’ could not be activated. See the server’s diagnostic trace logs

+ > If you get above error try below in PowerShell

$sts = Get-SPServiceApplication | ?{$_ -match "Security"}

$sts.Status

$sts.Provision()

Event log:
The Execute method of job definition Microsoft.SharePoint.Publishing.Internal.PersistedNavigationTermSetSyncJobDefinition.

ULS log:
The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc/actas is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that
the address is correct and try accessing the service again later.

+> If you get above in Powershell try below:

PSCONFIG.EXE -cmd upgrade -inplace b2b –force

Psconfig -cmd Secureresources

Note: Above needs to run in SharePoint PowerShell with account that has Farm Admin permission.

You might have the URL http://+:80 reserved. To check the same run command “netsh http show urlacl” in SharePoint Powershell. If this shows an output similar to:

Reserved URL : http://+:80/
User: BUILTINIIS_IUSRS
Listen: Yes
Delegate: Yes
User: BUILTINAdministrators
Listen: Yes
Delegate: Yes
User: NT AUTHORITYNETWORK SERVICE
Listen: Yes
Delegate: Yes
SDDL: D:(A;;GA;;;IS)(A;;GA;;;BA)(A;;GA;;;NS)

Then you have this port reserved which takes precedence over your http://localhost calls. Go ahead and remove this URL reservation by running the following command:

netsh http delete urlacl url=http://+:80/

5. Web Application started out as a 32-bit ASP.NET application and subsequently got converted (upgraded) to a SharePoint 2010 Web Application. In this case, you will see that the application pool has the «Enable 32-Bit Applications» property set to true,
which is incompatible with SharePoint 2010. Setting this property to false should solve the problem. In some cases, some SharePoint 2013 server Web Applications have this setting as true which is incorrect.

0079

Ensure that the enable32BitAppOnWin64 setting for the «SharePoint Central Administration» app pool is set to False, and the same for Other Application pool.

+> You can do the same by Editing applicationHost.config located at C:WindowsSystem32inetsrvconfig :
Change:
<globalModules>
…
<add name=»SharePoint14Module» image=»C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14isapiowssvr.dll» preCondition=»appPoolName=SharePoint Central Administration v4″ />
</globalModules>
To:
<add name=»SharePoint14Module» image=»C:Program FilesCommon FilesMicrosoft
SharedWeb Server Extensions14isapiowssvr.dll» preCondition=»appPoolName=SharePoint Central Administration v4,bitness64» />

Hope this helps you resolve your issue

Reference:
http://blogs.msdn.com/b/govindr/archive/2007/08/30/503-server-unavailable-failure-with-iis-7-0.aspx

Источник

This SharePoint 2013/2016 tutorial explains, how to resolve http error 503. the service is unavailable which comes in SharePoint 2013/2016. I got the “http error 503. the service is unavailable. SharePoint” error while opening SharePoint 2013/2016 Central Administration.

Recently some windows and SharePoint 2013 updates happened on my laptop. After that when I restart my laptop and try to open the SharePoint 2013 Central Administration, I got the below error:

HTTP Error 503. The service is unavailable.

http error 503. the service is unavailable. sharepoint

If you are getting http error 503. the service is unavailable error while openinSharePointnt 2013/2016 central administration, then you can check below things.

If you have changed your account password which you are using in SharePoint 2013/2016, then you may get this error.
Next thing is you can check whether some services like SharePoint Administration, SQL Server (MSSQLSERVER) are running or not. Go running and writing services.msc and click on OK. This will open the services screen. There you can check whether SharePoint Administration, SQL Server (MSSQLSERVER) are running or not. If those are not running then you can right-click on the particular service and click on Start.
But the problem I found in my case is that the SharePoint Central Administration Application Pool has been stopped like below:

http error 503. the service is unavailable. sharepoint 2013 central administration

To start go to Run -> inetmgr. This will open the IIS. There click on Application Pools from the left side. This will open all the application pools. Select the application pool, Right Click -> Start.

Once the application pool is in running mode, you should be able to Open SharePoint 2013/2016 central administration. The error http error 503. the service is unavailable should not come while opening SharePoint 2013 central administration or SharePoint 2016 central administration.

HTTP Error 503. The service is unavailable in SharePoint 2010

Now we will see the solution for the SharePoint error message “HTTP Error 503. The service is unavailable in SharePoint”. This error comes in my case when I changed the account password which I used to login to the central administration.

I will personally recommend you to do two things if you got the above error.

Solution-1
STSADM command-line tool provides a good command to update farm credentials. To use this:

Open command prompt in Administrator mode (Go to Start type cmd and then right click on cmd and click Run as Administrator).

Then in the command prompt navigate to Program FilesCommon FilesMicrosoft Sharedweb server extensions14BIN (for SharePoint 2010).

Then run the below command:

stsadm.exe -o updatefarmcredentials -userlogin <Domainusername> -password <give new password>

It will give a successful message.

After that do an IISRESET.

Now try opening your central administration, it should work now.

If the above solution did not work then you can try Solution-2 below:

Solution-2:
Go to Start -> All Programs -> Administrative Tools -> Internet Information Services (IIS) Manager.

Then Click on(+) the server name -> Application Pools then locate your application pools. Right click on the Application pool name go to Advance settings -> Go to process model then Identity Click on the Identity ->Set and then give the user name, password and confirm password.

Event ID: Application pool ‘SharePoint Central Administration v4’ is being automatically disabled due to a series of failures

Let us see how to resolve an error that comes from SharePoint 2013 central administration.

Below is the full error message:

HTTP Error 503 – Service is Unavailable

Error Message :
“Application pool ‘SharePoint Central Administration v4’ is being automatically disabled due to a series of failures in the process(es) serving that application pool.”

“The Module DLL ‘C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15isapiowssvr.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for an x86 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.”

Goto IIS manager ->Application Pool,

click ‘SharePoint Central Administration v4’

Right-click Advanced settings, and set “Enable 32-bit applications” to “False”

Hopefully one of the solutions will work for you.

You may like the following SharePoint 2013 tutorials:

SharePoint web application
Your changes could not be saved because this SharePoint web site has exceeded the storage quota limit
How to create custom webpart in SharePoint 2013 step by step
How to install and configure Active directory windows server 2012 r2
The following feature couldn’t be installed .net framework 3.5
Installation of one or more roles role services or features failed windows 2016
SharePoint Designer Workflow 2013 Error: Windows Workflow Foundation, part of .Net Framework 3.0, must be installed to use this feature
SharePoint 2016 installation errors

After working for more than 15 years in Microsoft technologies like SharePoint, Office 365, and Power Platform (Power Apps, Power Automate, and Power BI), I thought will share my SharePoint expertise knowledge with the world. Out audiences are from the United States, Canada, United Kingdom, Australia, New Zealand, etc. For my expertise knowledge and SharePoint tutorials, Microsoft has been awarded a SharePoint MVP(8 times), check out My MVP Profile. I have also worked in companies like HP, TCS, KPIT, etc.

Источник

When I open Central Administration I get this error

HTTP Error 503. The service is unavailable.

Same error also when I open my SharePoint Server 2010 site

HTTP Error 503. The service is unavailable

How to resolve this?

asked Feb 20, 2015 at 7:59

When you run into the issue “HTTP Error 503, the service is unavailable” when you launch the website through IIS (Internet Information Services), you will end up seeing the following message:

To remediate the issue, you will need to open IIS Manager (inetmgr.exe). This error is caused because specific website Application Pools were stopped or disabled by a certain circumstance. You will need to select the Application Pool, for the affected Web Applications, and hit Start. Once completed, please revisit your web application.

Note: If the application pool continues to stop, please verify that all SharePoint services are started, this error might occur because of changing the service account password. You may need to change the new password for the application pool or sharepoint timer service.

[ Source ]

answered Apr 29, 2015 at 2:02

Please, ensure, that the IIS application pools that belong to these SharePoint web applications are up and running. If they are running, you can try to restart them.

Often it happens as you install a new solution into the SharePoint farm. Most of the time this issue is only temporary (1-2 Minutues), but can be quite frustrating.

See this post as reference.

answered Feb 20, 2015 at 8:21

pholparpholpar

3,1821 gold badge13 silver badges14 bronze badges

answered Dec 6, 2016 at 18:30

Raghu ArigaRaghu Ariga

2402 silver badges8 bronze badges

Click the stopped application pool -> click advanced settings ->Identity ->click the user to retype the user ->Application Pool Identity dialog ->click set -> manually type the user name and password. Then restart the server.

answered Jul 17, 2017 at 14:47

Источник

This article features error number Code 503, commonly known as Microsoft Sharepoint Http Error 503. The Service Is Unavailable described as Error 503: Microsoft Sharepoint has encountered a problem and needs to close. We are sorry for the inconvenience.

About Runtime Code 503

Runtime Code 503 happens when Microsoft Sharepoint fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.

Definitions (Beta)

Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!

Http — Hypertext Transfer Protocol HTTP is an application level network protocol that is used for the transfer of content on the World Wide Web.
Http error — An error code as a result of an HTTP request.
Service — A Service is a long-running executable that performs specific functions and which is designed not to require user intervention.
Sharepoint — For SharePoint-specific questions, please see the SharePoint Stack Exchange https:sharepoint.stackexchange.com site

Symptoms of Code 503 — Microsoft Sharepoint Http Error 503. The Service Is Unavailable

Runtime errors happen without warning. The error message can come up the screen anytime Microsoft Sharepoint is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(For illustrative purposes only)

Causes of Microsoft Sharepoint Http Error 503. The Service Is Unavailable — Code 503

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.

Method 1 — Close Conflicting Programs

When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.

Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
You will need to observe if the error message will reoccur each time you stop a process.
Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.

Method 2 — Update / Reinstall Conflicting Programs

Using Control Panel

For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
Once inside Programs and Features, click the problem program and click Update or Uninstall.
If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.

Using Other Methods

For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
For Windows 10, you may click Start, then Settings, then choose Apps.
Scroll down to see the list of Apps and features installed in your computer.
Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.

Method 3 — Update your Virus protection program or download and install the latest Windows Update

Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.

Method 4 — Re-install Runtime Libraries

You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.

Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
Click Uninstall on top of the list, and when it is done, reboot your computer.
Download the latest redistributable package from Microsoft then install it.

Method 5 — Run Disk Cleanup

You might also be experiencing runtime error because of a very low free space on your computer.

You should consider backing up your files and freeing up space on your hard drive
You can also clear your cache and reboot your computer
You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
Click Properties and then click Disk Cleanup

Method 6 — Reinstall Your Graphics Driver

If the error is related to a bad graphics driver, then you may do the following:

Open your Device Manager, locate the graphics driver
Right click the video card driver then click uninstall, then restart your computer

Method 7 — IE related Runtime Error

If the error you are getting is related to the Internet Explorer, you may do the following:

Reset your browser.

For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.

Disable script debugging and error notifications.

On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
Put a check mark on the radio button
At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.

If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.

Other languages:

Wie beheben Fehler 503 (Microsoft Sharepoint Http-Fehler 503. Der Dienst ist nicht verfügbar) — Fehler 503: Microsoft Sharepoint hat ein Problem festgestellt und muss geschlossen werden. Wir entschuldigen uns für die Unannehmlichkeiten.
Come fissare Errore 503 (Errore 503 HTTP di Microsoft Sharepoint. Il servizio non è disponibile) — Errore 503: Microsoft Sharepoint ha riscontrato un problema e deve essere chiuso. Ci scusiamo per l’inconveniente.
Hoe maak je Fout 503 (Microsoft Sharepoint Http-fout 503. De service is niet beschikbaar) — Fout 503: Microsoft Sharepoint heeft een probleem ondervonden en moet worden afgesloten. Excuses voor het ongemak.
Comment réparer Erreur 503 (Erreur Microsoft Sharepoint Http 503. Le service n’est pas disponible) — Erreur 503 : Microsoft Sharepoint a rencontré un problème et doit fermer. Nous sommes désolés du dérangement.
어떻게 고치는 지 오류 503 (Microsoft Sharepoint Http 오류 503. 서비스를 사용할 수 없습니다.) — 오류 503: Microsoft Sharepoint에 문제가 발생해 닫아야 합니다. 불편을 드려 죄송합니다.
Como corrigir o Erro 503 (Erro 503 de HTTP do Microsoft Sharepoint. O serviço não está disponível) — Erro 503: O Microsoft Sharepoint encontrou um problema e precisa fechar. Lamentamos o inconveniente.
Hur man åtgärdar Fel 503 (Microsoft Sharepoint Http-fel 503. Tjänsten är inte tillgänglig) — Fel 503: Microsoft Sharepoint har stött på ett problem och måste avslutas. Vi är ledsna för besväret.
Как исправить Ошибка 503 (Ошибка HTTP 503 Microsoft Sharepoint. Служба недоступна) — Ошибка 503: Возникла ошибка в приложении Microsoft Sharepoint. Приложение будет закрыто. Приносим свои извинения за неудобства.
Jak naprawić Błąd 503 (Microsoft Sharepoint Http Error 503. Usługa jest niedostępna) — Błąd 503: Microsoft Sharepoint napotkał problem i musi zostać zamknięty. Przepraszamy za niedogodności.
Cómo arreglar Error 503 (Error 503 de Http de Microsoft Sharepoint. El servicio no está disponible) — Error 503: Microsoft Sharepoint ha detectado un problema y debe cerrarse. Lamentamos las molestias.

About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.

Follow Us:

Recommended Repair Tool:

This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.

STEP 1:

Click Here to Download and install the Windows repair tool.

STEP 2:

Click on Start Scan and let it analyze your device.

STEP 3:

Click on Repair All to fix all of the issues it detected.

DOWNLOAD NOW

Compatibility

Requirements

1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.

Article ID: ACX08007EN

Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000

Speed Up Tip #77

Creating Multiple Folders for your Files:

Managing your files can be done efficiently by creating multiple folders. A large number of files stored in a single folder can significantly affect the performance of the Explorer. So, it is best to spread them out in different folders.

Click Here for another way to speed up your Windows PC

Источник

KBID

EXP-INC-00003

Title

HTTP Error 503. Service Unavailable

Introduction

When you are working with SharePoint 2010 or SharePoint 2013 environments you probably have seen the HTTP Error 503. Service Unavailable error at some point. This error can have several causes, when you use your favourite search engine you can find a lot of articles on this subject.

Some common causes can be:

a disabled application pool
an invalid identity for a application pool because of an expired password.

This article describes how I ran into an issue with a group policy that caused a HTTP Error 503.

Symptoms

When you navigate to a SharePoint 2010 site you get an error:
HTTP Error 503. Service Unavailable

Steps to Reproduce

1. Navigate to your SharePoint 2010 site

Cause

In my case this error was caused by a removal of Log on as a batch permissions of the Application Pool account on one of the Application servers in a SharePoint 2010 farm. The application pool account of your web application needs this permission on the server where it is running, you can also check out Corey Roth his blogpost on this topic, Corey’s Guide to SharePoint Service Accounts.

When navigating to the System Log on one of the servers in the SharePoint 2010 farm I saw an event of the Windows Process Activation Service (WAS) source with ID 5021:
The identity of application pool ‘yourapplicationpoolname’ is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

After finding the 5021 event I wanted to check what my Application Pool Identity was. You can check what the identity of your application pool is via the Application Pools view in Internet Information Service (IIS) Manager.

When you established what your Application Pool identity is you can open the Local Security Policy Editor on the same server. You can also use run and type secpol.msc to fire it up. Check what the Security Setting is for the Log on as a batch job policy.

In my case a custom policy was set which had overwritten the default settings. The result was that the Log on as batch job permissions of the application pool Identity were removed.

Applies to

SharePoint 2010, SharePoint 2013

Workaround

Not Applicable

Solution

Add the Application Pool Identity account the Log on as a batch job group policy or give the account permissions via a local policy on the server if you are not using group policies.

References

Dot Net Mafia – Corey’s Guide to SharePoint Service Accounts
Technet – Account permissions and security settings in SharePoint 2013
Technet – Event ID 5021

Источник