Zum Hauptinhalt gehen

Report Crashing with datalinks

Kommentare

4 Kommentare

  • Permanently deleted user

    Hi Gordy,

    You can check the Essentials REST log file in  (normally) C:\Program Files\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\App_Data\Logs and it will have at least an entry about the failure. You can up the level of logging in REST Manager to get more information.

     

    regards,

    Edmond

     

    0
  • Permanently deleted user

    I check the log files before, there was no information in them about the error when trying to create a report. I took your suggestion and changed the ' REST Application Settings ' to System Log Level = Debug and Access Log Level = Debug and unfortunately there is still no information in the logs about the error when trying to create a report. Did I change the log levels correctly?

     

    Thanks, Gordy

    0
  • Permanently deleted user

    When I add that code to REST web.config file in the the system.web section essential manager no longer loads and i get a error

    "500 - Internal server error.

    There is a problem with the resource you are looking for, and it cannot be displayed."

     

     

     

     

    0
  • Martin Simonsen Bjørkenes

    Hi there

    We are having exactly the same problem. Our report always fails if running for more than approx. 2 minutes. If our selection is small enough for the report to complete within the 2 minute mark, it always succeeds.

    We do get an error in the log file though:

    <Event Timestamp="2012-12-06T11:17:25.3610625+01:00" Level="DEBUG " Identity="Guest"><Message>DataLink 'datalinklyssektor': Error executing DataLinkCustom 'datalinklyssektor' command. [Thread was being aborted .]</Message></Event>

    The error message seems to always be related to a datalink, but not the same data link every time (we have several datalinks in the report). We have run tracing (SQL Profiler) on the database the reveal whether the error is caused by a failed datalink-query or something, but that does not seem to be the case. No errors in the trace, and the database actually continues to run datalink queries related to the report job, even after the "The report operation could not be completed..." error is shown in the viewer...

    We have tried to change the sessionState parameters in the web.config file, but it did not have any effect on the report generation. Is there some kind of timeout setting in the Geocortex report engine?

     

    Regards, Martin

    0

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