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 (1.4.0): 

Qlik Sense February 2022 to Qlik Sense November 2023.

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

• Cannot migrate a 14.8 embedded database to a standalone
• 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 

You can access Qlik Sense demo apps from https://demos.qlik.com/.

If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.

If you are looking to download demo apps:

1. Go to https://demos.qlik.com/ 
2. Select Downloadable from the available Tags
   
3. Open the App
4. A Download button will be available (if logged in)
   
   

When attempting to deploy a Route in Talend Runtime, encountered the following error:

java.lang.NoClassDefFoundError: Could not initialize class org.talend.components.common.oauth.Jwt
Caused by: java.lang.NoClassDefFoundError: org/codehaus/jackson/map/ObjectMapper

Cause

Missing bundles for Jackson library.

Resolution

Launch the Karaf console (./trun) located in the <Runtime-Home>\bin directory, and then execute the following command:

list | grep Jackson

If the following bundles are not installed please install them using the command below:

bundle:install -s mvn:org.codehaus.jackson/jackson-mapper-asl/1.9.16-TALEND
bundle:install -s mvn:org.codehaus.jackson/jackson-core-asl/1.9.16-TALEND

Furthermore, you have the option to install the feature that encompasses all necessary bundles by running:

feature:install camel-jackson-avro

Environment

• Talend Studio R2025-02
• Talend Runtime R2025-02
• Azul Java 17 

With Qlik Application Automation, you can get data out of Qlik Cloud and distributing it to different users in formatted Excel. The workflow can be automated by leveraging the connectors for Office 365, specifically Microsoft SharePoint and Microsoft Excel. 

Here I share two example Qlik Application Automation workspaces that you can use and modify to suit your requirements. 

Content:

• Considerations
• Example 1: Scheduled Reports
• Example 2: On-Demand Reports
• Environment

Video:

Considerations

• This example is built on distributing a SharePoint link. It is also possible to use attachments with the Mail block (see Creating a Qlik Reporting Service report).
• Qlik Application Automation has a limit of 100,000 rows when getting data out of a Qlik Sense straight table object.
• The On-Demand example uses an extension in QSE SaaS to send data to the Automation. An update to the Qlik Sense Button object is expected soon, which will provide a native way to pass selections to an Automation.

Example 1: Scheduled Reports

1. Download the 'Scheduled Report.json' file attached to this document.
2. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right clicking in the editor canvas, and selecting 'Upload workspace'.
3. Select the 'Create Binary File (Personal One Drive)' block, select 'Connection' in the block configurator to the right, and then create your connection to Microsoft SharePoint.
4. Select the 'Get Straight Table Data' block. Under 'Inputs' in the block configurator, lookup your the App Id, Sheet Id, and Object Id for the relevant QSE SaaS table you wish to output.
5. Select the 'Create Excel Table With Headers' block, select 'Connection' in the block configurator, and then create your connection to Microsoft Excel.
6. Select the 'Send Mail' block. Under 'Inputs' in the block configurator update the 'To' to reflect the addresses you wish to deliver to.
7. With the 'Send Mail' block still selected, select 'Connection' in the block configurator and add your Sender details.
8. To test, Save and then Run the Automation
9. If you receive any warnings or errors, navigate to the relevant blocks and ensure your Connection is selected in the block configurator. 
10. Select the 'Start' block. Under 'Inputs' in the block configurator, change Run Mode to Scheduled and define your required schedule. 

Example 2: On-Demand Reports

Note - These instructions assume you have already created connections as required in Example 1.

1. Download the 'On-Demand Report v3.json' file attached to this document.
2. Download and install the 'qlik-blends' extension. See: 
   https://github.com/rileymd88/qlik-blends/files/6378232/qlik-blends.zip
3. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right-clicking in the editor canvas, and selecting 'Upload workspace'.
4. Ensure your Connections are selected in the block configurator for each of the following blocks, 'Create Binary File (Personal One Drive)', 'Create Excel Table With Headers', 'Add Rows To Excel Worksheet Table (Batch)', 'Create Sharing Link', and 'Send Mail'.  Save the Automation.
5. Select the 'Start' block and ensure Run Mode is set to Triggered. Make note of the of URL and Execution Token shown in the POST example. 
6. Open your chosen QSE SaaS application, and Edit the Sheet where you wish to add a Button to trigger an On-Demand report. 
7. Under 'Custom Objects' look for 'qlik-blends' from the Extensions menu and drag this into your Sheet.
8. Under the 'Blend' properties to the right, add-in your POST webhook URL and Token as noted in Step 5.
9. We will now add three measures to the 'qlik-blends' object. It is important you add them in the order described.  Add the first measure, using the following function in the expression editor: GetCurrentSelections()
10. Add the second measure, using the following function DocumentName()
11. The final measure will be the Object ID of the table you wish to use. To find the Object ID, select 'Done Editing'.  Then right click on the table, select 'Share', select 'Embed', then look for the Object ID under the preview. Copy this value, go back into Editing mode and paste this as your third measure value. 
12. With the 'qlik-blends' object selected, under Form select 'Add items'. For 'Item type' select Text. Under default value you can choose to add a default email address. For 'Label' and 'Reference'  type 'Email'. It is critical that Reference is updated to 'Email'.  Turn 'Required input' on. 
13. You can change the Appearance properties to suit your preferences, such as updating the Button label and message, enabling Dialog, and changing the Color under Theme.
14. Back in the Automation, under the Start Block. Set  'Run asynchronously' = yes to allow multiple requests to run at the same time (This will also increase the max run time from 1min to 60min)
15. Once happy, test the On-Demand report by entering an email and clicking the button.

This On-Demand Report Automation can be used across multiple apps and tables.  Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance. 

Environment

• Qlik Application Automation 
• Qlik Cloud 
• Microsoft Office 365

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.

Question I

Is there any limitation on Talend Data Stewardship storage space for campaigns/tasks creation?
 

For Talend Cloud Data Stewardship, regarding of Qlik Talend Help Documentation managing-tasks, this is a Warning: "You can store up to 20 GB of tasks in Talend Cloud Data Stewardship per account". 

The 20GB of tasks size is provided by mongo db stats on collections tds_tasks

For Talend on-prem Data Stewardship, there is no hard/soft Limit by default on storage per on-prem version as long as Talend Data Stewardship installation server has sufficient storage, please make sure to keep cleaning the old/unused campaigns/tasks to release storage from performance consideration.

Question II

Where to view the configuration about tds.tasks.storage.limit.mode and how to define the Limit?

There are 3 ways to define the limit:

1. For Cloud:
   • Talend Data Stewardship leverages the platform service tpsv-config service to define the max size. To do so, a property name tds_tasks_max_storage can be configured for a given tenant.
   • In case this property is not defined, a default value 20GB will be applied.
2. Manual Setting (onprem/hybrid)
   • Set the limit mode to manual setting 

     tds.tasks.storage.limit.mode=manualSetting

   • Define the limit via the property

     tds.tasks.storage.limit.value=   The defaut value is 20GB

3. No Limit

   tds.tasks.storage.limit.mode=disabled    No limit setting

   This is the default configuration for onprem/hybrid and no need for any extra setting

Question III

How to optimize campaign performance in Talend Data Stewardship?

To optimize your campaign performances in Talend Data Stewardship, you need to, at least, make sure the number of tasks in the campaign does not exceed 100,000.

The performances of a campaign can be impacted by various elements. When a campaign contains more than 100,000 tasks, a warning is displayed next to a campaign name in the Campaigns tab or in the Tasks tab. The Campaign Owner needs to, at least, reduce the number of tasks in the campaign below this threshold to remove the warning message.

For more information, please refer to Qlik Talend Help Documentation
campaign-performance-limitations

Besides, here are some elements to take into consideration to improve the performances of the campaign

• The number of tasks
• The number of attributes in the data model: Talend recommends not to exceed 50 attributes
• The campaign type
• The number of task sources in a Grouping or Merging campaign
• The number and type of constraints
• The number of rules
• The number of campaigns depending on the same data model

Environment

Talend Data Stewardship 

