Setting up Qlik Web Connectors may require you to provide administrator approval and consent for the respective apps (such as Azure storage, Office 358 Sharepoint, and similar). This article aims to provide you with information on what needs to be requested.

Account Types 

Personal Account: Once the connector has authorization to access the Microsoft account, there will be a corresponding entry in "My apps": https://myapps.microsoft.com/

Example:

 

Enterprise Account: These require additional configuration.

• Enabled for users to sign-in? (Yes)
• User assignment required? (Yes) This field is only mandatory if the administrator wants to restrict access to the users.
• Visible to users? (Yes)
   
   

 

Testing (with administrator rights)

1. Open the Qlik Office 365 SharePoint connector
2. Select "Can Authenticate"
3. Press the green button "Authenticate"
   
   
   
   
4. You will be redirected to a Microsoft login page that should look similar to the following picture:
   
   
   
   
5. If Azure grants access, the Qlik Webconnector application will generate a code as follows:
   
   

Testing (without administrator rights)

If a basic (non-admin) user attempts to authenticate, the following message would appear in Azure:

To fix this, the administrator needs to grant access to the users.

Once the administrator grants access, the user will see the warning:

Need admin approval

A list of required API permissions for each connector

At this stage, you will need to request your administrator to enable the following API permissions for your user:

Azure Storage

• https://storage.azure.com/user_impersonation
• https://graph.microsoft.com/User.Read
  
  

MSCRM V2

• https://admin.services.crm.dynamics.com/user_impersonation
• https://graph.microsoft.com/User.Read
  
  

Office365 SharePoint

• https://graph.microsoft.com/User.Read
• https://microsoft.sharepoint.com/AllSites.Manage
• https://microsoft.sharepoint.com/AllSites.Read
• https://microsoft.sharepoint.com/MyFiles.Read

OneDrive V2

• https://graph.microsoft.com/User.Read
  
  Files.Read.All will also be required, although this is not set in the app registration.
  
  

Outlook 365

• https://graph.microsoft.com/Calendars.Read
• https://graph.microsoft.com/Calendars.Read.Shared
• https://graph.microsoft.com/User.Read
• https://graph.microsoft.com/User.Read.All
• https://graph.microsoft.com/User.ReadBasic.All
  
  contacts.read, contacts.read.shared, files.read, files.read.all, mail.read, mail.read.shared will also be required, although this is not set in the app registration. 

 

Environment:

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows
• Qlik Web Connectors

Show Less

Some connectors require an encryption key before you create or edit a connection. Failing to generate a key will result in:

Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.

 

Environment

Qlik Sense Desktop February 2022 and onwards
Qlik Sense Enterprise on Windows February 2022 and onwards
all Qlik Web Storage Provider Connectors 
Google Drive and Spreadsheets Metadata 

 

Resolution

PowerShell demo on how to generate a key:

# Generates a 32 character base 64 encoded string based on a random 24 byte encryption key
function Get-Base64EncodedEncryptionKey {
$bytes = new-object 'System.Byte[]' (24)
(new-object System.Security.Cryptography.RNGCryptoServiceProvider).GetBytes($bytes)
[System.Convert]::ToBase64String($bytes)
}

$key = Get-Base64EncodedEncryptionKey
Write-Output "Get-Base64EncodedEncryptionKey: ""${key}"", Length: $($key.Length)"

Example output:

Get-Base64EncodedEncryptionKey: "muICTp4TwWZnQNCmM6CEj4gzASoA+7xB", Length: 32

 

Qlik Sense Desktop

This command must be run by the same user that is running the Qlik Sense Engine Service (Engine.exe). For Qlik Sense Desktop, this should be the currently logged-in user.

Do the following:

1. Open a command prompt and navigate to the directory containing the connector .exe file. For example:

   "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"
   
   

2. Run the following command:

   QvWebStorageProviderConnectorPackage.exe /key {key}

   Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

3. You will receive a confirmation message:

   Info: Set key. New key id=qseow_prm_custom.

   Info: key set successfully!

 

Qlik Sense Enterprise on Windows

The {sense service user} must be the name of the Windows account which is running your Qlik Sense Engine Service. You can see this in the Windows Services manager. In this example, the user is: MYCOMPANY\senseserver.

Do the following:

1. Open a command prompt and run:

   runas /user:{sense service user} cmd. For example:runas /user:MYCOMPANY\senseserver

2. Run the following two commands to switch to the directory containing the connectors and then set the key:

   1. "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"

   2. QvWebStorageProviderConnectorPackage.exe /key {key}

      Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

