Symptoms
Assume that you configure the AutoRefresh property for a SQL Server 2016 Reporting Services report so that its data can be automatically updated. When you open the report in a web browser and then let the browser idle for a while, you receive an error message that resembles the following:
The report execution session_id has expired or cannot be found. (rsExecutionNotFound)
Additionally, error messages that resemble the following are logged in the Reporting Services service trace log:
library!ReportServer_0-2!2258!date time:: i INFO: Call to GetPermissionsAction(/USERIDAutoRefresh).library!ReportServer_0-2!2258!date time:: i INFO: Call to GetSystemPropertiesAction().library!ReportServer_0-2!2258!date time:: i INFO: Call to GetPropertiesAction(/USERIDAutoRefresh, PathBased).library!ReportServer_0-2!2258!date time:: i INFO: Call to GetSystemPermissionsAction().library!ReportServer_0-2!22b8!date time:: i INFO: Call to GetSystemPropertiesAction().library!ReportServer_0-2!22b8!date time:: 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-2!22b8!date time:: e ERROR: Error in getting session data: Session session_id does not belong to NT Service\ReportServersession!ReportServer_0-2!22b8!date time:: i INFO: LoadSnapshot: Item with session: session_id, reportPath: /USERIDAutoRefresh, userName: NT Service\ReportServer not found in the databaselibrary!ReportServer_0-2!22b8!date time:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: The report execution session_id has expired or cannot be found.;webserver!ReportServer_0-2!22b8!date time:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: The report execution session_id has expired or cannot be found.
Resolution
The fix for this issue is included in the following cumulative update for SQL Server:
Cumulative Update 1 for SQL Server 2016 Note After you apply this update, the Reporting Services logs will provide more detailed information about why the session expired for administrators to diagnose and resolve the underlying problem.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.
