The max concurrent reloads can be configured in the Qlik Sense Management Console.

1. Open the Qlik Sense Management Console
2. Navigate to Schedulers 
3. Enable the Advanced section (if not already on by default)
4. Set the required max concurrent reloads
   
   
   

    

IMPORTANT TO REMEMBER

• A reload node can run NumberOfCores - 2 
  
  This means: If your reload node has 8 CPU Cores, it can run 6 concurrent reloads at its maximum.
  
  Use the guideline (NumberOfCPUCores - 2) when performing capacity planning on the possible amount of concurrent scheduled reloads.
  
  
• The cores can be physical cores or virtual cores; any CPU cores Qlik Sense can "see".
  
  
• While a reload task typically consumes one core, this is not a hard rule. It can require multiple cores.
  
  
• Allowing more parallel reloads than CPU cores available does not improve the runtime of concurrent tasks. The reload node's resources will deplete. 
  
  This also means: With more parallel reloads than cores the probability for total starvation increases since the QIX engine is CPU hungry and other processes (for example, the operating system) might not get enough CPU cycles to perform their duties.
  
  
• Each running reload is loaded into RAM. This means that the average RAM footprint grows with more parallel reloads.
  
  
• Qlik Sense will queue scheduled reloads when system resources reach their threshold 
  
  
• To validate that environment needs proper capacity planning, go to C:\ProgramData\Qlik\Sense\Log\Scheduler\Trace\<Server>_System_Scheduler.txt, an example log shows below:
  
  

  <ServerName>_System_Scheduler.txt
  Domain\qvservice    Engine connection released. 5 of 4 used 
  Domain\qvservice    Engine connection 6 of 4 established 
  Domain\qvservice    Request for engine-connection dequeued. Total in queue: 25

Concurrent settings

Use the "Max concurrent reloads" to limit the maximal concurrent tasks can be run at same time on current node. By default, it's set to 4, which means only 4 tasks can be run at same time on this node.

When the 5th task comes in:

1. It will be queued by sequence. 
2. The queue has a time setting, which will eliminate (erase) a queued task if the timeout limit reaches. By default, it's set to 30 mins, in this case, if none of the first 4 tasks finishes in 30 minutes after the 5th task comes in, then the 5th task will be cancelled due to timeout. It has to be triggered again (manually or next scheduled time slot).
3. Once one of the 4 running tasks finishes, the 5th task will be executed on this node if it's not timed out.
4. If you set timeout to 0, this will make the queue never timeout.
5. It's suggested not to run more than 10 concurrent reloads at once, unless the schedular node has an extreme amount of resources dedicated to it.
6. If there is low memory or cores available on the node, then some tasks may kick off however take several hours to complete. Adding resources to the node running the reloads is suggested.

Multi-node deployment

On a multi-node deployment, tasks will be balanced from the manager node to any node(s) designated as workers.

It's highly advised to check if the central node configured is set to Manager and Worker or Manager. When set to Manager, it will send all reload jobs to the reload/scheduler nodes, as it should. However if a central node is set to Manager and Worker, this means the Central node will also be involved in performing reloads. This is not recommended. 

The work flow looks as follows:

1. Manager node receives a new task execution request.
2. Manager node checks the resource availability on each of the worker nodes. 
3. Manager node assigns this task to the node with the lowest number of running tasks per "Max concurrent reloads" setting.

The improvement to track the Max concurrent reloads can, if desired, be disabled. This reverts Sense to an older load balancing method that relies only on CPU usage. 

To disable the setting:

1. Open the Scheduler.exe.config, which by default is located in: C:\Program Files\Qlik\Sense\Scheduler\Scheduler.exe.config
2. Set DisableLegacyLoadBalancingBehavior setting to false
3. Restart Qlik Sense Scheduler Service
4. Repeat these actions on each node of the cluster running the Qlik Sense Scheduler Service

Example

In our example, we allow one concurrent reload, but we assume that two reloads are executed at the same time.

• If Task A is executed first, Task B is queued.
• If Task A is executed first and then fails, Task B is executed after the failure.
• After Task A's failure, Task A is queued and will execute after Task B has finished.

How to purchase

You can purchase Qlik Replicate, Qlik Compose, and Qlik Enterprise Manager by contacting a local sales office.

How to obtain the license

Once you have completed the order and a deal has been signed, a license is delivered by email. You will receive a license.txt file. This file contains details such as the product expiration date (if any).

This usually happens within a day of Qlik receiving the order.

Where do I find my license?

If you lose access to the email holding the license, you can instead log on to the Qlik Support Portal an access the original case which includes your license details.

You can also find your license directly in the product after you have licensed it.

What does my license include?

Your license will allow you to:

• Run tasks using the endpoints specified. Example, if you have purchased an Oracle endpoint, you will be able to run tasks using an Oracle endpoint. 
• Grant you general access (not able to use the tool for QEM nor Compose)

To get a better understanding of what your individual license allows, review your license.txt file.

Qlik Replicate: 

license_type= (evaluation or permanent)
licensed_to= (your company name)
licensed_by= (the Qlik region responsible for providing the license)
serial_no= (serial internal reference)
expiration_date= (date of expiration)
hosts= (host names in which Replicate will run. If blank, means that any host can run)
source_types= (the source endpoints purchased by customer)
target_types= (the target endpoints purchased by customer)
features= (additional features)
version= (version of Replicate)
issue_date= (issue date)
checksum= (check sum so the engine can check validity)

Qlik Compose

Will in addition include: 

