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.

Issue

Description

Applies to

Report Builder runs in Full Trust mode only.

In earlier versions of Reporting Services running in native mode, Report Builder 1.0 could be started using the following URLS:

  • Full trust   For example, http://<servername>/reportserver/reportbuilder/reportbuilder.application

  • Partial trust   For example, http://<servername>/reportserver/reportbuilder/reportbuilderlocalintranet.application

For both URLs, <servername> is the name of the computer that specifies the report server. For both URLs, reportserver is the name of the report server instance.

In this release, you must use the full trust URL to run Report Builder 1.0. When you use the full trust URL for the first time, you might be prompted to grant a higher level of permissions for the application.

After you grant these permissions the first time, you do not have to set them again.

If you use the partial trust URL, the following error appears when you open or save a report, or switch report servers:

"Failed. An error occurred while processing your request. Save your report and restart the application."

SQL Server 2005 SP2

Interactivity information saved only for the last request.

In earlier versions of Reporting Services, snapshots saved all possible combinations of interactive choices, such as drillthrough 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 2000 SP2 and SQL Server 2005 SP2

Rendering and pagination have changed.

The Rendering Object Model (ROM) has changed for SQL Server 2008. 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 2000 SP2 and 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 2000 SP2 and 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 2000 SP2 and 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 2000 SP2 and 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 2000 SP2 and SQL Server 2005 SP2

Report object model namespace change.

In this release, 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.

For more information and examples, search for "Breaking Changes (Reporting Services)" in SQL Server Books Online.

SQL Server 2000 SP2 and SQL Server 2005 SP2

Expressions that contain a reference to the object result in report compilation errors.

If you are upgrading from SQL Server 2000 Reporting Services, be aware that reports that use expressions to set the Action property on an item will no longer compile if the expression includes a Me.Value reference. Upgrading reports that include Me.Value in Action property expressions will result in compiler errors similar to "The Value expression for the textbox ‘textbox1’ contains an error: [BC30456] 'Value' is not a member of 'ReportExprHostImpl.textbox1_TextBoxExprHost.DataValue1_DataValueExprHost'. (rsCompilerErrorInExpression)."

To avoid these errors and upgrade your reports, you must rewrite Action expressions, replacing Me.Value with the actual value expression. The following example illustrates how to replace Me.Value in a textbox-style expression with an actual value expression: =iif(Fields!Name.Value = 0, "Solid", "None").

SQL Server 2000 SP2 only

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 2000 SP2 and 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 2000 SP2 and SQL Server 2005 SP2

Authentication restrictions for data processing extensions.

If you are upgrading from SQL Server 2000 Reporting Services, be aware that there are new restrictions on how credentials are handled for some data processing extensions:

  • You cannot configure an Analysis Services data source connection to use database credentials. The connection will fail if you are using the ADOMD wrapper.

  • You cannot configure an XML data source connection to use database credentials. If you specify no credentials and the unattended execution account is not defined, the request is made through Anonymous access.

  • Third-party .NET Framework data processing extensions (for example, DB2.NET, Oracle ODP.NET, and Teradata) explicitly fail data processing if database credentials are passed on the connection string and the unattended execution account is not configured.

  • Custom data processing extensions that implement IDBConnection (but not IDBConnectionExtension) explicitly fail data processing in all cases unless the unattended execution account is configured.

  • In all cases where connection requests are made by the service account (that is, the security context of the service account is used for the network connection to the data source), Reporting Services removes administrator privileges from the service account before sending the request.

To configure the unattended execution account, use the Reporting Services Configuration tool or rsconfig utility.

SQL Server 2000 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
Show:
© 2015 Microsoft