Are you looking to download your purchased Qlik Products or download a Trial? All supported on-premise Qlik Products can be downloaded from Qlik's Product Download Site.

To access the Download Site, you need an active QlikID. You will be able to see all products your account is eligible for.

Qlik's download are hosted on GitHub. If you are unable to access GitHub and do not have the possibility of enabling exceptions, start a chat with us and we will be able to help you.

You can access the Download Page directly here, or navigate to it from the Community Home page:

1. Open the Qlik Community
2. Click on Support
3. Select Product Downloads
   
   
   
   

This shows the download page with the Latest release and patch preselected.

1. Choose a different filter in (1) Show Releases if you are looking for older product versions. By default, only the Latest release and patch will be displayed. 
   
   
   
   
2. From here:
   
   
   1. choose your Product Category (Qlik Data Analytics, Qlik Data Integration, Search All),
   2. your Product,
   3. your Release,
   4. and Release Number.
   5. Then click the Download Link
      
      

Unsupported versions are not available for download. See Product Lifecycle for details on what versions have reached end of support. 

Alternatively, instead of selecting your product directly, you can also search all available columns:

1. Click the Magnifying Glass
2. Begin typing your search
3. Select the result
4. Confirm the result

If you encounter issues with the download site start a chat with us and we will be able to help you right away.

 

Click here for video transcript

 

Show Less

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With two new Qlik Application Automation templates coupled with Qlik Data Alerts, you can now: 

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 required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. Repeat Step 1 to complete the update. 

The above allows you to deploy the monitoring apps to your tenant with a hands-off approach. Dive into the individual components below. 

Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.

Content:

• Part One: 'Qlik Cloud Monitoring Apps Installer' template overview
• Part Two: 'Qlik Cloud Monitoring Apps API Key Rotator' template overview
• Part Three: How to setup a Qlik Alert to know when an app is out of date
• A Qlik Cloud Monitoring Apps Workflow Demo (Video)
• FAQ

 

Part One: 'Qlik Cloud Monitoring Apps Installer' template overview

This automation template is a fully guided installer/updater for the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software GitHub and thus are subject to Qlik's open-source guidelines and policies.

For more information, refer to the GitHub repository.

 

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically handles pre-requisite settings, roles, and entitlements.
• Installs latest versions from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Can create custom reload schedules.
• Can reload post-install.
• Tags apps appropriately to track which are installed and their respective versions.
• Supports both user and capacity-based subscriptions

Click-through installer:

Flow:

Note that if the monitoring applications have been installed manually (i.e., not through this automation) then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

 

Part Two: 'Qlik Cloud Monitoring Apps API Key Rotator' template overview

 

This template is intended to be used alongside the Qlik Cloud Monitoring Apps for user-based subscriptions template. This automation provides the ability to keep the API key and associated data connection used for the Qlik Cloud Monitoring Apps up to date on a scheduled basis. Simply input the space Id where the monitoring_apps_REST data connection should reside, and the automation will recreate both the API key and data connection regularly. Ensure that the cadence of the automation’s schedule is less than the expiry of the API key.

 

Configuration

Enter in the Id of the space where the monitoring_apps_REST data connection should reside.

Ensure that this automation is run off-hours from your scheduled monitoring application reloads so it does not disrupt the reload process.

 

 

Part Three: How to setup a Qlik Alert to know when an app is out of date

Each Qlik Cloud Monitoring App has the following two variables:

• vLatestVersion: the latest version of the app released on Qlik’s OSS GitHub.
• vIsLatestVersion: a Boolean of whether the app’s current version is equal to the latest version of the app released on Qlik’s OSS GitHub (1 if true, 0 if false).

With these variables, we can create a new Qlik Data Alert on a per-app basis. For each monitoring app that you want to be notified on if it falls out of date:

1. Right-click on a chart in the app, select Alerts and then Create new alert.
2. Clear out the defaults and provide the alert with a name such as <Monitoring App Name> is Out of Date.
3. Select Add measure and select the fx icon to enter a custom expression. Enter the expression ’$(vLatestVersion)'. Ensure it is wrapped in single quotes, then provide the label for the expression Latest Version.
4. Select Add measure and select the fx icon to enter a custom expression. Enter the expression $(vIsLatestVersion), then provide the label for the expression Is Latest Version.
5. Confirm the Details & data tab resembles the following:
   
   
   
   
6. Navigate to the next tab, Conditions.
7. Set the Measure to Is Latest Version, the Operator to Equal to, and the Value to 0. This way, if the app is not the latest version (0), it will trigger the alert.
8. Confirm that the Conditions tab resembles the following:
   
   
   
   
9. Navigate to the Distribution tab and confirm that the alert is evaluated When data is refreshed.

