Reporting Services Tip #2:
The easiest way to install Reporting Services is to have the Report Server and SQL Server on the same server. It's the easiest way, but it certainly is not the best. IIS should not be installed on the database server for performance reasons. Now this isn't true for small systems, but I rarely work on small systems so this is a general rule for me. Due to this rule, the Report Server must be installed on a different server as it relies on IIS. And yes this way requires the Report Server to be licensed as well as SQL Server.
During the installation of the Report Server, you may receive the following error when SQL Server is not installed on the same server:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
This error occurs when the installation is trying to connect to the SQL Server to install the databases used by Reporting Services. You might be wondering why it doesn't just use the account that you specified in the installation wizard, but that account isn't used for the installation but rather for Reporting Services when it is installed. By default the credentials of the person logged into the server is what is used for installing the databases. I'm not sure why I have received the error as my account has local admin privileges on the database server and sysadmin fixed server role in SQL Server. For some reason, the credentials don't get passed correctly as I see from SQL Profiler the NT AUTHORITY\ANONYMOUS account trying to log in.
To get around this error, you can specify a SQL account (readme file says you can use Windows account but I've only had success with a SQL account) instead. You do this from the command line or by modifying template.ini file. Here is the command line way:
setup /i “D:\setup\rsrun.msi“ RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
Change the path for rsrun.msi if needed.
For the template.ini file way, there are two lines that will need to be changed:
There are two lines that will need to be changed in the template.ini file:
The template.ini file is located at the root of where you are installing Reporting Services from. If you are running this from a CD, you might find it easier to use the command line way as you won't be able to modify the file on the CD.
I've specified the sa account in both ways. It can be any account that has sysadmin privileges.
For Reporting Services service pack 1, you must do the command line way as there is no template.ini file:
sp1setup RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
You can not pass these parameters to the self-extracting sp1 file (SQL2KRSSP1-ENG.EXE). You must manually extract the files, then run the command line option.