The report execution has expired or cannot be found. (rsExecutionNotFound)

[Ccparkhill]

I am using the October release of PBIRS, when I call an SSRS report from a URL I am getting a "The report execution has expired or cannot be found. (rsExecutionNotFound)" error, for example:

http://myserver/Reports/report/myfolder/myreport?rs:Embed=true&rc:Toolbar=false&myparam=myvalue

It usually works the first time but if I try to pass a different value for the parameter I get the error.

However if I remove rc:Toolbar=false or add rs:ClearSession=true the report renders without issue. Unfortunately I need to remove the toolbar and ClearSession can't be added to a 'Go to report' action which is used on my report.

When checking the logs I see the following:

library!ReportServer_0-1!1238!11/22/2017-16:47:16:: i INFO: Entering StreamRequestHandler.ExecuteCommand - Command = 
library!ReportServer_0-1!1238!11/22/2017-16:47:16:: i INFO: Call to GetItemTypeAction(/LawyerDesktop/LIVE/LD - Time and Expenses). User: XXXX.
library!ReportServer_0-1!1238!11/22/2017-16:47:16:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database.;
session!ReportServer_0-1!1238!11/22/2017-16:47:16:: e ERROR: Error in getting session data: Invalid or Expired Session: vd00o4zvju03oym5r12zv1vy
session!ReportServer_0-1!1238!11/22/2017-16:47:16:: i INFO: LoadSnapshot: Item with session: vd00o4zvju03oym5r12zv1vy, reportPath: /LawyerDesktop/LIVE/LD - Time and Expenses, userName: XXXX not found in the database
library!ReportServer_0-1!1238!11/22/2017-16:47:16:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: The report execution vd00o4zvju03oym5r12zv1vy has expired or cannot be found.;

The only thing I can see that might be an issue is "An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database", but there are no issues with the database and this wouldn't explain why the report renders when omitting Toolbar or adding ClearSession.

Any help greatly appreciated.

Thanks

[johncpratt]

@Ccparkhill , @v-yulgu-msft :

Another bit of info to add to this regarding the specified error, with a client-side fix.  At this point, I am using Microsoft Power BI Report Server Version 15.0.1107.166 with SQL Server 2019 Enterprise.

I have been using the URL adjustments for several years now with success, but suddenly got the nasty session expired error again and none of the recommended solutions worked, including URL tweaks.  These days I am using Google Chrome as the primary browser.  In this particular case, I have a paginated report running in an iframe on a web page that I have been working on intensively for the last 24 hours.  So after exhausting all the other troubleshooting options, I hit F12 (Dev Tools) and started looking for sessions/cookies.

The session which is expiring is stored as a cookie on the client PC (assuming UseSessionCookies is True, but even when I set that to False it didn't fix the issue 😞 ).  I found the misbehaving session cookie in Dev Tools under the Application menu item.  Then on the left side bar, under Storage > Cookies, the report server base URL was listed.  I clicked that and the session ID reported in the error appears as the Value of one of the cookies in the list.

I deleted the offending cookie, refreshed the screen containing the iframe, and there was the report!

[johncpratt]

I have just encountered a similar error and symptoms after deploying Power BI Report Server October 2017 GA on a SQL Server 2016 Enterprise server. I had been running SSRS 2016 (and multiple versions before that) without issue. The error was occurring when clicking a URL link in a web page to run an SSRS/paginated report and generate it as a PDF so the user can save it to disk.  The same URL and report have been working for years, so the only known change was PBIRS.

Based on other posts I found, I added "&rs:ClearSession=True" to the URL and it worked immediately just by refreshing the web page containing the URL (no server-side resets or setting changes). I've had to use that parameter before with SSRS reports embedded in an iFrame. 

I know you don't want to or can't use that parameter, but the pointer to a session issue as opposed to Kerberos security, timeout settings, etc. was important to note.  Any further info you dig up will be great to post.

[Ccparkhill]

I haven't gotten any further with this but I've raised it on Connect:

https://connect.microsoft.com/SQLServer/feedback/details/3146194

Please vote!

I have also noticed that for a textbox with CanGrow set to false the text will render at the top of the textbox and then 'jump' to the centre (where I have specified it to be) when using rc:Toolbar=false, which is distracting for the user. This doesn't happen in SSRS 2014.

[v-yulgu-msft]

Hi @Ccparkhill,

I encountered the same error message as yours when I called the SSRS report the second time with a changed URL parameter. 

The first time:        http://servername/PowerBIReports/report/Report%20Project1/SSRSReport1?rs:Embed=true&rc:Toolbar=false

The second time:  http://servername/PowerBIReports/report/Report%20Project1/SSRSReport1?rs:Embed=true

But it looks like an occasional issue. This problem doesn't occur to other reports. And after I re-published the report to report server, I didn't come across this problem. In your scenario, please re-publish the report for a test. And try to reboot PBI report server service.

Regards,

Yuliana Gu

[Ccparkhill]

@v-yulgu-msft thanks for your reponse, it's not changing the URL parameters I'm having a problem with, it's changing the value of a report parameter via the URL when combined with &rc:Toolbar=false.  

First execution working: http://myserver/Reports/report/myfolder/myreport?rs:Embed=true&rc:Toolbar=false&Year=2016

Second execution not working: http://myserver/Reports/report/myfolder/myreport?rs:Embed=true&rc:Toolbar=false&Year=2017

Removing &rc:Toolbar=false results in both working without issue:

http://myserver/Reports/report/myfolder/myreport?rs:Embed=true&Year=2016

http://myserver/Reports/report/myfolder/myreport?rs:Embed=true&Year=2017

I have tried redeploying the reports but that does not solve the issue, I'm seeing this on our dev, UAT and production PBIRS installations. I also tried SSRS 2017 on another server with the same result.

It seems like &rc:Toolbar=false changes the behaviour of the session for some reason, is this expected?

I was able to work around this issue by setting UseSessionCookies to false in Advanced Server Properties via SSMS. 

[Ccparkhill]

I was able to reproduce this at home on my laptop with default installs of SQL Server 2017 Developer and PBIRS October 2017 using:

Adventure Works 2014 Full Database

AdventureWorks 2012 SSRS Samples

First execution working: http://localhost/reports/report/AdventureWorks%20Sample%20Reports/Sales%20Order%20Detail?rs:Embed=true&rc:Toolbar=false&SalesOrderNumber=SO50750

Second execution not working: http://localhost/reports/report/AdventureWorks%20Sample%20Reports/Sales%20Order%20Detail?rs:Embed=true&rc:Toolbar=false&SalesOrderNumber=SO50751

Removing &rc:Toolbar=false results in both working without issue:

http://localhost/reports/report/AdventureWorks%20Sample%20Reports/Sales%20Order%20Detail?rs:Embed=true&SalesOrderNumber=SO50751

http://localhost/reports/report/AdventureWorks%20Sample%20Reports/Sales%20Order%20Detail?rs:Embed=true&SalesOrderNumber=SO50750