3. You should repeat this step, using the same key, on each node in the multinode environment.

4. Encryption keys will be stored in: "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\"

   For example, encryption keys will be stored in "C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\"

Always run the command prompt while logged in with the Qlik Sense Service Account which is running your Qlik Sense Engine Service and which has access to all the required folders and files. 

Cause

This security requirement came into effect in February 2022. Old connections made before then will still work, but you will not be able to edit them. If you try to create or edit a connection that needs a key, you will receive an error message: Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING) - you must manually set an encryption key before creating new connections.

 

Related Content

Setting an encryption key

 

 

Show Less

Qlik Automate is a no-code automation and integration platform that lets you visually create automated workflows. It allows you to connect Qlik capabilities with other systems without writing code. Powered by Qlik Talend Cloud APIs, Qlik Automate enables users to create powerful automation workflows for their data pipelines.

Learn more about Qlik Automate.

 

In this article, you will learn how to set up Qlik Automate to deploy a Qlik Talend Cloud pipeline project across spaces or tenants.

To ease your implementation, there is a template on Qlik Automate that you can customize to fit your needs.
You will find it in the template picker: navigate to Add new → New automation → Search templates and search for ‘Deploying a Data Integration pipeline project from development to production' in the search bar, and click Use template.

ℹ️ This template wil be generally available on October 1, 2025.

Use case and pre-requisites

In this deployment use case, the development team made changes to an existing Qlik Talend Cloud (QTC) pipeline.

As the deployment owner, you will redeploy the updated pipeline project from a development space to a production space where an existing pipeline is already running.

To reproduce this workflow, you'll first need to create:

• Two data spaces:
• A DEV space
• A PROD space
• Two source databases
• A DEV source database
• A PROD source database
• Two target databases
• A DEV target database
• A PROD target database

Using separate spaces and databases ensures a clear separation of concerns and responsibilities in an organization, reduces the risk to production pipelines while the development team is working on feature changes.

 

Workflow steps:

1. Export the updated pipeline project from the DEV space
2. Get the project variables from DEV
3. Update the project variables for PROD before import
4. Stop the pipeline currently running in production
5. Import your project to the PROD space
6. Prepare your project and check the status
7. Restart the project in PROD

ℹ️ Note: This is a re-deployment workflow. For initial deployments, create a new project prior to proceeding with the import.

 

Step-by-step workflow

1. Export the updated pipeline project from the DEV space

Use the 'Export Project' block to call the corresponding API, using the ProjectID.

This will download your DEV project as a ZIP file. In Qlik Automate, you can use various cloud storage options, e.g. OneDrive. Configure the OneDrive 'Copy File on Microsoft OneDrive' block to store it at the desired location.

To avoid duplicate file names (which may casue the automation to fail) and to easily differentiate your project exports, use the 'Variable' block to define a unique prefix (such as dateTime). 

 

2. Get the project variables from DEV

From the 'Qlik Talend Data Integration' connector, use the 'Get Project Binding' block to call the API endpoint.

The 'bindings' are project variables that are tied to the project and can be customized for reuse in another project. Once you test-run it, store the text response for later use from the 'History' tab in the block configuration pane on the right side of the automation canvas:

 

3. Update the project variables for PROD before import

We will now use the 'bindings' from the previous step as a template to adjust the values for your PROD pipeline project, before proceeding with the import.

From the automation, use the 'Update Project Bindings' block. Copy the response from the 'Get Project Binding' block into the text editor and update the DEV values with the appropriate PROD variables (such as the source and target databases). Then, paste the updated text into the Variables input parameter of the 'Update Project Binding' block.

ℹ️ Note: these project variables are not applied dynamically when you run the 'Update Bindings' using the Qlik Automate block. They are appended and only take effect when you import the project.

 

4. Stop the pipeline currently running in production

For a Change Data Capture (CDC) project, you must stop the project before proceeding with the import.

Use the 'Stop Data Task' block from the 'Qlik Talend Data Integration' connector. You will find the connectors in the Block Library pane on the left side of the automation canvas.

Fill in the ProjectID and TaskID:

ℹ️ We recommend using a logic with variables to handle task stopping in the automation. Please refer to the template configuration and customize it to your needs.

 

5. Import your project to the PROD space

You’re now ready to import the DEV project contents into the existing PROD project.

⚠️ Warning: Importing the new project will overwrite any existing content in the PROD project.

