Skip to main content

Comments

8 comments

  • Official comment
    Gareth Evans

    Hi Ethan Granger! We have some docs around this: Analytics Administrator - Troubleshooting Scenarios (vertigisstudio.com) - the two topmost items are the most frequent cuplrits:

    • Verify that the Viewer’s proxy settings are correctly configured to allow outgoing requests to the Essential server. You set the proxy configuration in C:\inetpub\wwwroot\Html5ViewerDirectory\proxy.config. Ensure that you add a specific exception for the client relay URL. For more information, see Configure Access to Essentials Viewers.

    • Verify that the Essentials site URL detected by Analytics is the same URL as that configured to be used by the Viewer.

      • To verify the detected URL, open Configuration in Analytics, and select the Essentials instance.

      • Select the URL Substitution tab.

      • Compare the detected Essentials URL with the public URL used for the Essentials instance.

      • If the two URLs are different, or if the Essentials instance is accessed using multiple different URLs, then to add multiple URLs, click Add below the Alternate Instance URLs and paste in each alternate URL.

  • Ethan Granger

    I've added https://fileserver01.landadvisors.aws.cloud/Geocortex/Analytics/ClientRelay to my proxy.config and the url substitution is not needed. Where should the relay be running?

    0
  • Ethan Granger

    I think these two items might be issues:

    • In Windows Task Manager, check that the Geocortex Analytics Client Relay Role is running. If the role is not running, follow the steps in Check that a Role is Running.

    • Check to see if the URL for the viewer is publicly accessible. If the URL for your viewer is publicly accessible, then the Client Relay URL must also be publicly accessible.

    I can't find the role running on either the essentials machine or the analytics machine. We are running analytics on a LAN, so its not "publicly" accessible, but should still be accessible on the LAN. To confirm, are we just talking communication between Analytics, Essentials, and AGS? If so, what ports?

    0
  • Ethan Granger

    I'm seeing data now, it was either adding that client relay url or changing the AGS logs to verbose. Either way, it's working.

    Follow up questions though, services are responding pretty quickly, like sub 1 second, but starting an app seems to take much longer to load the service, like 8-10 seconds. Any thoughts as to why that might be?

    0
  • Ethan Granger

    Correction, i'm still not getting Essentials App Trends. I guess that was server trends that are now coming through.

    0
  • Ethan Granger

    it looks like Analytics reported data from 5/1 to 5/8 and then stopped. How do I get it going again (and keep it going?)

    0
  • Ethan Granger

    it looks like the Geocortex Core stopped running on our AGS box and after I restarted it, the data appeared. 

    0
  • Gareth Evans

    Hi Ethan Granger good catch. Yes, if the Core service were stopped on an Agent server that would mean it would stop reporting to Analytics. You should also see Server Unresponsive alarms from that resource.

    0

Please sign in to leave a comment.