host_role: (DEV, TEST, PROD or “*” for all)
source_db_types: (applicable for Compose for Data Warehouses only)
dwh_type: (Databases that’ll be used as DWH)
dl_type: (Databases that’ll be used as DL)
number_of_dms: (total number of Data Marts)
number_of_developers: (available if host_role is DEV)
managed_dwh_size: (size of the DWH)

Qlik Enterprise Manager

Similar to Qlik Replicate.

There is one license for Qlik Enterprise Manager Monitoring and another license for Qlik Enterprise Analytics. 

Please note that in order to have Qlik Replicate servers added to your Qlik Enterprise Manager monitoring, they need also to have a valid license, otherwise you will get an “Unauthorized” error when adding a Qlik Replicate server.

How to I extend or modify my license?

Qlik Replicate allows you to modify your license directly through the Qlik Replicate UI. See Requesting a license.

How do I apply the Qlik Replicate, Qlik Compose, or Enterprise Manager license?

• Qlik Replicate: Registering a license 
• Qlik Enterprise Manager: Replication Management license 
• Qlik Compose: License settings 

You can also apply licenses to Qlik Replicate servers programmatically by using the QEM API REST calls as seen in PutServerLicense 

Can I apply the same Qlik Replicate license on DEV, QA, and Production?

Yes, you can apply the same license on all three environments. 

The Upgrade of Qlik Sense Enterprise for Windows fails on the Qlik Dispatcher Service with:

ERROR: schema "MobilityRegistrarService" already exists
ERROR:  schema "qlik_notifier_service" already exists

Environment

• Qlik Sense Enterprise on Windows 

Resolution

The solution to this issue requires modifications to the database. Prior to applying the solution, take a backup. See Backup and Restore.

To resolve this, we will rename the 'qlik_mobility_registrar_service' (i.e. qlik_mobility_registrar_service_old) as well as the 'qlik_notifier_service' schema prior to performing the installation/upgrade.

This will allow for the creation of the schema. In multi-node environments, it is suggested to rename the schema prior to each rim node installation/upgrade.

To rename the schema, perform the following steps:

1.  Log on to the server running the PostgreSQL server
2. Use pgAdmin to access the database (Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinting)
3. Expand the SenseServices database so that Schemas is displayed and then expand Schemas so that the qlik_mobility_registrar_service schema is displayed
4. Right-click the qlik_mobility_registrar_service and choose Properties
5. Rename the qlik_mobility_registrar_service and click Save (i.e.  qlik_mobility_registrar_service_old)
6. Repeat 4 to 5 for qlik_notifier_service.
7. Run the Qlik Sense server installer on the Rim node

Cause 

The upgrade from November 2019 to February 2020 failed on the dispatcher service with the following error on the installation log:

CAQuietExec:  MobilityRegistrarService configuration started.
CAQuietExec:  WARNING: Skiping the database initialization. No superuser or password 
CAQuietExec:  specified.
CAQuietExec:  Creating schema 'qlik_mobility_registrar_service'.
CAQuietExec:  True
CAQuietExec:  Error executing database command "CREATE SCHEMA 
CAQuietExec:  "qlik_mobility_registrar_service" AUTHORIZATION "qliksenserepository"": ERROR: 
CAQuietExec:   schema "qlik_mobility_registrar_service" already exists
CAQuietExec:  At C:\Program Files\Qlik\Sense\MobilityRegistrarService\install\install-utils\P 
CAQuietExec:  ostgres.ps1:113 char:11
CAQuietExec:  +           throw  "Error executing database command  ...
CAQuietExec:  +           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CAQuietExec:      + CategoryInfo          : OperationStopped: (:) , Exception
CAQuietExec:      + FullyQualifiedErrorId : Error executing database command "CREATE SCHEMA  
CAQuietExec:     "qlik_mobility_registrar_service" AUTHORIZATION "qliksenserepository"": ER  
CAQuietExec:    ROR:  schema "qlik_mobility_registrar_service" already exists
CAQuietExec:   
CAQuietExec:  Error 0x80070001: Command line returned an error.
CAQuietExec:  Error 0x80070001: QuietExec Failed
CAQuietExec:  Error 0x80070001: Failed in ExecCommon method
CustomAction CA_SetupQMR returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

The Qlik Sense on Windows Content Monitor is intended for Qlik Administrators. Its purpose is to monitor and analyze your Qlik Sense content, including app usage, resource consumption, and data sources. This helps with governance, optimization, and identifying unused content.

Requirements

• Platform: Qlik Sense Enterprise on Windows
• Version: November 2025 onwards 
• Availability: Bundled with installation from version November 2025 onwards
• If you are running previous versions of Qlik Sense Enterprise on Windows, the Content Monitor is also available on Qlik's Downloads page here: Content Monitor (download page)
  • This must be manually installed, and a weekly reload is recommended.
  • The downloaded version is supported from Qlik Sense version Feb 2020.

Core Documentation

All technical details can be found in the two attached documents. These are your primary resources.

Qlik Sense Content Monitor User Guide

• • What it covers: A detailed, sheet-by-sheet explanation of the entire app. It describes what every KPI, chart, and table means for sections like "Weekly Summary," "Snapshot," "Applications," "Sessions," "Task Executions," "File Inventory," and "Infrastructure."

  • Use Case: 

    • Guiding a customer on how to read and interpret the data.

    • Answering customer questions like, "What does the 'Session Concurrency' sheet show?" or "How do I read the 'File Inventory' sheet?"

  • See the attached Qlik Sense Content Monitor User Guide

Configuration Guide