Here is an example of an alert received for the App Analyzer, showing that at this point in time, the latest version of the application is 5.1.3 and that the app is out of date:

 

A Qlik Cloud Monitoring Apps Workflow Demo (Video)

 

FAQ

Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?

A: Yes. Run the installer, select which applications should be checked and select the space that they reside in. If any of the selected applications are not installed or are upgradeable, a prompt will appear to continue to install/upgrade for the relevant applications.

Q: What if multiple people install monitoring applications in different spaces?

A: The template scopes the applications install process to a “target” space, i.e., a shared space (if not published) or a managed space. It will scope the API key name to `QCMA – {spaceId}` of that target space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already and it will install the application leveraging those pre-existing assets.

Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?

A: Yes. The template receives the list of applications dynamically from GitHub. If a new monitoring application is released, it will become available immediately through the template.

Q: I would like to be notified whenever a new version of a monitoring applications is released. Can this template do that?

A: As per the article above, the automation templates are not responsible for notifications of whether the applications are out of date. This is achieved using Qlik Alerting on a per-application basis as described in Part 3.

Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?

A: The history is preserved in the prior versions of the application’s QVDs so the data is never deleted and can be loaded into the older version. Each upgrade will generate a new set of QVDs as the data models for the applications sometimes change due to bug fixes, updates, new features, etc. If you want to preserve the history when updating, the application can be upgraded with the “Publish side-by-side” method so that the older version of the application will remain as an archival application. However note that the Qlik Alert (from Part 3) will need to be recreated and any community content that was created on the older application will not be transferred to the new application.

Show Less

I encountered this error when testing a csv file source endpoint.

When I setting up the task, I used the defaults in the Source File endpoint.

From logs I saw:

00041100: 2022-03-25T10:26:45 [SOURCE_UNLOAD ]E: Data error found: No delimiter found after a valid value on quotes mode - file: C:\tmp\datatest.csv, Record number: 2, Offset: 10 [1020417] (csv_util.c:545)
00041100: 2022-03-25T10:26:45 [SOURCE_UNLOAD ]E: CSV Util failed to write value to buffer [1020417] (csv_util.c:1003)
00041100: 2022-03-25T10:26:45 [SOURCE_UNLOAD ]E: Failed to read record number: 2. [1020417] (file_unload.c:259)
00041100: 2022-03-25T10:26:45 [SOURCE_UNLOAD ]E: Failed to init unloading table. [1020417] (file_unload.c:395)

When I opened in Notepad, I saw my csv file had CRFL carriage return and not FL.

 

I updated the source endpoint settings to resolve the 'Record delimiter field'.

 

Table was then able to load in the task. 

 

Environment

• Qlik Replicate 

 

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.

 

Show Less

Trying to access Qlik Sense Hub or Management Console (QMC) leads to the getting "refused to connect" on the web browser.

Investigating the issue with the command netstat | findstr :443 confirms there is not service listening on port 443 (or port QMC/Hub proxy is set to listen on).

Case 1:

An inspection of the System_Repository log located in C:\ProgramData\Qlik\Sense\Log\Repository\Trace shows an error message relating to being unable to remove soft deleted records. Sample:

Case 2:

The Repository Service to update fails on a table that iolates foreign key constraint.

• Qlik Sense Enterprise on Windows 

 

Cause:

In November 2017, February 2018, April 2018 and June 2018, when the Qlik Sense Repository Service initializes, it attempts to clean up the underlying Repository Database. If there are records which have broken referential integrity then the Repository Service will fail to initialize. This is a consequence of a change in behavior in November 2017/February 2018 where the Repository no longer does soft deletes.

This script can be obtained from the official Qlik site: Failed to remove soft deleted records. 
If logged on to our support site, it can be directly downloaded from the attachment. The attachment is unavailable for anonymous users. 

 

Resolution:

This article uses the recursive (recurse) cleanup sql script. After upgrading to Qlik Sense November 2017 or February 2018, the administrator is unable to access the Hub and/or QMC.

This article also fixes database issues and soft deletes, which cause numerous other problems besides being unable to access the QMC or HUB after an upgrade. This script is necessary to be run if upgrading from an older version to 11.14.3 or newer.
 

1. Stop all services but the Qlik Sense Repository Database
   • If using a stand-alone PostgreSQL server to host Qlik Sense content, then stop all Qlik Sense Services
