Official Support Articles

Recent Documents

Sort By:

Official Support Articles

Qlik Sense Client Managed: Adjust the MaxHttpHeaderSize for the Micro Services r...

When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too lar... Show More
When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

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 default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:
1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)
```
[globals]
LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
(...)
MaxHttpHeaderSize=16384
```
2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.
Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows

Show Less
By Sebastian_Linser 2023-08-18 / 08:13 AM Updated : 2024-12-12 / 07:59 AM

6 7523
Official Support Articles

Upgrading and unbundling the Qlik Sense Repository Database using the Qlik Postg...

In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see suppo... Show More
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
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
Show Less
By Mario_Petre 2022-05-24 / 02:40 AM Updated : 2024-11-13 / 09:31 AM

309 193553
Official Support Articles

What version of Qlik Sense Enterprise on Windows am I running?

Where can I find the installed version or service release of my Qlik Sense Enterprise on Windows server? You can locate the Qlik Sense Enterprise on ... Show More
Where can I find the installed version or service release of my Qlik Sense Enterprise on Windows server?

You can locate the Qlik Sense Enterprise on Windows version in three locations:
- The Qlik Sense Hub
- The Qlik Sense Enterprise Management Console
- The Windows Installed Programs menu
- The Engine.exe on disk
The Qlik Sense Hub
1. Open the Qlik Sense Hub
2. Locate and click the three horizontal dots on the landing screen (corner on the right)
3. Click the About link
4. The hub will display the installed version
The Qlik Sense Management Console
1. Open the Qlik Sense Management Console.
2. On the start screen, look in the bottom right corner for the version number. See Fig 1.
Fig 1

The Windows Installed Programs menu.
1. Open the Windows Installed Programs menu.
2. Expand the window until the version is visible. See Fig 2.
Fig 2

The Engine.exe
1. Open a Windows File explorer
2. Navigate to C:\Program Files\Qlik\Sense\Engine
3. Right-click the Engine.exe
4. Click Properties
5. Switch to the Details tab
6. The File version will be listed
Note that Qlik Sense Business and Qlik Sense SaaS do not list versions. They are managed by Qlik.

Show Less
By N/A 2017-07-05 / 02:50 AM Updated : 2022-12-14 / 03:11 AM

6 13041
Official Support Articles

Using REST Connector with OAuth2 against Microsoft Dynamics 365 Business Central

Background Microsoft is deprecating basic authentication in Microsoft Dynamics 365 Business Central (online), recommending users to instead authent... Show More

Background

Microsoft is deprecating basic authentication in Microsoft Dynamics 365 Business Central (online), recommending users to instead authenticate with OAuth2. This is in effect from version 20 of Business Central, rolled out in April 2022. Basic auth has been extended for users previously having Business Central v19 who now are upgraded to v20. New customers starting on version 20 must open a support ticket with Microsoft to have basic auth enabled. Basic auth will be turned off for all customers in Business Central v21 (targeted for October 2022).

Environment:

Qlik REST Connector
Qlik Cloud
Qlik Sense Enterprise on Windows

Assumed Scenario and Prerequisite

This article describes how the existing REST Connector in Qlik Sense can be configured to use OAuth2. The suggested OAuth flow uses Service-to-Service authentication against Microsoft Dynamics 365 Business Central. It requires that a single-page application is registered in the Azure portal with granted consent in the Business Central environment and that the related Client ID and Client Secret are known.

Obtain the Access Token

The configuration requires a separate connection definition for the initial login to get an access token from the Azure portal. The URL to use for this is:

https://login.microsoftonline.com/<BC Tenant ID>/oauth2/v2.0/token

Use the POST Method in a REST Connection

Within a REST Connector definition, use the URL noted above together with the POST method.

