Resolving the HTTP 500 error issue on clustered servers

Resolving the HTTP 500 error issue on clustered servers

Resolving the HTTP 500 Issue

When connecting to a clustered server, if you are able to search for studies, receive query results and thumbnails, and the Imageviewer displays an empty screen or an HTTP 500 error.

To sovle the issue, follow the procedure below.

  1. Check the hostnames and URLs of the clustered servers for Fully-Qualified-Domain-Name (FQDN) Depth (For example, server.domain.com). The depth must be the same across all clustered servers, for example:

    • server1.domain.com

    • server2.domain.com

      If depth is different (refer to the example below) clustering does not function, and an HTTP 500 error displays. To conform to HTTP Domain Cookie standards, the FQDN Depth must be the same.

    • server1.domain.com

    • server2.subdomain.domain.com

  2. Take the steps necessary to correct the FQDN depth on your clustered servers.

  • server1.domain.com

  • server2.domain.com

    If depth is different (refer to the example below) clustering does not function, and an HTTP 500 error displays. To conform to HTTP Domain Cookie standards, the FQDN Depth must be the same.

  • If depth is different (refer to the example below) clustering does not function, and an HTTP 500 error displays. To conform to HTTP Domain Cookie standards, the FQDN Depth must be the same.

  • server1.domain.com

  • server2.subdomain.domain.com

  • Tables can't be imported directly. Please insert an image of your table which can be found here.