Home/ Questions/Q 6531395
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T09:52:23+00:00

I have an ASP.NET app that exposes a Microsoft ReportViewer (actually an MVC3 app

  • 0

I have an ASP.NET app that exposes a Microsoft ReportViewer (actually an MVC3 app with one WebForm hosting the ReportViewer). When running large reports, a timeout occurs causing the request to stop and a blank page to show in place of a report. Yet the following timeout parameters are set programmatically:

Viewer.ServerReport.Timeout = Configuration.ReportViewerTimeout;
ScriptManager.AsyncPostBackTimeout = Configuration.ReportViewerAjaxTimeout;

The respective values are -1 and 0 which as per documentation are interpreted as no timeout. I also tried large values, it made no difference.

After about a minute or so waiting on the report to load ("Loading" message box), I get a blank report and I see this in my Firebug console window:

Aborted

Sys.WebForms.PageRequestManagerTimeoutException: The server request timed out.

[Break On This Error] this._endPostBack(this._cr…anagerTimeoutError(), sender, null);

I also tried adding this to my web.config:

<httpRuntime maxRequestLength="1024000" executionTimeout="999999" />

And in IIS > my site > Advanced Settings > Connection Limits I set "Connection Time-out (seconds)" to 1200. All this made no difference.

Does anyone know what I could be missing?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Turns out that the answer is: There is actually nothing missing!

    As it happens, the ScriptManager’s timeout value is not persisted in ViewState (unlike the ReportViewer’s timeout value) and the code was only setting it once inside a if (!PostBack) block. Fixed by setting the ScriptManager’s AsyncPostBackTimeout property at each request (even postbacks). An alternative is to set it to a fixed value using the Visual Studio WebForm designer.

    • 0