The request body must include the parameters Client ID (client_id) and the Client Secret (client_secret), together with grant_type=client_credentials and scope set to the API default (scope=https://api.businesscentral.dynamics.com/.default). You must separate the parameters with the ampersand character (&).

Adjust the Script to Capture a Token Parameter

This connection generates a JSON table (named ‘root’), which includes a column with the access token. You can extract the value of the access token into a parameter in the load script with the LET keyword.

Use TRACE in the script to output the accessToken value in the data load progress window. The token is necessary to copy as you will paste it in the subsequent step, for the initial load of data.

Get the Data with Separate REST Connection

The standard URL for the API endpoint is:

https://api.businesscentral.dynamics.com/v2.0/<environment name>/api/v2.0/<API resource>

See Microsoft documentation for alternatives and further details.

Use Query Header Parameters in REST Connection

Within a separate REST Connector definition, use the API URL together with the GET method, and other defaults or adjustments as required, to get access to the data from the desired Business Central API resource.

The connection definition must include two query header parameters, one for the authorization token and one to set accept-encoding to gzip, deflate.

The Authorization parameter must initially have the value Bearer followed by a valid accessToken value, for example, copied from the data load progress window in the previous step.

Adjust the Script to Dynamically use an Obtained Token

This connection generates a table with the data from the API resource defined in the URL. In this example, the company's resource was used (https://api.businesscentral.dynamics.com/v2.0/Sandbox/api/v2.0/companies).

Adjust the load script by adding a WITH CONNECTION statement including the Authorization header parameter and the accessToken parameter from the preceding script, i.e.
WITH CONNECTION (HTTPHEADER “Authorization” “Bearer $(accessToken)”)

This ensures that the new valid access token generated in the preceding part of the script gets inserted each time the load script is run.

You can configure additional API resources in separate connection definitions or by dynamically define the related URLs and tables in the load script.

Show Less

By Sonja_Bauernfeind 2022-05-11 / 10:22 AM Updated : 2022-09-05 / 08:27 AM

25 16061
Official Support Articles

Qlik Sense February 2023 and later: Apps listed as clickable links in the Qlik S...

From Qlik Sense February 2023 onwards, apps listed in the Qlik Sense Management Console (Apps view) are now represented with clickable links. Clicking... Show More
From Qlik Sense February 2023 onwards, apps listed in the Qlik Sense Management Console (Apps view) are now represented with clickable links. Clicking them will open the app directly on the hub.

This means the app names are no longer plain grey text but are now formatted as links (blue, underline). See Apps for details.

Example:

To disable clickable links in the Management Console:
1. On your Qlik Sense Enterprise Server, go to C:\Program Files\Qlik\Sense\CapabilityService
2. Open capabilities.json (using for example Notepad++)
3. Search for flag QmcOpenAppInHub
  Example:
  {
  "contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874",
  "originalClassName":"FeatureToggle",
  "flag":"QmcOpenAppInHub",
  "enabled":true
  },
4. Change "enabled":true to "enabled":false
5. Save and close the capabilities.json file
6. Restart the Qlik Sense Service Dispatcher service from the Windows services console
7. The links are now disabled
Known Limitation

Using only a custom virtual proxy prefix is currently not compatible. The default virtual proxy prefix must be accessible as the link generated will always refer to it.

Qlik is actively working on improving this feature: SHEND-1197.

Environment

Qlik Sense Enterprise on Windows February 2023 and above
Show Less
By Joseph_Musekura 2023-03-13 / 10:08 AM Updated : 2024-02-09 / 03:54 AM

25 6100
Official Support Articles

How to: Getting started with the Microsoft Outlook 365 connector in Qlik Applica...

This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation. Authentication and Authorization To... Show More
This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.

Authentication and Authorization

To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:
- Mail.Send
- User.Read
- Offline_access
Sending Email with the Microsoft Outlook 365 connector

The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.

The following parameters are available on the Send Email block:
- To: A comma separated list of recipients;
- CC: A comma separated list of recipients to which the email should be copied;
- BCC: A comma separated list of recipients to which the email should be blind copied;
- Subject: A title for your email;
- Type: Choose between plain text email or HTML;
- Body: The content of your email. You can use HTML for your email if chosen as the type.
Generating a report and sending an email with the report

As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.

Environment:

Qlik Automate

Show Less
By MarkGeurtsen 2022-11-08 / 07:25 PM Updated : 2022-11-09 / 04:02 AM

8 4811
Official Support Articles

Qlik Talend Product: On-prem/Hybrid Installer of Talend Data Stewardship could n...

Talend Data Stewardship Installer for on-prem and Hybrid version could not redirect the gateway.url to correct host from IAM server or Cloud Server an... Show More
Talend Data Stewardship Installer for on-prem and Hybrid version could not redirect the gateway.url to correct host from IAM server or Cloud Server and got error page.

Somehow, it points to localhost instead of the IP Server or HostName specified in the TMC->Configuration->TDS setting.

Resolution

Temporary Workaround
1. Edit data-stewardship.properties file which is available in <install_folder>\tds\config folder and change gateway.url to correct IP/Host (The real IP of the server on which TDS is installed )
2. iam/data/client/tds-client.json file also needs to be updated by adding URL item with the correct IP/Host
Final Solution

Wait for new installer versions released after R2025-05

Cause

It is a known bug from Installer level that IP/Host did not be propagated to the config of the Installed version of Talend Data Stewardship.

Internal Investigation ID(s)

Internal Jira case ID: SUPPORT-3964

Environment
- Talend Data Stewardship
- Talend Cloud
Show Less
By wei_guo 2025-06-18 / 03:45 AM Updated : 2025-06-18 / 03:45 AM

0 27
Official Support Articles

Qlik Replicate SAP Hana Source Initial Load: dates are replicated as 01.01.0101

Dates are processed to the target as 01.01.0101. This occurs when running a Full Load from a SAP Hana Source Endpoint while the Log-based CDC Mode is ... Show More
Dates are processed to the target as 01.01.0101.

This occurs when running a Full Load from a SAP Hana Source Endpoint while the Log-based CDC Mode is set on the SAP Hana task and the DATE columns are empty.

Resolution

This behavior has been identified as a defect (RECOB-9893) in Qlik Replicate 2024.11 SP02 and previous versions.

Fix Version

Install the latest Service Pack 2024.11 SP03 or any later releases.

If the latest Service Release is not available containing the Patch, contact Qlik Support.

Internal Investigation ID(s):

RECOB-9893

Environment
- Qlik Replicate 2024.11 SP02
Show Less
By Bill_Steinagle 2025-06-17 / 07:57 AM Updated : 2025-06-17 / 09:30 AM

0 55
Official Support Articles

Qlik NPrinting and RabbitMQ vulnerabilities in older RabbitMQ versions

Old versions of RabbitMQ include multiple vulnerabilities. This article covers: CVE-2020-5419 CVE-2022-31008 CVE-2017-4967 CVE-2019-11291 CVE-2017-49... Show More
Old versions of RabbitMQ include multiple vulnerabilities. This article covers:
- CVE-2020-5419
- CVE-2022-31008
- CVE-2017-4967
- CVE-2019-11291
- CVE-2017-4965
They do not impact Qlik NPrinting.

Qlik NPrinting 2023 versions and later use RabbitMQ 3.12, which is not affected by these vulnerabilities.

How can I verify the RabbitMQ version my Qlik NPrinting install uses?
1. Open the folder C:\Program Files\NPrintingServer
2. Find the folder named Rabbitmq_server-**
  
  This will show the deployed version.
  
  Example: C:\Program Files\NPrintingServer\rabbitmq_server-3.12.10
Environment
- Qlik NPrinting
Show Less
By David_Friend 2025-06-17 / 04:22 AM Updated : 2025-06-17 / 04:22 AM

0 103
Official Support Articles

Binary load fails with General Script Error when using app binary instead of .qv...

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 ... Show More
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
By Andre_Sostizzo 2015-12-03 / 05:54 PM Updated : 2025-06-04 / 11:06 AM

15 7370
Official Support Articles

Qlik NPrinting reports are not sent or tasks are stuck: 'Filters for request xxx...

A Qlik NPrinting task contains a report with filters applied, either on the report itself, the recipients, or the task itself. Not all recipients rec... Show More
A Qlik NPrinting task contains a report with filters applied, either on the report itself, the recipients, or the task itself.

Not all recipients receive the report, or the Qlik NPrinting task stalls.

The log files display the following error:

Filters for request xxx produce an invalid selection.

Other related errors that may appear in the Engine logs when running reports with invalid selections include:

ERROR: Error processing request of type Qlik.Reporting.Engine.Messages.Requests.FilterMaterializationRequest for sense app <app id>. ERROR: Cannot apply filter Filters:...
Bookmark: , Void: False to current document data. Requested fields with evaluates are: F\<field name>
...
Error processing request of type Qlik.Reporting.Engine.Messages.Requests.FormulaNodeRequest for sense app <app id>. ERROR: System.TimeoutException: Method "EvaluateEx" timed out

Resolution

The reports are not being generated due to filter incompatibility.

To resolve this:
1. Review the filters referenced in the logs and cross-check them in the source QlikView or Qlik Sense documents.
2. Apply the Qlik NPrinting filters manually to confirm which selections are causing the issue.
3. Fix the filters and rerun the report task.
Cause

Qlik NPrinting will not generate reports when the applied filters are incompatible. It automatically checks for incompatible filters at the beginning of task execution and stops report generation if any are detected. This is a standard feature in all Qlik NPrinting releases.

Without this safeguard, QlikView or Qlik Sense would remove the incompatible selections and proceed, potentially generating a report containing all (or no) data, which may expose confidential information.

What are incompatible filters?

Common incompatible filters are:

Duplicate Filter Application

Applying the same filter to multiple locations (such as to both a user and a task) can result in a conflict. Depending on how the filters interact, double selections can lead to all (or no) data being shown.

Removed or Non-Existent Filter Values

If a filter references a value that no longer exists in the source document, it becomes incompatible. For instance, if a filter was set to Country = "Germany" and the latest reload of the source data removed "Germany" from the Country field, the filter will no longer work.

Contextually Conflicting Filters (No Data in Common)

A filter might work independently, but it becomes incompatible when combined with other filters. For example, a filter for Country = "Germany" may function properly on its own. However, the selection is invalidated if you also apply Month = "April" if April has no data for Germany.

Environment
- Qlik NPrinting
Show Less
By Rakesh_HB 2025-06-17 / 03:14 AM Updated : 2025-06-17 / 03:14 AM

0 36
Official Support Articles

How to send straight table data to email as HTML table using Qlik Automate

This article provides an overview of how to send straight table data to email as an HTML table using Qlik Automate. The template is available on the t... Show More
This article provides an overview of how to send straight table data to email as an HTML table using Qlik Automate.

The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send straight table data to email as table' in the search bar, and clicking the Use template option.

You will find a version of this automation attached to this article: "Send-straight-table-data-to-email -as-HTML-table.json".

Content:
Full Automation

Automation structure

The following steps describe how to build the demo automation:
1. Add a variable called 'EmailBody' to build the email body, and append the body opening tag and opening text of the email as value to this variable.
2. Add another variable called 'EmailStraightTable' and append the table opening tag together with the table header opening tag as a value to this variable.
3. Use the 'Get Straight Table Data' block from the Qlik Cloud Services connector to get data from the straight table for a specific app to be sent as an email. Specify app ID, Sheet ID, and Object ID input parameters. You can use the do-lookup functionality to find value for all these parameters. There is a limit of 100,000 records that can be retrieved through the 'Get Straight Table Data' block. This block will not work with other table types.
4. Add a 'Loop' block to loop over the keys from the 'Get Straight Table Data' block response which act as the headers of the HTML table. Use the '{getkeys: {$.GetStraightTableData}}' formula in the 'Loop' block.
5. Add the key/column name as the header of the HTML table in the 'EmailStraightTable' variable block. Outside the loop, add the 'EmailStraightTable' variable block, and append the table header closing tag, and table body opening tag as values to this variable.
6. Add a 'Loop' block to loop over all the values from the 'Get Straight Table Data' block response. Within the 'Loop' block add the following blocks:
  1. Use the 'EmailStraightTable' variable block and append the table row opening tag as a value to this variable.
  2. Use another 'Loop' block to loop over all values from the straight table for the current key/ column of the straight table.
  3. Next, use the 'EmailStraightTable' variable block and append the table data opening tag along with the column value for the corresponding key from the straight table which ultimately gives a single row with values for all the keys in each iteration and the table data closing tag as value to this variable.
  4. Use the 'EmailStraightTable' variable block and append the table row closing tag as a value to this variable.
7. Add the 'EmailStraightTable' variable block and append the table body closing tag with table footer tags as a value to this variable.
8. Add the 'EmailBody' variable block and append the 'EmailStraightTable' variable, which contains the final HTML table with straight table data, together with the email footer, and body closing tag as a value to this variable.
9. Add a 'Send Mail' block from the Mail connector to send an email with the above constructed HTML table that contains straight table data. Specify values for all the mandatory input parameters. Please connect to the SMTP server by adding a connection to the Mail connector.
An example output of the email sent:

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

Related Content

How to export more than 100k cells using Get Straight Table Data Block

Environment
- Qlik Cloud Analytics
- Qlik Automate
Show Less
By AfeefaTk 2024-05-27 / 10:40 AM Updated : 2025-05-23 / 09:17 AM

1 2871

Qlik Sense OIDC: How to check user information from the userinfo endpoint manual...

This article explains how to request an access token manually from your Identity provider token endpoint and verify user information from the /useri... Show More

This article explains how to request an access token manually from your Identity provider token endpoint and verify user information from the /userinfo endpoint.

Environments:

Qlik Cloud (Except for "ADFS" and "Azure" Identity provider types - see here instead)

First of all, for testing purposes, add the URL "https://test/login/callback" used in this script in your Identity Provider (IdP) allowed redirect URIs. The reason we are doing this is because we want to request the token manually to check the userinfo endpoint content and not have it getting automatically processed by Qlik Sense.

Run the below PowerShell script to get your authorization URL. Variables authorization_endpoint, client_id, and scope need to be updated to match your IdP, those information can be found from the /.well-known/openid-configuration endpoint.

$authorization_endpoint = 'https://dev-4786010.okta.com/oauth2/v1/authorize'
$client_id = '3fgfdd23thuymwsiEANFd7'
$redirect_uri = [System.Web.HTTPUtility]::UrlEncode("https://test/login/callback")
$scope = 'openid%20profile%20email'
$code_challenge="7TsROgPKuP0hHoWWwEGqMsIOgzokT3xAz8kWoo7Ivp8"

#Paste this URL in your browser to get back the authorization code
$authorization_endpoint+'?response_type=code&client_id='+$client_id+'&redirect_uri='+$redirect_uri+'&state=xyzABC123&nonce=3O2bsVV99-kjikCWCxqzxOx007aXbKMUd0YXBwA3sUk&scope='+$scope+'&code_challenge_method=S256&code_challenge='+$code_challenge

Paste the URL output from the script in your browser and log in to your Identity provider, the URL should look like this:
```
https://dev-4786010.okta.com/oauth2/v1/authorize?response_type=code&client_id=3fgfdd23thuymwsiEANFd7&redirect_uri=https%3A%2F%2Ftest%2Flogin%2Fcallback&state=xyzABC123&nonce=3O2bsVV99-
kjikCWCxqzxOx007aXbKMUd0YXBwA3sUk&scope=openid%20profile%20email&code_challenge_method=S256&code_challenge=7TsROgPKuP0hHoWWwEGqMsIOgzokT3xAz8kWoo7Ivp8
```
After the authentication is completed, you will be redirected to https://test/login/callback with an authorization code in the URL, copy the authorization code that we will use in the next step.

Copy the value between code= and the next & sign. (The length of the authorization code may vary depending on the IdP)

Request the access token from the token_endpoint URL (also found from the /.well-known/openid-configuration endpoint)

$client_id = '3fgfdd23thuymwsiEANFd7'
$redirect_uri = [System.Web.HTTPUtility]::UrlEncode("https://test/login/callback")
$client_secret = '4Z45jlfsjf12l3231ljfsflsjfsdlriueiot3ucxh'
$token_endpoint = 'https://dev-4786010.okta.com/oauth2/v1/token'
$code_verifier="_fqY.Xg5srawq24h9_A57tjY-ycqX0PzzIcM7VcwLZRou_Mvqn-_tCTz4ICWcXoCTO8NXlm3b9RfGOjSZEH68a_gWgaLByddN5y52M06~Z8XlO3XMgOJRWK0DefsxcmC"

#Put your authorization code here
$auth_code = 'mq5iHdLyBSZkpFubWJC2v3hVptrYT2j9VeQ6QpgED_s'
$pair = "$($client_id):$($client_secret)"
$encodedCreds = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($pair))
$basicAuthValue = "Basic $encodedCreds"

