Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
May 7, 2025 10:17:55 AM
May 31, 2023 5:36:32 AM
The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.0.0.
Content
Improvement / Defect | Details |
SHEND-2273 |
|
QCB-28706 |
Upgraded PostgreSQL version to 14.17 to address the pg_dump vulnerability (CVE-2024-7348). |
SUPPORT-335 | Upgraded PostgreSQL version to 14.17 to address the libcurl vulnerability (CVE-2024-7264). |
QB-24990 | Fixed an issue with upgrades of PostgreSQL if Qlik Sense was installed in a custom directory, such as D:\Sense. |
Improvement / Defect | Details |
SHEND-1359, QB-15164: Add support for encoding special characters for Postgres password in QPI | If the super user password is set to have certain special characters, QPI did not allow upgrading PostgreSQL using this password. The workaround was to set a different password, use QPI to upgrade the PostgreSQL database and then reset the password after the upgrade. This workaround is not required anymore with 1.4.0 QPI, as 1.4.0 supports encoded passwords. |
SHEND-1408: Qlik Sense services were not started again by QPI after the upgrade | QPI failed to restart Qlik services after upgrading the PostgreSQL database. This has been fixed now. |
SHEND-1511: Upgrade not working from 9.6 database | In QPI 1.3.0, upgrade from PostgreSQL 9.6 version to 14.8 was failing. This issue is fixed in QPI 1.4.0 version. |
QB-21082: Upgrade from May 23 Patch 3 to August 23 RC3 fails when QPI is used before attempting upgrade. QB-20581: May 2023 installer breaks QRS if QPI was used with a patch before. |
Using QPI on a patched Qlik Sense version caused issues in the earlier version. This is now supported. |
Improvement / Defect | Details |
SHEND-1261: Allow upgrade from the bundled postgres version 12.5 to 14.8 version using QPI | You can now update the embedded Qlik Sense Repository Database from versions 9.6 and 12.5 to version 14.8. (This is due to the following security issues of PostgreSQL) |
SHEND-971: Allow custom Qlik Sense Installation Folder for use with QPI | When Qlik Sense is installed outside of the standardfolder C:\Program Files\Qlik\Sense e.g. (D:\Qlik\Sense), QPI can now be used to migrate the database. |
QB-17384: Users were allowed to create folder names which are not allowed in Windows | Fixed the issue that it was possible to create a folder with the following charaters (/,:,*,?,",<,>,|) which are not approved by Windows. |
To download the Qlik PostgreSQL installer and review the mandatory documentation, see Upgrading Qlik Sense Repository Database from PostgreSQL 9.6 to 12.5.
Improvement / Defect | Details |
SHEND-1106: Support custom install in Qlik PostgreSQL installer | It is now possible to select where to install the Postgres Database. |
SHEND-1066: Add Custom Upgrade | |
SHEND-1125: Default paths not set in Qlik PostgreSQL installer. | Installation and data paths are set to default PostgreSQL paths, instead of default Qlik Sense paths. |
SHEND-1074: Installation sometimes starts when you navigate forward and back in the installation wizard. | |
SHEND-1169: Update gradle plugins for new java version | |
SHEND-1173: Installation fails if the data folder is created inside the installation folder. |
Related Content
Upgrading Qlik Sense Repository Database from PostgreSQL 9.6 to 12.5
Qlik Sense upgrade to November 2022 fails with "An existing standalone PostgresSQL v 12 database has...
Hello everyone,
I am getting this error with the QPI 2.0 version: Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException: Error! Could not parse existing PostgreSQL service parameter: ""E:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin\pg_ctl.exe"" runservice -N "QlikSenseRepositoryDatabase" -D "C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\9.6" -o "-p 4432"! Registry entry exists but file does not exist on disk in path: "E
Does anyone know what could be causing this error and how to solve it?
Hello @esteban_manriquez
Please log a support ticket to have this investigated and potentially logged as a defect.
All the best,
Sonja