By default, the Oracle data type TIMESTAMP(6) WITH TIME ZONE is mapped to VARCHAR(38) in the SQL Server target when using Qlik Replicate. However, in some cases, you may prefer to preserve a more compatible datetime format on the SQL Server side. Below are two workarounds to achieve this:

Map to DATETIMEOFFSET(6) in SQL Server

You can map TIMESTAMP(6) WITH TIME ZONE to DATETIMEOFFSET(6) using the following transformation to trim the input:

substr($TZ, 1, 26)

This transformation will remove the time zone information.

For example, the source value "2025-04-18 14:43:06.000000000 +08:00" will become "2025-04-18 14:43:06.000000".

Without applying this transformation, Qlik Replicate may raise an error:

Invalid character value specified for cast

Map to DATETIMEOFFSET(7) in SQL Server

To retain both the full precision and the time zone, map the Oracle data type to DATETIMEOFFSET(7) and use the following transformation:

substr($TZ, 1, 27) || substr($TZ, 30, 7)

This approach preserves both the 7-digit fractional seconds and the time zone.

For example, the Oracle source value "2025-04-18 14:43:06.000000000 +08:00" will be converted to "2025-04-18 14:43:06.0000000 +08:00" on the SQL Server side.

Environment

• Qlik Replicate, all versions
• Oracle Server, all versions
• Microsoft SQL Server, all versions

With more than one data warehouse on your Microsoft Fabric target endpoint, the task may fail to find the target table and will produce the following error:

[TARGET_APPLY    ]T:  RetCode: SQL_ERROR  SqlState: 42S02 NativeError: 208 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Invalid object name 'Schema.Table'. Line: 1 Column: -1 [1022502]  (ar_odbc_stmt.c:5090)

The task may default to a different data warehouse than the one specified in your MS Fabric endpoint settings, which prevents the task from finding the target tables.

Resolution

The Internal Parameter additionalConnectionProperties can be applied to the Microsoft Fabric endpoint to ensure the right data warehouse is used.

Set the value to: database=DataWarehouseName

Where DataWarehouseName is the name of the warehouse you are trying to use under the Database name field in your MS Fabric endpoint.

For more information about Internal Parameters and now to set them, see Qlik Replicate: How to set Internal Parameters and what are they for?

Cause

This is caused by defect SUPPORT-2305 and affects tasks that use a default data warehouse other than the one specified in your MS Fabric endpoint. Symptoms can be found where this line of information does not match the value filled out in your MS Fabric Database name field:

[TARGET_APPLY    ]T:  ODBC database name: 'DifferentWarehouseName'  (ar_odbc_conn.c:639)

Internal Investigation ID(s)

SUPPORT-2305

Environment

• Qlik Replicate

The following error is thrown when running a Qlik Replicate task without sufficient authorization on the required Function module:

[AT_GLOBAL       ]E: java.lang.reflect.UndeclaredThrowableException com.sap.conn.jco.AbapException: (126) ERROR: ERROR Message 001 of class 00 type E, Par[1]: Not authorized to use this Function module java.lang.reflect.UndeclaredThrowableException         at com.sun.proxy.$Proxy94.getTableList(Unknown Source)
[METADATA_MANAGE ]E:  Failed to list datasets [1024719] (custom_endpoint_metadata.c:242)
[METADATA_MANAGE ]E:  Failed to get the capture list from the endpoint [1024719] (metadatamanager.c:4527)
[TABLES_MANAGER  ]E: Cannot get captured tables list [1024719]  (tasktablesmanager.c:1267)
[TASK_MANAGER    ]E: Build tables list failed [1024719] (replicationtask.c:2593)
[TASK_MANAGER    ]E: Task 'TEST_2LIS_13_VAITM_DELTA' failed [1024719]  (replicationtask.c:4020)

Resolution

Grant the necessary authorizations for /QTQVC/RFC to the communication user.

Cause

The Qlik Replicate user (specifically the communication user) lacks authorization to execute function modules under /QTQVC/RFC. These modules are essential for the replication process.