$hdrs = @{}
$hdrs.Add("Authorization",$basicAuthValue)
$body = 'code='+$auth_code+'&grant_type=authorization_code&redirect_uri='+$redirect_uri+'&code_verifier='+$code_verifier

$response = Invoke-WebRequest -Uri $token_endpoint -Method Post -Body $body -Headers $hdrs -ContentType 'application/x-www-form-urlencoded'
echo $response.Content > C:\temp\okta-accesstoken.txt

Copy the value in "access_token" from the request response in order to use it for the next request.

Request the user information from the userinfo_endpoint (also found from the /.well-known/openid-configuration endpoint) using the access token:

#Fill in userinfo endpoint URL here
$userinfo_endpoint = 'https://dev-4786010.okta.com/oauth2/v1/userinfo'

#Fill in your access token here
$accesstoken = "Bearer eyJraWQiOiJoVUIzX1N0WUMtdkh..._oOtPSAHF7qSPITfjd3l9V6JykndcxPlmPg"

$hdrs = @{}
$hdrs.Add("Authorization",$accesstoken)

$response = Invoke-WebRequest -Uri $userinfo_endpoint -Method Get -Headers $hdrs
echo $response.Content

You can confirm if the expected claims are included in the user info endpoint or not.

Show Less

2577

Official Support Articles

