"Report is not available"

  • 1p
    tix2garr1p 1 week, 2 days ago

    “Report is not available” error

    • ASP.NET application
    • IIS 7
    • Using Integrated application pools
    • Application Pool Idle Time-out (minutes) = 40
    • Have verified that the HTTP handlers are correct in the web.config and IIS for Integrated Mode.

    • Webviewer set to AcrobatReader
    • Run report.
    • Leave window open for 25 minutes.
    • Close the window.
    • Get the following pop-up:
    Message from webpage
    Error: Report is not available.

    • Webviewer set to Flashviewer
    • Run report.
    • Leave for 25 minutes.
    • Close the window.
    • Everything is fine, no message.

    Any ideas as to what is happening and how to resolve it?

    Thank you.


  • 1p
    tix2garr1p 1 week, 2 days ago

    Forgot to mention that we are running ActiveReports 11.


  • 10p
    Ruchir Agarwal10p 6 days, 19 hours ago

    Hi Michael,

    The error: “Report is not available” generally occurs due to incorrect mapping of IIS Handlers.
    However if the IIS Handlers are configured properly and in case you continue to receive the error, then could you please try testing with ActiveReports11 SP1 version “11.1.9726.0″. Also, you may refer to the following Blog discussing some similar issue:


    However, if the issue still does not resolve then we request you to share your application so that we can reproduce the issue at our end, look into it and help you further.

    Ruchir Agarwal

  • 1p
    tix2garr1p 6 days, 13 hours ago


    I went ahead and installed the SP1 version and there was no change, it still gives the error.

    Not sure if I made it clear or not… The reports always come up in their own window. Both the Flashviewer and the Adobe Acrobat settings display the report with no problem. It is only when closing that report window does the error occur and ONLY when it is set to Adobe Acrobat.

    If the handler mappings were set up incorrectly, I would think the reports wouldn’t come up in the first place.

    In addition, we don’t have the development server to test this.

    Any other thoughts or ideas?


  • 10p
    Ruchir Agarwal10p 5 days, 15 hours ago

    Hi Michael,

    Without being able to replicate the issue at our end it is very difficult for us to comment on what exactly may be causing this issue.
    Could you please share your application or atleast share a stripped version of your application, so that we can look into it and proceed further.

    Thanks & Regards
    Ruchir Agarwal

  • 1p
    tix2garr1p 4 days, 18 hours ago

    A little more info.

    Tony, a coworker, suggested looking at the developers tools (F12) when closing the window containing the report.

    (With our web app, we create one or more additional windows for the reports. Each window basically just loads the report and shows it. We use IE as the primary browser.)

    * In the main window (where our web app is), I hit F12, which brings up the F12 Developer Tools. I went to the Network tab in the F12 Developer Tools.
    * I ran the report, which showed up in a separate window (not just a separate tab).
    * I closed the report window.

    Here is where it gets a bit interesting…
    * Using the Adobe Acrobat setting, an event shows up in the Network tab of the F12 Developer Tools as follows (Sorry it’s so ugly, didn’t copy/paste well):

    Name Protocol Method Result Content type Received Time Initiator
    http://localhost/SchoolFinancial/ActiveReports.ReportService.asmx/CloseReport HTTP POST 200 application/json 126 B 28.12 ms XMLHttpRequest

    * Using the Flashviewer setting (which isn’t giving us any problem), this does NOT show up in the Network tab.

    * Is there a reason this fires with the Adobe Acrobat setting but not the Flashviewer setting?
    * Is there any way to turn it off to verify that is the issue?

    Thank you.


  • 10p
    Ruchir Agarwal10p 2 days, 19 hours ago

    Hi Michael,

    Thank you for sharing the information. I could observe the behavior you pointed at. However, the same behavior (i.e., CloseReport getting called on closing the window containing viewer) is observed with HtmlViewer and RawHtml viewers too. Are you facing the same issue with them too? Could you please test your application with above mentioned Viewer types and share your observations, this would clear it up whether CloseReport event is the reason of the issue or not.

    Ruchir Agarwal

  • 1p
    tix2garr1p 2 days, 17 hours ago

    OK, I tried it with both the HTMLViewer and RawHTML viewer settings.

    HTMLViewer setting
    * No CloseReport event
    * No error message after the tested 25 minutes.

    RawHTML setting
    * DID fire off the CloseReport
    * Gave the error message after the tested 25 minutes.

    So, I would say it is fair to say that the CloseReport is having issues.

    Is there any way to not fire off the CloseReport? Any other workarounds?


Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.