The missing role provides the necessary permissions to run these function modules, which are used by Qlik Replicate to fetch metadata and extract data through 2LIS_* extractors.

Environment

• Qlik Replicate

How can we get detailed table-level DML profiling data from Qlik Replicate?

Table-level DML profiling data can be retrieved by checking the Store change option when creating a Qlik Replicate task. See Store Changes Settings for details.

Once set, DML data will be saved in the target DB's <target_table>__ct table. DML statistics data can then be profiled from this table using customized SQL queries.

Environment

• Qlik Replicate

Are you looking for status information on Qlik Cloud?

Qlik makes data on uptime and incidents publicly available on status.qlikcloud.com.

There, you are able to:

• See the current operational health, from fully operational, to degraded, to full outages
• Review a history of past incidents beyond what is currently happening (login required)
• Subscribe to updates (login required)

What do I do if I experience an issue that is not reported?

Please contact Qlik Support.

How do I log in to the Qlik Cloud status page?

1. Navigate to status.qlikcloud.com
2. Click Login
   
   
   
   
3. From here, view historical information and subscribe to updates
   
   
   

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor and License Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

This article explains the steps to configure Kerberos with Qlik Sense. However, it's important to note that the actual setup, implementation, and configuration of Kerberos for Qlik is the responsibility of the customer.

For another set of instructions, see Seamless Single SignOn (SSSO) into Qlik Sense 

Note: The following will require appropriate permissions in Active Directory to add Service Principal Names on the account running Qlik Sense services.

A Service Principal Name may be registered using the following command:

setspn -A http/HOST serviceaccount

where

• HOST is the name of the server hosting Qlik Sense.
• serviceaccount is the account running Qlik Sense services.

Steps: 

1. Open a command prompt with administrative privileges and type :

setspn -U -S http/QlikServer1 COMPANYX\serviceAccount
setspn -U -S http/QlikServer1.companyx.local COMPANYX\serviceAccount

2. Go to the QMC > Proxy > Edit
Check the 'Enable Kerberos' checkbox.

NOTE: An SPN must be set for both the short hostname and FQDN for the target Qlik Sense server for Kerberos to work correctly. This is not related to URLs configured in the Web Client allowlist under the Virtual Proxy configuration.

For more information about Service Principal Names see: http://technet.microsoft.com/en-us/library/cc961723.aspx

Related Content:

Seamless Single SignOn (SSSO) into Qlik Sense 
Qlik Sense Mobile and Kerberos

This article explains how to avoid the "Failed to create search index" script error during reload.

A data load may fail with: 

An error occurred

Internal engine error.

The script log will show:

2017-02-28 17:17:55      Creating search index
2017-02-28 17:17:55      Failed to create search index
2017-02-28 17:17:55      Execution finished.

The cause is currently unknown. Suspected to be an App corruption caused by external influences.

Resolution

Solution 1

1. Remove all search index files from the shared location configured in your Service Cluster shared location for the app which fails to reload. To locate the AppID, see How to find App ID.
   Example: \\ShareDrive\Apps\Search\AppID folder
2. Reload the app again.

Solution 2

1. Open the Qlik Sense Management Console
2. Navigate to Engine
3. Select an engine
4. Open the tab Advanced
5. Uncheck "Create search index during reload"
6. Press Apply

Solution 3

Insert "Set CreateSearchIndexOnReload=0" in the load script.

Even if this is disabled during the reload, the search index will be created later after the first search request of users.

Solution 4

Increase the timeout value.

Rather than disabling or removing the Search Index, you can attempt to increase the timeout before the reload will error out.

To do so, you will need to modify the Qlik Sense engine settings.ini and add a customized timeout value. 

1. Follow the instructions documented in How to modify Qlik Sense Engine's Settings.ini 
2. Add SearchTimeoutLimit=40000
   Where 40000 is the default value and in milliseconds. Increase the value, for example by adding a 0 to increase it to 400000 or any value you wish to begin troubleshooting with. 

After upgrading to Talend Studio R2025-03, an ESB Job incorporating the tRestRequest component fails to start. During the deployment and start process, the following error was observed:

java.lang.ClassNotFoundException: jak