Migrating Qlik Sense Client-Managed To Qlik Cloud

This Techspert Talks session covers: - What to plan for- Migration Pathways- Cloud Best Practices Chapters: 01:20 - Cloud Tenant Locations 01:47... Show More
This Techspert Talks session covers:

- What to plan for
- Migration Pathways
- Cloud Best Practices

Chapters:
- 01:20 - Cloud Tenant Locations
- 01:47 - Qlik Cloud Architecture
- 03:08 - Planning the migration
- 03:50 - Migration Journey
- 05:13 - Licensing Guardrails
- 06:39 - Migrating users, groups, and permissions
- 11:11 - Migrating apps
- 14:44 - Migrating the data connections
- 21:07 - Completed Migration
- 21:35 - 5 Key Take Aways
- 22:48 - Q&A: How to license sync with hybrid?
- 23:59 - Q&A: Best practices for 1 app migration?
- 24:47 - Q&A: What's included with license cost?
- 26:03 - Q&A: How to customize the UI?
- 26:45 - Q&A: How safe is the data in Cloud?
- 27:37 - Q&A: What are common stumbling blocks?
- 28:41 - Q&A: How are reload monitored?
- 29:28 - Q&A: What is the data size cap?
- 30:15 - Q&A: What cannot be migrated?
Resources:
Show Less
By Troy_Raney 2024-06-21 / 03:34 AM Updated : 2024-06-28 / 08:53 AM

