Execution 'xxx' cannot be found (rsExecutionNotFound) when exporting SSRS report
System: SSRS 2008 64bits SP2 Our reports are executing successfully in our ReportViewer control (v10.0). However, after SSRS session times out (session timeout has been manualy set to 1 minute just to test using this command: http://blogs.msdn.com/b/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx), there is no way to handle ReportViewer's export behaviour. Indeed, after SSRS session timeout user still can press on export button and choose to export the report (as Excel for instance), which opens a popup window displaying "Execution 'xxx' cannot be found (rsExecutionNotFound)" server error. Note that we are able to handle this exception using try-catch or ReportViewer.ReportError event handler in all other cases but this one (popup window). Is there any way (maybe using ReportViewerTemporaryStorage?) to handle this 'rsExecutionNotFound' exception properly or at least in this specific export scenario? Thanks in advance.
July 23rd, 2010 8:54am

Hi Lybax, Read this thread about related topic at http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/dd1b4f39-afc4-4020-b797-db3a98decdda/ , and finially, the original poster added a ReportViewer.Reset() in the Page_Load to solve this issue. please follow and try it, and let us if you have more question. thanks, Jerry
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2010 2:37am

Hi Jerry, I'm sorry but I've already tried this solution in the past, but my current issue has nothing to do with this as it happens specifically in the client script side that opens a popup window to export the report (see ReportViewer export button). There is no PostBack. The "Execution 'xxx' cannot be found (rsExecutionNotFound)" error message is displayed in that popup screen. There is no way to catch that exception in code behind. Maybe the only solution is to refresh the page just before SSRS session times out (reseting and reinitializing the report and all its parameters). But that's no exactly what I was looking for... Thanks anyway.
July 26th, 2010 1:10pm

Hi, In my case, this error ocurred only in the Browsers Internet Explorer 8 and Internet Explorer 9 with reports that takes more than 20 minutes for execute. I solved this problem optimizing the sql query procedure ( before optimize took 30 minutes to execute ) and now takes 3 minutes. I tried to configure increasing the session timeout in ReportManager configuration but anything solve the problem. This error is weird because in Google Chrome and Firefox works fine! Ricardo PrattiRicardo G. Pratti
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2012 4:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics