Skip to main content

Dispatch Console not connecting in Alliance V15.  To troubleshoot, try the following:

  1.  Go to the Settings on the server and be sure that the Astea DSE Service is Running.  You can try to stop and then start the DSE Service to see it this works.
  2. Open Configuration Editor (Start > Programs > AsteaAlliance15.0 > Configuration Tools > Configuration Editor). The Configuration Editor main screen is displayed.
  3. In the sections pane, select GENERAL > DSE.
  4. In Sections Properties pane, under Allowed External Access, CommunicationWebServerURL, be sure that http:// precedes the IP address (as shown below) and then click Save URL
  5. Go back to the application, log out and back in, and try to reload the Dispatch Console.  The session should now connect.

NOTE:  Prior to Alliance Version 15.0, the DSE Server IP address was found on Dispatch Console Session, Main page, under Main Info.

What I have found in earlier versions of the application,  for example, V11.5, is that when the DC does not connect (icon is red as opposed to green), just restarting the DSE Service generally does not resolve the issue. In these instances, a full IISRESET is required.

In addition, if the cache service is down for any reason, the Dispatch Console may become disconnected as the DSE Service has a dependency on the Cache service.  It’s also recommended to check the cache sections in both the Configuration Editor and ServiceBus Web.Config to ensure the IP addresses for the cache servers are populated correctly as well as checking the Windows Event log to make sure that there aren’t any cache failures.

Reply


Terms & ConditionsCookie settings