2 2300
Official Support Articles

What Is the Service Account For Qlik Sense Enterprise on Windows?

The user that runs the Qlik Sense Enterprise on Windows services is commonly referred to as the Qlik Sense Enterprise service account. The user is def... Show More
The user that runs the Qlik Sense Enterprise on Windows services is commonly referred to as the Qlik Sense Enterprise service account. The user is defined as the "Log On As" user in Windows service settings.

In a multi-node deployment it is recommended to use the same domain user for all Qlik Sense services on all nodes the same deployment.
NOTE: Qlik Sense Repository Database service is an exception, and is expected to always run as Local System.

Confirm the current Qlik Sense Enterprise service account;
1. Login to Windows Server on Qlik Sense node
2. Open Services manager in Windows
3. Sort by Name column
4. Scroll down to show all Qlik Sense related processes in the window
5. Confirm that all services except Qlik Sense Repository Database runs with the same "Log On As" user
6. Repeat above steps on all nodes in the same Qlik Sense site to confirm that the same user is applied
Show Less
By ToniKautto 2020-01-28 / 07:32 PM Updated : 2021-07-23 / 12:55 PM

8 5128
Official Support Articles

Qlik NPrinting and the CVE-2025-32433 Erlang/OTP vulnerability

Erlang/Open Telecom Platform (OTP) has disclosed a critical security vulnerability: CVE-2025-32433. Is Qlik NPrinting affected by CVE-2025-32433? Reso... Show More
Erlang/Open Telecom Platform (OTP) has disclosed a critical security vulnerability: CVE-2025-32433.