• • What it covers: This is the primary guide for setup and reload issues. It contains:

    • Detailed definitions for all script parameters (e.g., vCentralNodeHostName, vVirtualProxyPrefix, vServerLogFolder).

    • Performance tuning options (e.g., vFileScanMaxDuration, vAppRetrievalLoop, exclusion lists).

    • A "Trial Mode" section is used for troubleshooting initial reload failures.

    • A "Troubleshooting" section.

  • Use Case:

    • New installations.

    • Troubleshootings.

    • Tuning performance for long reloads.

  • See the attached Qlik Sense Content Monitor Configuration Guide

Environment

• Qlik Sense Enterprise on Windows

Do Qlik Products support the use of Standalone Managed Service Accounts (GMSA)?

At this time, QlikView, Qlik Sense Enterprise on Windows, and Qlik NPrinting do not support the use of managed service accounts.

For general service account requirements, see:

QlikView Service Account Requirements 
Qlik Sense Enterprise on Windows Service Account Requirements 
Qlik NPrinting user account requirements 

Environment

Qlik Sense Enterprise on Windows 
Qlik NPrinting 
QlikView 

Qlik Data Gateway is shown as disconnected. Reviewing the Qlik Data Gateway logs shows:

System.Net.WebSockets.WebSocketException (0x80004005): The server returned status code '401' when status code '101' was expected.

Resolution

The error indicates Qlik Data Gateway may not be installed on a dedicated machine, that the time shared between hosts may be incorrect, or that the setup was not completed correctly.

Do not install Qlik Data Gateway on the actual server or on a server that hosts Qlik Sense Enterprise on Windows or, for example, Qlik Data Transfer.

Local Time on one host

Verify that both hosts use the same time zone and their times are aligned.

If the Windows server time is unaligned (due to, for example, an internal battery issues), the Direct Access Gateway will disconnect.

Incorrect setup

In rare cases, Qlik Data Gateway may not have been set up correctly. In this case, follow the below instructions on how to perform a clean re-install:

1. Uninstall Qlik Data Gateway.
   
   
2. Restart your server.
   
   
3. Reinstall Qlik Data Gateway but do not start the Qlik Data Gateway service and do not change the service account.
   
   
4. Run this below command in an elevated command prompt and from C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent
   
   connectoragent qcs set_config --tenant_url XXXX.YYYY.qlikcloud.com
   
   Where XXXX= is your Tenant Name and YYYY= is your Tenant Region.
   
   
5. Run:
   
   connectoragent qcs generate_keys
   
   
6. Run:
   
   connectoragent qcs get_registration
   
   
7. Copy the key and go to your Tenant's Management Console and data-gateway URL (example: https://YOURTENANTNAME.YOURREGION.qlikcloud.com/console/data-gateway/)
   
   
8. And create your deployment as described in Installing Qlik Data Gateway - Direct Access
   
   
9. After all the above is finished, start the Qlik Data Gateway service.

Related Content 

System requirements | Qlik Cloud Help 

Environment

Qlik Data Gateway  

In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).

For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.

Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.

Index

• Supported Scenarios
• Upgrades
• New installs
• Requirements
• Known limitations
• Installing anew Qlik Sense Repository Database using PostgreSQL
• Qlik PostgreSQL Installer - Download Link
• Upgrading an existing Qlik Sense Repository Database
• The Upgrade
• Next Steps and Compatibility with PostgreSQL installers
• How do I upgrade PostgreSQL from here on?
• Troubleshooting and FAQ
• Related Content

Video Walkthrough

Video chapters:

• 01:02 - Intro to PostgreSQL Repository
• 02:51 – Prerequisites
• 03:24 - What is the QPI tool?
• 05:09 - Using the QPI tool
• 09:27 - Removing the old Database Service
• 11:27 - Upgrading a stand-alone to the latest release
• 13:39 - How to roll-back to the previous version
• 14:46 - Troubleshooting upgrading a patched version
• 18:25 - Troubleshooting upgrade security error
• 21:15 - Additional config file settings

Supported Scenarios

Upgrades

The following versions have been tested and verified to work with QPI: 

Qlik Sense February 2022 to Qlik Sense November 2024.

If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.

New installs

The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.

Requirements

• Review the QPI Release Notes before you continue

• Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:

  • Uninstall all patches before using QPI (see Installing and Uninstalling Qlik Sense Patches) or
  • Upgrade to an IR release of Qlik Sense which supports QPI

• The PostgreSQL Installer can only upgrade bundled PostgreSQL database listening on the default port 4432.
• The user who runs the installer must be an administrator.
• The backup destination must have sufficient free disk space to dump the existing database  
• The backup destination must not be a network path or virtual storage folder. It is recommended the backup is stored on the main drive. 
• There will be downtime during this operation, please plan accordingly
• If upgrading to PostgreSQL 14 and later, the Windows OS must be at least Server 2016

Known limitations

• (Limitation removed in QPI 2.1 | Release Notes) Cannot migrate a 14.17 embedded database to a standalone
• (Limitation removed in QPI 2.1 | Release Notes) Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• The installer itself does not provide an automatic rollback feature.

Installing a new Qlik Sense Repository Database using PostgreSQL

1. Run the Qlik PostgreSQL Installer as an administrator 
   
   
2. Click on Install 
   
   
3. Accept the Qlik Customer Agreement 
   
   
4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 
   
   
5. Set your Database superuser password and click Next
   
   
6. Set the database installation folder, default: C:\Program Files\PostgreSQL\14

   Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

7. Set the database data folder, default: C:\Program Files\PostgreSQL\14\data

   Do not  use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

8. Review your settings and click Install, then click Finish
   
   
9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.
   
   The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.
   
   
10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  
    
    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 
    

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer Release Notes

Upgrading an existing Qlik Sense Repository Database

The following versions have been tested and verified to work with QPI (1.4.0): 

