Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
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. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in Manage Cases. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
After upgrading to QlikView 12.70 SR2 users cannot open documents from the AccessPoint once the session timeout is reached. The following error is displayed:
Failed to open document, You don't have access to this document
QlikView May 2022 (12.70) IR to SR2
QlikView May 2023 (12.80) IR
This is caused by QV-24743 and QV-24830.
Fix scheduled to be released in:
Upgrade to the appropriate version when it has become available. Refer to the QlikView Release Notes for details once the versions have been released.
QV-24743 and QV-24830
Qlik Sense or QlikView may not load all data from a CSV file.
Sometimes a special character is used to mark the end of the file. If this character is found in the middle of a text file (for example, enclosed by quotation marks), the file may not load correctly. In this instance, we can modify how Qlik Sense and QlikView read data.
Qlik Sense:
QlikView
Due to a problem with quotes or special characters in the file. See Help Site File Wizard: Type
Qlik Sense all supported versions, including Qlik Cloud
QlikView all supported versions
Previewing Qlik NPrinting report templates in the Qlik NPrinting Designer leads to the error:
An error occurred while elaborating the entity tags.
Please check if the entities are properly placed inside their level tags.
Error message:
TemplateEntities list does not contain this column
Parameter name: templateEntities
Qlik NPrinting Designer May 2023 IR, May 2023 SR 1
Upgrade to Qlik NPrinting May 2023 SR 2.
Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID OP-95892 for reference.
Replace the current Qlik.Reporting.Adapters.dll file in C:\Program Files (x86)\NPrinting\Designer\libs.
For this workaround to function, the installed Qlik NPrinting designer version must be May 2023 SR1.
Upgrade to May 2023 SR2 when released.
Qlik NPrinting May 2023 SR 2
OP-95892
Sometimes it might be necessary to deallocate licenses using the Qlik Command Line Interface, for instance in case of licenses allocated to users no longer in the system.
[
{
"created": "2023-04-03T11:24:05.101Z",
"excess": false,
"name": “Enzo Bearzot”,
"subject": "auth0|12345678”,
"type": "professional",
"userId": “userid1”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Vittorio Pozzo”,
"subject": "auth0|910111213”,
"type": “analyzer”,
"userId": “userid2”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Ferruccio Valcareggi”,
"subject": "auth0|14151617”,
"type": "professional",
"userId": “userid3”
},
{
"created": "2022-06-07T11:36:15.704Z",
"excess": false,
"subject": “18192021”,
"type": “professional”
},
{
"created": "2022-06-03T13:50:14.105Z",
"excess": false,
"subject": “22232425”,
"type": "analyzer"
},
]
The syntax below is for Unix shells. For usage in Windows Powershell add a "backslash" before each "doublequote" sign. '[{"subject"... will have to become '[{\"subject\"...
'[{"subject":"USERSUBJECT","type":"ASSIGNEDLICENSE"}]'
For instance, in the case of the final user in the list above it will be '[{"subject":"22232425","type":"analyzer"}]'
feed the string into this command:
qlik license assignment delete --delete STRING
With the example above you will run:
qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
Run the command and wait for the result.
A "200" will confirm that the removal worked
% qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
[
{
"status": 200,
"subject": "22232425",
"type": "analyzer"
}
]
Check the "Home" section of the management console to confirm that the allocation was removed
A Qlik Replicate task fails in writing to ADLS in parquet format from source DB2 z/os. The error in the task log is:
[TARGET_LOAD ]E: Failed to convert file from csv to parquet
Error:: failed to read csv temp file
The ODBCINST.ini may not be directed to the accurate DB2 64-bit ODBC driver. Resolving the issue may require a manual edit of the ODBCINST.ini file.
Original value:
./opt/ejvdb2odbc/lib/libdb2.so
Corrected to:
./opt/ejvdb2odbc/lib/libdb2o.so
After the changes have been made and saved, reload the task.
After an upgrade of Qlik Replicate to May 2023 (2023.5.0.322), Databricks tasks fail with the following error:
[METADATA_MANAGE ]E: The host configured in the proxy settings is not valid [1020401] (cloud_imp.c:2138)
[METADATA_MANAGE ]E: Failed while preparing stream component 'Databricks_AdageAZ'. [1020401] (metadatamanager.c:855)
[METADATA_MANAGE ]E: Cannot create the target utility component [1020401] (metadatamanager.c:760)
[TASK_MANAGER ]E: Creating Metadata Manager's utility components failed [1020401] (replicationtask.c:3896)
[TASK_MANAGER ]W: Task 'Adage_AZ_Apply_Changes_All' encountered a fatal error (repository.c:6064)
An upgrade of Qlik Replicate may set the proxy settings in the Databricks Lakehouse (Delta), even if no proxy has previously been used. Disable the proxy to resolve the issue.
The Qlik Sense PostgreSQL database was previously updated and unbundled using the Qlik PostgreSQL Installer (QPI).
Following an upgrade of Qlik Sense Enterprise on Windows, the Qlik Repository Service may not start or the Management Console open to the following error:
Failed to load properties. No data found.
Qlik Sense on Windows May 2023 (upgraded to)
Previous use of Qlik PostgreSQL Installer (QPI) while Qlik Sense had a patch installed
Repair the installation. See Repairing an installation.
Previously to using QPI, all patches need to be removed. See Requirements for QPI.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
QB-20581
In the data integration process from a Salesforce source to a Snowflake target, it's crucial to ensure all records are accurately captured. However, sometimes gaps can occur in Change Data Capture (CDC) operations, resulting in missing records.
In this article, we aim to explore such an issue and guide you through the required troubleshooting steps and eventual solution.
One of the source table in Salesforce is 'WorkOrder,' and discrepancies in data capture were observed in the logs. The root of the problem becomes evident when examining consecutive SELECT queries:
Timestamp: 2023-07-17 13:41:04.251
Query: SELECT count() FROM WorkOrder WHERE SystemModstamp > 2023-07-17T17:24:28.000Z and SystemModstamp < 2023-07-17T17:40:04Z
Timestamp: 2023-07-17 13:56:31.411
Query: SELECT count() FROM WorkOrder WHERE SystemModstamp > 2023-07-17T17:41:04.000Z and SystemModstamp < 2023-07-17T17:55:31Z
Upon closer examination, it's evident that the tracking column 'SystemModstamp' in Query 2, which is "> 2023-07-17T17:41:04.000Z," does not align with the previous query's 'SystemModstamp' value, which was "< 2023-07-17T17:40:04Z."
Consequently, any changes within this time period (SystemModstamp between '>= 2023-07-17T17:40:04Z' and '<= 2023-07-17T17:41:04.000Z') were not captured, leading to missing records.
After a thorough analysis, the root cause of this issue was identified. The transaction consistency timeout of 60 seconds was found to be inadequate. To address this problem effectively, the following steps are recommended:
By following these steps, you can enhance the accuracy and completeness of your data capture process when loading data from a Salesforce source to a Snowflake target. This proactive approach will help prevent future instances of missing records and maintain the integrity of your data integration pipeline.
The Qlik Compose Monitor UI does not show Inserted Rows or Updated Rows for the data mart even though the rows are inserted and updated in the database.
Upgrade to 2022.5.1032 (2022, May – sp13).
RECOB-7493
Information provided on this defect is given as is at the time of documentation. For up-to-date information, please review the most recent Release Notes with RECOB-7493 for reference.
Qlik Compose 2021.05 - sp11 (2022.5.0.958)
Creating and adding a new target endpoint to Azure SQL DB and testing the connection fails with:
SYS-E-HTTPFAIL, Failed to load dynamic endpoint properties.
SYS,GENERAL_EXCEPTION,Failed to load dynamic endpoint properties,Failed to get 'SQLServer_New' syntax
Review the active Internal Parameters set in the endpoint.
Due to an issue with MySQL ODBC Driver 8.0.027 to 8.0.033, empty TEXT columns may not be replicated correctly during Full Load.
Running the full load on a table, it appears the data alignment is off because the target .csv file has null values when the source field is defined as not nullable.
Qlik Replicate
Aurora Postgres
Verify the source table DDL:
Examining the source table DDL will show a datatype with no precision (varchar NOT NULL,).
Example:
CREATE TABLE tran.category ( | ||
id | integer NOT NULL, | |
name | varchar NOT NULL, | |
description | varchar NOT NULL, | |
category | varchar NOT NULL, | |
is_active | boolean NOT NULL DEFAULT true, | |
create_employee | integer NOT NULL, | |
create_datetime | timestamp NOT NULL, | |
PRIMARY KEY(id) | ||
) |
This is a documented limitation. See VARCHAR(n).
VARCHAR without a length (n) is not recognized as a valid data type by target endpoints. Consequently, if a source column data type is set to VARCHAR without an explicit length, Replicate will set a default length of 8000 bytes.
You can change the default by deploying an internal parameter, unboundedVarcharMaxSize, and setting a custom value.
This task needs to capture soft deletes and allow the source table to reuse primary key values without a PK violation on the target.
Setting up this task requires four steps:
Adding the two extra fields to the target side primary key and having the NOW timestamp ensures that the target record will be unique compared to the source record with only one field primary key.
This will allow the source to reuse a deleted records primary key without throwing a PK violation on the target. The transformations on the fields set unique values into the additional key segments.
Setting error handling and the apply conflicts handling policy to Upsert Mode (No record found for applying an Update: INSERT the messing target record) normally works by converting the source statement (whether Insert, Update, Delete) into a Delete followed by and Update. The unique three segment primary key is not able to be found during the delete which is why the records persist on the target.
Example source table structure:
Note the single field Primary Key MyPK.
In our example, we have added Operation and OperationDateTime as the additional fields.
Example source table records:
In the Table Settings for your task, go to Transform and mark your newly added fields as target side primary keys.
In our example, we have marked Operation and OperationDateTime.
Transformation are added through the Expression Builder, located in the Table Settings. You will modify the fields marked as keys in the previous step, Operation and OperationsDateTime.
Operation: set the expression to INSERT, UPDATE or DELETE based on the source transaction.
Transformation function:
CASE
WHEN $AR_H_STREAM_POSITION = ''
THEN "INSERTED"
ELSE operation_indicator("DELETED", "UPDATED", "INSERTED" )
END
OperationDateTime: set the expression to to NOW date time
Transformation function:
Datetime('now')
Show results of updates and deletes on the target table
Results in target table after updates and deleting source record #6 and reuse of primary key on source.
Target table after full load:
Target table results after updates and delete on source:
Target table after reuse of source primary key new record inserted.
Results show that the target table is acting like an Audit table; all source transactions are stored.
The target table can have multiple records that have the same primary key on the source (MyPk 6).
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.
When using Replicate to replicate data to Big Query Target the attrep_change Table gets dropped and recreated for the batches to send to Big Query which is causing the DML generated for the Table to exceed the 1500 default Quota Limit for Big Query Table.
For the Big Query Target in Replicate you can add an internal parameter below to use the Truncate method for the attrep_change Table so the data is truncated to reduce the Quota cost for the given Tables being Replicated in the Task.
Advanced Tab on Big Query Target Internal Parameters
$info.query_syntax.truncate_table (won't show up in the list, just hit enter)
With a value of: TRUNCATE TABLE ${QO}${TABLE_OWNER}${QC}.${QO}${TABLE_NAME}${QC}
The GCP (Google Cloud Provider) has Quota Limit setup on the given tables in Big Query with the default of 1500. During CDC processing with Replicate the attrep_change (temp table) to keep track of the batches to send to Target is dropping and recreating as the bulk process to send to Target. These are DML calls to Big Query which are the used via the Quota's per Table.
Reference
https://cloud.google.com/bigquery/docs/troubleshoot-quotas
This article provides step-by-step instructions for implementing Azure AD as an identify provider for Qlik Cloud. We cover configuring an App registration in Azure AD and configuring group support using MS Graph permissions.
It guides the reader through adding the necessary application configuration in Azure AD and Qlik Sense Enterprise SaaS identity provider configuration so that Qlik Sense Enterprise SaaS users may log into a tenant using their Azure AD credentials.
Content:
Throughout this tutorial, some words will be used interchangeably.
The tenant hostname required in this context is the original hostname provided to the Qlik Enterprise SaaS tenant.
Copy the "value of the client secret" and paste it somewhere safe.After saving the configuration the value will become hidden and unavailable.
In the OpenID permissions section, check email, openid, and profile. In the Users section, check user.read.
Failing to grant consent to GroupMember.Read.All may result in errors authenticating to Qlik using Azure AD. Make sure to complete this step before moving on.
In this example, I had to change the email claim to upn to obtain the user's email address from Azure AD. Your results may vary.
While not hard, configuring Azure AD to work with Qlik Sense Enterprise SaaS is not trivial. Most of the legwork to make this authentication scheme work is on the Azure side. However, it's important to note that without making some small tweaks to the IdP configuration in Qlik Sense you may receive a failure or two during the validation process.
For many of you, adding Azure AD means you potentially have a bunch of clean up you need to do to remove legacy groups. Unfortunately, there is no way to do this in the UI but there is an API endpoint for deleting groups. See Deleting guid group values from Qlik Sense Enterprise SaaS for a guide on how to delete groups from a Qlik Sense Enterprise SaaS tenant.
Qlik Cloud: Configure Azure Active Directory as an IdP
This article provides information on how to get started with the ServiceNow connector in Qlik Application Automation.
The connector for ServiceNow is making use of Basic Authentication. To connect you will also need the name of your instance.
When you connect to ServiceNow in Qlik Application Automation you will be presented with the following screen.
You can obtain the instance name from the URL that you use to access ServiceNow. You can use your username / password of your account provided it has enough privileges for what you aim to do. It is recommended to create a service account for integrations and limit it's roles to what is necessary.
Most of the blocks for the ServiceNow connector make use of the Table API of ServiceNow.
ServiceNow documentation for the Table API can be found at: https://developer.servicenow.com/dev.do#!/reference/api/rome/rest/c_TableAPI
The following data types have easy to use blocks for all CRUD operations:
• Incident
• Change Task
• Problem
• Change Request
Furthermore it is possible to work with user objects, listing journal items, audit lines, obtaining and adding attachments.
When modifying or deleting objects from the Table API, make sure to be using the "sys_id" field of objects as the identifier.
With the blocks "get table content by id", "create table content", "delete table content", "update table content", "list table content", it is possible to work with every object through the use of the Table API. These blocks also allow you to look up the name of a table with the "do lookup" functionality. As this lookup obtains information from the sys_db_object table in ServiceNow, it's possible that this lookup does not work due to your permissions.
There is also a "Raw API Request" available. This block allows providing your own sub path starting from the Base URL of ServiceNow, HTTP method and optionally a JSON body.
This can be used to contact other API groups than the Table API of ServiceNow as well as custom scripted API's.
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.
With Microsoft SQL as an endpoint, Qlik Replicate can be set up to Delete processed backup logs.
When the delete processed backup logs option is enabled, logs are deleted after a task processed the given log. This can lead to other tasks needing the log to complain about the missing log.
This is working as intended. Qlik Replicate tasks do not communicate with each other.
Disable Delete processed backup logs.
This will retain all log files. The files will need to be manually deleted.
As such, we advise reviewing latency and once it is zero, deleting the old logs. If Qlik Enterprise Manager has been deployed, we advise using API calls to check latency and to create a PowerShell script to delete the old files to automate the process.
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
The following versions have been tested and verified to work with QPI 1.3.0 (May 2023):
February 2022 to May 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Qlik Sense upgrade.
The Qlik PostgreSQL Installer supports installing a new Qlik Sense Repository Database cluster on a new server, setting up a new environment or migrating an existing Database to a separate host.
Download the installer here.
Qlik PostgreSQL installer version 1.3.0 Release Notes
The following versions have been tested and verified to work with QPI 1.3.0 (May 2023):
February 2022 to May 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Qlik Sense upgrade.
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Before upgrading Qlik Sense Enterprise on Windows to the next major release
The old Qlik Sense Repository Database service must be removed from the server.
Perform the following steps to delete the Qlik Sense Repository Database Service:
This version of the upgrade tool is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
If you have previously used the Qlik Postgres Installer (version 1.2.1 or earlier), you can simply install the latest PostgreSQL version (within your major release).
Example: You have used the old QPI to upgrade to 12.5. You can now easily upgrade to a later version in the same major release, such as 12.15.
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.
Qlik PostgreSQL installer version 1.3.0 Release Notes
Techspert Talks - Upgrading Qlik Sense Repository Service
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
Accessing the Qlik Replicate or Qlik Enterprise Manager console errors out with the following:
SYS,GENERAL_EXCEPTION,The requested security protocol is not supported.
After an upgrade of Windows to Windows 2019, the previously installed .NET 4.8 install may be reverted to an older .NET version. A reinstall of .NET may be required.
Qlik Replicate and Qlik Enterprise Manger require .NET framework 4.8 or later. See Windows software requirements.
To verify the currently installed .NET Framework version, open a command line prompt and run:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v version
A typical output looks like (in my sample the .NET Framework 4.8 was installed):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full
version REG_SZ 4.8.03761
Once you have confirmed that the wrong .NET Framework version is listed, reinstall .NET Framework 4.8.
.NET Framework 4.8.1 is not supported until Windows Server 2022 version, so version 4.8 is required.
This is .NET Framework 4.8 English edition Offline Installer from Microsoft Download Center.