Skip to main content

Comments

5 comments

Date Votes
  • Permanently deleted user
    Hi Ethan,

     

    Can you please try restarting the Geocortex Core service on the hub server, and see if that helps?  You might also want to check and see if all the roles are running (in the process list in the task manager).  There should be about 20, but if there are only 3 or 4, there may be an issue with Core.

     

    I hope this helps!

     

    Thanks,

     

    Danny
    0
  • Ethan Granger
    Restarting the Core worked. I rebooted the server twice last week, but it didn't work. Wouldn't restarting the machine have restarted the Core?
    0
  • Permanently deleted user
    Hi Ethan,

     

    Sometimes (depending on the specs of the server, and what else is running on it), Core will not start properly on a reboot, as other services are starting, and the resources needed to start Core are not available.  I'm not sure that is what happened here, it's just a guess.  

     

    One thing you can do to prevent this in the future, assuming that is the culprit, is to set the Geocortex Core service to "Automatic (Delayed Start)".  I've seen this solve the issue for a few customers in the past.  

     

    I hope this helps!

     

    Thanks,

     

    Danny
    0
  • Ethan Granger

    I've got a brand new install of Analytics and I'm still getting this error. I've tried restarting the core and rebooting with no luck. Please help.

    0
  • Gareth Evans

    Hey Ethan Granger have a look in C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs at DocumentStore.log & <clustername>.log - there should be relevant errors there. My suspicion is you've got corrupt indices somehow, though I'm not sure how that would occur with a fresh install. 

    If you can't make any sense of it, please email us to get a support case going. 

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post