Web service communications error(31): There was no endpoint listening at https://discover.gimmal.cloud/saigws
Issue:
Connectors try to contact the hub, but this connection fails. Symptoms for this may include any of the following (this list is not intended to be definitive or exhaustive):
Policies do not run at the scheduled time
User is unable to login to the Gimmal Console
Hub site is inaccessible
This error message below is found in the connector log file and means that the connector service was unable to communicate with the hub. This log is usually located at C:\$Sherpa Software\Altitude\Connector\Logs but may be different in your specific installation.
[08:02:03.6 Feb-16] ERROR: Web service communications error(31): There was no endpoint listening at https://discover.gimmal.cloud/saigws.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Occasional communication failures typically do not indicate a serious issue. As seen below the next attempt at 8:03:03.8, was successful.
[08:03:03.3 Feb-16] Starting web service communication session, hub comms thread - doStartWsSession.
[08:03:03.5 Feb-16] DEBUG: ** Secure Connection Made ** (Token: xxxxxx65-024b-44d3-9e74-b49e94921877)
[08:03:03.5 Feb-16] DEBUG: Sending status to the hub...
[08:03:03.7 Feb-16] DEBUG: Attempting to reconnect to the web service(1).
[08:03:03.7 Feb-16] Starting web service communication session, app - StopService.
[08:03:03.8 Feb-16] DEBUG: ** Secure Connection Made ** (Token: xxxxxxx8e-ed88-48e8-8246-f4212e72a982)
[08:03:04.0 Feb-16] DEBUG: Collecting owner searches from the hub...
[08:03:04.1 Feb-16] DEBUG: 1 owner searches found.
Resolution:
If this error occurs only occasionally and quickly ends within a minute or two, there is likely no issue.
However, if you see this error repeatedly for longer than 5 minutes, it could indicate that the server's firewall rules are blocking access to the hub address listed in the error. Please ensure that the server is able to access the hub at: https://discover.gimmal.cloud/.
If the server CAN reach these domains and it still can't communicate with the hub, please contact Gimmal Support.