Cause

The issue arose due to the Talend Runtime (ESB) environment continuing to operate with an old version, specifically R2024-05, which lacks full compatibility with the newer Talend Studio R2025-03. The missing class (jak) indicates a discrepancy in the runtime libraries between Talend Studio and Talend Runtime container.

Resolution

Upgrade Talend Runtime (ESB) to version R2025-03, aligning it with Talend Studio version currently in use.

Environment

• Talend Data Integration 8.0.1

PostgreSQL has identified a vulnerability (CVE-2025-1094) that allows for SQL injection under certain scenarios. For more information, see CVE-2025-1094: PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation.

Resolution

To allow for quick mitigation of PostgreSQL vulnerabilities, Qlik offers the ability to run and manage your own PostgreSQL instance independently of what Qlik Sense Enterprise on Windows is shipped with. 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.

Recommendations

Upgrade to Qlik Sense Enterprise on Windows May 2025 IR

Qlik Sense Enterprise on Windows May 2025 IR includes PostgreSQL 14.17 in its installer. See the System Requirements for details.

Upgrade PostgreSQL

If you have already 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.

See Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL.

Verify your Qlik Sense Enterprise on Windows version's System Requirements before committing to a PostgreSQL version.

Unbundle and upgrade PostgreSQL using QPI

If you have not yet installed a standalone PostgreSQL instance, this is the preferred method to gain direct control to upgrade at your own pace. For instructions, see Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer.

Manually switch to a dedicated PostgreSQL database

An alternative method to migrate to a standalone PostgreSQL instance is available in How to configure Qlik Sense to use a dedicated PostgreSQL database.

Related Content

• System requirements for Qlik Sense Enterprise
• Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL 
• Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer 
• How to configure Qlik Sense to use a dedicated PostgreSQL database 

Internal Investigation ID(s)

SUPPORT-896

Environment

• Qlik Sense Enterprise on Windows

The following public URLs will have their IP addresses changed on the 19th of May 2025:

• talend-update.talend.com
• update.talend.com
• talendforge.org

This change is being done in a consolidation effort and will only affect your environment if you have previously created firewall exceptions for the old set of IP addresses. Note that Qlik does not recommend the use of IP addresses in exceptions. Add domain names to your allowlists wherever possible.

When will the IP address change happen?

On the 19th of May 2025, 10 AM Central European time.

How will the IP address change impact me?

No impact should be noticeable unless the previous IP addresses were used to create an exception by your network team.

The following symptoms indicate a change is necessary:

• Qlik Talend Studio halts during startup and when checking for updates. 
• The CICD pipeline fails
• Qlik Talend Administration Center fails to retrieve patch lists and fails to download patches

If you encounter any of the above, advise your network team to switch to using domain names or to update the IP addresses where applicable.

Changes

Environment

• Qlik Talend Studio
• Qlik Talend Administration Center

After upgrading Qlik Replicate to version 2024.11, testing the connection for a Microsoft Azure ADLS Gen2 target endpoint causes the Qlik Replicate services to crash.

The Windows Event Viewer logs the following error:

Faulting application name: repctl.exe, version: 2024.11.0.177, time stamp: 0x672b5c2a
Faulting module name: j9vm29.dll, version: 11.0.17.0, time stamp: 0x63600655
Exception code: 0xc0000005
Fault offset: 0x00000000000d780c
Faulting process id: 0x1ba4
Faulting application start time: 0x01db6c896871a7dd
Faulting application path: E:\Program Files\Attunity\Replicate\bin\repctl.exe
Faulting module path: E:\Program Files\Attunity\Replicate\jvm\bin\default\j9vm29.dll
Report Id: 3a00eb98-08d6-4c3a-a9cd-7ac48e0debe0
Faulting package full name:
Faulting package-relative application ID:

The repsrv.log records the errors:

