Sdílet prostřednictvím

  • Článek

Troubleshooting Installation and Upgrade Issues (Reporting Services)

Use this topic to troubleshoot and work around issues that you encounter when installing or upgrading Reporting Services. For more information about Reporting Services installation prerequisites, logs, and configuration, see How to: Troubleshoot a Reporting Services Installation Problem.

This topic contains information about the following issues:

  • Performance counters are not visible after upgrading the operating system

  • Error when repairing a failed upgrade from SQL Server 2000 Reporting Services

  • ReportServerExternalURL and PassThroughCookies configuration properties are not configured after an upgrade from SQL Server 2005

  • SQL Server 2000 Reporting Services installation breaks the default instance of SQL Server 2008 Reporting Services

  • Installation fails for a default instance of SQL Server 2005 Reporting Services on a computer that runs SQL Server 2008 Reporting Services

  • 401-Unauthorized error when using Windows authentication after an upgrade from SQL Server 2005 to SQL Server 2008

  • Uninstalling 32-bit instance of SQL Server 2008 Reporting Services in side-by-side deployment with a 64-bit instance breaks the 64-bit instance

  • Error message during upgrade from the February CTP to a later release of SQL Server 2008 Reporting Services when an SSL certificate was installed after the February CTP

Performance counters are not visible after upgrading the operating system

If you upgrade the operating system to Windows Vista, Windows Server 2008, or a later version of the operating system on a computer that runs Reporting Services, Reporting Services performance counters will not be set after the upgrade.

To reinstate Reporting Services performance counters

  1. Delete the following registry keys:

    • HKLM\SYSTEM\CurrentControlSet\Services\MSRS 2008 Web Service

    • HKLM\SYSTEM\CurrentControlSet\Services\MSRS 2008 Windows Service

  2. Open a command window and type the following command at the prompt:

    • run <.NET 2.0 Framework directory**>\InstallUtil.exe <Report Server Bin directory>\ReportingServicesLibrary.dll**

      Note

      Replace <.NET 2.0 Framework directory> with the physical path of the .NET Framework 2.0 files and replace <Report Server Bin directory> with the physical path of the report server bin files.

  3. Restart the Reporting Services service.

To verify that the steps worked, open a Web browser and navigate to the Report Manager URL or the Report Server URL. Then open Performance Monitor to verify that the counters are working.

Top

Error when repairing a failed upgrade from SQL Server 2000 Reporting Services

If an upgrade from SQL Server 2000 to SQL Server 2008 Reporting Services fails, you can run Repair and try to fix it. However, you might receive the following error message when you try to access Reporting Services, such as by opening Report Manager or trying to render a report, after you run Repair:

"The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.6.54'. The expected version is 'C.0.9.45'. (rsInvalidReportServerDatabase)"

To fix this issue, you must add RSExecRole to the db_owner role in the Reporting Services databases.

To add RSExecRole to the db_owner role in the Reporting Services databases

  1. Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases.

  2. In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles, and Database Roles.

  3. Right-click db_owner, and click Properties.

  4. On the Database Role Properties page, click Add.

  5. On the Select Database User or Role page, type RSExecRole, and then click OK twice.

  6. Repeat these steps for the ReportServerTempDB.

  7. Restart the Report Server service. You might need to restart the service twice. For more information, see Starting and Stopping the Report Server Service.

Top

ReportServerExternalURL and PassThroughCookies configuration properties are not configured after an upgrade from SQL Server 2005

When you upgrade from SQL Server 2005 to SQL Server 2008 Reporting Services, the ReportServerExternalURL and PassThroughCookies configuration properties are not configured by the upgrade process. ReportServerExternalURL is an optional property, and it should be set only if you are using SharePoint 2.0 Web Parts and you want users to be able to retrieve a report and open it in a new browser window. For more information about ReportServerExternalURL, see URLs in Configuration Files (Reporting Services). PassThroughCookies is required only when using Custom authentication method. For more information about PassThroughCookies, see Enabling Report Manager to Pass Custom Authentication Cookies.

Note

When you use Custom authentication, it is recommended that you migrate your installation rather than performing an upgrade. For more information about migrating Reporting Services, see How to: Migrate a Reporting Services Installation.

By default, these properties do not exist in the SQL Server 2008 Reporting Services configuration. If you configured these properties in SQL Server 2005 and you continue to require the functionality that they provide, you must manually add them to the RSReportServer.config file following the upgrade process. For more information, see How to: Modify a Reporting Services Configuration File.

Top

SQL Server 2000 Reporting Services installation breaks the default instance of SQL Server 2008 Reporting Services

