Sorry about that. SQL 2008. Visual Studio 2008 (though we're upgrading to 2010 soon). Version 9.0.0.0 of the ReportViewer control. .NET Framework 3.5.Cane_92

HI Cane, What's the versions of SQL Server Reporting Services? thanks, Jerry

There's a ton of posts in this and other forums about dealing with the rsExecutionNotFound error by increasing the timeout. While that works, it has at least 2 negative effects. (1) Sessions are kept open longer than necessary which drains resources and (2) the user still may experience a timeout. I'm using a ReportViewer control. Users configure their parameters on our ASP.net site (rather than in the report toolbar), I read the values, pass them in to the ReportViewer control, and render the report to PDF. The users THEN typically change a parameter or two and click the run report button again. If they click that button after waiting however long the timeout is, they get the rsExecutionNotFound error. Increasing the timeout works but with the two negative effects. If I trap the error, how can I resubmit the report request but have the ReportViewer get a new execution ID like it does on the first request? I've tried clearing the execution ID using SetExecutionID to an empty string but that doesn't work (I get an error that the value passed isn't in the expected range). And I'm already calling the Refresh method so that the report doesn't load from cache. Thanks, Cane_92