Error message when you view a report from Report Manager, ReportViewer, or a SharePoint site: "Execution '<SessionID>' cannot be found (rsExecutionNotFound)"

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

When you view a report from Report Manager, ReportViewer or a SharePoint site, you may receive an error message similar to the following:

Execution '<SessionID>' cannot be found (rsExecutionNotFound).

You will also see the following message reported in the Reporting Services error log:

e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException:
Execution '<Session ID>' cannot be found

If you browse directly to the ReportServer virtual directory and view the report, it works correctly.

The issue usually happens when the following conditions are true:

• You have a 64 bit Operating System.
• You install a 64bit instance of SQL 2005 Reporting Services.
• You also install Exchange 2007 on the same server.

Aspnet.config file contains an element called <legacyImpersonationPolicy> that controls how impersonation works with a Web method call. When Exchange 2007 is installed it modifies this setting to false. The side effect of this change is that Reporting services fails to properly impersonate the user viewing the report. Thus, when the web method call makes a request to the database and passes incorrect credentials it cannot locate the session ID mentioned in the error message, since a session ID is associated with only one specific user account.

You can use one of the following options to resolve the problem:

• Move SQL Server 2005 Reporting services to a separate machine.
• Upgrade your SQL Server 2005 Reporting services to SQL Server 2008 Reporting services. The 2008 version does not suffer from the same problem as it does not depend on IIS.
• Manually set the <legacyImpersonationPolicy> back to true.
  
  Note This change may adversely affect Microsoft Exchange Server features that require impersonation and will result in an alert in the Exchange Best Practice Analyzer. To do this follow these steps:
  1. Locate the Aspnet.config file in the following folder:
     
     %windir%\Microsoft.NET\Framework64\v2.0.50727
  2. If Microsoft Visual Studio is installed on the computer that is running SQL Server 2005, double-click Aspnet.config. If Visual Studio is not installed on the computer, follow these steps:
     
     a. Right-click Aspnet.config, point to Open with, and then click Choose program.
     b. In the Programs list, click Notepad, and then click OK.
  3. Locate the following tag in the <runtime> section of the code.
     
     <legacyImpersonationPolicy enabled="false"/>
  4. Change the tag to:
     
     <legacyImpersonationPolicy enabled="true"/>
  5. Save the Aspnet.config file.
  6. Reset IIS.
  7. Try your report again.

This issue does not occur in SQL Server 2008 Reporting Services.

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.