Using the OneDrive block and the 'Import Project' blocks, we will import the previously saved ZIP file.

ℹ️ In this template, the project ID is handled dynamically using the variable block. Review and customize this built-in logic to match your environment and requirements.
 

 

After this step is completed, your project is now deployed to production.

 

6. Prepare your project and check the status

It is necessary to prepare your project before restarting it in production. Preparing ensures it’s ready to be run by creating or recreating the required artifacts (such as tables, etc).

The 'Prepare Project' block uses the ProjectID to prepare the project tasks by using the built-in project logic. You can also specify one or more specific tasks to prepare using the 'Data Task ID' field. In our example, we are reusing the previously set variable to prepare the same PROD project we just imported.

If your pipeline is damaged, and you need to recreate artifacts from scratch, enable the 'Allow recreate' option. Caution: this may result in data loss.

 

Triggering a 'Prepare' results in a new 'actionID'. This ID is used to query the action status via the 'Get Action Status' API block in Qlik Automate. We use an API polling strategy to check the status at a preset frequency. 

Depending on the number of tables, the preparation can take up to several minutes.

Once we get the confirmation that the preparation action was 'COMPLETED', we can move on with restarting the project tasks.

If the preparation fails, you can define an adequate course of action, such as creating a ServiceNow ticket or sending a message on a Teams channel.

ℹ️ Tip: Review the template's conditional blocks configuration to handle different preparation statuses and customize the logic to fit your needs.

 

7. Restart the project in PROD

Now that your project is successfully prepared, you can restart it in production.

In this workflow, we use the 'List Data Tasks' to filter on 'landing' and 'storage' for the production project, and restart these tasks automatically.

 

All done: your production pipeline has been updated, prepared, and restarted automatically!

Now it’s your turn: fetch the Qlik Automate template from the template library and start automating your pipeline deployments.

 

Related Content

About Qlik Automate

Start a Qlik Talend Cloud® trial

How to get started with the Qlik Talend Data Integration blocks in Qlik Automate

How to use the Qlik Automate templates

Show Less

This template was released on September 29, 2025.

Many customers rely on the Capacity Consumption Report in Qlik Cloud to understand usage and billing patterns. Until now, deploying and refreshing this app required repetitive manual steps: downloading from the admin console, publishing it into a managed space, and re-publishing every time a new version was needed.

This approach made monitoring difficult and often left customers with out-of-date insights.

 

What's new

A new Qlik Automate template automates the end-to-end deployment of the consumption app into a managed space of your choice. Once set up, the app is refreshed daily - ready for admins or billing users to work with.

With this in place, you can:

• Stay current – The app refreshes once per day (morning CET), so your analytics reflect the latest usage data.

• Collaborate easily – Place the app directly into a managed space for shared access.

• Enable subscriptions and alerts – Users can subscribe to sheets or KPIs, or create alerts on thresholds that matter to them.

• Maintain governance – The template creates/uses the right spaces and applies roles automatically.

• Eliminate manual work – No more re-publishing or searching through personal space copies.

 

How it works

 

• The automation checks that you are on a capacity-based subscription (your app size must be 100MB or less; larger data sets still need to be deployed manually or via script).

• It ensures you are a TenantAdmin (required for license and app access).

• It creates a staging space (for imports) and a managed space (for sharing).

• It imports the latest version of the app into staging, then publishes it to the managed space.

• You can configure how many historic versions you want to keep in the shared space. By default, no staged apps are kept.

 

Scheduling

Since the underlying data is refreshed once per day in the morning CET, we recommend scheduling this automation to run around midday CET. This ensures that your managed space always holds the latest daily version of the app.

 

Requirements

 

• TenantAdmin role

• Capacity-based subscription

• Report size ≤100MB (larger reports cannot currently be deployed with Qlik Automate)

 

Get Started

1. Create a new automation, navigate to the App Installer category, and select the Capacity consumption app deployer template.

2. Update the variables (space names, versions to keep).

3. Test manually once.

4. Schedule it to run daily (around midday CET).

Once enabled, you’ll have a single source of truth for consumption reporting - ready to drive alerts, subscriptions, and collaborative analysis across your admins.

 

 

 

Related Content

• Review the Help documentation on the capacity report to understand its metrics and counters.

 

Environment

• Qlik Cloud

Show Less

Beginning with Qlik Sense Enterprise on Windows 2024, Qlik has extended CSRF protection to WebSockets. For reference, see the Release Notes.

