Skip to main content
Qlik Resources
Announcements
Upgrading

ON THIS PAGE

Upgrading

You can upgrade from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later using the Qlik Sense setup program. When upgrading, the previous version is completely replaced by the new version.

To upgrade from Qlik Sense 3.1 SR2 or later with a shared persistence model to Qlik Sense June 2017 or later, see Upgrading from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later.

Warning noteDo not uninstall Qlik Sense before upgrading to Qlik Sense June 2017 or later. If you are upgrading to Qlik Sense June 2017 or later, and you have uninstalled Qlik Sense, see Upgrading to Qlik Sense June 2017 or later after uninstalling Qlik Sense 3.1 SR2 or later .

Qlik Sense June 2017 and later versions do not support the synchronized persistence model. To upgrade from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later and migrate from a synchronized persistence model to a shared persistence model, see Upgrading and migrating from synchronized to shared persistence.

Upgrading from any version of Qlik Sense earlier than 3.1 SR2 to Qlik Sense June 2017 or later cannot be done using the setup program. To upgrade from earlier versions of Qlik Sense with a synchronized persistence model to Qlik Sense June 2017 or later, see Upgrading to Qlik Sense June 2017 or later from Qlik Sense versions earlier than 3.1 SR2.

Information noteWhen you upgrade to a newer version of Qlik Sense, you will not get the option to configure centralized logging in the installer. Instead, if you want to enable centralized logging, you must configure it using the Qlik Logging service. See: Qlik Logging Service
Warning noteQlik Sense November 2017 and later versions do not support soft deleted records. Qlik Sense will clean up all soft deleted records on the first startup of the Qlik Sense Repository Service after an upgrade. For troubleshooting, refer to Failed to remove soft deleted records.
Warning noteDuring upgrade, configuration files are overwritten with the default settings. If a configuration file was manually changed in your previous deployment, you must make sure to restore your customized settings after the upgrade. Once the settings are restored, you must restart the corresponding Qlik Sense services. The following are the most common configuration files: %ProgramFiles%\Qlik\Sense\Repository\Repository.exe.config, %ProgramFiles%\Qlik\Sense\Proxy\Proxy.exe.config, %ProgramFiles%\Qlik\Sense\Scheduler\Scheduler.exe.config, and %ProgramFiles%\Qlik\Sense\ServiceDispatcher\services.conf.
Information noteAny custom manual configurations that you make to the PostgreSQL database must be manually reproduced after the upgrade.

Qlik Sense apps

When you upgrade Qlik Sense, all existing apps need to be migrated to ensure compatibility between the versions. App migration is not performed automatically when starting Qlik Sense. An app with an engine version later than 12.0 is migrated on the fly when you open it in the hub. On the apps overview page in the QMC you can see if there are apps that require manual migration. The text Migration needed is displayed in the Migration column for apps that need to be migrated. The Migration column is not displayed by default. Use the column selector to display the field. Use the Migrate button to perform manual migration.

Multi-node deployments

In a multi-node deployment, all nodes must run the same version of Qlik Sense to be able to communicate with each other. It is recommended to upgrade with all nodes offline, and to start with the central node.

Warning noteWhen upgrading a rim node, ensure that you use the same log-in account as was used for the initial installation of that node. Failure to do so means that the central node will not find the certificates installed on the node and you will need to perform a clean installation of the node.

Qlik Sense Repository Database

Qlik Sense June 2017 and later versions use PostgreSQL version 9.6 for the Qlik Sense Repository Database. If you upgrade in place without uninstalling Qlik Sense the Qlik Sense Repository Database is upgraded to PostgreSQL version 9.6 and your data, and standard settings are carried forward. If you have made custom configurations to your PostgreSQL installation, those must be recreated in the PostgreSQL after upgrade.

PostgreSQL version 9.6 is installed with the latest version of Qlik Sense. If you have uninstalled Qlik Sense but maintained your PostgreSQL database, and you want to upgrade your Qlik Sense deployment, you must create a database dump file and restore the PostgreSQL database manually. You will also need to manually reconfigure any custom parameters.

Information noteThe 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. Workaround: temporarily disable SSL during installation or upgrade.

The PostgreSQL installation included in the Qlik Sense June 2017 or later setup does not include pgAdmin tools. For information about manually installing the PostgreSQL database, see Installing and configuring PostgreSQL.

Upgrading Qlik Sense

Before you upgrade Qlik Sense, do the following:

Do the following:

  1. Stop your Qlik Sense services on all nodes in the deployment.
  2. Upgrade your central node by launching the Qlik Sense setup file (Qlik_Sense_setup.exe) as an administrator.

  3. If an unsupported Qlik Sense root certificate is detected on the central node, the root certificate must be removed as part of the upgrade. You cannot proceed with the upgrade if you do not select to remove the root certificate.

    Select Remove certificate(s) and click Next.

    Warning noteSelecting Remove certificate(s) and clicking Next will delete the Qlik Sense root certificate from this node. The certificate is automatically recreated after the upgrade.

    Make sure that you have backed up your Qlik Sense deployment before you continue

  4. Select Upgrade to upgrade your existing shared persistence deployment.
  5. Accept the license agreement and click Next.

  6. On the Service Credentials page, enter the Username and Password for your Windows Qlik Sense service user account.

    If the user is member of a domain, enter the service account as <domain>\<username>. For more information, see User accounts.

  7. On the Ready to upgrade page, select the appropriate check boxes if you want the setup to create desktop shortcuts and automatically start the Qlik Sense services when the setup is complete, and click Upgrade.
  8. Check that all of the Qlik Sense services have started successfully.

  9. Check the Apps overview page in the Qlik Management Console. The text Migration needed is displayed in the Migration column for apps that require migration, see Migrating apps.

  10. Upgrade the remaining nodes by following the applicable steps above for all nodes in the Qlik Sense cluster.

    If an unsupported Qlik Sense root certificate is detected on non-central node, all Qlik Sense certificates must be removed as part of the upgrade.

    Warning noteSelecting Remove certificate(s) and clicking Next will delete all Qlik Sense certificates from this node. The certificates must be manually redistributed as described in the next step.

    Make sure that you have already upgraded the Central node.

  11. If you removed the Qlik Sense certificates as described in the previous step, perform one of the following two steps depending on your setup.

    • Account running the Qlik Sense services has administrator privileges:

      1. Open the Qlik Management Console (QMC) and redistribute the certificates according to Redistributing a certificate.

      2. Restart all the services on the node and make sure they are using the newly distributed certificates.

    • Account running the Qlik Sense service does not have administrator privileges:

      1. In the command prompt, navigate to the install location, for example Program Files\Qlik\Sense\Repository, and run Repository.exe -bootstrap.
      2. When the Waiting for certificates to be installed.. message is displayed, redistribute the certificates according to Redistributing a certificate.
      3. Once the bootstrap mode has terminated, start the Qlik Sense Service Dispatcher, then start the Qlik Sense Repository Service (QRS), and finally the remaining Qlik Sense services.