rsExecutionNotFound error

Hello,

I am developing a report viewer application in ASP.NEt 2.0 and in that I have a page called ReportViewer.aspx page which has a report viewer control. The processing mode is remote and it is a SQL Server 2005. There are a couple of dropdownlists one which defines the names of the different reports and the other the reporting periods. Depending on the selection made by the user, the call is made to the reporting server and reporst are displayed. Initially when the page loads, the reports show up without any problems. But if a user is inactive for a while, and the user tries to the view the report, I get the following error

"Execution 'tmf3wgqtzuasux3trzliwx25' cannot be found (rsExecutionNotFound) "

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Microsoft.Reporting.WebForms.ReportServerException: Execution 'tmf3wgqtzuasux3trzliwx25' cannot be found (rsExecutionNotFound).

I did some research and came across this post which is the exact error which i am getting.

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124525

The above link is not working for some reason but if you click on the link below, it says that the issue has been fixed. But there is no information as to how to fix this. Does anybody have any idea as to what the solution is?This is the exact same error which I am getting and any help to resolve this error would be great.

http://64.233.183.104/search?q=cache:H2UEJj42ypcJ:connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx%3FFeedbackID%3D124525+rsExecutionNotFound+%2B+2005&hl=en&ct=clnk&cd=1&gl=us

There are some posts which advise to add the a guid at the end of the url but if you are using a viewer you cannot add anything else to the .ServerReport.ReportURL property other than the path to the report or else it returns an error.

As per my knowledge, the report veiwer control should be keeping the session alive using keep alive messages. There is also the possibility of IE caching and one can disable it by going to Tools -> Options and disabling the caching. But this is not something which I can tell my customers to do.

Any help would be greatly appreciated.

Regards,

arpan

Arpan,

My team came across this error a while ago, and found that Reporting Services has it's own session that is timing out. In the ReportServer database, there is a table called ConfigurationInfo. In this table there are values for a SessionTimeout and SessionAccessTimeout. I think the default is set to '600'. This value corresponds to the number of seconds that the report session will be open.

Our solution was to bump this number way up, say to a couple of hours or more. The problem with this is then you get a lot of data in the ReportServerTempDB, which may cause headaches. It's not a perfect solution, and this property should be more easily editable.

The other way to set this property is to use some Reporting Service Scripting, .rss files, and run them using the rs.exe utility that was installed with Reporting Services. There is a Good blog about this by John Gallardo (?) I think.

Good Luck,

Mac

blog url: http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx

|||

Mac.

Thanks for the quick reply. I shall try it out tomorrow and see if that helps.

Regards.

arpan