Why does AgilePoint Server Shut Down Periodically, even though AgilePoint Server Monitor is Running?

Prerequisites

Symptoms

AgilePoint server shuts down after a certain period of time, even though the AgilePoint Server Monitor is running.

Cause

The AgilePoint Server port number in the registry does not match the AgilePoint Server binding in IIS. This occurs when more than one binding is declared in IIS for the AgilePoint Server website.

The port number for the AgilePoint Server is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Ascentn\Server\port. When AgilePoint Server starts, it loops through the list of IIS bindings for the AgilePoint Server web site, attempting to match the port number in the registry. The loop stops at the first match it finds in the list. If the first match in the IIS binding list is not associated with the AgilePoint Server web site, AgilePoint Server does not start.

Resolution

AgilePoint recommends one of the following resolutions:

  • Make sure you are using a dedicated, unique port number for AgilePoint Server.
  • Set the Idle Timeout to zero (0) so that AgilePoint Server does not shut down.