Error exporting to XLSX

Dan Giersz

18. November 2015 15:16

Running GE 4.4.2 and GVH 2.5.2 (same issue in GVH 2.5.1)

 

We are receiving the following error when trying to export to CSV, XLSX, SHP format:

 

Exception has been thrown by the target of an invocation. Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property. Parameter name: input

 

It is only happening when there is a large number of features selected (when the buffer selects 50 features, export works fine, but a larger buffer on the same feature selects 550 features and we get the error).

 

What is the string that is too long? Is it from the service or something created by Geocortex during the export operation?

 

Can we adjust the maxJsonLength property somewhere?

 

 

0

• 

  Ryan Cooney

  18. November 2015 17:29

  Hi Dan,

   

  When you perform an extract the viewer packages up the faeture data data as JSON and posts it to Essentials. This error indicates that the size of that JSON payload is very large. The exact size depends a bit on encodings, but it should mean that it is more than 10 MB.

   

  The limit is currently derrived from a value in the REST web.config that limits the overall size of all incoming requests. You can increase this value, but keep in mind that this limit is there to protect your server. <httpRuntime maxRequestLength="20480" ...

   

  More info about the maxRequestLength property is available here https://msdn.microsoft.com/en-us/library/system.web.configuration.httpruntimesection.maxrequestlength(v=vs.110).aspx.

   

  --Ryan

  0
• 

  Dan Giersz

  18. November 2015 20:01

  Thanks for the reply, Ryan.

   

  Not sure why the request would be over 20MB...500 features is not that many.

  0
• 

  Ryan Cooney

  20. November 2015 16:43

  Often we find that is it the geometry associated with a few complex features that account for the majority of the data.

   

  Since you reported this we have made a subtle change. The overall maxRequestLength is still observed, but the limit on JSON parsing within the request is not restricted.

   

  --Ryan

   

   

  0
• 

  Dan Giersz

  20. November 2015 17:13

  That's great, thanks for following up on the issue.

  0
• 

  Permanently deleted user

  19. April 2016 05:50

  Hi, Ryan,

   

  what version does your changes apply? 

   

  I hit the same error with the same Essential 4.4.2 and HTML5 Viewer 2.5.2.

   

  Two error messages encountered in my case, the MaxJsonLength, and "Unable to load http://bai1gtx1.internal.dotars.gov.au/Geocortex/Essentials/dev442/REST/Utilities/Extract status: 404".

   

  I increase the value of maxRequestLength to large, because the polygon has many vertacies. the toal number of records is only 167. I contantly got 404 error.

   

  Do I need to install the new version of HMTL 5 Viewer?

   

  thanks

   

  Helen

  0

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