Qlik NPrinting upgrade
Starting from Qlik NPrinting 17.0, upgrade options are available for both major feature releases and service releases. The upgrade process preserves all of your data and renders it compatible with the newer version of Qlik NPrinting.
You must follow one of the approved upgrade paths to ensure that the Qlik NPrinting repository is rendered compatible with the newer version of Qlik NPrinting.
If you try to upgrade Qlik NPrinting without following an approved upgrade path, the installer will stop the procedure and display an error message.
The following table shows the supported upgrade paths starting from Qlik NPrinting version 17.0.
Upgrade paths from version 17.0 to 17.2
The following information applies if you are upgrading Qlik NPrinting to a version earlier than 17.3.
A Qlik NPrinting feature release must be upgraded to the next successive feature or service release. A Qlik NPrinting service release must be upgraded to the next successive service release. You cannot upgrade a service release directly to next major feature release. For example, from 17.0.1 you must upgrade to 17.0.2, then to 17.0.3, etc, without skipping any releases.
If the installed version is the final service release before a major feature release, you can upgrade it to the next feature release. For example, 17.0.5 is the final service release of the 17.0 series and you can upgrade it to 17.1.
You can not skip a major feature release. For example, you can not upgrade directly from 17.0.5 to 17.2. The previous feature release 17.1 must be installed before upgrading to 17.2.
from version 17.2 to version 17.3
The following information applies if you are upgrading Qlik NPrinting to version 17.3 or 17.3.1.
Qlik NPrinting 17.3 has increased the number of supported upgrade paths. To upgrade to Qlik NPrinting 17.3.0 you must start from any version of Qlik NPrinting in the 17.2 series. You cannot upgrade to Qlik NPrinting 17.3 from a version older then 17.2. For example, if you have installed Qlik NPrinting 17.1 you must first upgrade it to 17.2 before upgrading to 17.3.
The following upgrade paths are supported:
|Current Qlik NPrinting version||Upgrade to|
from version 17.3 to Qlik NPrinting June 2017 or later
The following information applies if you are upgrading to Qlik NPrinting June 2017 or later.
To upgrade to Qlik NPrinting June 2017 or later you must start from any previous version of Qlik NPrinting in the 17.3 series or later. You cannot upgrade to Qlik NPrinting June 2017 or later from a version older than 17.3. For example, if you have installed Qlik NPrinting 17.1 you must first upgrade to 17.2 and then to 17.3 before upgrading to Qlik NPrinting June 2017 or later.
Qlik NPrinting messaging service upgrade
Starting with Qlik NPrinting 17.2.1, the Qlik NPrinting Server upgrade removes
Repository database backups
The Qlik NPrinting upgrade process will attempt to close the Qlik NPrinting
The Qlik NPrinting upgrade process creates two backups of the repository :
- Backup before updating the repository.
The name is composed by concatenating a timestamp (YearMonthDayTime) with the fixed string _nprinting188.8.131.52_backup_old.zip (for example 201611180947162456_nprinting184.108.40.206_backup_old.zip).
- Backup after updating the repository.
The name is composed by concatenating a timestamp (YearMonthDayTime) with the fixed string _nprinting220.127.116.11_backup_new.zip (for example 201611180947162456_nprinting18.104.22.168_backup_new.zip).
Both backup files are stored in the folder %ProgramData%\NPrinting by default.
For example, if you are upgrading from Qlik NPrinting 22.214.171.124 to 126.96.36.199, Qlik NPrinting creates a backup 201611180947162456_nprinting188.8.131.52_backup_old.zip before making any changes to the repository database, and a backup 201611180947162456_nprinting184.108.40.206_backup_new.zip after upgrading the repository database. If, for any reason, you want to re-install Qlik NPrinting 220.127.116.11, you must restore the backup 201611180947162456_nprinting18.104.22.168_backup_old.zip.
We strongly recommend that you also manually create a backup before upgrading.