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 causi
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.