Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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 the Case Portal. (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:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
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.
For the Oracle database that integrates with the Avaloq Banking Suite, Qlik Replicate retrieves zero records from the source table during full load (without a warning or error messages). This occurs because the following PL/SQL procedure must be executed to obtain the data:
exec k.session#.open_session();
No mechanism exists to instruct Qlik Replicate to execute the above procedure before sending the query statement to the database.
On the Oracle Database, create a trigger that fires after logon and embeds the PL/SQL procedure within it. For example,
CREATE OR REPLACE TRIGGER AFTER_LOGON_TRIGGER_REPLICATE
AFTER LOGON ON DATABASE WHEN (USER = 'QR_ACCOUNT')
BEGIN
execute immediate 'call k.session#.open_session()';
COMMIT;
END;
Where QR_ACCOUNT is the account name used to access the Oracle database.
Qlik Replicate all versions
A user with a Root Admin role should be able to access all resources and functions in the Qlik Sense Management Console (QMC). In rare instances, the Root Admin will notice some options being unavailable (greyed out) such as Duplicate or Export buttons being disabled.
This applies to Root Admins without professional or analyzer licenses allocated and is seen in environments which were upgraded from previous versions of Qlik Sense.
Example:
This rule is a legacy rule which will only exist if you have upgraded your environment or still are on an older version of Qlik Sense.
((user.roles!="RootAdmin"))
If the Root Admin user is not allocated professional or analyzer license, analyzer capacity will be applied automatically by "Security rule for AnalyzerTimeAccessType" in old versions of Qlik Sense or if a legacy rule still exists.
It is possible to export the list of tenatnt users to a .json file using the "user ls" command from the Qlik Command Line Interface (qlik-cli).
The scripts provided in this article are provided as they are and they are for guidance only.
As a tenant admin, download and configure the Qlik-cli
qlik user ls --limit 1000 > tenantusers.json
[
{
"assignedGroups": [],
"assignedRoles": [
{
"id": "608050f7634644db3678b1a2",
"level": "user",
"name": "Developer",
"type": "default"
},
{
"id": "608050f7634644db3678b17f",
"level": "admin",
"name": "TenantAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af862",
"level": "user",
"name": "SharedSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af866",
"level": "user",
"name": "ManagedSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af86b",
"level": "user",
"name": "DataSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85d",
"level": "admin",
"name": "AnalyticsAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85f",
"level": "admin",
"name": "DataAdmin",
"type": "default"
},
{
"id": "63580b8d5cf9728f19217be0",
"level": "user",
"name": "PrivateAnalyticsContentCreator",
"type": "default"
},
{
"id": "6356f0425cf9728f1962b942",
"level": "user",
"name": "DataServicesContributor",
"type": "default"
}
],
"created": "2020-05-18T09:38:29.214Z",
"createdAt": "2020-05-18T09:38:29.214Z",
"email": "martina.testoni@dkdaklaldkdaklladaaddddl.com",
"id": "USERID1",
"lastUpdated": "2023-04-04T07:32:00.756Z",
"lastUpdatedAt": "2023-04-04T07:32:00.756Z",
"name": "Martina Testoni",
"picture": "https://s.gravatar.com/avatar/gravatarimage=pg\u0026d=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fdp.png",
"preferredLocale": "",
"preferredZoneinfo": "Europe/Copenhagen",
"roles": [
"Developer",
"TenantAdmin",
"SharedSpaceCreator",
"ManagedSpaceCreator",
"DataSpaceCreator",
"AnalyticsAdmin",
"DataAdmin",
"PrivateAnalyticsContentCreator",
"DataServicesContributor"
],
"status": "active",
"subject": "auth0|SUBJECTID2",
"tenantId": "TENANTID"
},
{
"assignedGroups": [],
"assignedRoles": [
{
"id": "608050f7634644db3678b17f",
"level": "admin",
"name": "TenantAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af86b",
"level": "user",
"name": "DataSpaceCreator",
"type": "default"
},
{
"id": "608050f7634644db3678b1a2",
"level": "user",
"name": "Developer",
"type": "default"
},
{
"id": "605a1c2151382ffc836af866",
"level": "user",
"name": "ManagedSpaceCreator",
"type": "default"
},
{
"id": "63580b8d5cf9728f19217be0",
"level": "user",
"name": "PrivateAnalyticsContentCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af862",
"level": "user",
"name": "SharedSpaceCreator",
"type": "default"
},
{
"id": "6356f0425cf9728f1962b95c",
"level": "user",
"name": "Steward",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85d",
"level": "admin",
"name": "AnalyticsAdmin",
"type": "default"
},
{
"id": "62bb165356d1879582c1b468",
"level": "admin",
"name": "AuditAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85f",
"level": "admin",
"name": "DataAdmin",
"type": "default"
}
],
"created": "2023-03-31T08:44:37.332Z",
"createdAt": "2023-03-31T08:44:37.332Z",
"email": "Gentile.Faccenda@dkdaklaldkdaklladaaddddl.com",
"id": "USERID2",
"lastUpdated": "2023-04-03T11:24:35.037Z",
"lastUpdatedAt": "2023-04-03T11:24:35.037Z",
"name": "Gentile Faccenda",
"picture": "https://s.gravatar.com/avatar/randomurl=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fdp.png",
"roles": [
"TenantAdmin",
"DataSpaceCreator",
"Developer",
"ManagedSpaceCreator",
"PrivateAnalyticsContentCreator",
"SharedSpaceCreator",
"Steward",
"AnalyticsAdmin",
"AuditAdmin",
"DataAdmin"
],
"status": "active",
"subject": "auth0|IDPSUBJECT2",
"tenantId": "TENANTID"
}
]
qlik user ls --limit 1000 | ConvertFrom-Json | ConvertTo-Csv > tenantusers.csv
This article documents how to convert a Direct Task into a Log Stream Task without reloading the target.
Re-enter the Password
While working with Google Cloud BigQuery as the target database, the task reports errors during the target apply stage.
The messages in task log file:
2024-08-01T11:22:33:395316 [TARGET_APPLY ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 70 Message: [Simba][BigQuery] (70) Invalid query: Unrecognized name: JW_L0 at [1:2853] [1022502] (ar_odbc_stmt.c:3974)
2024-08-01T11:22:33:433379 [TARGET_APPLY ]E: Failed to prepare statement 'UPDATE `JW_L0`.`ACCOUNTS` SET ...
2024-08-01T11:22:33:762878 [TARGET_APPLY ]E: Failed to get bulk update statement for table 'JW_L0'.'ACCOUNTS' [1022517] (odbc_util.c:4424)
Enable the Apply changes using SQL MERGE tuning option:
For more information and details regarding this tuning option, see Apply changes using SQL MERGE.
Qlik has observed the following error while working with Databricks Delta Lakehouse endpoint in Replicate 2023.05 or above. This Technical Advisory article aims to create awareness of the issue and provides a workaround.
[DEFAULT_FILE_NOT_FOUND] It is possible the underlying files have been updated. You can explicitly invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in SQL or by recreating the Dataset/DataFrame involved. If disk cache is stale or the underlying files have been removed, you can invalidate disk cache manually by restarting the cluster.
This causes the table to be suspended and requires a reload.
A fix is currently being worked on and patches will be made available at the earliest.
Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-28166 for reference.
Product Defect ID: QB-28166
This video will demonstrate how to install and configure Qlik-CLI for SaaS editions of Qlik Sense.
Content:
get-command qlik
choco install qlik-cli
if ( -not (Test-Path $PROFILE) ) {
echo "" > $PROFILE
}
qlik completion ps > "./qlik_completion.ps1" # Create a file containing the powershell completion.
. ./qlik_completion.ps1 # Source the completion.
Advanced and additional instructions as seen in the video can be found at Qlik-CLI on Qlik.Dev. Begin with Get Started.
This article explains how to set up OIDC authentication with Auth0 and map Auth0 roles to groups in Qlik Cloud.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
Note down Client ID and Client Secret
exports.onExecutePostLogin = async (event, api) => {
const namespace = 'https://my-app.example.com';
if (event.authorization) {
api.idToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
api.accessToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
api.user.setUserMetadata(`${namespace}/roles`, event.authorization.roles);
}
}
While accessing the Amazon RDS for Oracle as the source database, the task reports a warning message and an error message during the task startup.
The messages in task log file:
2024-08-01T10:22:33:282880 [SOURCE_CAPTURE ]W: ARCHIVELOG mode is not defined in the used Oracle database (oracle_endpoint_conn.c:179)
2024-08-01T10:22:33:395316 [SOURCE_CAPTURE ]E: Cannot retrieve Oracle archived Redo log destination ids [1020401] (oracdc_merger.c:661)
Setting up the Oracle database instance with Enabled Automatic Backups option to Yes by using AWS Management Console, or by AWS CLI command.
For example:
aws rds modify-db-instance --db-instance-identifier mydevdb --backup-retention-period 2 --apply-immediately
Where mydevdb is the identifier of DB instance to modify. This value is stored as a lowercase string.
00168581
Opening a QlikView document fails.
The QlikView Server event log reads:
Document Load: The document C:/Documents/DocumentName.qvw failed to load because of no file access [3000]
This is caused by someone trying to open a document that they do not have access to (not NTFS or DMS permissions).
To resolve: Verify the user has all required permissions or if they are attempting to open the correct document.
A user is attempting to access a document they do not have access to, most frequently because of an outdated or incorrect bookmark.
This article explains how to import and export master items to and from a Qlik Sense app using the Microsoft Excel connector in Qlik Application Automation.
Content:
The first part of this article will explain how to export all of your master items configured in your Qlik Sense App to a Microsoft Excel sheet. The second part will explain how to import those master items from the Microsoft Excel sheet back to a Qlik Sense App.
For this, you will need a Qlik Sense app in your tenant that contains measures, dimensions, and variables you want to export. You'll also need an empty Microsoft Excel file. The image below contains a basic example on exporting master items.
The following steps will guide you through recreating the above automation:
An export of the above automation can be found at the end of this article as Export master items to a Microsoft Excel sheet.json
For this example, you'll first need a Microsoft Excel file with sheets configured for each master item type (dimensions, measures, and variables). Use the above example to generate this file. The image below contains a basic example on importing master items from Microsoft Excel to a Qlik Sense app.
An export of the above automation can be found at the end of this article as Import master items from a Microsoft Excel Sheet.json
Follow the same steps to build automations that import/export dimensions and variables.
Let's go over some edge cases when exporting information to Microsoft Excel:
Please check the following articles for more information about working with master items in Qlik Application Automation and also uploading data to Microsoft Excel.
Follow the steps provided in this article How to import & export automations to import the automation from the shared JSON file.
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.
Qlik Sense Connectors are missing from the Data source except few REST connectors.
Repair Qlik Sense with the Qlik Sense Setup file (identical version).
Qlik ODBC connector package (database connector built-in Qlik Sense) fails to reload with error Connector reply error:
Executing non-SELECT queries is disabled. Please contact your system administrator to enable it.
The issue is observed when the query following SQL keyword is not SELECT, but another statement like INSERT, UPDATE, WITH .. AS or stored procedure call.
See the Qlik Sense February 2019 Release Notes for details on item QVXODBC-1406.
By default, non-SELECT queries are disabled in the Qlik ODBC Connector Package and users will get an error message indicating this if the query is present in the load script. In order to enable non-SELECT queries, allow-nonselect-queries setting should be set to True by the Qlik administrator.
To enable non-SELECT queries:
As we are modifying the configuration files, these files will be overwritten during an upgrade and will need to be made again.
Only apply !EXECUTE_NON_SELECT_QUERY if you use the default connector settings (such as bulk reader enabled and reading strategy "connector"). Applying !EXECUTE_NON_SELECT_QUERY to non-default settings may lead to unexpected reload results and/or error messages.
More details are documented in the Qlik ODBC Connector package help site.
Feature Request Delivered: Executing non-SELECT queries with Qlik Sense Business
Execute SQL Set statements or Non Select Queries
What types of storage drives can be used for the Qlik Replicate and Qlik Enterprise Manager data folder?
Using unsupported storage types can lead to issues such as:
Qlik recommends using a block device (physical, virtual or iSCSI-based) for the Qlik Replicate and Qlik Enterprise Manager data folder.
Downloading a sheet to PDF results in a blank PDF being exported.
This was a known defect in February 2024.
Qlik Sense Enterprise on Windows February 2024 Patch 7 or any later versions, including May 2024.
Product Defect ID: QB-26818
Using the change-owner REST API call for app objects or the qlik-cli app object change-owner command results in:
403 - Forbidden (empty response)
This is a current limitation. As specified on the API call information page, the user running the call must be the owner of the object. Even tenant admins won't be able to run the call, if they are not the object's current owners.
As the qlik-cli command uses the same API call, the behaviour is identical.
The user running the call/command is not the object owner.
Qlik Support advises using the driver version for your endpoints that was certified for the version of Qlik Replicate you are using. The use of a driver running a different version than what was certified can lead to unpredictable results.
Before troubleshooting a potential defect, always ensure a supported driver is in use.
However, it is acceptable in most cases to use a later patch for the driver so long as it is the same major version. For example:
The current release of Qlik Replicate is May 2024. It requires ODBC driver version 18.3 for Microsoft SQL Server source and target. The other currently supported Qlik Replicate releases, November 2023, May 2023, and November 2022, all were certified with driver version 18.1.
However, the driver version 18.3 can be used.
Generally speaking, if the version of the driver is the same and has only been patched (as is the case between driver 18.1 and 18.3) we do not anticipate any issues using it with November 2023, May 2023 and November 2022 versions. If an issue is encountered on these versions with ODBC driver version 18.3, please open a support case.
This is generally true with using a patched version of the certified driver for other databases/endpoints as well, but there might be exceptions. Some endpoints mandate only specific versions for the driver. If there is a doubt, please open a support case.
After a DB2 LUW Upgrade, Qlik Replicate tasks fail with:
"ReadNextBufferWait: Error reading buffer Error at 'Reading log records': Unexpected Error. Original SQLCODE -1263: ' message SQL1263N The archive log file "S0673464.LOG" is not a valid log file for database "REP" on database partition "0" and log stream "0".
Reload the task using the DB2 LUW Endpoint.
Qlik Replicate saves the last save stream position when a task is stopped.
Since the DB2 LUW environment was upgraded, the transaction log will be different and the task (tables) need to be reloaded.
An SQL Lite file called DB2LUW_TIMESTAMP_MAP is defined in the tasks directory, which stores the LSN/LRI position with the timestamp for the given task. This file includes the old DB2 LUW transaction log which is pointing to the old DB2 transaction log version.
Opening a local QlikView document (.qvw) using the QlikView Desktop running on ClientOS in WebView mode fails. The Desktop client does not respond as expected and displays:
Lost connection to server.
Reconnecting
The error occurs if:
Upgrade to QlikView 12.90 (May 2024) IR or higher.
As a temporary workaround, turn off WebView mode:
Product Defect ID: QV-25106