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.
Database previews are not shown successfully when loading Google BigQuery tables. An Unknown Error is shown.
The data load itself is successful.
Upgrade to a Qlik Sense version which includes updated Google BigQuery drivers that support the snapshot table type.
Upgrade to:
Avoid using the snapshot table type.
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-28365 for reference.
Product Defect ID: QB-28365
When connecting to a MySQL database via JDBC, there will occur below connection error message from TAC or Talend tMysqlConnection, tMysqlInput and tMysqlOutput components.
java.sql.SQLNonTransientConnectionException: Public Key Retrieval is not allowed
The error message java.sql.SQLNonTransientConnectionException: Public Key Retrieval is not allowed
typically occurs when you're trying to connect to a MySQL database using JDBC and the connection URL is not correctly configured to allow public key retrieval for SSL connections. This is a regular setting when using MySQL 8.0+ with certain security configurations.
Add client option to your connection URL mysql-connector allowPublicKeyRetrieval=true to allow the client to automatically request the public key from the server.
jdbc:mysql://localhost:3306/db?allowPublicKeyRetrieval=true&useSSL=false
Accessing the Qlik Sense Enterprise on Windows Hub or Management Console fails with the following error:
Your connection isn’t private
Attackers might be trying to steal your information.
NET:ERR_CERT_REVOKED
The currently installed 3rd party certificate has been revoked. To resolve the issue, we will locate the certificate currently used and delete it from the Windows certificate store. This will prompt Qlik Sense Enterprise on Windows to revert back to its self-signed certificate and allow access to the Hub and Management Console.
The currently installed 3rd party certificate has been revoked.
This article provides a guide on installing Qlik Replicate on a docker image.
sudo rpm -qa|grep dockersudo yum remove docker docker-client docker-client-latest docker-common docker-latest docker-laster-logrotate docker-logrotate docker-engine
sudo yum install -y yum-utils device-mapper-persistent-data lvm2 sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo sudo yum install --allowerasing docker-ce docker-ce-cli containerd.io sudo systemctl start docker sudo systemctl enable docker
/kit
" The /kit directory is a temporary folder used to store installation files. In the example below, the RPM file is areplicate-2024.5.0-357.x86_64.rpm
. Once the installation is complete, the entire /kit folder can be safely deleted.mkdir -p /kit/ar_docker
cd /kit
rpm2cpio areplicate-2024.5.0-357.x86_64.rpm | cpio -iv --make-directories --no-absolute-filenames -D ar_docker/ ./opt/attunity/replicate/addons/samples/docker/*
mv ./ar_docker/opt/attunity/replicate/addons/samples/docker/* ./ar_docker
rm -rf ./ar_docker/opt
cd /kit/ar_docker
cp ../areplicate-2024.5.0-357.x86_64.rpm .
./create-dockerfile.sh
/kit/ar_docker/Dockerfile
, from:
RUN yum -y install /tmp/areplicate-*.rpmto
RUN systemd=no yum -y install /tmp/areplicate-*.rpm
NOTE!
The parameter systemd=no is used to solve the below error you may hit during the docker build stage: This rpm is not supported on your system (no systemctl), exiting. error: %prein(areplicate-2024.5.0-357.x86_64) scriptlet failed, exit status 43
NOTE!
The password should not be empty and must be strong enough.
WARNING!
If you want to install ODBC Drivers, please make the corresponding ODBC Drivers rpm files are ready in this folder. If you want to skip the ODBC Drivers installation at present, rename or delete the file "drivers" in this folder.
docker build --no-cache -t johnw/replicate:2024.5 .where
/johnw/replicate:2024.5
is the image tag.Do not forget the last period "."
docker run -d --name ar --hostname cdc2 -e ReplicateRestPort=3552 -p 3552:3552 -v /dockermount/data/replicate/data:/replicate/data johnw/replicate:2024.5
Now Qlik Replicate is running in the docker and can be accessed from Qlik Replicate Console GUI.
A task may fail with the following error:
[STREAM_COMPONEN ]E: The "Retrieve all source columns on UPDATE" option is turned off in the log stream task settings, but the replication task configuration requires it to be turned on. [1020101] (ar_cdc_channel.c:315)
Qlik Replicate May 2024 Sp02 and later have introduced a fix for the following scenario in a log stream setup:
The fix requires the Retrieve all source columns on UPDATE option to be turned on in your parent log stream task or the task will encounter errors.
Turn on the Retrieve all source columns on UPDATE option in your parent log stream task.
C:\Windows\System32>sftp -P 22 username@ftptest.test.com
The authenticity of host 'ftptest.test.com (18x.6x.15x.21x)' can't be established.
RSA key fingerprint is SHA256:KijFUxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxapWjo
if the above does not retrieve your fingerprint, contact your SFTP server administrator who can provide fingerprint or public key details for you.
If there are connectivity issues, to request data from your data connections through a firewall, you need to add the underlying (all three) IP addresses for your region to your firewall's allow list. These addresses are static and will not change. See Allowlisting domain names and IP addresses.
Error in SFTP connector
Diagnostic
Example: (insert a valid SFTP server host IP)
Result:
In case of this or other SFTP connection errors, please work with the SFTP server administrator or SFTP server vendor in order in order to enable the generation of a publicly available fingerprint.
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.
How to retrieve users and user attributes from excel in Qlik Sense?
The setting and process for Qlik Sense to retrieve user information from excel are almost same as the following 'ODBC example'.
It is very important to review the below information to set up the data source files and Qlik Sense configuration correctly. The real example provided will give a better understanding how exactly it works.
Each data source has a different configuration and the following example (Excel) of adding an ODBC user directory connector.
For .csv and SQL examples, please see the help site: https://help.qlik.com/en-US/sense/Subsystems/ManagementConsole/Content/ODBC-example.htm
Do the following:
Verify that the Microsoft Excel Driver is installed.
Set up an ODBC source on the server.
You need to store the data in two separate sheets in the same excel file, for example, for example you can place it in this location: %ProgramData%\Qlik\Sense\temp.
The temp folder is not included in the default installation. You need to create the temp folder, if not already done by another QMC administrator.
SheetA contains the users and SheetB the user attributes.
Example:
SheetA
userid | name |
1 |
John |
2 |
Bill |
3 |
Tom |
SheetB
userid | type | value |
1 | jd@email.com | |
1 | lastname | Doe |
2 | bg@email.com | |
2 | lastname | Gates |
3 | th@email.com | |
3 | lastname | Hanks |
Select User directory connectors on the QMC start page or from the Start drop-down menu to display the overview. Create a new user directory connector (ODBC) and edit the properties.
Identification
All fields are mandatory and must not be empty.
Property DescriptionName | The name of the UDC configuration, defined from the QMC. |
Type |
The UDC type. |
User sync settings
Property Description Default valueSync user data for existing users |
|
Selected |
Connection
Property Description Default valueUser directory name |
The name of the user directory. Must be unique, otherwise the connector will not be configured. The name must not contain spaces. |
- |
Users table name | The name of the table containing the users. Include the file extension in the table name, for example: [SheetA$]. | - |
Attributes table name | The name of the table containing the user attributes. Include the file extension in the table name, for example: [SheetB$]. | - |
Visible connection string |
The visible part of the connection string that is used to connect to the data source. |
- |
Encrypted connection string |
The encrypted part of the connection string that is used to connect to the data source. Typically, this string contains user name and password. The two connection strings are concatenated into a single connection string when making the connection to the database. |
- |
Synchronization timeout (seconds) | The timeout for reading data from the data source. | 240 |
Example:
User table name: [SheetA$]
Attributes table name: [SheetB$]
Visible connections string: Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};Dbq=%ProgramData%\Qlik\Sense\temp
Click Apply to apply your changes.
Go to the User directory connectors overview and check if the user directory is displayed as Configured and Operational.
If the User directory name is not unique the connector will not be configured. If not operational, check the repository system log in: %ProgramData%\Qlik\Sense\Log\Repository\Trace.You have added an ODBC data source and initial synchronization will be performed within five minutes (by default).
R4Z Db2 mainframe install is completed but no Changes are coming through.
Check that the Tables you wish to be performing CDC replication upon, have been "turned on" for capturing the changes from the DB2 z/OS Logs.
Do this by using the following command. This can be performed by the DB2 Database Administrator.
Option 1: Make sure the Table has been altered for CDC:
ALTER TABLE schema.table DATA CAPTURE CHANGES
Option 2: If the UserId has the permissions it can be configured on the Db2z Endpoint in the Advanced tab.
Change Data Capture to: Automatically enable Data Capture Changes (requires admin privileges)
Varbinary Datatypes on Postgres Target databases are treated as LOB datatypes. Temporarily CSV Files generated by Replicate currently include LOB datatypes even when LOB support is turned off for the task. This leads to data being inputted into the wrong columns if there are LOB datatypes in your tables and LOB support is turned off.
Sample error of a numeric datatype column flowing into a Datetime column:
[TARGET_LOAD ]E: Command failed to load data with exit error code 3, Command output: psql:M:/Replicate/data/tasks/x3_testr4x_rez_ods_ls_pqsl_AgentTest_ac/data_files/1/LOAD00000001.csv.sql:1: ERROR: date/time field value out of range: "0"
The temporary CSV files of Replicate do not remove the LOB columns when LOB support is turned off. This leads to incorrect column matches.
QB-28455
A common request received is a method of grouping Qlik Sense apps into a folder. Eg: If there are many documents that address different categories (such as economics, politics, entertainment, charity etc) in the Hub, it may be good to be able to create folders within 'My work' in Hub to organize my documents and have them in the right folder.
See Folders in your own workspace and streams for details on the feature request and vote to provide us with more feedback!
The request is partially implemented using application tagging. See Fig 1.
Fig 1
A Qlik Replicate task using a SAP ODP Endpoint to replicate a table fails with the error:
[SOURCE_CAPTURE ]E: Text '%% TO BE DEFINED %%' could not be parsed at index 0 [1024719] (custom_endpoint_capture.c:800)
Modify the custom extractor and verify that the table or object is Delta enabled in SAP.
The Extractor or Object defined in the Qlik task is custom and not Delta enabled.
RECOB-8311
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