Hoppa till huvudinnehållet

Generic Report Error

Kommentarer

6 kommentarer

  • Justin Kraemer
    Hi Lisa,

     

    I'm running the same versions, and have just run into this error today when trying to run a report that formerly worked. It has several subreports based on Data Links. I too, find the message too generic to help me find the cause. The only thing I can think of is to try pulling it apart by removing the sub reports (in my case one-at-a-time) until it works, and then go from there. That's my plan, but if anyone has a better suggestion, I'm interested.
    0
  • Permanently deleted user
    So my reports were running fine, now I'm getting that error again. Have you looked in the system log files here:

     

    C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\App_Data\Logs\SYSTEM-2016-04-25.log

     

    I'm getting this error: <Event Timestamp="2016-04-25T09:48:16.1595101-07:00" Level="ERROR" Identity="Guest"><Message>Exception has been thrown by the target of an invocation.

     

    Error performing the query: [Failed to execute query.].

     

    Failed to execute query.</Message></Event>

     

    Which also doesn't really tell me a lot...
    0
  • Permanently deleted user
    Update: I have two places that people can run the report, from a link in the pop-up and from the search results details panel. I can get the report to run from both places sometimes. I can also get the report to run from just clicking on the feature in the map, as well as searching in the global search box, sometimes. Because of this, of being able to run the report from all the different locations and ways, I have a feeling this is a bug in the system and not in the report or viewer configuration...
    0
  • Permanently deleted user
    I am experiencing the same issue. Any luck in getting this one resolved?

     

    Thanks,

     

    Aaron
    0
  • Permanently deleted user
    Hi Aaron, my problem ended up being on the ArcMap side. I did not have a primary key set on the SQL view that I was using so when I was tyring to run the report, different OID's were being called, which would soemtimes return the completely wrong feature in the report, and also sometimes return the error. This probably doesn't apply to you, sorry I couldn't be more help!
    0
  • Permanently deleted user
    Hi Lisa, 

     

    Thank you for getting back to me. I think you are right, I am having a separate issue.
    0

Du måste logga in om du vill lämna en kommentar.