In the case of mashups, extensions,and or other cross-site domain setups, the following two steps are necessary: 

1. Add additional response headers. These headers help protect against Cross-Site Forgery (CSRF) attacks.
2. Change the applicable code in your mashup or extension.

 

Content

• Add the Response Headers
• Adapt your Mashup or Extension code
• Workflow
• Verification

 

Add the Response Headers

The three additional response headers are:

Access-Control-Allow-Origin: https://localhost:8080
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: qlik-csrf-token

Localhost and port 8080 are examples. Replace them with the appropriate hostname. Defining the port is optional. 

If you have multiple origins, seperate them by comma.

Example:

For more information about adding response headers to the Qlik Sense Virtual proxy, see Creating a virtual proxy. Expand the Advanced section to access Additional response headers.

 

Adapt your Mashup or Extension code

In certain scenarios, the additional headers on the virtual proxy will not be enough and a code change is required. In these cases, you need to request the CSRF token and then send it forward when opening the session on the WebSocket. See Workflow for a visualisation of the process.

An example written in Enigma.js is available here:

• Authentication: Qlik Sense JSON Web Token (JWT) 
• Code Sample 

The information and example in this article are provided as-is and are not directly supported by Qlik Support. More assistance can be found on the Qlik Integration forum. Professional Services are available to help where needed.

Workflow

Workflow

Verification

To verify if the header information is correctly passed on, capture the web traffic in your browser's debug tool.

 

Environment

• Qlik Sense Enterprise on Windows November 2024 and later

Show Less

Oracle to SQL Violation of PRIMARY KEY constraint. During full load, table is suspended due to Primary Key Violation.

[TARGET_LOAD     ]E:  RetCode: SQL_SUCCESS  SqlState: 23000 NativeError: 2627 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Violation of PRIMARY KEY constraint 'SERVICE_SYS_C001817631'. Cannot insert duplicate key in object 'dbo.SERVICE'. The duplicate key value is (G2190)

00010944: 2025-06-16T10:35:15 [TASK_MANAGER    ]W:  Table 'dbo'.'SERVICE' (subtask 1 thread 1) is suspended. RetCode: SQL_SUCCESS  SqlState: 23000 NativeError: 2627 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Violation of PRIMARY KEY constraint 'SERVICE_SYS_C001817631'. Cannot insert duplicate key in object 'dbo.SERVICE'. The duplicate key value is (G2190).; Failed to commit 10000 rows to target 'dbo.SERVICE'  (replicationtask.c:3239)

 

Resolution

This could be a classic capitalization issue between Oracle source to SQL target

Example

CREATE TABLE adam.products (
product_sku VARCHAR2(50) NOT NULL,
product_name VARCHAR2(255) NOT NULL,
price NUMBER(10, 2),
CONSTRAINT products_pk PRIMARY KEY (product_sku)
);

Then insert 2 identical records except for their capitalizations:

• Insert the first row with a lowercase PK.

  INSERT INTO adam.products (product_sku, product_name, price)
  VALUES ('key-logi-mx-m', 'Logitech MX Keys Mechanical (lowercase sku)', 169.00);

• Insert the second row with an uppercase PK
• This is also a simple, standard insert. It will success.
  

  INSERT INTO adam.products (product_sku, product_name, price)
  VALUES ('KEY-LOGI-MX-M', 'Logitech MX Keys Mechanical (UPPERCASE SKU)', 169.00);

Now, since Oracle is case-sensitive and the default installation of SQL Server is case-insensitive, it is a duplicate in SQL.

RetCode: SQL_SUCCESS SqlState: 23000 NativeError: 2627 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Violation of PRIMARY KEY constraint 'PRODUCTS_PRODUCTS_PK'. Cannot insert duplicate key in object 'ADAM.PRODUCTS'. The duplicate key value is (KEY-LOGI-MX-M). [1022510] (sqlserver_endpoint_imp.c:5764)

 

 

Cause

It is changeable, by ALTER table on target.

ALTER TABLE ADAM.Products
ALTER COLUMN product_sku VARCHAR(50) COLLATE Latin1_General_CS_AS NOT NULL;

For Replicate , you would have to:

1. ALTER table on SQL target.
2. Set task to truncate on full load.
3. Reload table.

 

Environment

Qlik Replicate 

Show Less

Unable to login to Talend Administration Center(TAC) and getting the error after providing the credentials:

"SSO prevent direct login from windows Please login by identity provider system"

 

Resolution

