Save project error

Permanently deleted user

30. August 2016 22:53

When trying to save a project, I got a project error "The project could not be saved. Refer to the log for more details".

 

The log file says

 

The document store failed to handle an operation:

 

Geocortex.Platform.Role.Documents.ServiceRequestFailedException: [io failed] There was a problem interacting with the underlying data store. ---> System.AggregateException: One or more errors occurred. ---> System.InvalidCastException: Cannot cast Newtonsoft.Json.Linq.JObject to Newtonsoft.Json.Linq.JToken.

 

   at Newtonsoft.Json.Linq.Extensions.Convert[T,U](T token)

 

   at Newtonsoft.Json.Linq.JToken.Value[T](Object key)

 

   at Geocortex.Platform.Role.Documents.Support.DocumentStoreMultiplexer.IsError(JObject response, Host host)

 

   at Geocortex.Platform.Role.Documents.Support.DocumentStoreMultiplexer.<UpgradeCoreAsync>d__2.MoveNext()

 

--- End of stack trace from previous location where exception was thrown ---

 

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

 

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

 

   at Geocortex.Platform.Role.Documents.Support.DocumentStoreMultiplexer.<PrepareCoreAsync>d__3.MoveNext()

 

...

 

I'm not sure why it happened.

 

Any help would be greatly appreciated.

 

 

0

• 

  Permanently deleted user

  30. August 2016 22:57

  Hi Yunsic,

   

  I'm sorry to say that this is a bug in Core 3.0.1, which shipped with Essentials 4.6.  We've fixed it in Core 3.0.2, but we're waiting to see if there is a workaround that can be applied now.  I'll post an update to this post as soon as I hear something from the development team.

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  31. August 2016 17:49

  Hey Danny,

   

  When you are able to find a workaround, can you update the Knowldge Base article Essentials 2.6 Known Issues? By doing that it allows other users to see and accommodate these issues before running into them themselves and having to track down this post.

   

  That being said, I do not know Latitude's protocol for adding issuess/solutions to that article.

   

  Thanks!

  0
• 

  Permanently deleted user

  31. August 2016 19:39

  Count me as encoutnering the same bug with 4.6/ GVH 2.7

  0
• 

  Permanently deleted user

  31. August 2016 23:07

  Sure thing Ian!  I've published the Known issues KBA here's the link:

   

  https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&feedtype=SINGLE_ARTICLE_DETAIL&criteria=BESTANSWERS&id=kA360000000GqpLCAS

   

  I'll add a workaround if we find one.  

   

  In the meantime, I'll add you and Allen as stakeholders on this issue.

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  2. September 2016 14:59

  Thanks Danny -

   

  Looking at that link, it seems that we are having a slightly different issue.  The save buttons are available, and we can proceed with saving a map, but it fails after trying to save for a minute or so.  Not many clues in the developer tools other than a 'Timeout exceeded' message.

  0
• 

  Permanently deleted user

  2. September 2016 16:05

  Just an extra note after a bit more testing - dev tools show a 'problem interacting with the underlying data store' error. 

  0
• 

  Permanently deleted user

  2. September 2016 16:57

  Hi Allen,

   

  That "problem interacting with the underlying data store" message is another symptom of this bug, but that being said, if you'd like us to hop on a screen share with you to verify that on your server, please open a case and reference this thread, and we are happy to do so!

   

  Thanks,

   

  Danny

  0
• 

  Permanently deleted user

  7. September 2016 21:51

  Thanks Danny - didn't see your reply until just now.  The 4.6.1 release seems to have taken care of this.  Appreciate the quick turnaround on that one!

   

  Allen

  0
• 

  Permanently deleted user

  7. September 2016 22:43

  Hi Everyone!  

   

  The developers are requesting some additional information to track down a workaround for this issue.  Can you please open a support case and reference the bug ID CORE-2382?

   

  Allen, the fix in 4.6.1 applies to customers that have not yet upgraded to 4.6.0.  If you're going from 4.5.1 and older to 4.6.1, you should be free of this bug, but if you're going from 4.6.0 to 4.6.1, as I understand it, it won't help.  Are you seeing something different in your environment?  

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  12. Oktober 2016 18:41

  As far as we're able to ascertain, we've managed to correct this issue for everyone who upgraded to 4.6.0 and was subsequently unable to access or save their HTML5 viewer projects. If anyone is still seeing errors with projects after upgrading their Essentials (whether to 4.6.0 or to 4.6.1 or higher), please contact (To: support@latitudegeo.com) Technical Support so we can help you. 

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.