FIX: The data in a custom report item is displayed incorrectly after you export the report to a PDF format file by using the ReportExecutionService.Render method in SQL Server 2008 Reporting Services or SQL Server 2008 R2 Reporting Services

Article translations Article translations
Article ID: 981973 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 or SQL Server 2008 R2 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 or SQL Server 2008 R2 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2008  Reporting  Services (SSRS) or SSRS 2008 R2 , you create a report that contains a custom report item (CRI). 
  • You create a second report that contains a subreport control in a tablix or in a list control.
  • The first report is embedded in the subreport control in the second report.
  • You deploy both reports to Report Server.
  • You use the ReportExecutionService.Render method to export the second report to any of the Hard Page Break (HPB) formats. For example, you export the report to a file in the PDF format.
In this scenario, the data in the CRI is displayed incorrectly in the exported PDF file.

Notes
  • This issue cannot be easily reproduced because only a few report designs cause this behavior.
  • This issue does not occur if you export the report to any Soft Page Break (SPB) formats, such as the HTML format, the Excel format, and so on, by using the ReportExecutionService.Render method.
  • This issue does not occur when you export the report to any format from Report Manager.
  • The issue also occurs if you export the report to any Hard Page Break (HPB) formats from the report preview in Business Intelligence Development Studio (BIDS).

RESOLUTION

Cumulative update information



SQL Server 2008 R2


The fix for this issue was first released in Cumulative Update 2. 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:
2072493 Cumulative update package 2 for SQL Server 2008 R2
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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008

The fix for this issue was first released in Cumulative Update 8 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
981702 Cumulative update package 8 for SQL Server 2008 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 2008 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

STATUS

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

MORE INFORMATION

For more information about custom report items, visit the following Microsoft Web site:
Custom report items

REFERENCES

For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 981973 - Last Review: June 23, 2010 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB981973

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com