2. Take a backup of the Qlik Sense Repository Database
   • Sample command using cmd.exe: cd / & mkdir QSR & "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin\pg_dump.exe" -h localhost -p 4432 -U postgres -b -F t -f "c:\QSR\QSR_backup_%date:~-4,4%%date:~-10,2%%date:~-7,2%.tar" QSR
     • This assumes that:
       • Qlik Sense is installed to C:\Program Files
       • That the site is not using a stand-alone PostgreSQL server
         • Make any necessary adjustments if neither of those assumptions are true
3. Download the attached .sql file and place it into the same directory as pg_dump.exe
4. Run the following command in cmd.exe (run them one at a time and hit Enter then continue with the next one):
   • cd C:\"Program Files"\Qlik\Sense\Repository\PostgreSQL\9.6\bin
   • SET PGCLIENTENCODING=utf-8
   • chcp 65001
   • psql.exe -h localhost -p 4432 -U postgres -d QSR -e -f recurse_cleanup.sql
     • Note: If Qlik Sense is installed to a non-default directory then make the necessary adjustments
5. Start all Qlik Sense Services
6. Validate that the error about Failed to remove soft deleted records is not present in the System_Repository log
7. If this does not resolve the issue then do contact Qlik Support for a more customized query

Show Less

Qlik NPrinting tasks appear to run but are stuck on the same percentage.

Qlik NPrinting can work for days or even weeks, completing tasks correctly. Suddenly, all task stops at different levels of execution. New tasks start, but stay on 0%.

Idle sessions have already been removed by applying How to remove the Idle Connections from Nprinting Related processes.

This error message is shown in the rabbit logs in C:\ProgramData\NPrinting\RabbitMQ for a default installation:

