Troubleshooting your upgrade

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.

• Repair the missing database

• Fix the QMSQ database ownership information

• Re-create all of the databases

Common error code when an upgrade of patch fails:

• Patch was uninstalled with exit code: -1

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.

• Can't access Hub or Management Console after upgrade

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.

• Fatal exception password authentication failed for user "postgres"

• SeSecurityPrivilege error

• How to create a PostgreSQL database dump file after uninstalling Qlik Sense

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.

• Error 1053: The service did not respond to the start control request in a timely fashion when trying to start the services

• How to change the Qlik Sense Service Account and what to consider

• Manual stop-start order for Qlik Sense services

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.

• Rim node remains offline after upgrade because of certificates

• Rim nod remains offline after upgrade because can't connect to license service

• How to change the Qlik Sense Proxy certificate if the service account does not have local administrative permissions

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.

• Exclude Qlik Sense folders from anti-virus scanning