February 2022 to November 2023.

If you are on any version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade.  From Qlik Sense August 2023 a 9.6 update is blocked.

The Upgrade

1. Stop all services on rim nodes 
   
   
2. On your Central Node, stop all services except the Qlik Sense Repository Database 
   
   
   
   
3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 
   
   
   
   
4. Highlight the database and click Upgrade 
   
5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (b) Next.
   
   
   
   
6. Provide your existing Database superuser password and click Next.
   
   
7. Define your Database backup path and click Next.
   
   
   
   
8. Define your Install Location (default is prefilled) and click Next.
   
   
   
   
9. Define your database data path (default is prefilled) and click Next.
   
   
    
10. Review all properties and click Upgrade.
    
    The review screen lists the settings which will be migrated. No manual changes are required post-upgrade.
    
    
    
    
11. The upgrade is completed. Click Close.
     
12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.
    
    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 
    
    
    
    You will also find a new postgresql-x64-14 service. Do not rename this service. 
    
    
    

     

13. Start all services except the Qlik Sense Repository Database service. 
    
    
14. Start all services on your rim nodes.
    
    
15. Validate that all services and nodes are operating as expected. The original database folder in C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
    

     

16. Uninstall the old Qlik Sense Repository Database service.

    This step is required. Failing to remove the old service will lead the upgrade or patching issues.

    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the appropriate msi file.
       
       
       
       If you were running 9.6 before the upgrade, search PostgreSQL.msi
       If you were running 12.5 before the upgrade, search PostgreSQL125.msi
       
       
    3. The msi will be revealed.
       
       
    4. Right-click the msi file and select uninstall from the menu.
       
       
       
       
    
    
17. Re-install the PostgreSQL binaries. This step is optional if Qlik Sense is immediately upgraded following the use of QPI. The Sense upgrade will install the correct binaries automatically. 
    

    Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts. 

    If you do not immediately upgrade:
    
    
    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the .msi file appropriate for your currently installed Qlik Sense version
       
       
       
       For Qlik Sense August 2023 and later: PostgreSQL14.msi
       Qlik Sense February 2022 to May 2023: PostgreSQL125.msi
       
       
    3. Right-click the file
    4. Click Open file location
       
       
       
       
    5. Highlight the file path, right-click on the path, and click Copy
       
       
       
       
    6. Open a Windows Command prompt as administrator
       
       
    7. Navigate to the location of the folder you copied
       
       Example command line: 
       
       cd C:\ProgramData\Package Cache\{GUID}
       
       Where GUID is the value of the folder name.
       
       
    8. Run the following command depending on the version you have installed: 
       
       Qlik Sense August 2023 and later
       
       msiexec.exe /qb /i "PostgreSQL14.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       Qlik Sense February 2022 to May 2023
       
       msiexec.exe /qb /i "PostgreSQL125.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       This will re-install the binaries without installing a database. If you installed with a custom directory adjust the INSTALLDIR parameter accordingly. E.g. you installed in D:\Qlik\Sense then the parameter would be INSTALLDIR="D:\Qlik\Sense".
       
       
18. Finalize the process by updating the references to the PostgreSQL binaries paths in the SetupDatabase.ps1 and Configure-Service.ps1 files. For detailed steps, see Cannot change the qliksenserepository password for microservices of the service dispatcher: The system cannot find the file specified.

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

Next Steps and Compatibility with PostgreSQL installers

Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.

Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads. 

How do I upgrade PostgreSQL from here on?

See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.

Troubleshooting and FAQ

1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:
   
   C:\Users\Username\AppData\Local\Temp\2
   
   A backup of the original database contents is available in your chosen location, or by default in:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\X.X
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
   
   
2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:
   
   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.
   
   See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.
   
   To resolve this, start the postgresql-x64-XX service.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

Related Content

Qlik PostgreSQL installer version 1.3.0 Release Notes  
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades 

When restarting the services for Qlik Sense Enterprise, bundled extensions disappear from the system. The files are missing from the service cluster extension folder and the apps that use those extension are now showing problems. Reinstalling the extensions works, but at the first reinstall, they get removed again.

Environment

•  Qlik Sense Enterprise on Windows, any

Resolution

This usually happens for obsolete extensions that are no longer supported in the current version of Qlik Sense Enterprise. Usually, the functionality of these extensions was replaced by product features. So, apps should be redesigned to use the new features, in order to have a fully supported functionality.
If they are needed for a transition period, following the following steps will prevent the automated deletion.

1. edit the .qext file for each of the affected extensions (they are in the Service Cluster Folder --> StaticContent ---> Extensions ---> folder name of the extension )
2. replace the line:
   
   "installer": "QlikExtensionBundler"
   
   with
   
   "installer": "none"

By doing this, they will not be detected as unsupported extensions, and therefore not removed.

Following a QlikView Server upgrade:

When attempting to generate an NPrinting report by clicking on the Qlik NPrinting On-Demand Extension in the QV IIS Accesspoint, this may result in the following error:

On-demand Compilation Error: Failed to load resource

The error is only encountered if the QlikView AccessPoint is hosted by Microsoft IIS. The built-in QlikView Ajax AccessPoint is not affected.

Resolution

The problem can be avoided by following the upgrade instructions documented in the QlikView Release Notes.

However, if you have already performed the QlikView Upgrade and did not follow the steps in the release notes above, to remedy the issue post-upgrade:

1. Run the QlikView installer or modify the QlikView installation
2. Choose to repair the installation, repairing only the QlikView IIS Server Settings component

Cause

Inspecting the QlikView server file system will show the following files as missing DLLs:

Location:

