January 2004
© Copyright Microsoft Corporation, 2004. All rights reserved.
The Reporting Services documentation team welcomes your comments about this readme documentation. You can send e-mail feedback using the link below. All feedback must be in English. If you are using a non-English browser and are configuring Outlook Express for the first time, you may need to click the link again after Outlook Express is configured. Users of Asian language browsers should ignore any corrupted characters that appear in the subject line or body of the e-mail message. To submit written feedback about this document, click here: Submit feedback.
This file contains information that supplements the Microsoft® SQL Server™ Reporting Services documentation. Items are organized into two sections: Installation and Configuration Issues, and Known Issues related to ongoing server operations.
Late-breaking information that was not available in time to be included in this readme file will be published on the Microsoft Product Support Services Web site in Microsoft Knowledge Base article 832976.
1.1 Installing from a network share is not supported
1.2 Configuration files and upgrading
1.3 Parameter requirements for running an unattended installation
1.4 Authz.dll prerequisite for Windows 2000 server with SP4
1.5 User account requirement for the SQL Server Agent service
1.6 Requirements for hosting the report server database on a remote SQL Server instance
1.8 Reporting Services on a domain controller requires manual configuration after setup
1.9 Report Designer and upgrading from Beta 2
1.11 Local Service is not supported for the ReportServer Windows service
1.12 Microsoft Data Access Components (MDAC) 2.6 or later must be installed
1.13 ASP.NET version 1.1 must be installed and correctly configured
1.14 Installing Reporting Services with Windows SharePoint Services
2.1 Blank passwords are not supported
2.2 AutoRefresh has a lower limit of 10 seconds
2.3 Report Server system properties are not automatically updated on all members of a Web farm
2.4 RSKeymgmt utility does not delete all encrypted subscription data
2.5 Renaming a computer requires updates to report server settings
Before you run Setup, open the setup documentation to review prerequisites and installation instructions. To open the setup documentation, double-click Rssetup.chm on the product CD-ROM. To ensure a smooth installation, Microsoft recommends that you read the following topics before you start: Hardware Requirements, Software Requirements, System and User Accounts Used During Installation, Preparing to Install.
1.1 Installing from a network share is not supported
Setup error 2755 occurs when you attempt to run Setup from a network share. Note that you can run Setup from a remote computer using a Universal Naming Convention (UNC) path. The error only occurs when you assign a drive letter to a network computer or folder, and then attempt to run Setup using the mapped drive.
1.2 Configuration files and upgrading
Before upgrading, save a copy of all existing configuration files that you have modified. During an upgrade from Beta 2, Setup replaces existing configuration files with newer versions. If you added or removed settings (for example, if you added custom extensions or removed default extensions), your changes will be lost during setup.
If you modified a value for an existing setting (for example, if you changed PollingInterval from the default value to some other value), the value you specified will be copied to the new configuration file.
If you modified rsreportdesigner.config in any way, it will not be overwritten. To complete the upgrade, you must manually copy rsreportdesigner.config from the product CD-ROM (the file is located in the \Setup\x86 folder) to your local system. Except for permission sets, you can paste any custom entries that you want to continue using into the new file. Note that rsreportdesigner.config has been modified for the final release. You cannot use the beta 2 version of rsreportdesigner.config in the final product release.
Configuration files no longer contain permission sets for custom assemblies. If you deployed a custom assembly, you must copy the permission set to a new permission file and then map the file to your assembly. For more information, search Reporting Services Books Online for custom assemblies.
1.3 Parameter requirements for running an unattended installation
When specifying parameters for an unattended installation, be sure to specify RSDATABASELOGFILELOCATION and RSDATABASEFILELOCATION in the same setup operation. If you specify RSDATABASELOGFILELOCATION by itself, a setup error will occur.
When running an unattended setup on a Windows 2000 server, specifying a domain user account for the RSACCOUNT requires that you specify a SQL Server login for RSSQLACCOUNT. Otherwise, you will get an activation error at the end of setup.
1.4 Authz.dll prerequisite for Windows 2000 server with SP4
Some installations of Windows 2000 and Service Pack (SP) 4 may not include the Authorization Framework (Authz.dll) file. If you upgraded to SP4 from a previous version (such as SP3), Authz.dll should be installed. If you installed Windows 2000 with SP4 included (i.e., "slipstream"), Authz.dll is probably missing. This can be corrected by installing SP4 separately or by installing a hotfix as described in Knowledge Base Article 320211. You can obtain the hotfix through Product Support Services (PSS) when you reference this KB article.
Authz.dll is used by Reporting Services to perform authorization checks when the report server executes a scheduled process (such as a subscription or snapshot refresh). If the file is not installed on your computer, a warning is displayed during the prerequisite check in Setup.
1.5 User account requirement for the SQL Server Agent service
SQL Server Agent service must run under a domain user account if you configured the report server to connect to SQL Server using a domain account and Windows authentication (as opposed to a SQL Server login or Service Account). When the report server runs as a domain user, the report server creates SQL Server Agent jobs that are owned by that domain account. Before SQL Server Agent can route a task to the Scheduling and Delivery Processor, SQL Server Agent must have permission to access job information for jobs owned by a domain account. If SQL Server Agent happens to run as a local user account, the service will not have permission to access domain account information, and report subscription and delivery will subsequently fail.
1.6 Requirements for hosting the report server database on a remote SQL Server instance
Setup requires that you specify an authentication method and credentials that the report server uses to connect to the report server database. If you are using a remote SQL Server instance to host the report server database, your choices about which authentication method to use will vary depending on the account that the remote SQL Server service runs under.
To specify these values, use the Report Server Database page of the Setup wizard.
1.7 Install Hotfix 859 if using Service Account credentials to access the report server database on Windows 2003 server
SQL Server Hotfix 859 is required when you install a report server on Windows Server 2003, and you use the Service Account credentials to connect to a local SQL Server instance hosting the report server database. Details about the hotfix are described in Knowledge Base article 821334.
To continue installation, you can do one of the following: apply the hotfix, choose a different SQL Server instance (specifically, one that is located on a different computer), or choose a different credentials type. To download Hotfix 859, go to the Reporting Services web site.
1.8. Reporting Services on a domain controller requires manual configuration after setup
On Windows 2003 server, no manual configuration is necessary in order for Reporting Services to install and run properly on a computer that is also a domain controller. On Windows 2000 server, Reporting Services installs properly on a domain controller, but is not activated. Do the following either before or after running setup in order to properly configure Reporting Services to run on a domain controller:
On both Windows 2000 and Windows 2003, if you are using a Windows account to connect to the report server database, the Windows user must be granted the privilege to log on locally to the domain controller on which the report server is running, even if the report server database is on a different computer. Domain users are not granted this permission by default. If any of the above steps are performed after setup is completed, run rsactivate.exe to activate your installation of Reporting Services.
1.9 Report Designer and upgrading from Beta 2
Report Designer may fail to work properly after uninstalling Beta 2 and upgrading to a release version of Reporting Services. If you upgrade or uninstall Report Designer and install a newer version, be sure to empty your private assembly cache on the computer to which you install Report Designer. In some cases, older versions of Report Designer assemblies are loaded from the cache and the new, updated assemblies are ignored. To clear your private assembly cache, go to C:\Documents and Settings\username\Local Settings\Application Data\assembly (assuming a default installation to the C drive) and delete any files or sub-folders at that location.
1.10 Domain user account requirement for subscriptions and ReportServer Windows service running under Windows 2000 or Windows XP
If the ReportServer Windows service is running under Windows 2000 or Windows XP, you must configure the service to run under a domain account. If you use an account that does not have sufficient domain permissions, subscription delivery will fail when the report server attempts to deliver reports to domain user accounts. The following error occurs when report delivery fails due to authorization and domain access issues: Failure sending mail: The Report Server has encountered a configuration error.
1.11 Local Service is not supported for the ReportServer Windows service
Use of the Local Service account for the ReportServer Windows service is not supported. If you are installing a report server on a Windows XP or a Windows Server 2003 computer, you must choose another account to run the ReportServer Windows service.
1.12 Microsoft Data Access Components (MDAC) 2.6 or later must be installed
Report Server and Report Designer components require MDAC version 2.6 or later. To install either Reporting Services component, you must first download and install MDAC 2.6 or later. To download MDAC, go to the MSDN Downloads Site: Data Access Downloads. System requirements and installation instructions are available with the download.
1.13 ASP.NET version 1.1 must be installed and correctly configured
Report Manager is an ASP.NET application. If you are installing Report Manager, you must have ASP.NET installed and configured. Setup requires that version 1.1.4322 of ASP.NET be registered with IIS. If you are installing Reporting Services on Windows Server 2003, ASP.NET must be running as Network Service. For information about installing and configuring ASP.NET, see the setup documentation.
1.14 Installing Reporting Services with Windows SharePoint Services
On Windows Server 2003, if you install Reporting Services with Windows SharePoint Services, you need to follow some basic steps in order for your system to function properly. For more information, see "Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services" in the setup documentation. You can omit step 3 (increasing the trust level to full trust) in the troubleshooting topic. A modification was made to the default policy file that makes this step obsolete.
2.1 Blank passwords are not supported
All accounts that are used by Reporting Services or Setup must have a valid password. If an account does not have a password, you will get a validation error.
2.2 AutoRefresh has a lower limit of 10 seconds
If you are using AutoRefresh to specify a refresh rate for a report, be aware that there is a lower limit of 10 seconds that is imposed by the report server. If you specify a value lower than 10 seconds, it will be ignored.
2.3 Report Server system properties are not automatically updated on all members of a Web farm
Report server system properties are stored in the report server database and are used by each report server in a Web farm. Each server in a Web farm caches a local copy of the system properties in memory. Modifying system properties (such as SessionTimeout) does not automatically initiate a global update of the system properties for all members. The system properties are not refreshed until the Application Domain is reset (IIS resets) for each member of the Web farm. This process happens periodically, but may not be often enough to enforce immediate changes to system functionality.
2.4 RSKeymgmt utility does not delete all encrypted subscription data
If you are deleting encrypted content because it is no longer accessible, be aware that some encrypted content may remain. Specifically, the rskeymgmt utility does not delete encrypted credentials defined for subscriptions that target a file share delivery. This is the only case where encrypted credentials are not deleted when you run rskeymgmt with the –d option.
You can use Report Manager to identify and update the affected subscriptions. If the Status column in My Subscriptions states "Bad Data", the subscription requires updating. To delete the encrypted settings, open the subscription, respecify the credentials, and then save the subscription.
2.5 Renaming a computer requires updates to report server settings
Renaming a computer causes a corresponding name change for the Web server and SQL Server instance (if it is on the same computer). In some cases, Reporting Services is not functional after a computer name change. If you are running a Windows 2000 server and the ReportServer Windows service runs as Local System, the ReportServer Windows service no longer starts automatically when you restart the computer. If you are running Windows Server 2003, the service will start, but you cannot connect to the report server database. To restore service after a computer name change, follow these steps:
rsconfig -s<NewServerName> -dreportserver -aSQL -uSA -p<SAPassword>
If you are running Windows 2000 server, perform these additional steps:
rsactivate -c"%installdir%\Reporting Services\ReportServer\RSReportServer.config"