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

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.

If your Qlik Talend Studio has Internet access, patches can be directly applied from within Qlik Talend Studio.

For details, see Setting up the Update URL of Talend Studio.

If your Qlik Talend Studio environment is not connected to the Internet, contact support for a download link to the required patch zip file, then follow the instructions in Qlik Talend Studio: How to add features or update Talend Studio Manually in Offline Mode?

Environment

• Qlik Talend Studio

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

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

Upgrading Qlik Compose across multiple versions requires a specific upgrade path. See Qlik Compose December 2024 Initial Release Notes for details.

After an upgrade, following the steps from 2022.5 to 2023.11 and finally 2024.12, Qlik Compose returns a generic UI error during connection tests. 

UI ERROR
Unable to connect to the remote server

Reviewing the Qlik Compose server log reveals the Java process is failing to start entirely:

[INFO ] Java Server: .
[ERROR] Java Server: Error: Could not create the Java Virtual Machine.
[ERROR] Java Server: Error: A fatal exception has occurred. Program will exit.
[INFO ] Java Server: <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.
[WARN ] The Compose java server was restarted.
[ERROR] Java Server: Error: Could not create the Java Virtual Machine.
[ERROR] Java Server: Error: A fatal exception has occurred. Program will exit.

While the Qlik Compose server is running, the Java agent is down.

The details upgrade path followed was:

• 2022.5.0.2333 to 2023.11.0.1029, which was successful
• 2023.11.0.1029 to 2024.12.0.402, which was unsuccessful

Resolution

1. Stop the Qlik Compose services
2. Rename or remove the /ext folder in the Compose/java/lib/jre/lib directory
3. Start the Qlik Compose services

Cause

When the second hop was done, the installation recreated the /ext folder within Compose/java/lib/jre/lib with no files within. As Compose 2024.12 uses Java 17, it doesn’t support ext folder.

Environment

• Qlik Compose

The TDQRules qlikrules jar file is missing even after enabling the component in the feature manager.  

Resolution

This is caused by QTDQ-1404 and addressed in the 2026-04 release of Qlik Talend Studio. The issue is triggered by a space or special character in the install folder name.

Workaround:

Move or install Qlik Talend Studio in a different folder than the default \Program Files folder, and make sure that there is no blank space or special character in the new install path. 

Internal Investigation ID(s)

QTDQ-1404

Environment

• Qlik Talend Studio

What is the default user session timeout for Qlik Sense Business and Qlik Sense Enterprise SaaS? Can the session timeout for Qlik Cloud be changed?

The default (fixed) value is set to 30 minutes. This is controlled by SESSION_TTL.

It is not currently possible to adjust the session timeouts in the Qlik Cloud.

Environment:

Qlik Cloud 

The installation of Teradata on the Qlik NPrinting Server machine causes instabilities. The Qlik NPrinting Scheduler Service stops frequently without obvious warnings, and restarting it may lead to an immediate crash of the service.

Resolution

Installing Teradata causes changes in the native images that cannot be reverted and which impact basic functionalities of the Qlik NPrinting services. This results in the installation of Teradata being incompatible with Qlik NPrinting.

To resolve the issue with Qlik NPrinting:

1. Uninstall Teradata
2. Take a backup of your Qlik NPrinting database; see Backup and restore Qlik NPrinting 
3. Uninstall and reinstall Qlik NPrinting
4. Restore your Qlik NPrinting database; see Backup and restore Qlik NPrinting 

In rare instances, the Windows Operating system will need to be reinstalled or reverted back to a pre-Teradata state.

Internal Investigation ID(s)

SUPPORT-8105

Environment

• Qlik NPrinting

The Qlik Sense Desktop .unlock file (Qlik_Sense_Desktop.unlock) expires regularly but will be replaced with a new version. Should no new version be available just yet, then:

• Wait for the new .unlock file to be made available; a short delay during a release cycle is expected
• Authenticate your Qlik Sense Desktop client as per Starting Qlik Sense Desktop

Environment

• Qlik Sense Desktop

Qlik Sense patches can be downloaded from the Qlik Download page. Patches are cumulative, and only one patch can be installed at a time.

Example: Patch 4 for Qlik Sense February 2019 will include all fixes from 3, 2, and 1.

Before applying a patch:

