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.
Qlik Sense upgrade process was completed successfully. However, upon attempting to run Qlik Sense services, the CPU usage spiked to 99% to 100%, rendering the Qlik server unresponsive.
Restarting the Qlik Sense services or rebooting the Qlik Sense Windows machine does not resolve the issue.
The Windows Task Manager on the Qlik Sense Windows machine reveals the Qlik Dispatcher service causes the CPU spike.
This article provides a solution for one possible root cause leading to a high CPU load. Other root causes may exist (such as an unoptimized Qlik Sense document) and will require additional troubleshooting.
To resolve this particular root cause:
C:\Program Files\Qlik\Sense\ServiceDispatcher\
on the Qlik Sense Windows machineservices.conf
fileNote: In a multi-node environment, this verification must be performed on all nodes.
A duplicated command in the configuration file was leading to multiple instances of the service being triggered, creating an infinite loop. This misconfiguration resulted in an excessive number of threads and consumed all available CPU resources.
This article documents the use case scenario of using CVENT Core.
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.
Qlik has used CVENT Core to organize sessions for Qlik Connect, allowing Qlik to extract data hourly into a Qlik Sense app.
Cvent Core uses 2-legged oAuth2. Qlik Application Automation's oAuth2 connectors currently only support 3-legged oAuth2, so I had to work around by connecting straight to Qlik Sense REST Connector, where we could do 2-legged. Here's how we did this.
// Get access token using Basic Auth
LIB CONNECT TO 'QlikWorld:CVENT_TOKENREFRESH';
TokenRaw:
SQL SELECT
"access_token"
FROM JSON (wrap on) "root";
[Token]:
LOAD [access_token]
RESIDENT TokenRaw;
DROP TABLE TokenRaw;
let vAuthToken=peek('access_token',-1);
drop table Token;
//Trace $(vAuthToken);
FROM JSON (wrap on) "root" PK "__KEY_root"
WITH CONNECTION (
HTTPHEADER "Authorization" "Bearer $(vAuthToken)"
);
In Replicate Oracle source endpoint there was a limitation:
Object names exceeding 30 characters are not supported. Consequently, tables with names exceeding 30 characters or tables containing column names exceeding 30 characters will not be replicated.
The limitation comes from low versions Oracle behavior. However since Oracle v12.2, Oracle can support object name up to 128 bytes, long object name is common usage at present. The limitation in User Guide Object names exceeding 30 characters are not supported can be overcome now.
There are two major types of long identifier name in Oracle, 1- long table name, and 2- long column name.
1- Error messages of long table name
[METADATA_MANAGE ]W: Table 'SCOTT.VERYVERYVERYLONGLONGLONGTABLETABLETABLENAMENAMENAME' cannot be captured because the name contains 51 bytes (more than 30 bytes)
Add an internal parameter skipValidationLongNames to the Oracle source endpoint and set its value to true (default is false) then re-run the task:
2- Error messages of long column name
There are different messages if the column name exceeds 30 characters
[METADATA_MANAGE ]W: Table 'SCOTT.TEST1' cannot be captured because it contains column with too long name (more than 30 bytes)
Or
[SOURCE_CAPTURE ]E: Key segment 'CASE_LINEITEM_SEQ_NO' value of the table 'SCOTT.MY_IMPORT_ORDERS_APPLY_LINEITEM32' was not found in the bookmark
Or (incomplete WHERE clause)
[TARGET_APPLY ]E: Failed to build update statement, statement 'UPDATE "SCOTT"."MY_IMPORT_ORDERS_APPLY_LINEITEM32"
SET "COMMENTS"='This is final status' WHERE ', stream position '0000008e.64121e70.00000001.0000.02.0000:1529.17048.16']
There are 2 steps to solve above errors for long column name :
(1) Add internal parameter skipValidationLongNames (see above) in endpoint
(2) It also requires a parameter called "enable_goldengate_replication" is enabled in Oracle. This can only be done by end user and their DBA:
alter system set ENABLE_GOLDENGATE_REPLICATION=true;
Take notes this is supported when the user has GoldenGate license, and Oracle routinely audits licenses. Consult with the user DBA before alter the system settings.
Internal support case ID: # 00045265.
Is it possible to disable the Qlik Sense Dev Hub for end-users?
Qlik Sense Enterprise on Windows
It is not possible to disable the Qlik Sense Dev Hub for end users. This is working as designed.
The default security rules will restrict access for standards users to read-only. Customization is available using Security Rules in the Qlik Sense Management.
Please refer to the Qlik Sense Online Help for more details.
"C:\Program Files\NPrintingServer\Settings\SenseCertificates"
NOTE: Reminder that the NPrinting Engine service domain user account MUST be ROOTADMIN on each Qlik Sense server which NPrinting is connecting to.
The Qlik NPrinting server target folder for exported Qlik Sense certificates
"C:\Program Files\NPrintingServer\Settings\SenseCertificates"
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.
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.
Inside Qlik Application Automation, the Amazon S3 functionality is split into two connectors: the native Cloud Storage connector and the specific Amazon S3 connector. To create, update, and delete files, it’s highly recommended to use the native Cloud Storage connector. To get the information and metadata of regions & buckets, use the Amazon S3 connector.
The following is an example of automation using the Amazon S3 connector to output a paginated list of regions and buckets in each region (not covered in this article).
This article focuses on the available blocks in the native Cloud Storage connector in Qlik Application Automation to work with files stored in S3 buckets. It will provide some examples of basic operations such as listing files in a bucket, opening a file, reading from an existing file, creating a new file in a bucket, and writing lines to an existing file.
The Cloud Storage connector supports additional building blocks to copy files, move files, and check if a file already exists in a bucket, which can help with additional use cases. The Amazon S3 connection also supports advanced use cases such as generating a URL that grants temporary access to an S3 object, or downloading a file from a public URL and uploading this to Amazon S3.
Let’s get started.
Authentication for this connector is based on tokens or keys.
Log in to the AWS console with an IAM user to generate the access key ID and secret access key required to authenticate.
Now let's go over the basic use cases and the supporting building blocks in the Cloud Storage connector to work with Amazon S3:
The Amazon S3 connector in Qlik Application Automation now supports adding the SSE header value for creating new files. This header is available on the Create File and Copy File blocks. It's possible to choose the default behavior which is AES256 encryption. As an alternative, it's possible to choose aws:kms encryption and provide a valid KMS Key ID.
Attached example file: create_and_write_files_amazon_s3.json
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.
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
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