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.
After a Qlik Sense upgrade, the Qlik Sense Repository service fails to start. The following error is logged in the Windows Application Event log:
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
System.IO.FileLoadException: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5'
at Repository.QRSService.Start(Action`1 terminate)
at
The initial recommendation is to repair the installation. See How to repair an installation.
If the repair does not resolve the problem:
The Qlik.Sense.Logging.dll present in [Installation Qlik Sense folder]\Repository\ was missing required inforamtion.
Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch.
All Qlik Replicate versions older than the 2024.5 SP03 release are affected.
Upgrade to Qlik Replicate 2024.5 SP03 or later.
The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly.
RECOB-8698
Making changes to a Qlikview document (.qvw) or Qlik Sense app (.qvf) will sometimes break already existing bookmarks. This is sometimes unavoidable and is a risk developers need to be mindful of when making changes to existing deployments.
Bookmark functionality can be affected by the following changes:
Making any of these changes can lead to bookmarks that only apply some of the intended selections, or even none at all.
A developer making changes to a document will need to keep these limitations in mind, and test any existing bookmarks, especially after using sensitive functions like "Always One Selected". If a bookmark is discovered to be broken, recreating it after the changes have been made is the best method to get back to a working state.
We in Qlik Support have virtually no scope when it comes to debugging or writing custom security rules for customers. That level of implementation advice needs to be handled by the folks in Professional Services or Presales. That being said, this example is provided for demonstration purposes to explain a specific scenario. No Support or maintenance is implied or provided. Further customization is expected to be necessary and it is the responsibility of the end administrator to test and implement an appropriate rule for their specific use case. For access to more tips and tricks, best practices, and ever-evolving creative solutions, we recommend joining us in our active Qlik Community.
In this scenario, the administrator wants to grant access to the Data Load Editor on a series of apps which the user or set of users already have read rights to.
When Qlik Replicate runs in CDC mode and CT tables are enabled, primary keys are replicated as null values in the CT tables.
Base tables are not affected by this.
The Oracle patch from the 19th of October 2023 changed the redo log format around how they log before images. Qlik has issued a patch (2023.5 SP5) to read the new format correctly.
A fix has been provided in Qlik Replicate 2023.5 SP5 and 2023.11 SP1.
Download and install one of the provided patches:
Qlik Replicate May, version 2023.5.0.516 and earlier.
Qlik Replicate 2023.11.0.159 (GA)
Scenario: Qlik Replicate is using a DB2 Z/OS Source Endpoint. During an IPL, tasks fail while connecting to the DB2 instance in the Data Sharing Group.
The errors in the log are:
00124988: 2024-06-20T12:11:18 [TASK_MANAGER ]I: Task error notification received from subtask 0, thread 0, status 1020101 (replicationtask.c:3519) 00124988: 2024-06-20T12:11:18 [TASK_MANAGER ]W: Task 'ECS_GRP2_LS_IC0A_ECS_03' encountered a fatal error (repository.c:6064) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]E: Reading IFI packet encountered a fatal error upon UDTF execution. Aborting... [1020101] (db2z_ifi_api.c:405)our prod Logstream and Aurora tasks encountered multiple errors failing with DB2 communication error. Attaching the required logs and diagnostic package. Some of the tasks were able to recover, but two tasks tried to recover and finally errored out. When we tried to resume with resume option they threw an error and were able to resume with locally stored checkpoint option.:: this is what the error looks on simple resume: 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]E: R4DB2: Instance state has been recreated (r4z2util.c:1294 [20014] (db2z_ifi_api.c:995) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]I: IFI306 Skew is 3927874278216977 micro seconds (db2z_endpoint_util.c:510) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]I: IFI306 is initialized with buffer size of 262144 bytes (db2z_ifi_cdc.c:113) 00124988: 2024-06-20T12:11:18 [TASK_MANAGER ]I: Task error notification received from subtask 0, thread 0, status 1020101 (replicationtask.c:3519) 00124988: 2024-06-20T12:11:18 [TASK_MANAGER ]W: Task 'ECS_GRP2_LS_IC0A_ECS_03' encountered a fatal error (repository.c:6064) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]E: Reading IFI packet encountered a fatal error upon UDTF execution. Aborting... [1020101] (db2z_ifi_api.c:405) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]E: db2z_capture_start: Error connecting to IFI306 [1020101] (db2z_endpoint_capture.c:3109) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]E: Error executing command [1020101] (streamcomponent.c:2052) 00125214: 2024-06-20T12:11:18 [TASK_MANAGER ]E: Stream component failed at subtask 0, component st_0_cadm_db2_DDFIC0A_0523 [1020101] (subtask.c:1431) 00125214: 2024-06-20T12:11:18 [SOURCE_CAPTURE ]E: Stream component 'st_0_cadm_db2_DDFIC0A_0523' terminated [1020101] (subtask.c:1602)
A DB2 configuration parameter (enableAcr) can be added to the db2dsdriver.cfg configuration file, which maintains the connection to DB2 during an IPL when the instance is in a Data Sharing Group.
For more information about enableAcr, see Element in the <acr> section of the db2dsdriver configuration file (Source: IBM.com).
Specifies whether automatic client reroute is in effect. The default is true. If the server accessed is Db2 for z/OS, the enableAcr parameter should be enabled only when the enableWLB parameter is in effect.
Qlik Data Gateway erroring out with "Invalid metadata response (DirectAccess-2201) " message. The error could be due to a different issues.
The cause of the issue is usually configuration, if the suggestions above didn't fix the issue it will be necessary to report the issue for further analysis.
Qlik Data Gateway: Direct Access Data Gateway failing with Internal Error
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.