Upgrading Report Server
To upgrade an existing Report Server installation, run a newer version of the Telerik Report Server Installer than the installed one.
Telerik Report Server installer replaces all files in the selected installation folder deployed by the previous installer, including the configuration files /Telerik.ReportServer.Web/Web.config and /Services/Telerik.ReportServer.ServiceAgent.exe.config.
The only configuration files in the installation folder that will be preserved after the upgrade are /Telerik.ReportServer.Web/ReportServerAdmin.config, /Telerik.ReportServer.Web/TelerikReporting.config, and /Services/ServiceAgent.config.
This way the previously configured assets storage will be preserved after the upgrade as well as any report generation engine configuration options applied in the /Telerik.ReportServer.Web/TelerikReporting.config file.
The installer has a step that backs up the assets' storage used from the Report Server. This step is optional and turned on by default. We recommend keeping it. On the first run after the upgrade, the Report Server will upgrade the assets storage schema version if necessary. Keep the backed-up assets' storage at least until the Report Server is up and running again.
Before upgrading the Report Server
The MSI installer of the Report Server for the .NET Framework 4.6.2 will suggest making a storage backup. We recommend this as explained below.
Storage Backup
Depending on the changes introduced in new Report Server versions, the assets storage schema version may be upgraded. This upgrade happens automatically either during the installation process while performing the Storage backup, or when the new Report Server version is started for the first time.
The upgraded Storage will not work with previous versions of Telerik Report Server that use an older assets storage schema version.
The assets storage schema version is updated only when necessary, not with each Report Server version. Two consecutive Report Server versions may have the same assets storage schema version.
To ensure you will be able to use the older Report Server after migrating it to a newer version, back up the Storage before upgrading by using the Migration Tool version that matches the pre-upgrade Report Server version.
File Backup
You need to back up your own configuration files, as they will be overwritten by the installation/upgrade process.
For example, if you have changed the Report Server application configuration file, /Telerik.ReportServer.Web/Web.config and/or the Service Agent configuration file /Services/Telerik.ReportServer.ServiceAgent.exe.config (the corresponding appsettings.json files when using Report Server for .NET), you need to back them up before the upgrade and restore them after that.
IIS Settings
The Telerik Report Server settings applied in the IIS console, including the HTTPS bindings and AppPool identity, will be preserved if you are with version R3 2023 SP1 (9.2.23.1114) or later and upgrade to a newer version.
When upgrading from Telerik Report Server 9.2.23.1010 or older, you need to reapply the IIS Settings after the upgrade.
This means that if you need to automatically preserve the IIS Settings, first you need to upgrade to 9.2.23.1114 or later and reapply the settings.
Example:
-
IIS settings will be lost
When upgrading from
9.0.23.118to10.0.24.131When upgrading from
9.2.23.1010to9.2.23.1114 -
IIS settings will be kept
When upgrading from
9.2.23.1114to10.0.24.131When upgrading from
10.0.24.131to10.1.24.605
After upgrading the Report Server
After the upgrade progress has passed, open the Report Server Manager (the Finish button of the installer UI will do that by default). This will intrinsically trigger the upgrade of the assets storage schema version if necessary. When the manager loads the default Reports view of the Manager, this upgrade process has passed successfully.
Open the IIS manager and reapply the web application settings, including the Bindings, noted before the upgrade. Make sure the Telerik Report Server web application is working again.
The Report Server Manager is a web application and it is possible to have its styles and scripts cached by the browser, which may result in unpredictable behavior when upgrading or installing a new version. We recommend clearing the browser cache or force-reloading the page, usually with Ctrl+F5.