• C:\Program Files\QlikView\Server\QlikViewClients\QlikViewAjax\bin

DLLs:

• Microsoft.IdentityModel.Abstractions.dll
• Microsoft.IdentityModel.JsonWebTokens.dll
• Microsoft.IdentityModel.Logging.dll
• Microsoft.IdentityModel.Tokens.dll
• Newtonsoft.Json.dll
• System.IdentityModel.Tokens.Jwt.dll

Internal Investigation ID(s)

SUPPORT-10536

Environment

• QlikView upgraded to September 2025 or a later version
• QlikView IIS Settings service 
• Qlik NPrinting On-demand

This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.

If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.

Content

• Requirements:
• Preparation
• Upgrading to a later service release
• Upgrading to a new major PostgreSQL release

Requirements:

• Only upgrade to a supported version of PostgreSQL. See the Qlik Sense Enterprise on Windows System Requirements for details. 
• This guide covers deployments where PostgreSQL has been installed separately or previously unbundled using the Qlik PostgreSQL installer. 

This document covers the following scenario:

• Windows Server OS. The use of Linux, in managed cloud deployments or on-prem, is not covered. 
• Generic PostgreSQL deployment. Stream replication, SSL, or any other advanced configuration are not covered.

Preparation

Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.

• Qlik Sense Repository Database (from PostgreSQL database server)
• Qlik Sense share folder
• Qlik Sense CA-signed certificates

Upgrading to a later service release

These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8). 

1. Download the PostgreSQL installer from them PostgreSQL site
2. Stop the Qlik Sense Enterprise on Windows services. Leave your standalone PostgreSQL database running.
3. Run the PostgreSQL installer and follow the instructions.
4. Start the Qlik Sense Enterprise on Windows services.

No further steps are required.

Upgrading to a new major PostgreSQL release

If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14. 

1. Download the PostgreSQL installer from them PostgreSQL site
   
   
2. Run the installer
   
   During install:
   
   
   • Install the database on the standard 5432 port. 
     
     This allows us to have 12 running on the Qlik Sense default 4432 port and the 14 instance on 5432.
     
     
   • Set the same password as the one currently in use with the version 12 PostgreSQL instance. 
     
     
3. Open a Windows File explorer and create a backup folder, such as C:\backup 
   
   
4. Backup your version 12 database 
   
   This step is crucial. You may have already backed up your site, but in this step we will create the specific backup we will use to migrate your database, using a modified command.
   
   To do so:
   
   
   1. Stop all Qlik Sense Enterprise on Windows services on all nodes. Leave postgresql-x64-12 service (your current repository) running
      
      
   2. Stop postgresql-x64-14 (your newly installed PostgreSQL instance)
      
      
   3. Open a Windows Command Line (CMD) as administrator
      
      
   4. Run:
      SET PGPASSWORD=postgrespassword (replace this with the actual password)
      
      
   5. Run:
      cd “C:\Program Files\PostgreSQL\12\bin”
      
      
   6. Run
      pg_dumpall.exe -h localhost -U postgres -p 4432 -f c:\backup\backup_db.sql
      
      
   7. Follow the onscreen instructions and wait until the backup is finished
      
      Note: If you are prompted to input the password (even if it was previously entered correctly), you will need to modify pg_hba.conf. 
      
      Location: C:\Program Files\PostgreSQL\12\data\pg_hba.conf
      
      Change md5 to trust and restart the postgresql-x64-12 service. See Changing the Database Superuser Password without Qlik Sense Installed for details.
      
      Once the backup has completed, revert back to md5.
      
      
5. Migrate from 12 to 14
   
   We are now moving our Qlik Sense repository from the earlier release of PostgreSQL into the new one.
   
   
   1. Start the postgresql-x64-14 service
      
      
   2. Stop postgresql-x64-12
      
      
   3. Open a Windows Command Line (CMD) as administrator
      
      
   4. Run:
      cd “C:\Program Files\PostgreSQL\14\bin”
      
      
   5. Run
      psql -h localhost -U postgres -p 5432 -f c:\backup\backup_db.sql
      
      
   6. Follow the onscreen instructions.
      
      Note: If you receive the error password authentication failed for user "postgres", (even if it is correct), you will need to modify pg_hba.conf. 
      
      Location: C:\Program Files\PostgreSQL\14\data\pg_hba.conf
      
      Change scram-sha-256 to md5 and restart the postgresql-x64-14 service  and redo step e). See Changing the Database Superuser Password without Qlik Sense Installed for details.
      
      
6. With the import finished, copy the following two files from your old 12 data folder into your new 14 data folder:
   
   
   • pg_hba.conf 
   • postgresql.conf 
     
     
7. Open postgresql.conf and verify that the port is set to 4432 (the standard Qlik Sense port)
   
   
8. (If not done already) stop the postgres-x64-12 service
   
   
9. Restart the postgres-x64-14 service
   
   
10. Start all Qlik Sense services
    
    
11. Once you have confirmed all functionality and tested, uninstall PostgreSQL 12. This can be done directly from the Windows Control Panel and Programs and Features

Related Content:

Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer 
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version 
Changing the Database Superuser Password without Qlik Sense Installed 

Installing the QlikView Plugin with the executable file and parameters /S /v /qn doesn't work.
The system is installing but after the installation the software isn't available on the target system.

Environment:

• QlikView Desktop, all versions
• QlikView IE Plugin, all versions

Resolution:

Note1: The same procedure below can be done for QlikView Desktop .exe file
Note2: Newer versions of QlikView installation includes a 64-bit version of the QV IE Plugin, by default.

1. First you'll need to extract the msi file from the exe file. 

2. Start the installation file. The QlikView installation will come op with the following dialog: 