Is Qlik NPrinting affected by CVE-2025-32433?

Resolution

Qlik NPrinting installs Erlang OTP as part of the RabbitMQ installation, which is essential to the correct functioning of the Qlik NPrinting services.

RabbitMQ does not use SSH, meaning the workaround documented in Unauthenticated Remote Code Execution in Erlang/OTP SSH is already applied. Consequently, Qlik NPrinting remains unaffected by CVE-2025-32433.

All future Qlik NPrinting versions from the 20th of May 2025 and onwards will include patched versions of OTP and fully address this vulnerability.

Environment
- Qlik NPrinting
Opens in new window

PDF Download

Word Download

Excel Download

PowerPoint Download

Document Download

Opens in new window

PDF Download

Word Download

Excel Download

PowerPoint Download

Document Download

Opens in new window

PDF Download

Word Download

Excel Download

PowerPoint Download

Document Download

Opens in new window

PDF Download

Word Download

Excel Download

PowerPoint Download

Document Download

Show Less
By Andrea_Bertazzo 2025-04-28 / 04:33 AM Updated : 2025-04-28 / 08:18 AM

2 1302

Official Support Articles

Qlik Talend Data Integration: Snowflake JDBC Driver Logs Switch Writing to Users...

When upgrading Talend Studio to a newer patch level that is at or higher than R2024-12, those Snowflake jobs that have logging enabled may suddenly sw... Show More

