SharePoint is a popular content and document management system with a multitasking set of web based technologies. Despite great performance, users sometimes encounter problems while performing specific tasks, such as Error 503 while trying to get access to the content on server that runs IIS 7.0 using HTTP. Here, you see a numeric code returned by IIS (Internet Information Services) 7.0; the code shows the response status and is recorded in IIS log. You may also see the status code in client browser.
With the status code, it is easy to find out whether the request is successful or not, along with the reason if request goes unsuccessful. You may see the following two HTTP status codes that associate the specific reason of the problem.
- 503.0 – The code indicates that the application pool is not available.
- 503.2 – It indicates that the limit of concurrent request has been exceeded.
It means that the requested limit value (0 by default) caused the application pool error. The default value 0 simply means that an indefinite number of requests can be processed by the application pool. You can understand the scenario by the following:
The application pool is stopped, which results in WAS (Windows Process Activation Service) to shut down all the worker processes that are running to serve that application pool. Once the worker processes are shut down, WAS does not restart them, rather an administrator has to restart the processes and hence, the applications associated to stopped application pool encounter 503 Service Unavailable errors.
Resolution
Since it is frightening to face annoying issues that just restrict you to continue the task you are supposed to perform, you need to resolve the problem at the earliest. In order to fix the issue, you need to isolate application pool or consider using separate service accounts.
Note that when a single account is used for all service accounts, and if this account is under policy and you change the password forcibly, SharePoint application pool and services are affected. As a result, the Error 503 or ‘Can’t connect configuration database’ crops up. Besides, when you lose password, the security will be at risk.
Moreover, if you are not able to restart application pool, it is good to check if the permissions have not changed by right clicking the Advanced Settings. I f the password has been changed, you can update it by selecting the user identity, and then using the ‘Set’ button.
Other than the above-mentioned issue and its resolution, there are specific things that an inexperienced administrator needs to implement in SharePoint as follows:
- Sp_install: The account facilitates the installation of SharePoint.
- Sp_apppool: This account is helpful when problems occur with Application pool that is a worker processor, processing web services for SharePoint. If application pool is changed, web application crashes, and then you face errors while logging into Central administrator.
- Sp_farm: This is a farm account and can be used for Timer Service. However, it is good to use a separate account for Timer service.
- Sp_timeservice: You can use this account for SharePoint Timer Service, if SharePoint is working great. In this case, you need to find Service and check the account that is using SharePoint Timer Service.
- Sp_userprofile: The Sp_userprofile is used for User Profile service, if you want to synchronize SharePoint with AD. However, make sure that you are using this account carefully, as it may create issues if you are not attentive enough.
This is all you can do to get rid of the SharePoint Error 503 along with the recommendations to avoid the issues you may come across.