3. Do not close the dialogue box. Now you have to move to the user temp folder to pick up the .msi file. 

QVPlugin:

QlikView:

4. Copy the .msi file to your target location. (e.g C:\)
5. Now you can close the dialog box.
6. Once the .msi file has been extracted. Press Start -> Run and enter the following command:

msiexec /i "C:\QVPluginSetup.msi" ALLUSERS=1 /quiet

 7. Another example with the QlikView msi:

qlikviewx64.msi REINSTALL=ALL REINSTALLMODE=vomus

Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.

The behaviour began after an upgrade of Qlik Sense Enterprise on Windows. 

Fix version:

This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.

Solution for August 2023 and above:

Enable QmcTaskTableCacheDisabled.

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify or add the QmcTaskTableCacheDisabled flag for these values to true
   
   {"contentHash":"CONTENTHASHHERE","originalClassName":"FeatureToggle","flag":"QmcTaskTableCacheDisabled","enabled":true}
   
   Where CONTENTHASHHERE matches the number in all other features listed in the capabilities.json.
   
   Example:
   
   
   
   This will disable the caching on the tasks table only, leaving the overall QMC Cache intact to gain performance. If you had previously set QmcCacheEnabled, QmcDirtyChecking, QmcExtendedCaching to false, please set it to true again.
   
   
4. Restart the Qlik Sense services

Workaround for earlier versions:

Upgrade to the latest Service Release and disable the caching functionality: 

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify the flag for these values to false
   • QmcCacheEnabled
   • QmcDirtyChecking
   • QmcExtendedCaching
4. Restart the Qlik Sense services
   
   

NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.

Should the issue persist after applying the workaround/fix, contact Qlik Support.

Internal Investigation ID(s): 

QB-2096
QB-5168
QB-7655
QB-17238

Environment

Qlik Sense Enterprise on Windows 

Qlik Talend Studio failed to install JAR files with the error:

Network is unavailable, please fix it

This occurred even though the machine had an active internet connection and the complete SSL certificate chain had been successfully imported.

Log Snippet:

javax.net.ssl.SSLHandshakeException: (certificate_unknown) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target: https://talend-update.talend.com/nexus/content/groups/studio-libraries/

Resolution

Enable Windows long path support in the Windows registry:

Registry Change (long-path.reg):

Windows Registry Editor Version 5.00: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001

Alternatively, enable it using the Group Policy under Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths

A system restart is required after the changes are applied.

Cause

The "Network is unavailable" error and the subsequent failure to install JAR files in Qlik Talend Studio are caused by the Windows long path limitation, rather than by network or SSL issues.

The following troubleshooting steps can be used to trace the conclusion:

1. SSL Verification: Imported all relevant certificates into the cacerts keystore and verified using: keytool -import -alias <alias_name> -keystore "%JAVA_HOME%/jre/lib/security/cacerts"
2. Connectivity Test: Ran a standalone, simple Java application to test the HTTPS connection to https://talend-update.talend.com. The connection was successful, confirming that SSL communication and certificates were functioning correctly.
3. Isolating the Issue: Suspecting Qlik Talend Studio corruption, a fresh instance was unzipped. During extraction, Windows threw a "Destination Path Too Long" warning. This revealed that the Windows maximum path length limitation (MAX_PATH) was causing Qlik Talend Studio components to malfunction and misreport the issue as a network failure.

Environment

• Qlik Talend Studio

The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.1.0.

Content

• What's New
• 2.1.0 September 2025 Release Notes
• Known Limitations (2.1.0)
• 2.0.0 May 2025 Release Notes
• Known Limitations (2.0.0)
• 1.4.0 December 2023 Release Notes
• Known Limitations (1.4.0)
• 1.3.0 May 2023Release Notes
• Known Limitations (1.3.0)
• 1.2.0 Release Notes

What's New

• The PostgreSQL version used by QPI has been updated to 14.17
• An upgrade of an already upgraded external instance is now possible
• Support for an upgrade of the embedded 14.8 database was added
• Silent installs and upgrades are supported beginning with Qlik PostgreSQL Installer 1.4.0 and later. QPI can now be used with silent commands to install or upgrade the PostgreSQL database. (SHEND-973)

2.1.0 September 2025 Release Notes

