Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in Manage Cases. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
Your advantages:
If you require a support case escalation, you have two options:
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
Qlik Cloud is a modern analytics and data platform built on the same software engine as QlikView and Qlik Sense Client-Managed and adds significant value to empower everyone in an organization to make better decisions daily. Qlik Cloud allows you to use one common platform for all users – executives, decision-makers, and analysts.
Navigation:
Migrating to Qlik Cloud can help your organization:
Q&A with Qlik: Qlik Sense Migration to Qlik Cloud
Articles relevant to migration and new Qlik Cloud users
This site provides you the tools to monitor, manage, and execute a migration from Client-Managed Qlik Sense to Qlik Cloud.
Index and home
Planning your migration
Setting up the Qlik Cloud migration tools
Create and configure a cloud tenant
This site provides you the tools to begin your journey to move from QlikView to Qlik Sense and Qlik Cloud.
With Qlik SAP Connector version 8.0.2, when extracting data using SAP BW Connector, decimal values are separated by comma instead of point. This issue occurs also in version 8.0.1.
The behavior may depend on regional settings
Example of expected behavior.
Bug QB-18820 reported to R&D was closed as fixed. A solution will be available in next release.
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-18820 for reference.
Step 1: Download and apply the attached patch
Step 2:
Product Defect ID: QB-18820
When using Qlik Map Object to display countries like Canada, France, Spain etc., their respective overseas territories will normally not be included.
The example below shows Canada, but the Overseas Territories (see yellow circled area) are not rendered as belonging to Canada
Qlik Map object is based on OpenStreetMap data (see https://www.openstreetmap.org/copyright) and Overseas Territories have special status.
When using GeoAnalytics Map Extension, you may need to avoid users to overwrite the "GeoAnalytics Server URL".
Thus, to hide "GeoAnalytics Server URL" when implementing app with map extension,
The following error can occur when using SAP BW Connector to extract data from InfoProvider/CompositeProvider.
--------
[ERR] [QVX] RfcAbapException:JOB_CANCELLED
Job aborted, check log for Job /QTQVC/READ_MPDATA in Job Overview (transaction SM37)
---------
Reported bug QB-18952 was closed by R&D as WAD(working as designed) .
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-18952 for reference.
From the SAP System,
The allowed maximum width is 8192 characters.
From the INFOPROVIDER, if the field is of, for example 15282 characters wide, a simple workaround would be to split the extraction into two or more extractions. Then in Qlik Sense or QlikView, depending on your data model, use JOIN / CONCATENATE.
Product Defect ID: QB-18952
After upgrading Qlik Replicate may cause scheduled jobs to fail due to changes in the Scheduler functionality.
Example error:
[UTILITIES ]E: Command request 'RESUMETASK_REQ' (55) cannot be found. [1020111] (scheduler.c:270)
In this specific example, the scheduled job didn't run because it had selected the option to "RESUME TASK", which has been removed in more recent versions of Replicate.
A quick solution is to export/import the repository, below are the steps:
repctl exportrepository
"scheduler": {
},
repctl importrepository json_file=Replication_Definition.json
With Qlik Application Automation, you can get data out of Qlik Cloud and distributing it to different users in formatted Excel. The workflow can be automated by leveraging the connectors for Office 365, specifically Microsoft SharePoint and Microsoft Excel.
Here I share two example Qlik Application Automation workspaces that you can use and modify to suit your requirements.
Content:
Video:
Note - These instructions assume you have already created connections as required in Example 1.
This On-Demand Report Automation can be used across multiple apps and tables. Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance.
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.
Starting at Qlik Sense Enterprise on Windows May 2021, the bundled PostgreSQL has been upgraded to version 12.5.
However, PostgreSQL 12.5 will only be deployed during a fresh installation of Qlik Sense Enterprise on Windows May 2021. This means that, if you are upgrading to Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.
For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:
Content:
The information in this article is provided as-is and to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.
It is highly recommended to test this process in a test environment to get familiar with it.
The first step is to upgrade your environment to Qlik Sense Enterprise on Windows May 2021 following the steps and recommendations provided on this link.
Once the upgrade is done make sure your Qlik Sense site is completely operational.
At this point, you have an operational Qlik Sense site running on Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.
The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.
You will now need to uninstall Qlik Sense from the central node following these instructions.
During the uninstall:
Now that Qlik Sense Enterprise on Windows May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5. Instructions available here.
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.
You now have a clean Qlik Sense Enterprise on Windows May 2021 deployed on your central node with PostgreSQL 12.5. You now need to restore your environment to retrieve all your configurations and apps.
Please follow the Restoring a Qlik Sense site (including the certificates).
Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;
pg_restore: warning: errors ignored on restore: 1
Once the environment is restored, you should be able to start your central node and rim nodes successfully.
Qlik Sense Enterprise on Windows May 2021 and later
This article shows how to generate a report from a Qlik Sense app, upload the report to any cloud storage platform, create a sharing link, and send out an email with the link in the body.
We can send the report as an attachment using the Send Mail block in the Mail connector, but this block only supports attachments of size 40MB. An alternative solution is to store reports in any of the cloud storage platforms that support the creation of sharing links and send emails with the links.
I will go through a few examples to show how this can be achieved using the following cloud storage connectors:
I will not go through the steps on how to generate the report using Qlik Reporting blocks as it's already explained in this article.
The four automation files used in the examples are attached to this article. More information on importing automations can be found here.
The following steps explain how to create a public URL using the Dropbox connector.
The following steps explain how to create a public URL using the Microsoft OneDrive connector.
The following steps explain how to create a public URL using the Microsoft SharePoint connector.
Amazon S3
The following steps explain how to create a public URL using the Amazon S3 connector.
Can Qlik Replicate be integrated into a third-party monitoring tool, such as APM Agent?
Qlik Replicate can be monitored using the Qlik Enterprise Manager API, but cannot be directly integrated into (for example) APM Agent for monitoring purposes.
For information on the Qlik Enterprise Manager APIs, see Qlik Enterprise Manager API guide .
The below error is logged in the QlikView Server Event logs:
Error System: file system LastWriteTimeException: Last write time for \ failed: LastWriteTimeException \ failed: boost::filesystem::last_write_
For information on QlikView logs, see QlikView Services and Log Guide
Check the extension name (in red above) to make sure it is installed properly .
You can set the audit trail retention size and age using the CLI in Qlik Enterprise Manager.
The command: aemctl.exe audit_trail control [--age hours] [--size megabyte]
See Setting the audit trail retention size and age for details.
Previous documentation versions of Qlik Enterprise Manager may refer to an incorrect syntax. Always use the most recent guide.
Scenario:
Records are missing from the __CT table.
An enhancement was introduced in Qlik Replicate (version 2022.11), adding a feature which forces Qlik Replicate always to write the change table entry.
Enable the feature in the task settings:
Apply latency increases in a task. The target endpoint Snowflake Azure has a custom policy defined meant to mask/hide values for certain fields in the target. LOB support in the task is disabled.
The following is logged:
00005856: 2023-04-02T00:08:37 [TARGET_APPLY ]I: Column 'Field_Name' is unsupported in table def 'table_XX' since the LOB support is disabled (metadatamanager.c:2632)
The target table has a masking policy defined. This policy is not applied by Qlik Replicate.
Example: Field_Name VARCHAR(30) NOT NULL WITH MASKING POLICY #unknown_policy,
If there is masking policy in the target table, Qlik Replicate will consider it as a LOB column. Therefore, when LOB is support is disabled, we see the mentioned warning.
Field_Name is part of the Primary key. To prepare any update statement the PK columns, values are needed. Without them, Qlik Replicate cannot prepare the update statements.
If Qlik Replicate creates the table without a masking policy in the target table, then disabling LOB support will not impact this table to replicate all columns.
A Qlik Replicate task has stopped due to a Connection error at Kafka Target endpoint:
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: Failed to get Kafka metadata: Local: Broker transport failure. _TRANSPORT [1020401] (kafka_client.c:432)
00003824: 2023-04-13T08:24:16 [TASK_MANAGER ]E: Failed while preparing stream component 'st_0_INT_Bootstrap_Kafka_Target'. [1020401] (subtask.c:853)
00003824: 2023-04-13T08:24:16 [TASK_MANAGER ]E: Cannot initialize subtask [1020401] (subtask.c:1297)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: Stream component 'st_0_INT_Bootstrap_Kafka_Target' terminated [1020401] (subtask.c:1565)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2022.11/kafka#producer-1: sasl_ssl://URL:1921: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed: broker certificate could not be verified, verify that ssl.ca.location is correctly configured or root CA certificates are installed (add broker's CA certificate to the Windows Root certificate store) (after 82ms in state CONNECT) [1022601] (kafka_client.c:236)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2022.11/kafka#producer-1: sasl_ssl://URL:9093/bootstrap: SSL handshake failed: ssl\statem\statem_clnt.c:1921: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed: broker certificate could not be verified, verify that ssl.ca.location is correctly configured or root CA certificates are installed (add broker's CA certificate to the Windows Root certificate store)
Add broker's CA certificate to the Windows Root certificate store. Once this is done, put the cert file on the Qlik Replicate installation server and refer to the .pem at the CA path field.
After updating the EP settings with the above-mentioned, restart the task or stop and resume so the changes will take effect. First, test the connection using the test connection button.
When trying to use Qlik Data Transfer for the first time after a correct installation, you might have the below white screen:
Having a white screen basically means one of the Qlik DataTransfer micro service is not started and/or not working. This can be checked in the Windows Event Application (Source: Qlik Sense Service Dispatcher) or in the Qlik DataTransfer logs (C:\ProgramData\Qlik\DataTransfer\Log).
In the \DataUploadService logs you will see this error message:
localhost 6.0.0 Global INFO Responding certificates after reading it from defined location.
localhost 6.0.0 Global ERROR Unable to unlock the ReloadService, cannot continue.
localhost 6.0.0 Global ERROR Exception: Error: Unable to unlock the reload service.
This error message is happening directly after the step of reading certificate:
INFO Responding certificates after reading it from defined location.
Verify what certificates you have listed in the MMC console.
A group policy or other system security settings may have prevented certificates from being installed. Follow the Reset certificates steps found in the second half of the article after lifting potential restrictions on the account or machine which previously prevented the certificates from being installed.
Installing Qlik Sense Enterprise on Windows (Desktop or otherwise) will also lead to compatibility issues, including certificate mismatches.
A proxy system variable may be set in Windows. Example: https_proxy=http://PROXY:80
Qlik Data Transfer does not support the use of a proxy. Delete the Windows variable.
If only Qlik DataTransfer is installed on the machine, do the following:
In Windows Services, stop the Qlik DataTransfer service.
Navigate to C:\Program Files\Qlik\DataTransfer\DataUploadService\install-utils.
Run Remove-Certificate.ps1 in PowerShell.
Start the Qlik DataTransfer service.
Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:
client.pfx
server.pfx
If Qlik DataTransfer and Qlik Sense Enterprise on Windows are installed on the machine, do the following:
In Windows, Services, stop the Qlik DataTransfer service.
In the Windows Certificate Store, delete the following certificates:
Local Computer > Personal > QdtClient
Local Computer > Trusted Root Certification Authority > <hostname.domain> or <hostname>
Current user > Personal > QdtClient
Alternatively, you can run Remove-Certificate.ps1 in PowerShell as the administrator.
Run Configure-Service.ps1 in PowerShell as the Qlik Sense services user.
For the first input dataTransferCertificatePath, enter C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate.
For the second input qsefwPresent, enter Yes.
Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:
root.pfx
client.pfx
server.pfx
Restart the Qlik DataTransfer service.
Installing and Using Qlik DataTransfer
Troubleshooting Qlik DataTransfer
Qlik Data Transfer any release
The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."
Please, reach out to your account manager to have that fixed.
Your Qlik Cloud license includes information on what licenses and features are enabled for you. You will receive a list of all your enabled features in your original license email and we always recommend to store the email for future reference.
However, you can also call the License APIs in your browser and obtain information on what features are included in your license from there.
{"name":"qvNodes","valid":"./.","values":{"count":3}},
{"name":"reportingService","valid":"./.","values":{"quantity":1000,"value":""}}]
Testing the connection to an AWS RDS hosted Mariadb database fails with:
SYS-E-HTTPFAIL, No MySQL ODBC Unicode Driver version x.x or above is installed..
SYS,GENERAL_EXCEPTION, No MySQL ODBC Unicode Driver version x.x or above is installed.
Verify that the Qlik Replicate documentation was followed correctly and that the /etc/odbcinst.ini file contains an entry for MySQL. See Driver prerequisites | Qlik Replicate Help.
If a new driver was installed, it may have overwritten a previous entry or wrongly added a new one.
Per Qlik documentation:
[MySQL ODBC 5.3.13 Unicode Driver]
Driver = /usr/lib64/libmyodbc5w.so
UsageCount = 1
Per the driver installation:
[MySQL ODBC 5.3 Unicode Driver]
Driver=/usr/lib64/libmyodbc5w.so
UsageCount=1
Remove .13 in the .ini file to resolve this.