Refreshing a SQL Server Reporting Services (SSRS) Report Error Message

By Garth Jones

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

I see this error every so often and it always occurs when I “wake” my PC and re-fresh a SQL Server Reporting Services (SSRS) report.

There isn’t really a fix for this, but all you need to do is re-run the original report. This will give you a new SSRS ID and everything will be good.

Refreshing a SSRS Report Error Message

email

Written by , Posted .
  • Chad Simmons

    I normally leave reports open for days on end and it is very often that I receive this message after about a day… very annoying. I’ve searched for a way to extend the expiration threshold but I came up empty. Perhaps someone with more SSRS/IIS knowledge than me can find a way to configure that.

    • Enhansoft

      Hi Chad,

      Why are you leaving the report open? Is it dashboard?

      I don’t think there is a way to extend the token
      timeout in either SSRS or IIS but have you looked at enabling the auto refresh
      feature for the report and therefore it should help keep the access token
      alive.