FIX: Incorrect page numbers are displayed when you export a SSRS 2008 R2 report into PDF format

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

On This Page

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) or Microsoft SQL Server 2012 fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) or Microsoft SQL Server 2012 update release.

SYMPTOMS

Consider the following scenario:
  • You have a report that contains a row group in Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2).
  • The report has a field that uses some Globals collection members in its expression to show page number information.
    For example, you use the following expression in the report to show the current page number and the total number of pages:
    ="PAGE : " & Globals.PageNumber & " OF " & Globals.TotalPages
  • You set the PageBreak group properties ResetPageNumber to True and BreakLocation to Between.
  • You try to export the report into PDF format.

In this scenario, the report displays incorrect page numbers and the page number is reset unexpectedly, even when there is no group change.

RESOLUTION

Cumulative update information

SQL Server 2012

The 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 Cumulative update package 1 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. 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

Cumulative update package 4 for SQL Server 2008 R2 SP1

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


STATUS

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

Properties

Article ID: 2647120 - Last Review: April 12, 2012 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2008 R2 Reporting Services
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2647120

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