Skip to main content

An error occurred. Unable to load Desktop.json.js status: 500

Comments

11 comments

  • Permanently deleted user
    Are all the map service in your site working correctly? (This is one of the main causes for that kind of error)

     

    Do you have any custom activity that might be invalid because of an error or deployment.

     

    Every time that you make a change to the viewer in Geocortex Essential Manager desktop.json.js is updated.

     

    I hope this helps
    0
  • Permanently deleted user
    I have three users in my deployment that are getting this error.  200+ are not. Any ideas why al of a sudden 3, not all of my users are getting this error?
    0
  • Leon Bowers
    Was there ever a solution to this? I have the same issue.
    0
  • Permanently deleted user
    Hi Leon,

     

    As Francesca mentioned, you can check to see if all your map services are running.  If you don't see any issues there, you can check your Windows Event viewer on the server, or your REST logs which are located here:

     

    C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\App_Data\Logs

     

    If all else fails, please open a support case, so we can assist you directly!

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    Hi Francesca,

     

     

     

    Could you please elaborate a bit more on this:

     

     

     

    “Every time that you make a change to the viewer in Geocortex Essential Manager desktop.json.js is updated.”

     

     

     

    I assume that when changing anything via the Manager, all should stay ok. Am I correct? We hope to reach a degree to avoid touching the geocortex files for whatever reason and all can be managed and sorted out by the manager.

     

     
    0
  • Permanently deleted user
    Hi Jamal,

     

    From your first post it was not clear if you had recently made changes to your viewer: just the fact that you didn’t change it “manually”.

     

    My comment was just to underline that Desktop.json.js is re-saved every time that you apply a change to the viewer using Essential Manager. It was a pointer to compare that file with previous version or run a json validation check to see if accidentally a change (manual from a colleague or using manager with a new setting / plug in) was applied that could have break json syntax …

     

    I hope this clarifies my previous comment

     

    Thank you
    0
  • Permanently deleted user
    Thank you Francesca.

     

     

     

    We got this message even in case some changes are applied with the manager with no edits are performed on the desktop.json.js. this looks for us a bit weird.

     

     
    0
  • Permanently deleted user
    Then this is a good pointer to problem with map services: I would suggest to monitor map services to ensure that they are not intermittent. We had a similar problem with an external map service and we ended up caching it ... no problems since then ...
    0
  • Permanently deleted user
    I experienced this issue as well. Another symptom was that the site was not showing up on Essentials Manager. It was because I initially made a backup of a map folder (site.xml) within the site folder. Essentials Manager sees two copies of the same named xml file and get confused.
    0
  • Permanently deleted user
     

     

    Geocortex is very sensitive when it comes to broken or unhealthy services. I have pointed this idea several times and wanted to say that Geocortex Manager (GM) and Geocortex Viewer (GV) should start anyway while indicating services with issues with exclamation mark. This is the only way out for this challenge. Hope that Geocortex developers can hear us.

     

     
    0
  • Permanently deleted user
    In our case the solution to implement the solution from https://support.geocortex.com/customer/essentialsGSCForumDetail?id=0D5f200006mCc6kCAC&main-nav=essentials&sub-nav=forum (IIS "CorsModule" conflict with GeoCortex Cors Module), though but uninstalling the IIS CORS Module ...
    0

Please sign in to leave a comment.