Skip to main content

Troubleshooting your upgrade

This section contains links to common problems and solutions based on real user support cases reported in the Qlik Community. When you encounter a problem during a upgrade, there are several steps to take to begin troubleshooting the issue.

Start with the troubleshooting overview section to learn how to investigate problems and find errors in the log files. Here, you'll also find troubleshooting topics that may address your upgrade issue.

Failed upgrade or patch

If the upgrade fails before finishing, there are several possible causes. The most common reason is that a required component is missing. Depending on which version you are upgrading to, you may need to resolve the missing component before continuing.

Common error messages that indicate that you are missing a component:

  • This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities...

  • This version of Qlik Sense requires a 'QSMQ' database for multi cloud capabilities...

  • This version of Qlik Sense requires a 'License' database for license capabilities...

For details on how to resolve the issue, see the links below.

Common error code when an upgrade of patch fails:

Connecting to QMC and the Hub

After you complete the upgrade, you might be unable to connect to the Management Console or the Hub. This is a common problem for users who upgrade from older versions to Qlik Sense November 2017 or later. The most common reason for this issue is that the Qlik Sense Repository Service does not delete soft records in Qlik Sense November 2017 or later. This results in broken references from the repository service. For details on how to resolve the issue, see the link below.

Centralized logging

You might receive a warning or failure due to a communication issue with the logging service. The most common communication issues are with incorrect passwords or SSL encryption. For details on how to resolve the issue, see the links below.

Common error messages when the logging service fails:

  • The Centralized logging setup failed.

  • Could not validate database user.

For details on how to resolve the issue, see the links below.

Common error code when logging service fails:

If the installer Window is missing the centralized logging setup, see centralized logging missing from May 2021 installer to learn about this issue.

Repository service and PostgreSQL database

After completing your upgrade, the repository service might fail to start. The most common reason for this issue is that the repository service is passing incorrect information. For details on how to resolve the issue, see the links below.

Windows user accounts and service credentials

After completing the upgrade, the Qlik Sense services may fail to start. This could be caused by Microsoft Windows updates, authentication problems, or service timeout. For details on how to resolve the issue, see the links below.

Certificates and licenses

Certificates let the services and nodes in your Qlik Sense deployment communicate with each other. After an upgrade, when there are issues with individual nodes, the cause is usually problems with the certificates. For details on how to resolve the issue, see the links below.

Antivirus software

Qlik Sense requires access to certain ports. An upgrade may fail or your deployment may have issues due to anti-virus software preventing Qlik Sense access to required ports. For details on how to resolve the issue, see the link below.