Troubleshooting an Installation of Reporting Services
This topic lists errors you might encounter while running Setup and describes how to resolve them.
Note If the information in this topic does not resolve your problem, please check the language-specific Readme files located at C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services.
Some complex errors have additional content requirements. The following errors and problems are documented in separate topics. Click on the following links to view the topics. All other errors are documented in the "Miscellaneous Setup Problems" section in this topic.
Miscellaneous Setup Problems
Reboot required if setup fails
You may be required to restart your computer if Setup fails. Specifically, if certain prerequisites are missing, Setup will not continue. In some cases, a reboot is necessary to fully clear the setup process from your system.
SQLSpars.rll file is missing
An error message about a missing sqlspars.rll file may occur when installing Reporting Services on a computer that is running a Spanish or Portuguese version of the operating system. You can work around this error by performing the following steps:
- Create a local folder named C:\MSRS and copy the installation files to the folder. You can use folder names that are different from the ones suggested in these steps as long as the folder names are short and do not include spaces.
- Create a folder named C:\RSInstallTemp.
- Open a command prompt window and run the following command:
msiexec /i C:\MSRS\Setup\bootmsi.dat /lfarmviewcup C:\mylog.log INSTALLDIR=c:\RSInstallTemp
- Ignore all errors.
- After the command completes, run setup.exe.
Report Server Evaluation Edition Stops Working
Reporting Services Evaluation Edition stops working 120 days after the date of installation. When the evaluation period expires, the report server ceases to run or fails on start-up.
Error Installing Performance Monitor Objects
Reporting Services Setup may encounter performance counters that were not removed during the uninstall of a previous instance.
In such a case, the following error message is displayed:
Installing Performance Monitor Objects
You can safely ignore the error and continue Setup.
SQL Setup failed to connect to the database service for server configuration
This error can occur when you install a report server on a computer that is configured to use Terminal Services, and you have selected a remote SQL Server instance to host the report server database. To work around this error, turn off Terminal Services while running Setup.
Setup error 25619
Setup uses IWAM_computername account to configure IIS. Disabling the account results in Setup error code 25619. This error will also occur if you are installing a report server on Windows XP and Distributed Transaction Coordinator service is not running. To work around this error, enable the account or start the service, and then rerun Setup.
Network access error for a local account
In some cases, Setup will return an error that a local account does not have network access. This error can occur if you install Reporting Services on Windows XP or Windows 2000, and the local SQL Server is a named instance. When checking for a local SQL Server instance, Setup compares the computer name to the instance name. If the names do not match, Setup assumes that the SQL Server is not local.
ASP.NET installation or configuration errors
If you receive the error, "ASP.NET version 1.1 is not installed or is incorrectly configured", during Setup, and ASP.NET is already installed, run
aspnet_regiis -i from the %windir%\Microsoft.Net\Framework\v1.1.4322 folder.