When upgrading Talend Studio to a newer patch level that is at or higher than R2024-12, those Snowflake jobs that have logging enabled may suddenly switch writing to the home directory (or users directory on Windows) instead of "/tmp" directory that the default file output.

If the home/users directory folder size has been restricted or there are other restrictions on the environment, those Snowflake jobs may fill up the home/users directory and error out outofmemory or get a Permission Denied Issue.

Resolution

In order to continue collecting logs from the Snowflake JDBC driver, you should create a JSON file to configure your logging on the Jobserver/Remote Engine instance. This JSON file will tell the Snowflake Driver what logging level it should be using, where to write the log, and any additional configurations that may be required for the use case. Once created and stored in a location the Jobserver/Remote Engine can access, create an environmental variable called "SF_CLIENT_CONFIG_FILE" that points to the specific folder where the JSON file was written.

An example of a logging JSON file for Snowflake has been shared below:

###########################################################
#   Default Logging Configuration File
#
# You can use a different file by specifying a filename
# with the java.util.logging.config.file system property.
# For example java -Djava.util.logging.config.file=myfile
############################################################
############################################################
#   Global properties
############################################################
# "handlers" specifies a comma-separated list of log Handler
# classes.  These handlers will be installed during VM startup.
# Note that these classes must be on the system classpath.
# ConsoleHandler and FileHandler are configured here such that
# the logs are dumped into both a standard error and a file.
handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler
# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers.  For any given facility this global level
# can be overriden by a facility specific level.
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level = INFO
############################################################
# Handler specific properties.
# Describes specific configuration information for Handlers.
############################################################
# default file output is in the tmp dir
java.util.logging.FileHandler.pattern = /tmp/snowflake_jdbc%u.log
java.util.logging.FileHandler.limit = 5000000000000000
java.util.logging.FileHandler.count = 10
java.util.logging.FileHandler.level = INFO
java.util.logging.FileHandler.formatter = net.snowflake.client.log.SFFormatter
# Limit the messages that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = INFO
java.util.logging.ConsoleHandler.formatter = net.snowflake.client.log.SFFormatter
# Example to customize the SimpleFormatter output format
# to print one-line log message like this:
#     <level>: <log message> [<date/time>]
#
# java.util.logging.SimpleFormatter.format=%4$s: %5$s [%1$tc]%n
############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################
# Snowflake JDBC logging level.
net.snowflake.level = INFO
net.snowflake.handler = java.util.logging.FileHandler