When you must run both SQL Server 2000 Reporting Services and SQL Server 2008 Reporting Services on the same computer, install the SQL Server 2000 instance first. If you do not, the SQL Server 2008 Reporting Services service entry for the default instance will be overwritten when you install SQL Server 2000 Reporting Services, and the SQL Server 2008 instance will break. This happens because SQL Server 2000 Reporting Services installs only as the default instance but the install process does not detect that the default instance is already in use by the SQL Server 2008 Reporting Services instance. If you try to repair the SQL Server 2008 instance, the SQL Server 2008 instance will be repaired but the SQL Server 2000 instance will break.

Top

Installation fails for a default instance of SQL Server 2005 Reporting Services on a computer that runs SQL Server 2008 Reporting Services

If you attempt to install a default instance of SQL Server 2005 Reporting Services on a computer that already runs an instance of SQL Server 2008 Reporting Services, the SQL Server 2005 Reporting Services instance will fail to install with the following error message:

"An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name."

This issue happens regardless of whether the SQL Server 2008 Reporting Services instance is a default or named instance, and regardless of whether a SQL Server 2008 Reporting Services instance with that name already exists on the computer.

To workaround this issue, you have one of the following options:

  • If you must run SQL Server 2005 Reporting Services as the default instance on the computer, you must install the SQL Server 2005 Reporting Services instance before the SQL Server 2008 Reporting Services instance.

  • If the SQL Server 2005 Reporting Services instance does not need to be a default instance, you can install the SQL Server 2005 Reporting Services instance as a named instance after you install the SQL Server 2008 Reporting Services instance.

Top

401-Unauthorized error when using Windows authentication after an upgrade from SQL Server 2005 to SQL Server 2008

If you upgrade from SQL Server 2005 Reporting Services to SQL Server 2008 Reporting Services, and you use NTLM authentication with a built-in account for the Report Server service account, you might encounter a 401-Unauthorized error when you access the report server or Report Manager after the upgrade.

This happens because of a change in the default SQL Server 2008 Reporting Services configuration for Windows authentication. Negotiate is configured when the Report Server service account is either Network Service or Local System. NTLM is configured when the Report Server service account is not one of those built-in accounts. To fix this issue after you upgrade, you can edit the RSReportServer.config file and configure the AuthenticationType to be RSWindowsNTLM. For more information, see How to: Configure Windows Authentication in Reporting Services.

Top

Uninstalling 32-bit instance of SQL Server 2008 Reporting Services in side-by-side deployment with a 64-bit instance breaks the 64-bit instance

When you install a 32-bit instance and a 64-bit instance of SQL Server 2008 Reporting Services side-by-side on a computer, and you uninstall the 32-bit instance, four Reporting Services registry keys are removed. This breaks the 64-bit instance of Reporting Services. The Reporting Services registry keys that are removed when you uninstall the 32-bit instance are:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2008 Web Service\Performance:Counter NamesHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2008 Windows Service\Performance:Counter NamesHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2008 Web Service\Performance:Counter TypesHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2008 Windows Service\Performance:Counter Types

To fix this issue, you can repair the 64-bit instance. Although it is recommended to use repair, you can re-add the registry keys manually by using Registry Editor.

Warning

Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

To re-add the performance registry keys by using Registry Editor

  1. Open the Registry Editor:

    1. Click Start, and click Run.

    2. In the Run dialog box, in the Open box, type regedit.

  2. In Registry Editor, select the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2008 Web Service\Performance

  3. Right-click the Performance node, point to New, and click Multi-String Value.

  4. Type Counter Names and then press ENTER.

  5. Repeat to add the Counter Types registry key in this node.

  6. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSRS 2008 Web Service\Performance

  7. Right-click the Performance node, point to New, and click Multi-String Value.

  8. Type Counter Names and then press ENTER.

  9. Repeat to add the Counter Types registry key in this node.

After you repair the 64-bit instance or re-add the registry keys manually, you can use Performance Monitor to configure the Reporting Services performance objects that you want to monitor.

Top

Error message during upgrade from the February CTP to a later release of SQL Server 2008 Reporting Services when an SSL certificate was installed after the February CTP

When you upgrade SQL Server 2008 Reporting Services from the February CTP to Release Candidate 0 (RC0) or later, and you installed a Secure Sockets Layer (SSL) certificate on the default Web site in Internet Information Services (IIS) after you installed or upgraded to the February CTP version, you receive the following error during upgrade:

"SQL Server Setup failed to retrieve the SSL Certificate Name."

This issue prevents the upgrade from continuing. To avoid this issue, remove the SSL certificate on the default Web site before you upgrade to RC0 or RTM, and then reapply it to the default IIS Web site after the upgrade is successful.

Top

Change History

Updated content

Updated the list of affected operating systems in the section about performance counters not being set after upgrading the operating system on a computer that runs Reporting Services.