V: load_dll: <- (at_loader.c:209)
E: An exception occurred!!! (win32_exception_handler.c:109)
E: Backtrace at exception: !{E:\Program Files\Attunity\Replicate\bin\at_base.dll!462bdb,E:\Program Files\Attunity\Replicate\bin\at_base.dll!37fde9,E:\Program Files\Attunity\Replicate\bin\at_base.dll!675af1,...,C:\windows\System32\KERNEL32.DLL!84d4,C:\windows\SYSTEM32
tdll.dll!51a11,}! (win32_exception_handler.c:110)
E: exception code is 3221225477 (win32_exception_handler.c:112)
E: tid=8152 (win32_exception_handler.c:115)
E: exception as string is EXCEPTION_ACCESS_VIOLATION (win32_exception_handler.c:118)
E: for more details about win32 exceptions, look at http://msdn.microsoft.com/en-us/library/aa908962.aspx (win32_exception_handler.c:121)
E: exception record (nest level = 0): (win32_exception_handler.c:42)
E: exception code: 3221225477 (win32_exception_handler.c:44)
E: exception flags: 0 (win32_exc)

Resolution

Performing a clean reinstallation of Qlik Replicate resolves the issue by restoring the correct JVM components and DLLs:

1. Stop all Qlik Replicate services
2. Back up the Qlik Replicate data directory
3. Uninstall Qlik Replicate via Windows Control Panel
4. Reinstall Qlik Replicate using the latest installation package
5. Start the Qlik Replicate services
6. Verify the ADLS Gen2 target endpoint and test the connection

Cause

The upgrade did not properly clean up the j9vm folder and related DLL files under the Attunity\Replicate\jvm directory, leading to conflicts during runtime.

Environment

• Qlik Replicate 2024.11
• Microsoft Azure ADLS Gen2 target endpoint, All Versions

When distributing an app with extensions from a client-managed Qlik Sense instance, these extensions are pushed to Qlik Cloud.

This happens despite the alert saying Extensions that are included in your apps will not be available in Qlik Sense Cloud in the Distribution Policy settings.

The issue only happens for tenants not in the EU, US, or AP regions.

Resolution

A fix was developed and will be available in future releases of Qlik Sense Enterprise on Windows. Review the Release Notes for the ID QCB-27940.

Cause

Product Defect ID: QCB-27940

The issue was caused by the distribution of extensions only being excluded for the original tenant regions (EU, US, and AP) and not for other regions, such as DE.

Exclusion URLs will now be built dynamically. When new regions are added, the bundled extensions will not be distributed. 

Internal Investigation ID(s):

QCB-27940

Environment

• Qlik Sense Enterprise on Windows
• Qlik Cloud Analytics

This capability is being rolled out across regions over time:

1. May 5: India, Japan, Middle East, Sweden
2. TBD: Asia Pacific, Germany, United Kingdom, Singapore
3. TBD: United States
4. TBD: Europe
5. TBD: Qlik Cloud Government

[Update: May 7] The previously-scheduled rollouts of Automation Sharing and Collaboration for some regions have been temporarily postponed. We are working on an updated release plan and updated release dates are soon to be determined (TBD). Thank you for your understanding.

With the introduction of shared automations, it will be possible to create, run, and manage automations in shared spaces. 

Content

• Allow other users to run an automation
• Collaborate on existing automations
• Collaborate through duplication
• Extended context menus
• Context menu for owners:
• Context menu for non-owners:
• Monitoring
• Administration Center
• Activity Center
• Run history details
• Metrics

Allow other users to run an automation

Limit the execution of an automation to specific users.

Every automation has an owner. When an automation runs, it will always run using the automation connections configured by the owner. Any Qlik connectors that are used will use the owner's Qlik account. This guarantees that the execution happens as the owner intended it to happen.

The user who created the run, along with the automation's owner at run time, are both logged in the automation run history.

These are five options on how to run an automation:

1. Run an automation from the Hub and Catalog
   
   
   
   
2. Run an automation from the Automations activity center
   
   

    

3. Run an automation through a button in an app
   
   You can now allow other users to run an automation through the Button object in an app without needing the automation to be configured in Triggered run mode. This allows you to limit the users who can execute the automation to members of the automation's space.
   
   More information about using the Button object in an app to trigger automation can be found in How to run an automation with custom parameters through the Qlik Sense button.
   
   