Known Limitations (2.1.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.17. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.17. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

• QB-24990: Cannot upgrade PostgreSQL if Qlik Sense was installed in a custom directory such as D:\Sense. See Qlik PostgreSQL Installer (QPI): No supported existing Qlik Sense PostgreSQL database found.
• Rollback is not supported.
• Database size is not checked against free disk space before a backup is taken.
• QPI can only upgrade bundled PostgreSQL database listening on the default port 4432. Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• Cannot migrate a 14.8 embedded DB to standalone
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

1.3.0 May 2023 Release Notes

This article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

The Qlik Sense Repository Database (QSR) can be moved to a dedicated, standalone PostgreSQL instance not hosted on the same machine as other Qlik Sense Services. It is also possible to move an already existing QSR from a local Sense install to a dedicated PostgreSQL database.

Content:

• Set up a PostgreSQL database
• Simplified checklist of steps:
• Moving the Qlik Sense Share Folders as well?
• Backup
• Restore
• Changing the Connection String to QSR and QSMQ Database
• Changing the Connection Stringto SenseServices Databases.
• Changing the Connection String to Licenses Database ( April 2019 and up )
• Remove Database Service dependency and Postgres Server
• Finalize

Set up a PostgreSQL database

Instructions for this might vary slightly. Please refer to the Qlik Online Help for details.  We recommend watching this video.

Qlik Sense Enterprise server has a set of five databases. For more details, visit Installing and configuring PostgreSQL on help.qlik.com.

1. The Qlik Sense repository database (QSR):

The QSR is the primary database in your Qlik Sense deployment.

2. The Qlik Sense services database (SenseServices):

The SenseServices database contains schemas for each of the Qlik Sense services and allows growth independently of the Qlik Sense Repository Database, while still sharing the same PostgreSQL instance and login role.

3. The Qlik Sense message queue database (QSMQ):

The QSMQ database provides a light-weight method of passing messages internally between services in Qlik Sense Enterprise. The NOTIFY and LISTEN functionality in PostgreSQL allows services to be notified about new messages that have been written to the messaging table.

4. The Qlik Sense logging database (QLogs): No longer supported after May 2021

The QLogs database centralizes logging by collecting log messages from all Qlik Sense nodes in your deployment and storing them in a PostgreSQL database.

5. The Qlik Sense license service database (Licenses):

The Licenses database is used to sync the assignments between the Qlik license backend and the local installation.

Simplified checklist of steps:

1. Download a valid version of PostgreSQL.  For Sense June 2017 and up, 9.6.x is required, from November 2019 version 11.5.x as well. From May 2021, version 12.5 can be used. Review the system requirements of your version before proceeding.
2. Follow the instructions in Installing and configuring PostgreSQL 

Moving the Qlik Sense Share Folders as well?

Follow How to change the shared path in Qlik Sense 

Backup 

Depending on the version, you need to back up different databases. On the current Qlik Sense central node hosting the Qlik Sense Repository Database service, follow the backup instructions to obtain a database copy of each Qlik Sense Database Present. 

Restore

On the dedicated remote PostgreSQL host, perform a restore of the backed-up databases of previous point. 

Changing the Connection String to QSR and QSMQ Database 

1. On the Qlik Sense central node, all services but the Qlik Sense Repository Service are shut down.
2. Open QlikSenseUtil. By default, this will be installed in: C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
3. Open the Connection String Editor and Read the current configuration, decrypting the current data.
   
   
4. Replace all mentions of the current database hostname.  In our example, the new database resides on 172.16.16.103. Instead of an IP you can also use the FQDN of the db server.
5. You need to repeat this step for the   sections <add name="QSMQ" and <add name="postgres"
6. Hit Save Value in config file encrypted, committing any changes. 

Changing the Connection String to SenseServices Databases. 

Execute steps in Moved Postgress database to new host, but some qliksense is still accessing the SenseServices old database; check if different versions of the article are present for different Qlik Sense version.

Changing the Connection String to Licenses Database ( April 2019 and up ) 

Starting from April 2019, the new License Service implementation is using this database.

1.   Open an elevated PowerShell and change directory to C:\Program Files\Qlik\Sense\Licenses
2.    Run the script .\Configure-Service.ps1 and provide:
   • new Hostname or IP  
   • database port default is 4432
   • database user qliksenserepository
   • databasepassword is the qliksenserepository password used during configuration of the new database.
3. example: 
4. cd  'C:\Program Files\Qlik\Sense\Licenses'
5. .\Configure-Service.ps1 172.16.16.102 4432 qliksenserepository Password123!

It will look like this:

repeat this for:

Remove Database Service dependency and Postgres Server

After successfully verifying your new setup, remove the Qlik Sense Repository service dependencies and the old Postgres database. This is done to avoid issues with future upgrades of the environment. 

1. In an elevated command prompt, execute the following on prompt:
   
   c:\sc config "QlikSenseRepositoryService" depend= ""
   c:\sc config "QlikLoggingService" depend= ""
   
   This will return: 
   
   [SC] ChangeServiceConfig SUCCESS
   
   
2. Restart the Qlik Sense Repository Service.
   
   Check that Qlik Sense Repository Database doesn't start (confirms [SC] ChangeServiceConfig SUCCESS ).
   
   
3. Remove the (local) Qlik Sense Repository Database
   
   Find the most recent PostgreSQL.msi in C:\ProgramData\Package Cache\  and remove it. This removes the service, but no old local database data. This is needed to prevent issues on future upgrades of the environment.
   
   You can find the precise folder with this command, depending on the PostgreSQL version you used to install the initial release.
   
   9.6:
   
   c:\cd ProgramData\Package Cache
   c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
   
   The folder containing PostgreSQL.msi will be revealed. Right-click on the PostgreSQL.msi file and select Uninstall from the menu.
   
   12.5:
   
   c:\cd ProgramData\Package Cache
   c:\ProgramData\Package Cache\dir /s PostgreSQL125.msi
   
   The folder containing PostgreSQL.msi will be revealed. Right-click on the PostgreSQL.msi file and select Uninstall from the menu.
   

Finalize

1. Restart the Qlik Sense Repository Service and verify that the Qlik Sense Repository Database Service doesn't exist when following the previous steps.
2. Start all remaining Sense Services 
3. Progress on the startup sequence (including the connection to the new database) can be tracked in the _System_Repository log files located in C:\ProgramData\Qlik\Sense\Log\Repository\Trace
4. Verify functionality.

5. In a multi-node scenario, you need to repeat steps "Changing the Connection Strings to Databases" on all Rim nodes (QlikSenseUtil for Repository.exe.config and Configure-Service.ps1 for the micro services), and if required, configure "Update the Qlik Logging Service Connection String" (note that is EOL with Qlik Sense Enterprise on Windows February 2022).   

Environment

Qlik Sense Enterprise on Windows 

NPrinting has a library of APIs that can be used to customize many native NPrinting functions outside the NPrinting Web Console.

Environment:

Qlik NPrinting 

An example of two of the more common capabilities available via NPrinting APIs are as follows

• Connection reloads
• Publish Task executions

These and many other public NPrinting APIs can be found here: Qlik NPrinting API

In the Qlik Sense data load editor of your Qlik Sense app, two REST connections are required (These two REST Connectors must also be configured in the QlikView Desktop application>load where the API's are used. See Nprinting Rest API Connection through QlikView desktop)

• GET
• POST

Requirements of REST user account:

• Windows Authentication is required in both these connectors. The required user account is the NPrinting service account (which is also ROOTADMIN on the Qlik Sense server)
• This user account must also be a member of the NPrinting 'Administrators' Security Role on the NPrinting Server.

Creating REST "GET" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Creating REST "POST" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Ensure to enter the 'Name' Origin and 'Value' of the Qlik Sense (or QlikView) server address in your POST REST connection only.

Replace https://qlikserver1.domain.local with your Qlik sense (or QlikView) server address.

Ensure that the 'Origin' Qlik Sense or QlikView server is added as a 'Trusted Origin' on the NPrinting Server computer

Related Content

• Distribute NPrinting reports after reloading a Qlik App
• Extending Qlik NPrinting
• Run a Qlik NPrinting API POST command via QlikView reload script
• Troubleshooting Common NPrinting API Errors

NOTE: The information in this article is provided as-is and to be used at own discretion. NPrinting API usage requires developer expertise and usage therein is significant customization outside the turnkey NPrinting Web Console functionality. Depending on tool(s) used, customization(s), and/or other factors ongoing, support on the solution below may not be provided by Qlik Support.

The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."

Environment

• QlikView 
• Qlik Cloud 

Resolution

• The license used in Qlik Cloud is missing the QV_NODES tag, which allows the access to QlikView apps from Sense Deployments. For QlikView to distribute to a Qlik Cloud tenant,  the tag must be present in the tenant license.

Please, reach out to your account manager to have that fixed.

• This issue could also occur if there are missing configuration entries in he QVDistributionService.exe.config  file, refer to the following article QlikView Distribute to cloud fails: The type initializer for System.IdentityModel.Tokens.Jwt.JsonExtensions threw an exception.

Qlik Software Windows executables (such as Qlik Talend Studio, Talend Installers, Qlik NPrinting) come with an embedded digital signature, which signals Windows (and any security software) that the executable has been verified.

The digital signature is typically valid for 2 to 3 years before requiring renewal.

However, when reviewing the signature, it may show that it was revoked by the issuer around April 28th of 2026, even though it should still be valid for another 6-12 months.

Consequently, security software may block any executable that does not have a valid or current digital signature, leading to users being unable to launch the installed Qlik software.

Resolution

While proceeding by bypassing the signature check is an option, it is not always a feasible workaround. Qlik is actively replacing the affected installation files with executables that include both the digital signature and a new (valid) countersignature. 

Re-downloading the installation package from the Qlik Download page will resolve the issue in most instances. 

• Qlik Sense Enterprise on Windows and Desktop May 2026 IR
• Qlik Sense Enterprise on Windows November 2024 Patch 28 (release expected May 27th)
• Qlik Sense Enterprise on Windows May 2025 Patch 20 (release expected May 27th)
• Qlik Sense Enterprise on Windows November 2025 Patch 10 (release expected May 27th)

Not all files have been replaced at this point. Specifically, major releases (IR) are still undergoing processing.

To prevent this from recurring, Qlik has updated its digital signing processes.

If your product is not available on the Qlik Download page (such as Qlik Talend Studio), contact Qlik Support to receive the newly compiled executable (R2024-05 through R2026-05). 

Cause

The revocation of the digital signature was due to identifying a countersignature that did not have a timestamp set. 

Internal Investigation ID(s)

ITSYS-16864

Environment

• Qlik Products

Installing Qlik Data Gateway v1.7.13.0 on Windows may fail. The installation remains stuck in a loop.

The system first requires a restart of Windows, but will not complete the installation afterwards. Instead, a Microsoft Visual C++ Redistributable Modify Setup prompt will be displayed:

Whatever option is chosen, a new pop-up appears stating, 'Please restart your system before running the Qlik Data Gateway - Direct access installation'. This will restart the loop. 

Resolution

Install v1.7.14.0 when available.

If it's necessary to perform a new installation in the meantime, use v1.7.11.0.

Cause

This is a known defect (SUPPORT-8964) affecting v1.7.13.0.

Internal Investigation ID(s)

SUPPORT-8964

Environment

• Qlik Direct Access Gateway

Installing Qlik Replicate 2025.5 and 2025.11 GA versions on Linux 9.7, an error may occur during installation or when attempting to start the services.

This issue is typically observed when the installation is performed using a different account than the one intended to run the services.

For example, installing Qlik Replicate with the account apsup while specifying qlik as the service account:

sudo user=qlik group=qlik verbose=true rpm -ivh --prefix /opt areplicate-2025.11.0-164.x86_64.rpm

A typical error message is:

arep.sh: created /opt/attunity/replicate/bin/areplicate
arep.sh: created /etc/systemd/system/areplicate.service
systemctl daemon-reload failed
failed to install areplicate as a service, areplicate will not be run
warning: %posttrans(areplicate-2025.11.0-164.x86_64) scriptlet failed, exit status 9  

Resolution

Upgrade your Qlik Replicate installation. This issue has been resolved in Qlik Replicate 2025.11 SP3 (2025.11.0.437 and later).

Internal Investigation ID(s)

00443949

Environment

• Qlik Replicate 2025.5
• Qliklik Replicate 2025.11 GA/SP1/SP2
• Linux 9.7