• Read the Release Notes to locate any dependencies of new features or changes to features which can affect your environment
• Verify and record all customisations (manual changes to setting files or configuration files not otherwise represented in the GUI). While patches generally do not change settings or revert configuration files to default, a drastically changed feature (see release notes) can impact customisations.
• Previously installed patches on the same release track do not need to be uninstalled

To install:

1. Download the required patch 
2. Schedule a brief downtime as the server will need to be restarted
3. Execute the patch installation package and follow the on-screen instructions
4. Restart the Windows server host

To uninstall:

Executing a patch installation package will automatically uninstall the previous patch and install the new one. If you need to uninstall a patch manually:

1. Open the Windows Add and Remove Programs menu
2. Click View installed updates from the left panel
3. Locate the Patch
4. Uninstall the Patch
5. Restart the Windows Server host

If uninstall through Control Panel is not possible:

1. Locate the Qlik_Sense_update.exe installer package in C:\ProgramData\Package Cache\[guid]\.
   
   If the package required for the uninstall has been removed or renamed, a possible workaround is to obtain an exact copy (same version, release) of the Qlik_Sense_update.exe from a different environment and manually replacing it.
   
   
2. Right click the Qlik_Sense_update.exe and click Uninstall

Related Content:

Custom configuration file changes not kept after Qlik Sense upgrade 

Qlik Sense may be unable to access the Qlik Sense Management Console (QMC) and/or HUB. You will find below some guidance explaining how to troubleshoot those.

To start your troubleshooting you will need to clearly identify your issue: 

• Is the issue only regarding the HUB?
• Is the issue only regarding the QMC?
• Is the issue regarding both the QMC and the HUB?

In this troubleshooting guide we will talk about the third scenario where you are unable to open neither the Qlik Sense Management Console (QMC) and the HUB

As a second steps to identify your issue, you will need to answer the three following questions:

• Is this issue has started occurring after a fresh installation or an upgrade of the product without having worked before?
• Is this issue occurring on a random basis from time to time? 

We will discuss the following two scenarios below.

Below is a provided list of article containing specific root causes that that could help you after following the above steps: 

No Hub or QMC access after upgrade to Sense November 2017 or higher - recursive script
How to approach Qlik Sense Error 404 when access Hub/QMC
Qlik Sense: Cannot access QMC or Hub. Error in repository log: implementation not part of Windows FIPS validated cryptographic algorithms
Qlik Sense Installation successful but problem opening QMC/HUB
Can't access Qlik Sense QMC or HUB using local service account
Cannot open Qlik Sense Management Console or hub after upgrade - RootFolder and AppFolder are not defined at startup 
Qlik Sense Management Console (QMC) and Hub are not accessible and connection to QRS Database times out after 90 seconds 

Resolution

General verification

Before starting to investigate deeper into the issue you need to apply some basic steps to troubleshoot:

• Verify general network connectivity. Qlik Sense relies on the usage of WebSockets, which may be blocked. See How to troubleshoot web socket issue for Qlik Sense? for details. 
• Are you following the minimal requirements (Please make sure you select the correct version). 
• Are the Qlik Sense services up and running? => Try to start and restart them to see if it comes back up and running. (You might need to wait a few minutes before the services become operational)
• Are you using the correct URL to access the Qlik Sense Management (QMC) and HUB? => You can try to access them connected remotely to the Qlik Sense Server by accessing the URL https://localhost/qmc or https://localhost/hub. If this works you might have a DNS and/or a network issue.
• Do you have connectivity to the Qlik Sense Server from the machine you are attempting to connect?  Verify with a network ping and/or telnet to Qlik Sense on the relevant ports. Please see How To Check Open Ports Using PowerShell and the relevant version help site.  

The issue has started occurring after a fresh installation or an upgrade of the product without having worked before

If after checking the above points you still experience issues, you need to know that to start properly, the Qlik Sense Management Console will need to have few services properly working: 

• The Qlik Sense Repository Database
• The Qlik Sense Repository Service
• The Qlik Sense Dispatcher
• The Qlik Sense Proxy

To verify if those services are actually functioning correctly, you will need to check their logs.
Start by looking into the Qlik Sense Repository logs stored by default in C:\Programdata\Qlik\Sense\Log\Repository\Trace\Servername_System_Repository.txt. (You might want to restart the services before looking into this log to get fresh information)

If the Qlik Sense Repository Database and Service starts correctly you are basically looking at the following string in this logs (It might take few minute to initialize after a service restart)
Startup phase completed

If you do not find this string in the logs, then you will likely need to search for the first ERROR and/or WARN showing in this logs. You can then grab the content of the message and search it in our knowledge base

However if you find this string in the logs, the next step is to check the Qlik Sense Proxy logs stored by default in C:\Programdata\Qlik\Sense\Log\Proxy\Trace\Servername_System_Proxy.txt
Once again we would recommend to restart the Qlik Sense Proxy Service before looking into the logs to get fresh information.

In this log you might see few errors at the beginning saying
When contacting https://localhost:4242/    No connection could be made because the target machine actively refused it 127.0.0.1:4242
Could not contact local repository to retrieve local server node configuration    No connection could be made because the target machine actively refused it 127.0.0.1:4242

Those will be expected since the Qlik Sense Proxy service will try to connect to the Qlik Sense Repository Service, so as long as the startup phase is not completed for the Qlik Sense Repository service you will keep getting those events in the logs.
Basically if the Qlik Sense Proxy service is starting correctly you should expect the following event in the logs: 

Proxy is running

As for the Qlik Sense Repository if you do not find this string in the logs, then you will likely need to search for the first ERROR and/or WARN showing in these logs. You can then grab the content of the message and search it in our knowledge base.

E.g. Here is an example of the types of error you can get in the Qlik Sense logs: 

Proxy will NOT be listening to port 443, likely bound by another process An attempt was made to access a socket in a way forbidden by its access permissions.

The above steps should help you to investigate the root cause of your issue for this scenario.

The issue occurs on a random basis from time to time

In the following scenario we are more looking into an environment issue such as network connectivity, resource overload, ...
The first step would be to check the Qlik Sense Repository Service and Proxy logs as described above to find any relevant ERROR and/or WARN that could explain the root cause. 

Then you can start looking into the Windows Event logs (Application and System) to find any problem at a system level around the time you are getting this issue.

Below are common causes/events that you could find in those logs: 

• Memory starvation Windows successfully diagnosed a low virtual memory condition?
• Network issue The network link is down.  Check to make sure the network cable is properly connected

Those types of event require often to involve your system and/or network and/or virtualization team for further troubleshooting.

In addition you can run a performance monitor to check the resource consumption on your machine following How to log CPU and memory with Microsoft Performance Monitor on a windows 2012 Server (PerfMon)

 

This article documents how to configure a Qlik tenant to send emails using MS365.

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

Prerequisite

An account with an active Office365 license is required for this setup.

MS365 Setup

First, we configure the MS365 tenant to support the configuration.

Once you have an account set up on the MS365 side, let's go to the Microsoft Tenant settings:

1. Open the Microsoft Entra admin center (Home - Microsoft Entra admin center)
   1. Go to Overview
   2. In the overview screen, you will see your Tenant ID. Copy this value, you will need it to configure your Qlik Cloud Tenant.
   3. Click Application to register an application
   4. Click + New registration
      
      
      
      
   5. Name your application
   6. Select the Supported account type that matches your needs
   7. Click Register to register your application
2. Create a Client Credential 
1. Click Certificates & Secrets
2. Click + New client secret
3. Describe (name) the client secret and select its expiration value
4. Click Add to finish this step
   
   
   
   
5. After creating your client secret, the following is displayed:
   
   
   
   
6. Copy the value and save it in a safe place. You will need it to complete your Qlik Cloud Tenant setup.
   
   
3. Enabling the right APIs:
   1. Go to API Permissions
   2. Click + Add Permission
   3. Select Microsoft Graph
   4. Select Application permissions
   5. In the Select permissions field look for Mail.Send
   6. Select the Mail.Send permission

      Setting Application permissions to Mail.Send grants the application to use any email address from your organization.

   7. Click Add permission
   8. Click Grant admin consent for <MS Tenant Name> to finish this step
      
      
      
      
4. Select an Owner for the application
   1. Click + Add Owner
   2. Type the name of the User who will be the Owner
   3. Mark the user and click Select 

Qlik Cloud Tenant Setup

1. Open your Administration activity center (see Accessing the Administration activity center)
2. Go to the Email Provider section
3. Select Microsoft 365
   
   
   
   
4. Insert all previously set information:
   1. Sender email address: Insert an email registered on Microsoft. This can be your email address or another dedicated account created specifically for this purpose. 
   2. Tenant ID: Obtained from the Microsoft Entra Overview section.
   3. Client ID: The Application (client) ID you previously created.
   4. Client secret: The Client secret value which you saved in the previous setup steps.
      
      
      
      
