FIX: Reports are not printed in the defined page size when you use the RSClientPrint control to print reports in SSRS 2008 R2 or in SSRS 2012

Article translations Article translations
Article ID: 2734191 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You create some web-based reports in Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) or in Microsoft SQL Server 2012 Reporting Services (SSRS 2012).
  • You define the page size of the reports in the Report Properties dialog box.
  • You use the RSClientPrint control to print the reports.
In this scenario, the printed reports may not have the same page size that is defined in the report properties.

Cause

The issue occurs because of a rounding problem that occurs when the dimensions of the report page are converted from inches to millimeters (mm). For example, if a report page that is 210 x 297 mm (A4) is rounded by the RSClientPrint control, the new size will be 210.1 x 296.9 mm. When the new dimensions are sent to certain printers the A4 size is not selected. This occurs because the new report page is larger than the standard A4 size.

Resolution

Cumulative update information

Cumulative update 6 for SQL Server 2012

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 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2728897 Cumulative update package 6 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 2008 R2 SP2

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 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:
2797460 Cumulative update package 5 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 SP 2 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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative Update 2 for SQL Server 2012 SP1

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 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2790947 Cumulative update package 2 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 SP1 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 10 for SQL Server 2008 R2 Service Pack 1 (SP1)

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

Workaround

To work around this issue, re-select the page size in the Print dialog box.

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 how to use RSClientPrint control in custom applications, go to the following MSDN website:

How to use RSClientPrint control in custom applications

Properties

Article ID: 2734191 - Last Review: February 18, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 2008 R2 Reporting Services
  • SQL Server 2012 Enterprise Core
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Developer
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2734191

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