4. Programmatic executions of an automation
   
   
   1. Automations API: Members of a shared space will be able to run the automations over the /runs endpoint if they have sufficient permissions.
   2. Run Automation and Call Automation blocks
      
      
5. Note for triggered automations: the user who creates the run is not logged as no user specific information is used to start the run. The authentication to run a triggered automation depends on the Execution Token only.

Collaborate on existing automations

Collaborate on an automation through duplication.

Automations are used to orchestrate various tasks; from Qlik use cases like reload task chaining, app versioning, or tenant management, to action-oriented use cases like updating opportunities in your CRM, managing supply chain operations, or managing warehouse inventories.

Collaborate through duplication

To prevent users from editing these live automations, we're putting forward a collaborate through duplication approach. This makes it impossible for non-owners to change an automation that can negatively impact operations.

When a user duplicates an existing automation, they will become the owner of the duplicate. This means the new owner's Qlik account will be used for any Qlik connectors, so they must have sufficient permissions to access the resources used by the automation. They will also need permissions to use the automation connections required in any third-party blocks. 

Automations can be duplicated through the context menu:

As it is not possible to display a preview of the automation blocks before duplication, please use the automation's description to provide a clear summary of the purpose of the automation:

Extended context menus

• Start a run from the context menu in the hub
• Duplicate automation
• Move automation to shared space
• Edit details (owners only)
• Open in new tab (owners only)

Context menu for owners:

 

Context menu for non-owners:

 

 

Monitoring

The Automations Activity Centers have been expanded with information about the space in which an automation lives. The Run page now also tracks which user created a run.

Note: Triggered automation runs will be displayed as if the owner created them.

Administration Center

The Automations view in Administration Center now includes the Space field and filter.

The Runs view in Administration Center now includes the Executed by and Space at runtime fields and filters.

Activity Center

The Automations view in Automations Activity Center now includes Space field and filter.

Note: Users can configure which columns are displayed here.

The Runs view in the Automations Activity Center now includes the Space at runtime, Executed by, and Owner fields and filters.

In this view, you can see all runs from automations you own as well as runs executed by other users. You can also see runs of other users's automations where you are the executor.

Run history details

To see the full details of an automation run, go to Run History through the automation's context menu. This is also accessible to non-owners with sufficient permissions in the space.

The run history view will show the automation's runs across users, and the user who created the run is indicated by the Executed by field.

Metrics

The metrics tab in the automations activity center has been deprecated in favor of the automations usage app which gives a more detailed view of automation consumption.

Qlik Replicate provides the option to set different types of notification rules. These notifications then send emails when specific events occur during a task's runtime. 

Every notification rule is set for a specific event of interest. You can define one or more notification rules for one or more tasks.

For detailed information on the different notification options, please refer to the section Notification settings in the Qlik Replicate Users guide

This article describes how to set up a notification rule that will send an email to a recipient list when a task faces latency:

1. In the Qlik Replicate UI, go to SERVER (A), then select Notifications (B), and click New Notification... (C)
   
   
   
   
2. Click Task Events... (D) 
   
   Task events will notify on the task, while Server events notify on Qlik Replicate server events.
   
   
   
   
3. Name the rule (E) and configure it based on your specifications. For our task latency event, we configure the rule as follows:
   1. Expand Performance/Resources (F)
   2. Select Latency exceeds [ ] seconds and enter your desired value and define the Clear notification when latency drops below [ ] seconds value (G)
      
      In our example, a notification email will be sent when task latency exceeds 90 seconds and will then be cleared when latency drops to one minute (60 seconds).
      
      
      
      
      
4. Define the email addresses of the recipients to whom the email notification will be sent. You can also edit the email content and define the tasks to which the rule applies. 
   
   
5. Once finalized, the rule will appear in the notifications rule list. It will take effect once the task is next started.
   

To deactivate the notification, untick the active check box: 

Related Content 

• Qlik Replicate Loading Best Practices
• Troubleshooting Qlik Replicate Latency
• How to create a Replicate notification for an individual task
• Replicate "Any Error" Notification

Environment

• Qlik Replicate