5. Save the changes
6. Send a test email

If mail.send is blocked by Active Directory group policy, mail delivery will fail. Please consult your AD administrator(s) if mail delivery fails when the above steps are followed.

Environment

• Qlik Cloud Analytics
• Microsoft Office 365

Navigating to the Software Update page of the Qlik Talend Administration Center UI leads to the following error:

Unexpected HTTP status 302' when accessing (https://talend-update.talend.com/nexus/service/local/status) redirect to (https://talend-update.talend.com/)").

This can affect any Patch Release of Qlik Talend Administration Center (TAC).

SoftwareUpdate

The Configuration page will reflect the error: 

Resolution

To resolve, change the Talend update URL (https://talend-update.talend.com/nexus) to https://talend-update.talend.com, removing /nexus from the path.

This is done in the Configuration page.

UpdateURLwithoutNexus

Cause

This issue began to appear after January 26th, 2026, at which point the URL backend was updated.  

The URL needs to be changed in the Qlik Talend Administration Center backend.

Environment

Talend Administration Center 

Qlik Talend Data Stewardship R2025-02 keeps on loading and does not open up in Talend Management Console.

Resolution

Patch fix

Apply the latest Patch_20260105_TPS-6013_v2-8.0.1-.zip or latter version of patch 

TCP stack tunning 

##sysctl
sudo vi /etc/sysctl.conf
#add the following lines 
net.ipv4.tcp_keepalive_time=200
net.ipv4.tcp_keepalive_intvl=75
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_retries2=5

sudo sysctl -p #activate 

MTU change (avoid TCP traffic re-transmission)

temp change  without rebooting : 

sudo ip link set dev eth0  mtu 1280

Persist on os: 

sudo vi /etc/sysconfig/network-scripts/ifcfg-eth0
MTU=1280

network_mtu.html | docs.aws.amazon.com

Explanation on the Linux  tcp tunning parameters

These sysctl settings are primarily used to make your server more aggressive at detecting and closing "dead" or "hung" network connections. By default, Linux settings are very conservative, which can lead to resources being tied up by connections that are no longer active.

Here is a breakdown of what these specific changes do and why they are beneficial.

TCP Keepalive Settings 

The first three parameters control how the system checks if a connection is still alive when no data is being sent (the "idle" state).

The Benefit: In a standard Linux setup, it can take over 2 hours to realize a peer has crashed. With your settings, a dead connection will be detected and cleared in roughly 20 minutes (200 + (75* 5) = 575 seconds). This prevents "ghost" connections from filling up your connection tables and wasting memory. 
 

TCP Retries

The Benefit: The default value is usually 15, which can lead to a connection hanging for 13 to 30 minutes during a network partition or server failure because the "backoff" timer doubles with each retry. By dropping this to 5, the connection will "fail fast" (usually within a few minutes).
 
This is excellent for high-availability systems where you want the application to realize there is a network issue quickly so it can failover to a backup or return an error to the user immediately rather than leaving them in a loading state.
 

Use Cases for These Settings

Microservices: To ensure fast failover and prevent a "cascade" of waiting services in a distributed system.

If These changes are not permanent until you add them to /etc/sysctl.conf. Running the command with -w only applies them until the next reboot.

Cause

There are 2 major factors contributing to this issue

1. invalid_grant error caused by current design defects

   ERROR [http-nio-19999-exec-2] g.c.s.Oauth2RestClientRequestInterceptor : #1# Message: '[invalid_grant] ', CauseMessage: '[invalid_grant] ', LocalizedMessage: '[invalid_grant] '

2. EC2 Linux sysctl tcp stack default setting not ideal for clean the hang connections.

Environment

Talend Data Stewardship 

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 

In this article, we detail the 12 steps necessary to successfully configure Qlik Sense Enterprise on Windows after an Active Directory Domain name change or moving Qlik Sense to a new domain.

Depending on how you have configured your platform, not all the steps might be applicable. Before updating any hostname in Qlik Sense, make sure that the original value is using the old domain name. In some case, you may have configured “localhost” or the server name without any reference to the domain so there is no need in these cases to perform any update.

Environment

• Qlik Sense Enterprise on Windows 

Scenario

In this scenario we are updating a three-node environment running Qlik Sense February 2021:

The domain has been changed from DOMAIN.local to DOMAIN2.local

The servers mentioned below are already part of the new domain name DOMAIN2.local and their Fully Qualified Domain Name (FQDN) is already updated as followed:

• QlikServer1.domain.local to QlikServer1.domain2.local: Central node
• QlikServer2.domain.local to QlikServer2.domain2.local: Rim node
• QlikServer3.domain.local to QlikServer3.domain2.local:  Dedicated Postgres and hosting the Qlik shared folder

All Qlik Sense services have been stopped on every node.

Step 1: Update the Postgres Configuration File

The first step is to update the postgres.conf file to listen on the correct hostname

1. Open the postgres.conf (make sure to make a copy) under
   • C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\<version> (for an environment running the native Qlik Sense Repository Database)
   • C:\Program Files\PostgreSQL\<version>\data (for an environment running a dedicated PostgreSQL database)
2. Search for the parameter listen_addresses and update the hostname value if required
   
   
   
   
3. Save the file, close it and start the Qlik Sense Repository Database or PosgresSQL service depending if you are using the native PostgreSQL or a dedicated instance

Step 2: Backup your Qlik Sense site

Before doing any further changes, it is important to take a backup of your Qlik Sense Platform

• Backing up a Qlik Sense site

Step 3: Rename Server Node in QSR database

Now we update the node names in the database with the new Fully Qualified Domain Name.

1. Connect to the Qlik Sense Database using Installing and Configuring PGAdmin4 to access the PostgreSQL
2. Open the QSR Database and navigate through Schemas -> public ->Tables
3. Right-click on ServerNodeConfiguration -> View/Edit Data -> All Rows
4. Modify the hostname of each node if required
   
   
   
   
5. Save by clicking on the below icon available in the toolbar
   
   
   
   
6. Close PGAdmin

Step 4: Rename User Directory for existing users

1. Connect to the Qlik Sense Database using Installing and Configuring PGAdmin4 to access the PostgreSQL
2. Right-click on the QSR Database and select “Query Tool”
3. Run the following query
   

   UPDATE public."Users"
   SET "UserDirectory" = 'DOMAIN2'
   WHERE "UserDirectory" = 'DOMAIN';​

4. Validate the change by running the following query
   

   SELECT * FROM public."Users"​

   
   The User Directory should be updated to the new domain:
   
   
   
   
5. Close PGAdmin

Step 5: Update Service Cluster configuration

1. On the central node run the program C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe and Connect to Database
   
   
   
   
2. Once connected, click on Service cluster and then OK
3. Update the FQDN with the new domain if required and press Save
   
   
   
   
4. Close QlikSenseUtil.exe

Step 6: Update the repository Connection Strings

1. On the central node run the program C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
2. Select Connection String Editor and click on Read
3. Update the FQDN with the new domain if required and press Save Value in config file encrypted
   
   
   
   
4. Close QlikSenseUtil.exe
5. Repeat the above steps on every rim node

Step 7: Update the dispatcher services connection strings

Verify if a hostname update is required

1. On the central node, open File Explorer and navigate to C:\Program Files\Qlik\Sense\Licenses and open the appsetting.json
2. Check if the parameter host contains the old domain name. If it does then you need to follow the below steps to update it otherwise you can jump to the next section

Update hostname on all Qlik Sense Dispatcher subservices

1. Search for the file called Configure-Service.ps1
   
   In Qlik Sense February, there are 8 of these files placed in different Qlik Sense Dispatcher sub-services. We need to run each of these files with a specific argument. In the previous or later version of Qlik Sense, the list presented below may need to be adapted.
   
   
2. Run the following command in PowerShell ISE as Administrator
   

   cd "C:\Program Files\Qlik\Sense\NLAppSearch\install"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\AppDistributionService"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\HybridDeploymentService"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\Licenses"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\NotifierService\install"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\MobilityRegistrarService\install"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\PrecedentsService\install"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
   
   cd "C:\Program Files\Qlik\Sense\DataPrepService\install"
   .\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>

3. Repeat the above steps on every node (Including the verification)

Step 8: Update the Qlik Logging Service

If you are using the Qlik Logging Service;

1. Run the following command in Command Prompt:
   

   cd "C:\Program Files\Qlik\Sense\Logging"
   Qlik.Logging.Service.exe validate​

2. If you get something like:
   
   Failed to validate logging database. Database does not exist or is an invalid version.
   
   Then it probably means that the hostname needs to be updated
   
   
3. If so, run the following command in Command Prompt:
   

   cd "C:\Program Files\Qlik\Sense\Logging"
   Qlik.Logging.Service.exe update -h QlikServer3.domain2.local​

4. Once done, run the validate command again to verify that the connectivity is working
   
   
   
   
5. Repeat the above steps on every rim node

Step 9: Update the service account running the Qlik Sense services

1. On the central node, open the Windows Service Console an update each Qlik Sense services with the new domain (DO NOT START THE SERVICE AT THIS POINT)
   
   
   
   
2. Repeat the above step on every rim node

Step 10: Update the host.cfg and remove the certificate

1. On the central node login as the service account
2. Backup the Qlik Sense certificate following Backing up certificates
3. Remove the certificate you have previous backed up from the MMC
4. Make a copy of %ProgramData%\Qlik\Sense\Host.cfg and rename the copy to Host.cfg.old
   • Host.cfg contains the hostname encoded in base64. You can generate this string for the new hostname using a site such as https://www.base64encode.org/ (You may want to decode the original string to see if it contains the old domain name.
5. Open Host.cfg and replace the content with the new encoded hostname.
6. Run Windows Command Prompt as Administrator and execute the following command:
   

   "C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname​

7. In parallel start the Qlik Sense Dispatcher services
8. When the command has completed successfully you should see the following message in command prompt:
   
   Bootstrap mode has terminated. Press ENTER to exit..
   
   
9. Start every Qlik Sense services on the central node and try to access the QMC with https://localhost/qmc

Step 11: Distribute the certificate on the rim node(s)

1. On the rim node(s) login as the service account
2. Backup the Qlik Sense certificate following Backing up certificates
3. Remove the certificate you have previous backed up from the MMC
4. Start the Qlik Sense services
5. On the central node, open the QMC and go to Nodes
6. After a few minutes the rim node should have the status The certificates has not been installed
   
   
   
   
7. Click on Redistribute and follow the instructions to redistribute the certificates on the rim node(s)
8. After a few minutes, the services should be running
   
   

Step 12: Additional updates

User Directory Connector

If you are syncing your users with a User Directory Connector you will need to change the LDAP path to point to the new domain.

1. In the QMC -> User Directory Connector
2. Edit your existing User Directory Connector, check the LDAP Path and update if necessary
   
   

Monitoring Application

You will need to update the monitoring apps and their associated data connection to use the new Fully Qualified Domain Name

• Configuring the Monitoring apps

Data Connections password

• Part of the steps followed earlier, the certificates had to be recreated. As a result, the passwords for the existing data connection needs to be re-typed and saved for all Data Connections and User Directory Connectors that include password information.

Security Rules and Licenses rules

It is possible that you have created rules based on the User Directory. As you have changed the domain name, the user directory has also changed in Qlik Sense so you will need to update those to reflect that. 

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.

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 

Talend Management Console Release Notes R2025-11 | Qlik Talend Documentation informs of the New storage Service which is currently not yet available for EU and US regions.

"New storage service endpoint for unified access to artifacts and execution logs: This storage service is planned to be deployed to AWS EU and AWS US in January 2026. Update your proxy and firewall settings when it is available." 

Questions and Answers

•  Is this addition to the firewall allowlist optional or is it mandatory? 
  • This change is mandatory for customers using firewall rules, you have to add this new endpoint to the allowlist. Without adjustment, you will face multiple issues to run Jobs, upload logs… etc. 
•  Will our Jobs and artifacts still be executable even if we do not make this adjustment? 
  • The new URL must be added to the firewall allowlist to ensure the tasks will run, if firewall proxy rules block connections to/from the service there will be multiple issues for task executions on Remote Engines as well as new artifacts being published.
•  When will the update be released for EU region? The notes only say “January 2026.” 
  • The switch from minio to storage endpoints on EU and US stacks will be done by Jan 14th, so the firewall allow list addition will have to be in place before this date.
• The allowlist contains URLs, but we'd like to add IPs, not URLs, to add/adjust our proxy and firewall allowlist. Where are these documented?
  • We can only provide DNS as IPs can change. Since it is a common for Cloud providers such as Amazon or Azure to dynamically change host IP when necessary, DNS will be the best way for such configurations.

Internal Investigation ID(s) 

Support-7691

Environment

• Talend Cloud