Consider the following scenario:
In this scenario, the report's rendering performance is much slower than the rendering performance in Native mode. Additionally, many "FileNotFoundException" errors are written to the Reporting Services log.
This issue occurs because of an error in SSRS SharePoint Integrated mode. Every Tablix text box that contains rsViewerpage.aspx in the Go to URL
expression tries to call the SharePoint Object Model. However, this call fails with a "FileNotFoundException" error. Therefore, a decrease in performance occurs if there are many text boxes of this kind to be rendered.
Cumulative update information
The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative Update package 6 for SQL Server 2008 R2
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to pass URL report parameters directly to a report in a SharePoint Document Library, visit the following Microsoft website:
For more information about how to add a hyperlink to a URL, visit the following Microsoft website:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates