GFI LanGuard's Central Management Server (CMS) runs using Microsoft Internet Information Services (IIS), making it prone to common http errors when hosting the website. It is common for a 503 error to appear. It is usually returned while attempting to open the console or while configuring the synchronization. The CMS returns a 503 server error, as shown below:
The remote server returned an error: (503) Server Unavailable.
This article demonstrates how to diagnose a 503 error along with the possible solutions.
The Windows event log generally provides more information on why the Application Pool may not be able to start. To diagnose a server error, follow these steps:
- Navigate to Start > Run.
eventvwr.mscin the textbox.
- Expand the Windows Logs > Application.
- Locate the time frame of the attempted website or application pool start by launching IIS and attempting to start the application pool to receive a new copy of the error at the current time.
- Review the reported error and adjust accordingly.
While the LanGuard Central Management Server uses Microsoft IIS to run, we do not support troubleshooting IIS errors directly.
Depending on the error found in the event logs, there are many possible resolutions. The most common problem, along with its possible resolution, is outlined below.
|503.0||Service or Server unavailable.||
The request is sent to an application pool that is currently stopped or that is currently disabled.
To resolve this issue, make sure that the destination application pool is started. The event log may give information about why the application pool is stopped or disabled.
This 503 error can occur due to conflicts among websites already running in IIS, such as conflicting bindings, or the application pool credentials used are expired or no longer valid. Once the IIS error preventing the application pool has been resolved, perform the steps below:
- Restart the GFI LanGuard Services.
- Attempt console access/synchronization again.