1. Check if you are not enabled SSO and have accidentally turned it on.
2. If yes for point #1, then please try to get into TAC using the emergency SSO user: defining-emergency-user-for-talend and then manually set SSO to false in the Configuration setting of TAC.
3. If for some reason the emergency SSO user fails, then please try to modify the database configuration table to set to false and restart TAC. 
   Below are the steps to do the same
   • Go to the TAC database and find table "configuration" then set

     sso.field.useSSOLogin=false

   • Restart the TAC server

Ensure you take a backup of the table and also are using correct credential details.

 

Cause

Accidentally turn on SSO login or might be DB table corruption.

 

Environment

Talend Administration Center 8.0.1

Show Less

Show Less

Stitch only offers account consolidation at the billing level.

If you have multiple Stitch accounts, you can reach out to the Sales team to help you consolidate your accounts so that you only get billed once for all accounts.

However, the accounts themselves cannot be merged, i.e., integrations and destinations setup in one account cannot be migrated to another. If you prefer to avoid managing multiple accounts, you will need to setup your workflows in your preferred account, and this will include historical loads for newly setup integrations.

Please note that Stitch offers a 7-day exemption for newly named integrations. This implies that if you setup an integration with a schema name that was not previously used in the account, it will be regarded as a new integration. Schema names are verified against individual Stitch accounts only.

If you intend to manage multiple Stitch accounts and need to add the same team members in each account, please use the naming convention outlined here to add new members.

 

Environment

• Stitch 

Show Less

During our company's auditing, we have been alerted to several vulnerabilities in the embedded Java VM for Replicate v2024.11.0.177

https://nvd.nist.gov/vuln/detail/CVE-2024-21235

https://nvd.nist.gov/vuln/detail/CVE-2024-21208

https://nvd.nist.gov/vuln/detail/CVE-2024-21217

https://nvd.nist.gov/vuln/detail/CVE-2024-21211

https://nvd.nist.gov/vuln/detail/CVE-2024-21210

Is there a newer version of Replicate that addresses these? If not, what is the recommended path to fix these vulnerabilities?

 

Resolution

To resolve the Issue, upgrade OpenJDK to version 17.0.13 or later or upgrade Replicate to version 2025.5. 

Upgrade only Java while keeping your current Replicate version 24.11

1. Upgrade to a minor version (e.g., 17.0.X), not a major version, to maintain compatibility. 
2.  Important Instructions: Test the Java upgrade in a Replicate test environment first.
3. Create a backup before proceeding with the Java upgrade.

You should upgrade to a Java version that addresses the CVE (JAVA version 17.0.14+7), but not a major version. Alternatively, download any other relevant JRE binaries. 

 

Manual steps to update the JRE for Replicater

1. Download JRE binaries to Replicate host.
   you can download JRE binaries from: https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.12%2B7 
   Example: ( OpenJDK17U-jre_x64_windows_hotspot_17.0.13_11.zip)
2. Stop Replicate services.
3. Backup <product dir>\jvm directory.
   For instance:  C:\Program Files\Attunity\Replicate\jvm
