Select the product you need help with
FIX: Pages of an SSRS 2008 R2 or an SSRS 2012 report are delivered incorrectly if you use the ReportExecutionService.Render method to render the report in image format or in EMF formatArticle ID: 2637802 - View products that this article applies to. On This PageMicrosoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 or SQL Server 2012 fix release. SymptomsConsider the following scenario:
Note This issue does not occur in Microsoft SQL Server 2005 Reporting Services (SSRS 2005) or in Microsoft SQL Server 2008 Reporting Services (SSRS 2008). CauseThis issue occurs because a function is changed in the ReportExecutionService.Render method in SSRS 2008 R2. The method only returns an empty array in StreamIds. Therefore, it cannot be used to render the report pages except for the first page. ResolutionCumulative update informationSQL Server 2008 R2 Service Pack 2The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2720425 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 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:
(http://support.microsoft.com/kb/2720425/
)
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2679367 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 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:
(http://support.microsoft.com/kb/2679367/
)
Cumulative Update package 6 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released SQL Server 2012The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2679368 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. Microsoft recommends 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:
(http://support.microsoft.com/kb/2679368/LN/
)
Cumulative update package 1 for SQL Server 20122692828 You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
(http://support.microsoft.com/kb/2692828/LN/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released Cumulative update package 12 for SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 12. 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:2659692 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 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:
(http://support.microsoft.com/kb/2659692/
)
Cumulative update package 12 for SQL Server 2008 R2981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedWorkaroundTo work around this issue, render every page by specifying a StartPage value in the DeviceInfo string. Note This workaround might decrease performance. More informationFor more information about the ReportExecutionService.Render method, visit the following MSDN website: General information about the ReportExecutionService.Render method
(http://msdn.microsoft.com/en-us/library/reportexecution2005.reportexecutionservice.render(v=SQL.105).aspx)
StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2637802 - Last Review: November 19, 2012 - Revision: 5.0 Applies to
| Article Translations
 |
Back to the top
