Export (0) Print
Expand All

Other Reporting Services Upgrade Issues

This topic describes known issues you may experience upgrading Reporting Services functionality. These issues are not detected by Upgrade Advisor. For additional information, see SQL Server 2014 Release Notes

Applies to: Reporting Services Native mode | Reporting Services SharePoint mode.

Issue

Description

Applies to

SharePoint farm upgrade

Upgrade the Reporting Services shared service only after all other Reporting Services components in the farm have been upgraded to SQL Server 2014.

  • To upgrade Reporting Services in a multi node SharePoint farm to SQL Server 2014 Reporting Services, all instances of the Reporting Services add-in for SharePoint in the farm must be upgraded to the SQL Server 2014 version before you upgrade the Reporting Services shared service.

  • Report rendering will fail when the Reporting Services SharePoint shared service has been upgraded to SQL Server 2014 but other Reporting Services components in the farm are still version SQL Server 2012.

For more information, see SQL Server 2014 Reporting Services Tips, Tricks, and Troubleshooting.

SQL Server 2012 and SQL Server 2012 SP1

Side by Side installation

SQL Server 2012 Reporting Services Native Mode cannot run side by side with either of the following:

  • SQL Server 2014 Reporting Services add-in for SharePoint

  • SQL Server 2014 Reporting Services SharePoint shared service

The side by side installation prevents the SQL Server 2012 Reporting Services Native Mode Windows Service from starting. Error messages similar to the following will be seen in the Windows Event log:

  • Description: The report server database is an invalid version.

  • Description: Report Server [server name] cannot connect to the report server database.

SQL Server 2012 Native mode

Error during the repair of a failed upgrade

Issue: You attempt to run a repair after an upgrade has failed. The repair operation also fails and you see messages similar to the following in the setup log files:

(01) 2011-10-27 12:23:15 Slp: 
(01) 2011-10-27 12:23:15 Slp: Exception type: System.Exception
(01) 2011-10-27 12:23:15 Slp:     Message: 
(01) 2011-10-27 12:23:15 Slp:         SQLPath element is missing
(01) 2011-10-27 12:23:15 Slp:     Data: 
(01) 2011-10-27 12:23:15 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure

For more information on the log files, see View and Read SQL Server Setup Log Files.

Solution: You need to uninstall Reporting Services and reinstall Reporting Services. An upgrade is no longer possible.

SQL Server 2012 and SQL Server 2012 SP1

Interactivity information saved only for the last request.

In earlier versions of Reporting Services, snapshots saved all possible combinations of interactive choices, such as drill through information and toggle choices. For example, you could view page five of a report, but programmatically toggle an item on page one by keeping track of the correct ID for the toggle.

In SQL Server 2008, interactivity information is generated and saved only for the last rendering request. You cannot view a page and programmatically toggle an item on another page. You can only toggle drilldown items on the current report page.

SQL Server 2005 SP2

Rendering and pagination have changed.

The Rendering Object Model (ROM) changed in SQL Server 2008 Reporting Services. Earlier versions of the rendering object model are no longer supported. Accessing the Rendering Object Model from a multi-threaded rendering extension (and switching context from multiple threads) is not supported.

SQL Server 2005 SP2

Redesigned CSV export format.

In earlier versions of Reporting Services, when you exported a report to a CSV file format, the data was formatted in a way that preserved the way the data appeared on the report page. For matrix data regions, this resulted in a data format that was inconvenient to import into other applications.

In this release, when you export a report to a CSV file, you can choose between two supported formats: Default mode and Compliant mode. Default mode is optimized for Excel. Compliant mode is optimized for third-party applications.

The earlier format for CSV files is no longer available. However, for reports that do not use matrix data regions, you can use Compliant mode to get a file format closest to the earlier CSV file format.

SQL Server 2005 SP2

Aggregates with conditional visibility in page headers and footers.

In earlier versions of Reporting Services, different renderers used different rules to determine which items with conditional visibility to include on a report page. For example, aggregate calculations were not performed for hidden items in printed reports, but were calculated for hidden items in reports that you viewed with a browser or in Microsoft Office Excel.

In this release, all renderers use the same set of rules to determine which items are on a page.

SQL Server 2005 SP2

No formula support in Excel.

In earlier versions of Reporting Services, there was limited support for translating expressions in RDL to Excel formulas. In this release, when you export a report to Excel, RDL expressions are not translated to Excel formulas.

SQL Server 2005 SP2

Overlapping items.

In earlier versions of Reporting Services, if a report had overlapping items on the report design surface, publishing the report produced a warning ("Overlapping report items are not supported in all renderers."), but the report items remained in their original location on the design surface. In SQL Server 2008, report items may be moved to correct overlapping boundaries when a report is viewed or exported to a renderer that does not support overlapping items.

SQL Server 2005 SP2

Report object model namespace change.

In SQL Server 2008 Reporting Services, the Report Object Model namespace has changed. This namespace provides read-only access from custom code to global collections like Fields, Parameters, and ReportItems. If existing custom code explicitly uses a fully qualified reference to an earlier namespace, this change is a breaking change.

It is recommended that you do not use fully qualified references to access built-in collections from your code. By not explicitly specifying the namespace, custom code references resolve to the version of the report object model for the currently installed version of Reporting Services.

SQL Server 2005 SP2

Report Server Windows Management Instrumentation (WMI) Provider from SQL Server 2000 or SQL Server 2005 is not supported.

Reporting Services includes a WMI provider that you can use to programmatically configure the environment in which a report server runs. The SQL Server 2008 release of Reporting Services includes an all-new version of the WMI provider that completely replaces the previous version. SQL Server 2000 and 2005 versions are not supported in this release of SQL Server.

SQL Server 2005 SP2

Service Principal Names (SPN) are not recreated on an upgraded report server.

If you created an SPN for the Report Server Web service, verify that constrained delegation still works for the upgraded report server.

SQL Server 2005 SP2

Custom assemblies must be moved manually to the new installation folder.

Custom assemblies are not detected by upgrade advisor, and they must be moved manually to the new installation folder if you want to continue using the custom functionality in reports.

If these assemblies are installed in the report server installation folder, they need to be moved to the new installation folder after the upgrade completes.

SQL Server 2005 SP2

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft