Skip to main content

How to Troubleshoot an IIS 503 Service Unavailable Error

An IIS 503 Service Unavailable error indicates that the web server is currently unable to handle the request. This typically occurs because the specific Application Pool hosting the website has stopped or crashed.

An IIS 503 Service Unavailable error indicates that the web server is currently unable to handle the request. This typically occurs because the specific Application Pool hosting the website has stopped or crashed.

Note: This issue is specific to the Internet Information Services (IIS) web server on a Windows Server environment.

Before you begin

You will need:

  • Administrator access to the Windows Server.

  • Access to the Internet Information Services (IIS) Manager console.

Check the Application Pool status

The most common cause of a 503 error is a stopped Application Pool.

  1. Open the Internet Information Services (IIS) Manager.

  2. In the Connections pane, expand the server node and select Application Pools.

  3. Locate the Application Pool associated with the affected website.

  4. Check the Status column. If the status is Stopped, right-click the Application Pool and select Start.

  5. Refresh the website in a browser.

Verify Application Pool identity and permissions

If the Application Pool starts but stops again shortly after, it may be failing due to an invalid identity or insufficient permissions.

  1. In IIS Manager, select the problematic Application Pool under Application Pools.

  2. Right-click the pool and select Advanced Settings.

  3. Locate the Identity property. Ensure the account specified has the necessary permissions to run the application.

  4. If the identity is a specific domain account, verify that the password has not expired and the account is not locked.

  5. Click OK to save the changes.

Check for configuration errors in web.config

A malformed web.config file can cause the Application Pool to crash immediately upon attempting to load the site.

  1. Navigate to the website's root directory on the server.

  2. Open the web.config file in a text editor.

  3. Check for any recent changes or syntax errors, such as unclosed tags or incorrect attributes.

  4. If you recently added a new module or feature, ensure the corresponding IIS components are installed.

Examine Windows System and IIS Logs

If the Application Pool continues to stop, you must examine the system logs to identify the specific error code.

  1. Open the Event Viewer from the Start menu.

  2. Navigate to Windows Logs > System.

  3. Look for errors sourced from WAS (Windows Process Activation Service) or IIS-__ during the time the 503 error occurred.

  4. Check Windows Logs > Application for errors related to the specific application or .NET runtime.

  5. Review the IIS Access Logs (typically located in C:\inetpub\logs\LogFiles\W3SVC1\) to see if the request reached the server before the 503 error was generated.

Contact Hostek support

If the Application Pool remains in a "Stopped" state after a manual start attempt, or if the Event Viewer shows a "Rapid Fail Protection" error, contact Hostek support. Provide the following information:

  • The specific website and IP address.

  • The exact time the 503 error began.

  • The specific error codes found in the Event Viewer (System and Application logs).

Did this answer your question?