Ignite Global Support Home
How can we help?
  1. FogBugz Support
  2. Fogbugz
  3. FogBugz On-Premises
  4. Install, Upgrade, Migrate

Troubleshooting an HTTP 503 Error After Restarting Your FogBugz On-Premise Server or its Application Pool


Abraham Hardjana
  • Updated
Follow

Overview

After restarting the server (or the FogBugz Application Pool) you are getting an HTTP 503 Service Unavailable error when trying to access your FogBugz On-Premise server.

Workflow

code2flow_VNu0X2.png

Instructions

Check that the FogBugz Application Pool is Started.

In the Internet Information Services (IIS) Manager, check that the FogBugz Application Pool has a status of Started.  If the FogBugz Application Pool has not started it could result in the HTTP 503 Service Unavailable error when attempting to access FogBugz.

 

Restart the FogBugz Application Pool

In the Internet Information Services (IIS) Manager, if the FogBugz Application Pool has a status of Stopped, you will need to start the pool to see if that will resolve the HTTP 503 Service Unavailable error when attempting to access FogBugz.

 

Check the Windows Event Viewer's Windows System Logs

If your FogBugz Application Pool was not able to start, please check the Windows System Logs using the Event Viewer to see if there are any warnings or errors associated with the FogBugz Application Pool on your FogBugz On-Premise server.

 

Check the FogBugz Application Pool's Identity User for the Required Rights and the Correct Password

If there is an error like the following in the Windows System Logs:

The identity of application pool <name of your FogBugz application pool> is invalid. The user name or password that is specified for the identity may be incorrect or the user may not have batch login right.  If the identity is not corrected, the application pool will be disabled when the application pool received its first request.

This indicates one of the following issues with the identity used for the FogBugz Application Pool:

Re-enter the user's password in IIS for the given Application Pool and verify it has assigned the required rights.

 

Use the default ApplicationPoolIdentity for your FogBugz Application Pool

If you are not allowed to assign the required rights for the user used for the FogBugz Application Pool's Identity (eg: AD domain policies prevent you to set "Log on as a batch job" for a local Administrator user) use the default ApplicationPoolIdentity (available on IIS starting from Windows Server 2008 SP2).

If using the default ApplicationPooldentity does not solve your issue, or this solution is not applicable for you (using an older IIS version), you will need to request from your Network or Domain Administrator a user with the required rights and set the given user for your Application Pool's Identity.

Open a Support Ticket

Open a FogBugz Support Ticket with details about the issue you are encountering with an HTTP 503 Error with your FogBugz On-Premise server and please provide the following details:

  • FogBugz logs as per our Logging in FogBugz On-Premises article. (if they aren't already enabled, turn them on, create the error again then share with us the logs).
  • IIS logs
  • Windows event log errors for your Application Pool