Cause

The change was done by Snowflake itself on the JDBC side, which can explain the driver changes, regardless of the Studio version being used. These changes are required for all Snowflake jobs that use a JDBC driver version higher than 3.14.4, which does get upgraded in Studio (and those affiliated Snowflake Components) from 3.13.30 to 3.18.0.

This can also apply for Studio instances older than R2024-12, where users have upgraded to a newer driver (such as 3.30.0) manually.

Support		*Professional Services ()**

Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning.		Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement.
Error messages Task crashes Latency issues (due to errors or 1-1 mode) Performance degradation without config changes Specific questions Licensing requests Bug Report / Hotfixes Not functioning as designed or documented Software regression		Deployment Implementation Setting up new endpoints Performance Tuning Architecture design or optimization Automation Customization Environment Migration Health Check New functionality walkthrough Realtime upgrade assistance

Official Support Articles

Featured Content

Support and Professional Services; who to contact when.

Qlik Support: How to access the support you need

1. Qlik Community, Forums & Knowledge Base

The Knowledge Base

Blogs

Our Support programs:

The Qlik Forums

Ideation

How to create a Qlik ID

2. Chat

3. Qlik Support Case Portal

​Your advantages:​

Problem Type

Priority

Severity

Escalate a Support Case

Phone Numbers

Resources

Recent Documents

Resolution

Environment:

Supported Scenarios

Upgrades

New installs

Requirements

Known limitations

Installing a new 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

The Qlik Sense Hub

The Qlik Sense Management Console

The Windows Installed Programs menu.

The Engine.exe

Background

Environment:

Assumed Scenario and Prerequisite

Obtain the Access Token

Use the POST Method in a REST Connection

Adjust the Script to Capture a Token Parameter

Get the Data with Separate REST Connection

Use Query Header Parameters in REST Connection

Adjust the Script to Dynamically use an Obtained Token

Known Limitation

Environment

Authentication and Authorization

Sending Email with the Microsoft Outlook 365 connector

Generating a report and sending an email with the report

Environment:

Resolution

Cause

Internal Investigation ID(s)

Environment

Resolution

Fix Version

Internal Investigation ID(s):

Environment

How can I verify the RabbitMQ version my Qlik NPrinting install uses?

Environment

Environment

Resolution

Cause

What are incompatible filters?

Environment

Full Automation

Automation structure

Related Content

Environment

Environments:

Resolution

Environment

Resolution

Cause

Your advantages: