Test SQL Server Reporting Services

Prepare the System for Installation

Before you start the installation, make sure you have the following prerequisites set up.

1. UAC (User Account Control) must be disabled for the script to run.
2. A local user in the Reporting Services server with login name erv and password erv or any other password that complies with your security rules. Inform all the software users what that password is and share with Netsmart Systems support if you need help with Reporting Services based reports. This user may have minimum access to the computer; it doesn’t have to belong to any user group in the server – it will be used only for users to have view access to the reports.
3. A computer with access to the Reporting Services server (it can be the Reporting Services Server itself).
4. A Reporting Services Server user and password with Administrative rights.
5. The files in the installation packages.
6. The rs.exe utility. This utility is installed with the Reporting Services and with the Business Intelligence Visual Studio. It is also provided with the installation package.

Install the Script

1. Copy the installation package (entire SSRS folder from downloaded upgrade package) in a temporary folder on the server or the computer with network access to the server. Note: Preserve the folder structure.
2. Run the file Install.cmd (double-click the file). A screen will appear asking your Reporting Services Server information.

Note: If you enter information incorrectly, you can always press Ctrl+C to stop the installation and start again. You will be prompted with the message, “Terminate batch job (Y/N)?” Answer Y to confirm.

1. Enter the Reporting Services server name or IP address when prompted.
2. Enter the user name and password with administrative rights in the Reporting Services server. If you are installing remotely, enter the server name with the user name in the following format:

servername\username

6. Enter the EvolvCS database server name and the database name of EvolvCS system this will apply to.
7. Now you will be prompted for the EvolvCS SQL Server user name and password

At this point, you should have something like the following:

Where:

rs_server – is the name (or IP address) of your Reporting Services Server which may or may not be the same as the database server.

rs_username – is the user name with administrative rights in the Reporting Services Server.

This normally would be your domain account if you have admin rights or local server admin account (on the machine where reporting service is set up).

your_rs_password – is the password for this user

ev_db_server – is your Evolv-CS SQL Server name (or IP address)

ev_db_name – is the name of the Evolv-CS database (like evolv_cs)

db_username – is the SQL server login name for the Evolv-CS database, like "evolvcsuser"

your_db_password – is the password for this user

8. The script will proceed configuring the Reports in the Reporting Services. When it finishes, it will ask, “Press any key to continue…” as displayed below.

9. Once finished, you can verify the installation by going to the Report Manager web page. You may need to login with the administrator user you entered in step 5.

http://rs_server/Reports

10. Navigate through the folders and check if the new reports are there. If you provided the correct server name, user name, and password, it should work.

Identifying errors with the log file

The file RS Scripter Load Log.txt is created with the installation log. If something goes wrong, refer to this file for debugging. This log file tells you when something goes wrong. You can open it while the installation proceeds; this way you can check the progress.

First you will see a header with some debugging information, then the actual installation begins. Each script’s run is grouped in a few lines. The first is the script that is being executed. Next, some information, it can be one or more lines. Then eventually the errors that happened when running the script, it starts with “Error :”. Finally, a line indicating that that script has finished executing. The following is one example:

Running script "EvolvCS\Clients\SomeReport.rdl.rss"

The data set `EvolvCs' refers to the shared data source `EvolvCs', which is not published on the report server.

The textbox `textbox8' extends beyond the right edge of its container.

Error : rsDataSourceNotFound (The data source 'EvolvCS' cannot be found.)

The command completed successfully.

Here you can see in the first line that the SomeReport is being installed. Then, in the next two lines, some warnings are displayed; these do not prevent the installation of the reports. The next line displays an error – it starts with “Error :”. This error indicates that due to some problems about the data source, the report in question could not be installed. The last line informs that the script to install SomeReport has finished the execution.

If no errors are found in the log file, the installation should have succeeded.