Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _
Upgrading Qlik Sense running a standalone/remote PostgreSQL Database or a PostgreSQL Database upgraded with the Qlik PostgreSQL Installer fails with the following error:
The following information has been collected from your system: This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.
Verify that the database is started.
For stand-alone PostgreSQL installations, the database needs to run for the installer to be able to verify its requirements.
The requirement extends to Qlik Sense systems in which the PostgreSQL database has been upgraded with the Qlik PostgreSQL Installer.
Verify that all required databases are created before the upgrade.
See your version of Qlik Sense to verify what databases are required: Databases.
Looking at the Connection String using the Qlik Sense Utility tool (stored underC:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil) verify if the parameter Ssl Mode=Requireis included.
The Qlik Sense installer cannot use SSL encryption for establishing connection to PostgreSQL. When SSL encryption is enabled, the installer does not recognize any already installed PostgreSQL databases, and as a consequence, installation cannot be completed.
The next most common scenario is that the server which Qlik Sense is installed is configured to enforce FIPS policy. Due to a dependency in the install, additional steps are needed to allow the installer to operate in a FIPS environment. Reference article Unable to install Qlik Sense to a remote PostgreSQL database with FIPS enabled for more details on the resolution for this variant of blockers.
Incorrect Database ownership
A previous upgrade failure or inconsistency can cause the QMSQ database ownership to be incorrect. Since the Qlik Sense installer tries to validate the connection to all underlying databases, a failure to do so against any of them will result in a failure to upgrade.