{{badmatch,{error,eacces}}

Qlik NPrinting is installed on a Windows 2019 server, and the version of Qlik NPrinting works with RabbitMQ 4 or higher (see the system requirements page to identify your Qlik NPrinting track).

Environment

• Qlik NPrinting all versions

 

Resolution

Restarting all Qlik NPrinting and Qlik Sense services can temporarily resolve the problem.

It is possible to mitigate the problem by installing the latest release of Qlik NPrinting, but this is still not a full solution, as the same issue may repeat due to a defect in Windows Server 2019.

A complete solution is to upgrade the operating system where Qlik NPrinting is installed to a higher version.

 

Cause

The problem is caused by specific updates affecting Windows file system components in Windows Server 2019 that occasionally prevent system access for our messaging service.

Show Less

Instead of pulling the data from the Primary node, which can potentially negatively affect performance, we can force Qlik Replicate to connect to a secondary read-only node during Full Load.

To do so:

1. When starting the task for the first time, Qlik Replicate will connect to the primary database and create a publication with all required articles. Once the creation of the publication is finished and the articles are added to the publication, stop the task. 
   
   
2. Set a new Internal Parameter in the SQL server endpoint, routing the connections to the secondary node.
   
   Parameter: additionalConnectionProperties   
   Value:  ApplicationIntent=ReadOnly
   
   For more information regarding Internal Parameters, see  Qlik Replicate: How to set Internal Parameters and what are they for.
   
   
3. Start the reload. As soon as you finished the Full load, stop the task and remove the additional parameter which you added in Step 2.
   
   
4. Resume the task. All connections will now resume on the primary node. 

 

 

Environment

Qlik Replicate 

Show Less

Qlik Sense Search Folder is growing in size.

Smart search is the global search tool in Qlik Sense, enabling you to search the entire data set in your app from any sheet in the app. See Using Smart Search on the official Qlik Online Help for details. 

This search is indexed to disk at %Share%/Apps/Search.

As time goes on, the index grows and commits more disk space. 
 

Environment: 

 

Resolution:

The contents of the Qlik Sense Search folders can be deleted to free up disk space. The content pertains to App ID's, so it would be best to remove those which are not often used. The only effect this would have is increasing the amount of time needed to complete a Smart Search for this same App in the future.

Qlik Sense can also be configured to purge the Search Folder on a schedule. The setting will need to be applied in the settings.ini of either the Qlik Sense Enterprise Server or the Qlik Sense Desktop. For information on how to edit the settings.ini file, reference How to modify Qlik Sense Engine's Settings.ini.
 

Qlik Sense Server	%PROGRAMDATA%/Qlik/Sense/Engine/Settings.ini
Qlik Sense Desktop	%USERPROFILE%/Documents/Qlik/Sense/Settings.ini

 

Name

ServerPurgeSearchIndexFileInterval

Default Value

3600

Description

• -1 the search index folder is never purged.
• 0 or negative (except -1), the purge happens constantly.
• strictly positive value, the search index folder is purged each ServerPurgeSearchIndexFileInterval seconds.

The purge system removes the unused search index files. In addition, it removes the oldest used search index files until the search index folder is smaller than ServerSearchIndexFileDirectoryMaximumSizeInMBytes.

Name

ServerSearchIndexFileDirectoryMaximumSizeInMBytes

Default Value

-1

Description

Maximum size of the search index directory in megabytes. During the periodic purge, old indexes are removed until the total size of index files is below this threshold. If negative, do not limit the size of the directory.

 

Make sure to add both parameters mentioned above into the settings.ini, the cleaning will happen at the specified intervall but only after the size limit is reached.

Show Less

The Data Load Editor in Qlik Sense Enterprise on Windows 2025 experiences noticeable performance issues.

 

Resolution

The issue is caused by defect SUPPORT-6006. Qlik is actively working on a fix.

Fix Version

A fix is planned for the next possible patches. Review the Release Notes for SUPPORT-6006.

Workaround

A workaround is available. It is viable as long as the Qlik SAP Connector is not in use.

1. In a Windows file browser, navigate to C:\Program Files\Common Files\Qlik\Custom Data\
2. Move the QvSapConnectorPackage directory to a different location

No service restart is required.

 

Internal Investigation ID(s) 

SUPPORT-6006

 

Environment

• Qlik Sense Enterprise on Windows

Show Less

This article outlines recommended retention policies for Oracle redo logs and provides detailed recovery steps in scenarios where redo logs are needed. It includes guidance on preserving logs, identifying stream positions, verifying log availability, and using SCN-based recovery with SQL_REDO extraction for issue resolution.

Resolution

Generally, Qlik recommends a 24-hour retention period for redo logs, but this can vary depending on the storage capacity and backup policies of each organization, as they have different requirements.

When customers back up their redo logs, they typically retain backups for at least 2 weeks to 1 month. This allows them to restore the logs if necessary. The specific policy regarding the retention of redo logs in backup media should be clarified with the customer.

Steps to Take When Redo Logs Are Required for Recovery

1. Preserve the Redo Logs: When an incident occurs, it’s critical to preserve the redo logs as quickly as possible. This ensures that they can be replayed if necessary.
   
   
2. Identify the Stream Position: First, identify the stream position of the record that is failing. You can use the task log to locate the problematic record and its corresponding stream position.
   
   
3. Verify Redo Log Existence: Once you have the stream position, determine the corresponding redo log sequence number and thread number. Verify whether the redo log still exists on disk.
   
   If it exists on disk, copy it to a different filesystem to ensure it is not deleted by RMAN backups.
   
   If the redo log has already been deleted, you will need to restore it from backup media. The DBA can assist in restoring the file from backup.

Replay the Redo Logs

1. Locate the Redo Log File: Once the redo log is available, query the v$archived_log view to find where the redo log file is located. You can use the following SQL:
   

   SELECT name, sequence#, thread#, first_change#
   FROM v$archived_log
   WHERE sequence# = [sequence#] AND thread# = [thread#];

2. Get the SCN (System Change Number): Use the first_change# value from the query above as the starting point for the redo log recovery.
   
   
3. Create a New Task in Replication: In your replication setup, create a new task and add the affected table. In the advanced options, provide the SCN value from the first_change# column, which marks the point where the task should start.
   
   
4. Verify Reproduction: After setting the SCN, verify whether you can reproduce the issue. If you can, proceed with the next step.
   
   
5. Log Mining and SQL_REDO: Use standard log mining to extract the SQL_REDO statements from the redo logs. These can be found in the V$logmnr_contents view. The SQL_REDO statements will provide the actual SQL that was executed, which will allow you to check if all column data was included in the redo log. 

By following these steps, you can ensure proper recovery from redo logs and address any issues related to missing or inconsistent data.

 

Environment

• Qlik Replicate

Show Less

During a CICD artifact update or redeployment, the custom context variables are lost.

 

Cause

CICD only publishes a new version of the artifact to the Qlik Talend Management Console. When creating a task via the Qlik Talend Management Console API call, if the user includes the following parameters in their JSON request (as demonstrated in the Resolution section), it will result in updating the task with the newly published artifact and the default artifact context values.

 

Resolution

When creating a task via the Qlik Talend Management Console API for the first time, please ensure that the "overrideWithDefaultParameters" parameter is set to false in the "autoUpgradeInfo" section of the JSON body. For example:

"autoUpgradeInfo": {
"autoUpgradable": true,
"overrideWithDefaultParameters": false
}

By setting overrideWithDefaultParameters to false during task creation, you can prevent the task from being updated with default context values for future artifact deployments via CICD.

 

Related Content

Qlik Talend API documentation

 

Environment

• Qlik Talend Studio

Show Less

This article is provided as is. For further customization or assistance, reach out to Qlik's Professional Services or engage in our Qlik Sense Administration and Configuration forum.

This details the steps required to use a Microsoft Excel (XLS) file as a User Directory in the User Directory Connector (UDC).

The instructions in this article are written for Microsoft Office 2016, which has reached end of life as of October 2025. As an alternative, use Microsoft 365 Access Runtime. See Download and install Microsoft 365 Access Runtime.

The required Microsoft Excel Driver may not be installed by default.  

1. Verify if the drivers are already installed on your server:
   
   Open the Windows Registry Editor and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\
   
   
    

   

   
   
   If it is not installed, download the latest Microsoft package.
   
   This file can be directly sourced from the Microsoft Download site. The 64-bit version is required.
   
   Example: Microsoft Access Database Engine 2016 Redistributable
   
   
   
2. Run the installer
   
   
3. Refresh the registry editor and verify that the drivers are correctly installed
   
   
   
   
4. Create an XLS file that contains your users
   
   A sample XLS file is attached to this article:
   
   
   • This file contains two sheets, "MyUsers" and "Attributes"; they can be renamed to fit your naming convention
   • The first sheet contains two columns: "userid" and "name"; those names are important and mandatory.

     Do not change them, or the import will fail.

   • The second sheet contains three columns: "userid", "type", and "value"
     
     
5. Create a new UDC
   1. Navigate to your User Directory Connector in the Qlik Sense Management Console
   2. Create a new connection: Excel (via ODBC)
   3. Untick the checkbox Sync user data for existing users
   4. User table Name must match your first sheet ("[MyUsers$]" here)
   5. Attribute table name must match the second sheet ("[Attributes$]" here)
   6. Modify the connection string to point to your Excel file: DRIVER={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=C:\temp\SomeUsers.xls
      
      
      
      
6. Validate and check in the logs
   
   The following should be logged:
   
   Connection creation verified.
   Connection open verified.
   Tables verified.
   The userid field of the [MyUsers$] table is verified successfully.
   The name field of the [MyUsers$] table is verified successfully.   
   The userid field of the [Attributes$] table is verified successfully.   
   The type field of the [Attributes$] table is verified successfully.     
   The value field of the [Attributes$] table is verified successfully.  
   
   
7. Sync the UDC and check the logs
   
   Started synchronizing all users for ...
   Started syncing users
   ODBC dataReader have been successfully created
   Retrieved 3 entities from directory 'TEST' of type Repository.UserDirectoryConnectors.ODBC.OdbcExcel
   Database done with 3 users and 0 groups in user directory (TEST, ...)
   Ended saving users in repository
   Finished synchronizing all users for ...
   
   
8. Verify that the users were added in the Qlik Sense Management Console
   
   
   
   
9. Verify the attributes are reflected in the user's properties
   
   
   

 

Troubleshooting

The following errors you may be logged in C:\ProgramData\Qlik\Sense\Log\Repository\Trace\<SERVER>_UserManagement_Repository.txt
 

Verify that the name and userid columns in the file are correctly named and have not been renamed. 

 

Environment 

• Any version of Qlik Sense

Show Less

The new Straight Table was moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one.

This article aims to answer any frequently asked questions around this switch, beginning with:

• The old table will not be removed anytime soon. It will continue to work until further notice. We encourage you to subscribe to the Qlik Support Blog and What's New in Qlik Cloud to stay ahead of updates.
• The old table will not be updated further. Use the new table to benefit from future improvements.
• We monitor your feedback and will improve the functionality of the new table.

FAQ

What improvements does the Straight table come with?

Here are some examples:

• Grid styling
• Totals styling
• Pagination or virtual scroll
• Scrollbars outside of the table
• Add, delete many fields at the same time
• Cell font family, size and color styling
• Font styling by expression
• Column width options pixels, percentages
• Chart exploration, end user can pick dimensions and measures
• Header on/off
• Zebra striping
• Null value styling
• Selection info in export
• Totals in export
• Titles in export
• Cyclic dimension controls in dropdown

Will the old table be removed?

No, the old table will continue to work in the foreseeable future. Any changes will be notified in advance. Regardless, we highly recommend upgrading your tables as soon as possible to enjoy the new Straight Table's new functions. 

How do I convert to the new table?

The easiest way to convert your tables is to drop the new table chart onto the old one.

1. First, copy the old table
2. Edit the sheet that includes the Table
3. Open the Charts pane
4. Drag the Straight table over your table
5. Choose Convert to: Straight table

The new table looks different and offers more functionality that must be enabled to be used.

When will the old table be deprecated?

Not anytime soon, it will be a soft fade out. The new Straight Table will be the preferred choice for all new applications, and we anticipate many will upgrade to benefit from new functionality. Over time, the usage of the old table will diminish until most applications are using the new table anyway.

Will this affect Qlik Sense Enterprise on Windows?

Qlik Sense Enterprise on Windows will have the table feature aligned with Qlik Cloud Analytics in a future release.

I’m not happy with X and Y of the new table, will that be changed?

We’re closely monitoring feedback on the new table and are dedicated to creating the best possible experience, including improvements to accessibility. We are committed to accessible standards so people with disabilities can use our products. Printing, the tables should, of course, print in as consistent a manner as possible. As for usability, we aim to enable experienced users to reach functionality quickly, while also not overwhelming new users.

Originally, the old table was identified as table (retired). We removed the (retired) label.

 

Environment

• Qlik Analytics

Show Less

After upgrading Qlik Replicate from 2023.11 to 2024.11 or 2025.5, testing connections and other UI endpoint operations fail whenever you are using an ADDON (such as UDF) that retrieves the password from the Vault.

The task works correctly. It is only the connection test that fails.

The following messages are from the task logs:

Error: SYS-E-HTTPFAIL, SYS-E-HTTPFAIL, Failed in prepare imp for Snowflake.. SYS,GENERAL_EXCEPTION,SYS-E-HTTPFAIL, Failed in prepare imp for Snowflake.,SYS,GENERAL_EXCEPTION,Failed in prepare imp for Snowflake,Failed to deobfuscate password

[INFRASTRUCTURE ]W: Password provider is not registered (at_secure.c:2454) (child_proc_exec.c:36)
[SERVER ]E: Failed to deobfuscate password [1003200] (cloud_imp.c:3700) (child_proc_exec.c:36)
[INFRASTRUCTURE ]T: Process id 396 : 00005244: 2025-06-26T12:42:26 [SERVER ]E: Failed in prepare imp for Snowflake [1003200] (cloud_imp.c:4770) (child_proc_exec.c:36)

 

Resolution

This has been identified as a defect (ID RECOB-10010).

Fix Version

The fix is scheduled for the Qilk Replicate release in November 2025. See the Release Notes for details.

Cause

The child REPCTL process does not identify the ADDON.

Internal Investigation ID(s)

RECOB-10010

 

Environment

• Qlik Replicate

Show Less

A Qlik Replicate task with MSSQL as a source and Oracle as a target fails during Full Load and CDC.

The error logged:

Failure in resolving table name for objid %

 

Resolution

Failure in resolving table name for objid is commonly linked to temporary tables. When applications create temporary tables, they are logged in the transaction log. Qlik Replicate attempts to resolve the object ID from the log, but may fail if the object is unknown or transient.

To investigate further and to identify if there is data loss:

• Run the following query to identify the table name:

  SELECT name, object_id FROM sys.objects WHERE type = 'U' AND object_id LIKE '%' -- Replace % with the actual objid

   

• Consult with your database administrator to determine whether the object is a temporary table or if any maintenance activities have been performed. 
  
  
•  If the table is a temporary table, you can disregard the error.
  
  
• If data loss occurs due to maintenance activities, please open a support case with Qlik Support.

 

Cause

This error is often associated with temporary tables. When an application creates temporary tables, they are written to the transaction log. 

Qlik Replicate then attempts to read an unknown object ID from this log and fails to resolve it to a table name.

 

Environment

• Qlik Replicate

Show Less

Insight Advisor supports natural language searches, such as Show me Product Inventory for Japan under 2500. The feature is available in Qlik Sense Enterprise on Windows (September 2019 and later) and Qlik Cloud. 

For Insight Advisor best practices with Qlik Cloud, see:

Best practices for improving performance of apps 
Best practices for using business logic 
Best practices for asking questions in Insight Advisor 

 

For general advice and information for Qlik Sense Enterprise on Windows (client managed), see the whitepaper attached to this article.  

If you're instead looking for information about Qlik Insights Advisor chat, see Configuring Qlik Insight Advisor Chat in Qlik Sense Enterprise on Windows.

 

Related Content:

Creating visualizations with Insight Advisor 
Using natural language with Insight Advisor
Tagging master items 
Configuring Qlik Insight Advisor Chat in Qlik Sense Enterprise on Windows 
Customizing logical models for Insight Advisor 




 

Show Less

You may encounter an error : 400 - Invalid SNI when calling Talend Runtime API (Job as service) after installed 2025-02 patch or later. In the past before the patch version R2025-02 of Talend Runtime Server, it did work well when using the same certificate for SSL connection with Talend Runtime Server and did not cause any issue. 

The SNI validation is active after 2025-02 patch or later.

 

Resolution

There are three options to slove this issue

1. Obtain and install a proper certificate that references the correct host name and then access it with the hostname rather than by IP.
2. Disable SNI host check.
3. Tell Talend component to resolve IP as hostname

Disable SNI Host Check

This has the same security risk as jetty before it was updated (low security)

In <RuntimeInstallationFolder>/etc/org.ops4j.pax.web.cfg file, please add

jetty.ssl.sniRequired=false

and 

jetty.ssl.sniHostCheck=false

 

Or configuring these jetty parameters in <RuntimeInstallationFolder>/etc/jetty.xml or jetty-ssl.xml file

• Find the <New class="org.eclipse.jetty.server.SecureRequestCustomizer"> block in your jetty.xml or jetty-ssl.xml 
  
  
• Edit the <Arg name="sniRequired" ...> and <Arg name="sniHostCheck" ...> lines so that the properties' defaults are set to false as shown below:
  
  

  <New id="sslHttpConfig" class="org.eclipse.jetty.server.HttpConfiguration">
  <Arg><Ref refid="httpConfig"/></Arg>
  <Call name="addCustomizer">
  <Arg>
  <New class="org.eclipse.jetty.server.SecureRequestCustomizer">
  <Arg name="sniRequired" type="boolean">
  <Property name="jetty.ssl.sniRequired" default="false"/>
  </Arg>
  <Arg name="sniHostCheck" type="boolean">
  <Property name="jetty.ssl.sniHostCheck" default="false"/>
  </Arg>
  <Arg name="stsMaxAgeSeconds" type="int">
  <Property name="jetty.ssl.stsMaxAgeSeconds" default="-1"/>
  </Arg>
  <Arg name="stsIncludeSubdomains" type="boolean">
  <Property name="jetty.ssl.stsIncludeSubdomains" default="false"/>
  </Arg>
  </New>
  </Arg>
  </Call>
  </New>

  

 

Resolve IP to Hostname

If the certification includes the domain name, you should use that domain name instead of the IP with the Jetty security updates in Talend Runtime Server.

But if your DNS server does not resolve the IP, you must call it by the IP address, so please check it at first to see if the workaround is feasible for your current situation.

In the examples the hostname is unresolvedhost.net and the IP is 10.20.30.40.

Try this API call at the command line:

curl -k -X GET --resolve unresolvedhost.net:9001:10.20.30.40 https://unresolvedhost.net:9001/services/

or

curl -k -X GET -H "Host: unresolvedhost.net" https://10.20.30.20:9001/services/

If this works, in your Talend component that makes the API call, go to "Advanced settings" or "Headers" table, add a row with Key: Host and Value: The hostname that matches your SSL certificate (e.g. unresolvedhost.net)

This will instruct Talend to send the correct Host header, which most HTTP clients (including Java's HttpClient) will also use as the SNI value during the TLS handshake.
 

Cause

The SNI enforcement is there for a security reason. With the 2025-02 patch, the Jetty components on Talend Runtime Server resolved a CVE security issue where they allowed a hostname to connect to a server that doesn't match the hostname in the server's TLS certificate.

Certificates require the URI not to be localhost or an IP address, and to have at least one dot, so a fully qualified domain name is best.

 

 

Related Content 

 https://stackoverflow.com/questions/69945173/org-eclipse-jetty-http-badmessageexception-400-invalid-sni

 

 

Environment

Talend ESB 

Show Less

A binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with:

General Script Error

or

Binary load fails with error Cannot open file

 

Before Qlik Sense Enterprise on Windows November 2024 Patch 8, the Qlik Engine permitted an unsupported and insecure method of binary loading from applications managed by Qlik Sense Enterprise on Windows.

Due to security hardening, this unsupported and insecure action is now denied.

Binary loads of Qlik Sense applications require a QVF file extension. In practice, this will require exporting the Qlik Sense app from the Qlik Sense Enterprise on Windows site to a folder location from which a binary load can be performed. See  Binary Load and Limitations for details.

Example of a valid binary load:

Binary [lib://My_Extract_Apps/Sales_Model.qvf];

Example of an invalid binary load:

"Binary [lib://Apps/777a0a66-555x-8888-xx7e-64442fa4xxx44];"

 

Environment

• Qlik Sense Enterprise on Windows November 2024 Patch 8 and any later releases

Show Less

A third-party certificate was configured in the Qlik Sense Proxy, but is not being used.

The connection is not private" NET::ERR_CERT_COMMON_NAME_INVALID may be displayed on HUB access. 

Qlik Sense Enterprise on Windows uses self-signed and self-generated certificates to protect communication between services, as well as user web traffic to the hub and management console.  It is possible to use a third-party-issued SSL certificate to protect client web traffic. Using the self-signed certificate will cause a certificate warning to be displayed in the web browser (such as Google Chrome or Internet Explorer). 

If the third-party certificate for the Qlik Sense Proxy Service is not fully compatible with Qlik Sense or it does not have the correct attributes and cyphers, the Qlik Sense Repository Service will revert to using the default certificates. The following error may occur in the Proxy Security logs:

Example:  C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\HOSTNAME_Security_Proxy.txt

No private key found for certificate 'CN=qliksense.domain.com' ([CERTIFICATE THUMBPRINT HERE]) Couldn't find a valid ssl certificate with thumbprint [CERTIFICATE THUMBPRINT HERE] Reverting to default Qlik Sense SSLCertificate Set certificate 'CN=qliksenseserver1.domain.com' ([CERTIFICATE THUMBPRINT HERE]) as SSL certificate presented to browser

 

Resolution:

In order for Qlik Sense Enterprise to correctly recognize the third-party certificate as valid, the certificate will have to meet the following requirements:

Note: Root and Intermediate CA certificates need to be correctly installed. Should any be missing, Qlik Sense proxy will not use the server certificate and will revert back to using the self-signed certificate instead.

Certificates that are known to work well with Qlik Sense have the following attributes:

• Certificates that are x509 version 3. More information including filename extensions under https://en.wikipedia.org/wiki/X.509 
• Use signature algorithm sha256RSA
• Use signature hash algorithm sha256
• Signed by a valid, and OS/browser configured , CA
• Are valid according to date restrictions (valid from/valid to)
• Key in format CryptoAPI (not in CNG)
• The certificate itself has to contain private key no matter what Qlik Sense version.

 Related Content:

How to: Change the certificate used by the Qlik Sense Proxy to a custom third party certificate 

 

Show Less

After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed. 

The Qlik Sense System_Repository log file will read:

"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes." 

Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt

This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.

Resolution

The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.

Take a backup of your environment before proceeding.

1. Verify the version you are using and verify that you are at least on one of the versions (and patches) listed: 
   
   
   • May 2023 Patch 13
   • August 2023 Patch 10
   • November 2023 Patch 4 
   • February 2024 IR
     
2. Back up the following files:
   
   
   • C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   • C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
     
     *where C:\Program Files can be replaced by your custom installation path.
     
     
3. Stop the Qlik Sense Repository Service and the Qlik Sense Dispatcher Service
   
4. Open and edit the capabilities.json with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   2. Locate: "enabled": true,"flag": "QMCShowAppSize"
   3. Change this to: "enabled": false,"flag": "QMCShowAppSize"
   4. Save the file  
5. Open and edit the repository.exe.config with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   2. Locate: </appSettings>
   3. Before the </appSettings> closing statement, add:
      <add key="AppStaticByteSizeUpdate.Enable" value="false"/>
   4. Save
6. Start all Qlik Sense services
7. Verify you can access the Management Console

If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article. 

Related Content

Show base memory size of apps in QMC

 

Internal Investigation:

QB-22795
QB-24301

 

Environment

Qlik Sense Enterprise on Windows  May 2023, August 2023, November 2023, February 2024. 

Show Less

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

 

Environment:

Qlik NPrinting 

 

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

• Connection reloads
• Publish Task executions

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

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

• GET
• POST

 

Requirements of REST user account:

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

 

Creating REST "GET" connections

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

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

 

Creating REST "POST" connections

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

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

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

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

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

 

Related Content

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

 

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

 

Show Less