Edit this page

Installation

The Report Server web application is installed by a Windows installer which automatically creates a separate web site with its own application pool on the IIS. The application pool runs under the LocalSystem identity and has Enable 32-Bit Applications set to true by default. Note that this setting might cause external entities like ODBC drivers to fail to work with Report Server due to architecture mismatch between the driver and the application.

The installer registers the new web site under port 83 by default. The installation process includes registering and starting of a Scheduler windows service.

Downloading and Installing

You can download the licensed product version from the Telerik Control Panel which you can get from Your Account. The Control Panel is a small Windows utility which will notify you when a new version of the Telerik product(s) you have purchased is available. Once you download the product, run the installer to install it on your machine.

New Versions

The best way is to download the Control Panel from Your Account:

control panel

It automatically detects the latest version and lets you install it for the products you have access to.

Other Product Files and Latest Internal Builds

  1. From Your Account page, go to “Products & Subscriptions” and select the product: latest internal build step 1
  2. Hit the "Download" button: latest internal build step 2
  3. From there select the product file you want to download: latest internal build step 3

Backup

The Report Server storage contains all user assets like reports and scheduled tasks definitions. After a product upgrade, when the Report Server web manager application initially starts, there is a great chance that the Report Server storage schema gets changed as well. This is part of the product evolution and such schema changes get released with the major Report Server releases.

During product update or upgrade, the .msi installer package automatically performs a backup of the storage and approving this step in the install process is highly recommended in order to avoid any eventual data loss during the pending schema change. In order for the automatic backup to kick in, the current version of the product should be R2 2017 (3.1.17.503) or later (as this version introduced the necessary storage migration tool). If this is not the case, we still strongly encourage you to perform manual backup of the storage to eliminate any chance of data loss.

Is this article helpful? Yes / No
Thank you for your feedback!

Give article feedback

Tell us how we can improve this article

close
Dummy