I'm working on an ASP.NET 2.0 project and we are using Reporting Services 2005, the web application is configured to work with a State Server. Our users are getting the following error randomly:
[ReportServerException: No se encuentra la ejecución 'bla bla bla' (rsExecutionNotFound)]
Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo() + 367
Microsoft.Reporting.WebForms.ServerReport.SetExecutionId(String executionId) + 117
Microsoft.Reporting.WebForms.ServerReport..ctor(SerializationInfo info, StreamingContext context() + 206
[TargetInvocationException: Exception has been thrown by the target invocation]
System.RuntimeMethodHandle._SerializationInvoke(Object target, SignatureStruct& declaringType, ...
...
System.Web.SessionState.SessionStateItemCollection.DeserializeAllItems() + 88
System.Web.SessionState.SessionStateItemCollection.get_Keys() + 9
System.Web.SessionState.HttpSessionStateContainer.get_Keys() + 10
System.Web.SessionState.HttpSessionState.get_Keys() + 10
...
This exception is thrown in a request when we access the session context to get a variable. After some investigation we have found that the report viewer is storing reports in the session context, we supose that when the report execution expires on server this error is thrown and the user must close Internet explorer and reenter the application.
Is there any way to avoid Report viewer storing reports on session context, if not I think that this is a bug because when using a state server this error is not recoverable and the user must close the Internet explorer. This think doesn' like them much ;-)
Any help would be appreciated
thanks in advance
I'm sorry, I'm not currently bringing a solution to your problem, although:
- I did post the issue on MSDN Labs: http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=90396e94-e868-4a33-b784-f43dcd5a7393
- There is a solution, although it's a hack: http://groups.google.fr/group/ReportingServices/browse_thread/thread/685274e5aa25310/bae5e060b65863b0?lnk=st&q=rsexecutionnotfound&rnum=3&hl=fr#bae5e060b65863b0
Trace.axd brings nothing useful session-wise.
If you did find a solution, please post it, as I too need one!
|||Microsoft says that this is solved, but I can't find where, may be in Sql Server 2005 SP1?