The execution of "iwy2vpzo52pmp555ftfn4455" could not be found (rsExecutionNotFound)

Question

Some users get the following error when running reports.

• The execution of "iwy2vpzo52pmp555ftfn4455" could not be found (rsExecutionNotFound)

They work fine in the morning. Any suggestions?

thanks

Answer 1

I can help.

The problem is that the ReportViewer control uses Session to store the current executable report. After you switch from reports, the element still remains and ultimately loses its "execution context" because the report server caches reports.

Therefore, before viewing a report, you should try to clear the session of these reports so that there are no cached reports in the session and the ReportViewer control may work correctly.

You will also find that sometimes when accessing Session.Keys.Count this error can occur, as is the case with the execution context.

Make sure you do this on the message page!

2 options:

if (!IsPostBack) { HttpContext.Current.Session.Clear(); ReportViewer1.ServerReport.ReportServerUrl = new Uri(ReportServerUrl, System.UriKind.Absolute); ReportViewer1.ServerReport.ReportPath = ReportPath; System.Collections.Generic.List<ReportParameter> parameters = new System.Collections.Generic.List<ReportParameter>(); .... ReportViewer1.ServerReport.SetParameters(parameters); ReportViewer1.ServerReport.Refresh(); } 

or

 for (int i = 0; i < HttpContext.Current.Session.Keys.Count; ) { if (HttpContext.Current.Session[i].ToString() == "Microsoft.Reporting.WebForms.ReportHierarchy") HttpContext.Current.Session.RemoveAt(i); else i++; } 

Answer 2

Look at the ending space in the report path. That was the reason for me.

Answer 3

I am using SSRS 2017 and encountered this problem when trying to load a report into my MVC project using Access URL. The question for me was related to the session.

To verify this, try deleting the RSExecutionSession cookie and reload the report. Unfortunately, this is only a temporary fix.

If this works, try adding rs:ClearSession=true to the query string.
You can read about this parameter here .

Answer 4

read this and this

and this is for more information

Answer 5

Use the identifier as the impersonation of web.config

 impersonate="true" userName="xxxxx" password="xxxxx" 

instead !--<identity impersonate="true"

Hope this helps

Answer 6

This error caused my application to display a runtime error.

I added this to the Global.asax class to fix the error. I tried the server. Clean, but received nothing. Session.Clear completely got rid of the error.

 Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs) If ex.InnerException IsNot Nothing Then If ex.InnerException.ToString.Contains("The report execution") AndAlso ex.InnerException.ToString.Contains("rsExecutionNotFound") Then Session.Clear() Return End If End If End Sub 

Although this may not be 100% in relation to the above question, I could not find another resolution.

Answer 7

If you are using SQL Server Express edition, SQL Server Agent is not working to clean up your old SSRS sessions. You will need to run the job in the SSRS database to clear old sessions.

My report took 10 seconds to start and 2 seconds to export - so this is not related to the session expiration time.

I get an error when exporting a report to Excel within an hour after exporting the report.