Qlik Sense Upgrade fails: Initializing 'QSMQ' database

[Mario_Petre]

A Qlik Sense Enterprise on Windows upgrade may fail with the error: 

Initializing 'QSMQ' database.

The error can be found in the installer log (see How to read the installation logs for Qlik products ).

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, failing to do so against any of them will fail to upgrade.

Example error message:

This version of Qlik Sense requires a 'SenseServices'" database for multi cloud capabilities. Ensure that you have created a 'SenseServices' database in your cluster before upgrading.

Resolution

1. Stop the install
   
   
2. Download the latest version of PGAdmin from www.pgadmin.org
   
   
3. Follow instructions in the following article to connect to the Database: Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense
   
   
4. Select the QSMQ database and expand it (to make sure the connection is established)
   
   
5. Go to Tools -> Query 
   
   
6. Paste the content below and execute the queries. These queries will re-establish correct ownership of the QSMQ database and allow the upgrade to complete:
   

   ALTER DATABASE "QSMQ" OWNER TO qliksenserepository; --sets qliksenserepository as owner of the QSMQ database
   GRANT TEMPORARY, CONNECT ON DATABASE "QSMQ" TO PUBLIC;
   GRANT ALL ON DATABASE "QSMQ" TO postgres;
   GRANT CREATE ON DATABASE "QSMQ" TO qliksenserepository;​

   
   NOTE: This can be performed while all other services are running, since it does not affect any other component in the Repository. Remote database services must be running during the upgrade process.
    
7. Start the install again

Related Content:

Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _ 

[Ken_T]

does this procedure still need to be done on current versions of qlik ?

[Sonja_Bauernfeind]

Hello @Ken_T The root cause (ownership changed) can still occur on newer versions of Qlik Sense (or may have been changed intentionally or by accident). In both these cases, the solution here still applies.

I will rewrite the article to be clearer that we are more so talking about the root cause, rather than an upgrade from one specific version to the other.

All the best,
Sonja