4. Remove <product dir>\jvm directory.
5. Extract the JRE binaries you have downloaded to <product dir>\jvm directory and make sure <product dir>\jvm\bin\java.exe exist (usually there is a parent directory with a naming convention 'jdk-<jre version>-jre' when extracting the JRE binaries, make sure to copy all it's subdirectories and files to <product dir>\jvm)
   For instance, if you download the directory  OpenJDK 17U-jre_x64_windows_hotspot_17.0.13_11, it has a sub-directory  jdk-17.0.13+11-jre.
6. Copy from the backed up jvm directory the following files: 
   <jvm backup>\conf\security\java.security  
   <jvm backup>\conf\security\java.security.default 
   <jvm backup>\conf\security\java.security.FIPS 
   To Replicate's jvm directory: 
   <product dir>\jvm\conf\security\java.security 
   <product dir>\jvm\conf\security\java.security.default 
   <product dir>\jvm\conf\security\java.security.FIPS
7. Start Replicate services.

The steps are similar for Replicate on Windows or Unix.

 

Cause

Defects: CVE-2024-21235;CVE-2024-21208;CVE-2024-21217;CVE-2024-21211;CVE-2024-21210

 

Environment

Qlik Replicate 

Show Less

When opening the Qlik Sense hub, the following error is displayed: 

Error requesting "https://_:4242/qrs/license/" - Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 80808080:80



However, the Qlik Sense logs are relatively clean during this time.

Only log files in C:\ProgramData\Qlik\Sense\Log\HubService shows the same message repeatedly:

6    20180409T133219.753+1000    ServerName    0.15.8    Global    INFO    Requesting GET https://ServerName:4242/qrs/license/, referrer /license/
7    20180409T133222.053+1000    ServerName    0.15.8    Global    ERROR     [ Error requesting GET https://ServerName:4242/qrs/license/ ] - Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 8080 8080:80
 

Cause:

Proxy Service is accessing Repository Service via URL https://ServerName:4242.

This connection respects the Proxy Settings in Environment Variables. Any limitations caused by the environment proxy settings will prevent service communication.

 

Resolution:

 

1. Run the batch file in Windows Commands To Retrieve Environment Information on Qlik Sense servers that are running Proxy.exe
2. Inspect "Environment Variable" section in the result files.
3. Find out whether following variables exist:
   • HTTPS_PROXY
   • HTTP_PROXY
4. If they do, contact Windows Administrator and remove them. Restart the server.

Important: There might be settings automatically add these variables back to the server after a restart or certain time period. Should that happen please contact Windows Administrator to resolve.

1. Access the System Properties in Control Panel > All Control Panel Items > System
2. Advanced system settings 
3. Under “Advanced” tab > Environment Variables 
4. Under system variables tab delete: “HTTPS Proxy” & “HTTP Proxy” 
5. Restart the server

Show Less

The Stitch Free Trial offers the full Premium functionality of Stitch for 14 days. This time is provided for users to setup and test their use-case for data replication.

However, there are instances where 14 days is not enough for a thorough evaluation and the Qlik team is able to accommodate such scenarios.

If you require a trial extension, please contact Qlik Support for assistance. You free trial can be extended up to 7 days via the Support team. Please note this is a one-time courtesy for our users.

Once an account is extended, you may need to refresh the browser for the change to take effect. We hope that you are then able to select a plan that meets your needs.

 

Additional Notes

• Every new integration comes with a 7-day historic load period in which replicated rows are not counted against billed rows. This applies to all new integrations, regardless of subscription plan.
• A Free Trial does not officially start until rows are replicated. If you have only setup an integration but it has not been enabled, your trial is not started.

Advanced Connectivity is available upon request for paying customers only.

 

Environment

Stitch 

Show Less

 

Description

• Error "Object reference not set to an instance of an object" when previewing NPrinting Designer Excel Template Editor reports that contain merged cells

 

Diagnosis:

• After upgrade, open an NPrinting Report in the NP designer and preview a report that his known to contain merged cells
• Preview the Report
• Error encountered "The preview request failed with message: Object reference not set to an instance of an object"

 

Environment

• Discovered following an upgrade from older unsupported NP versions (NP November 2019) to Current Supported NP versions

 

Resolution

• Please note that this issue has been resolved and will be available in NPrinting May 2022 SR 4.
• Keep an eye on the Qlik Community Downloads site and Product release notes for new product and service releases.

 

Workaround:

• None at this time

 

Cause

• Product Defect ID: OP-95768

 

Related Content

• Release Notes | Qlik Community
• Downloads | Qlik Community

Show Less

When a task is processing CDC data, the internal replicate engine uses "Linux iconv" API to convert the incoming delta records. If the conversion fails, following warning and error is displayed in the logs:

2025-07-09T06:44:56:68127[SERVER W: Conversion error 84,CodepageFrom=943, CodepageTo=65001, insize=16, output='', outSize=99(str.c:509)

2025-07-09T06:44:56:70391[SOURCE_CAPTURE]E: Error converting column 'column name' in table 'table name' to UTF8 using codepage 943 [1020112](db2luw_endpoint_capture.c:1321)

2025-07-09T06:44:56:70414[ASSERTION]W:The problematic column value: 

7f7a040a921a: 834F838A815B8358834183628376FCFC | .O...[.X.A.b.v..

7f7a040a922a: 8140814081408140814081408140| .@.@.@.@.@.@.@

(db2luw_endpoint_capture.c:1323)

 

 

Resolution

1. Convert the data to hexadecimal and identify the characters that cannot be converted and remove those.
2. Reload the table

 

Cause

The change data converted to hexadecimal contained character value "FCFC", which could not be converted to Unicode.

To validate whether the issue is caused by the data itself, we can also use third-party tool such as DBeaver to check if throws the same error when selecting the data from source DB.

 

Environment

Qlik Cloud 

Show Less

 

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