FIX: An UnhandledReportRenderingException error occurs when a report is rendered in Report Manager in SQL Server 2008 R2 Service Pack 2 or SQL Server 2012

Applies to: SQL Server 2008 R2 Service Pack 2SQL Server 2008 R2 DatacenterSQL Server 2008 R2 Developer

Symptoms


Consider the following scenario:
  • You have Service Pack 2 for Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 installed.
  • You have a report in SQL Server 2008 R2 Reporting Services or SQL Server 2012 Reporting Services, and the report has a page header or page footer.
  • You have a background image in the page header or page footer that is from a database as part of a value expression.
  • You render the report in Report Manager.

In this scenario, an UnhandledReportRenderingException error occurs.

Notes
  • This problem does not occur if you render the report outside Report Manager.
  • This problem does not occur if the source of the image is external or if the image is embedded.

Resolution


Cumulative update information

Cumulative update 9 for SQL Server 2012

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2867319 Cumulative update package 9 for SQL Server 2012
Note 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 2012 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

Cumulative update 5 for SQL Server 2012 Service Pack 1

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2861107 Cumulative update package 5 for SQL Server 2012 Service Pack 1
Note 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 2012 Service Pack 1 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative update 7 for SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update package 7 for SQL Server 2008 R2 Service Pack 2 .

Note 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 Service Pack 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.

See The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released for more information.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.