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 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.
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:
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.
Operation Monitor and License Monitor apps in Qlik Sense failed to reload with error message;
"Error: QVX_UNEXPECTED_END_OF_DATA: Unexpected character encountered while parsing value: <. Path '', line 0, position 0."
Check the connection string of the data connections for your monitor_apps_*.
The connection string should be: queryHeaders=X-Qlik-XrfKey%20000000000000000%1User-Agent%2Windows;PaginationType=None;
If the string is instead: queryHeaders=X-Qlik-XrfKey%20000000000000000%1User-Agent%2Forms;PaginationType=None; then modify it to User-Agent%2Windows.
Create a secondary virtual proxy using standard windows authentication. In our example we use "win" as the prefix. For detailed instructions on how to add a new Virtual Proxy, see Qlik Sense: How to create a new Virtual Proxy.
Edit all Data Connections prefixed with monitor_apps_ to use the new virtual proxy. Change the connector URL path to contain the Windows authenticated virtual proxy.
Operations Monitor and License Monitor apps use the Qlik REST Connector to fetch data. The connector requires Windows Authentication to be successful in fetching data. This issue occurs when no virtual proxy in the Qlik Sense deployment utilizes Windows authentication.
This article gives an overview of the available blocks in the Qlik Platform Operations connector in Qlik Application Automation.
The purpose of the Qlik Platform Operations connector is to simplify the deployment and management of multiple tenants within Qlik Cloud. To learn more about the multitenant model in Qlik Cloud, please review the following series of tutorials.
This connector consists of:
To authenticate, you will need to provide your OAuth2 client ID and client secret. If you have a multitenant license, enter a regional OAuth client (generated via My Qlik) or a tenant OAuth client (generated from within a tenant). Note that only regional OAuth clients can create new Qlik Cloud tenants. In order to use your own tenant, you need to create an OAuth m2m client (trusted) in the management console on your tenant. For more information, please check this article.
Most blocks require a specified tenant as the target. A tenant is uniquely identified by name and the region that it is deployed to. For example, for mytenant.eu.qlikcloud.com, enter mytenant.eu. You can use the Get Tenant Name and Region block to obtain the tenant from a full URL.
Let's now go over a basic example of how to deploy a tenant, create an automation inside the deployed tenant and run it using the Qlik Platform Operations:
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.
MySQL allows the zero date (and/or zero month) in data rows, which is a specific behaviour of MySQL and does not exist in most other RDBMS. This behaviour causes invalid date errors while replicating data to heterogeneous databases.
In this article, we will explain the solutions in both Full Load and CDC stages.
To handle zero date in Qlik Replicate for both Full Load and CDC stages:
MySQL provides an ODBC parameter ZERO_DATE_TO_MIN to control this behavior. please take note MySQL adds one day for zero date values.
Based on this setting, the Full Load stage gets a non-zero date. For example, the source value 2022-12-00 in MySQL will become 2022-12-01 in the target endpoint after the Full Load is finished.
The Full Load steps will not have an impact on the CDC stage. That means the source value 2022-12-00 will be 2022-12-00 still in the CDC stage. To mitigate this, we need to create a transformation to replace the zero date 00 with 01 as we do in the Full Load stage.
The simple global transformation expression can be:
date(substr($AR_M_SOURCE_COLUMN_DATA,1,8)||replace(substr($AR_M_SOURCE_COLUMN_DATA,9,2),'00','01'))
For more information on how to set transformations, see: Starting the Global Transformation Rules wizard.
Transformation: Date Time - Invalid Value - MySQL
Qlik Replicate all versions
MySQL all versions
Support case #00107317
It is important to understand the options which PostgreSQL uses to allow connectivity. These principles are valid no matter whether you are using the Qlik Sense Repository Database service to host the database or using a standalone PostgreSQL instance. The two key files which PostgreSQL uses to define who can connect, how they connect, where they can connect from, and how many connections are allowed are:
For bundled PostgreSQL instances, the files are located in:
C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\x.x
If you have unbundled PostgreSQL using the Qlik PostgreSQL installer (QPI), the default location is:
C:\Program Files\PostgreSQL\xx\data
For any other standalone PostgreSQL instances, consulting with your database admin to locate the data directory.
Note: Any changes to these files will require a restart of the Qlik Sense Repository Database or PostgreSQL.
Note: Any lines prefixed with a # are commented out and not active.
In the postgresql.conf, in a basic Qlik Sense configuration, there are two key configuration options which are important:
Where these lines are can vary but an expected single node Qlik Sense site would look like this:
listen_addresses = '*' max_connections = 100
The pg_hba.conf file defines a variety of aspects:
# TYPE DATABASE USER ADDRESS METHOD # IPv4 local connections: host all all 127.0.0.1/32 md5 # IPv6 local connections: host all all ::/0 md5 # Allow replication connections from localhost, by a user with the # replication privilege. #host replication postgres 127.0.0.1/32 md5 #host replication postgres ::1/128 md5 host all all 0.0.0.0/0 md5
In this example pg_hba.conf file there two active lines. The first line specifies that all users can connect to all databases from the local loopback IP using MD5 authentication (host all all 127.0.0.1/32 md5). The second line specifies that all users can connect to all databases from any valid IPv4 address using MD5 authenication (host all all 0.0.0.0/0 md5)
Please review our help for references to more sophisticated configurations where specific IP addresses or IP address ranges are covered.
To recap, when ensuring connectivity in a Qlik Sense Shared Persistence environment, especially a multi-node site, the core configurations which are needed are:
An Automation fails with the below error when trying to run,
The following error occurred: Connector *********:****** not found (: Requested endpoint could not be provisioned due to failure to acquire a load slot: The user does not have permission to the gateway (DirectAccess-0002) LIB CONNECT TO '*********:******') The error occurred here: LIB CONNECT TO '*********:******'
The User must have at least edit permissions to the space the gateway is registered with.
The User needs at least CanConsume on both spaces: the one that the data connection resides in and the space that the Direct Access gateway is associated with. Those spaces might be one and the same, but they can also be separate.
Error "DirectAccess-0002" indicates that the User does not have permission to the gateway.
After a Qlik Replicate upgrade from 7.0.0-1221 to 2021.11.0-107 (or similar), logstream tasks may fail with the following error when resumed:
SYS-E-HTTPFAIL, Failed to deobfuscate password of endpoint 'SRC_ORA_MDMSP1_RO'..
SYS,GENERAL_EXCEPTION,Failed to deobfuscate password of endpoint 'SRC_ORA_MDMSP1_RO'.
Initially, the object MyPasswordProvider.so was missing execute permission. Once the permission was granted, the real error showed up in repcmd.log file.
[ADDONS ]W: Failed to load add-on path </home/attunity/MyPasswordProvider.so>, error: </home/attunity/MyPasswordProvider.so: undefined symbol: curl_easy_getinfo>
This error indicates that the CURL library is not defined in site_arep_login.sh.
To resolve this issue, either manually modify the .sh or copy the content from a functioning environment.
Example:
The issue exists in a QA environment, but not in production. Copy the content from the production environment's site_arep_login.sh and sourced arep_login (source arep_login.sh), and then restart Qlik Replicate to resolve the issue.
What to look for:
The planned fix for this is currently being reviewed.
After an upgrade to Qlik Sense Enterprise on Windows May 2023 patch 3 and 4, REST connectors fail with the following error:
"WITH CONNECTION" is not allowed. To allow "WITH CONNECTION", select Allow "WITH CONNECTION" in the connector settings.
The Allow WITH CONNECTION option is not exposed in the REST Connector GUI and cannot be changed.
Qlik is actively working on a permanent solution.
Resolving the issue requires us to replace a file which previous patches have not updated correctly.
Backup the affected file before continuing with the workaround. When taking the backup, do not keep the backed up file in the same folder. (see end notes)
End notes:
The folder C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector can only contain one qliksourceconfig file with correct name: qsdfw_qsefw_qlikview.qliksourceconfig
If there are two qliksourceconfig files (even with different names, such as a backup), the first one in alphabetical order will be chosen.
QB-20735.
Qlik Sense Enterprise on Windows May 2023 Patch 3 and 4 (as of the documentation of this article)
QB-20735
Logging in to the Qlik Enterprise Manager fails with the following HTTP error:
HTTP Error 400. The size of the request headers is too long
The size of request headers is too long error is caused by the used credentials being too long. Different authentication methods, such as Microsoft Azure Active Domain, will encrypt your credentials differently which can lead to varying lengths for the request headers.
A solution to the Qlik Enterprise Manager login error of the size of the request header is too long requires to either
If you choose to modify the header size, contact your Windows Administrator team to decide the size and configure the new value in the Windows Registry.
Case 00100348
This article collects some best practices to reduce the time to load Sense apps in the HUB.
There can be different causes for an app to open slowly.
A part of the optimizations reported here above, it must be considered that the most relevant factors affecting the app load time is the size and the complexity of the app. Qlik recommends not to exceed 1-2 GB for any apps. Complex expressions should be reduced or moved to the script whenever it is possible. It is also important to check that the system has sufficient resources anytime an app is loaded, also when complex reloads run or many users are connecting at the same time.
In some scenarios we need stop and resume a task. However for Hana trigger-based CDC task, if the option "Use log table" is enabled, resuming the task, or while you trying to startup the task from a given timestamp, you may get the below information (with SOURCE_CAPTURE set to Trace):
2021-09-09T22:12:34:881897 [SOURCE_CAPTURE ]T: Resume from 'timestamp:2021-09-09T20:30:00'
2021-09-09T22:12:34:881897 [SOURCE_CAPTURE ]T: Start from timestamp is not supported in the Log-Table mode
The option "Use log table" is enabled by an Internal Parameter in versions 6.6/7.0. In version 2021.5 it's in GUI property like below:
Start the task by source change position, rather than the timestamp. Here is a query to prepare the stream position in the correct format by a timestamp:
;Get the stream position by timestamp
;Before using the query, please replace the $SCHEMA$ to your artifacts schema where the table "attrep_cdc_log" is located.
;The timestamp format is 'YYYY-MM-DD HH:MM:SS' (Note, the timestamp should be the one on HAHA Server side, not the replicate server's)
;The range will be from the first (not included) event that happened after the time specified to the last (included) event in the table
SELECT 'V1:'||MIN("$rowid$")||':'||MAX("$rowid$")||':0:'||MIN("$rowid$") AS "STREAM POSITION" from "$SCHEMA$"."attrep_cdc_log" WHERE "CHANGE_EVENT_TIME" >= 'YYYY-MM-DD HH:MM:SS'
A unique row will be returned:
V1:670636:686112:0:670333
Then in the Replicate UI, start the task by source change stream position:
Salesforce support case #02260694.
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.
Generating a Qlik NPrinting report with an output of more than 512MB will fail with:
ERROR: System. IO .IOException: Stream was too long.↓↓ at System. IO .MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)↓↓ at Ionic.Zip.CountingStream.Write(Byte[] buffer, Int32 offset, Int32 count)
Since the November 2020 release, RabbitMQ Server (deployed as Qlik NPrinting Messaging Service) has been updated to version 3.8.3. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to generate Qlik NPrinting reports bigger than 512MB.
See Report size limit | Qlik NPrinting Release Notes.
OP-9628
If a Qlik Sense Dashboard is secured with Section Access, a Qlik NPrinting report generated from it may fail if the user does not have full RDUP permissions. If only Read access has been provided, the report fails to generate with the error:
ERROR in setting limited dimension default label: Access denied [5]:Access denied(SetProperties)
This was identified as an old defect in versions of Qlik NPrinting prior to September 2020. Later versions should no longer be affected.
However, if the error occurs, verify that the user running the report has Read permissions or full permissions.
OP-9376
The Chart Exploration panel is not shown in straight tables after the upgrade to Qlik Sense May 2023 Patch 3. The option is still visible when you right click on the table, but it does not work: the table is just enlarged or an empty window appears instead of the Chart Exploration.
The problem is not present in any Qlik Sense releases previous to May 2023 Patch 3. It is fixed in Qlik Sense May 2023 Patch 6 and higher releases. The Qlik Sense August release was not affected.
In releases prior to May Patch 6, it is possible to resolve the problem on the affected releases by following these steps:
An incorrect formatting of the paths in the 'import-map.json' file causes the problem.
QB-20719, QB-21856
Duplicate "Mobile Content" collections are present on a tenant.
The option to delete them is not present.
Note: there is no "undo". Make sure to remove the right collection.
"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.
The Qlik Sense PostgreSQL database was previously updated and unbundled using the Qlik PostgreSQL Installer (QPI).
Following an upgrade of Qlik Sense Enterprise on Windows, the Qlik Repository Service may not start or the Management Console open to the following error:
Failed to load properties. No data found.
Qlik Sense on Windows May 2023 (upgraded to)
Previous use of Qlik PostgreSQL Installer (QPI) while Qlik Sense had a patch installed
Repair the installation. See Repairing an installation.
Previously to using QPI, all patches need to be removed. See Requirements for QPI.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
QB-20581
After upgrading to QlikView 12.70 SR2 users cannot open documents from the AccessPoint once the session timeout is reached. The following error is displayed:
Failed to open document, You don't have access to this document
QlikView May 2022 (12.70) IR to SR2
QlikView May 2023 (12.80) IR
This is caused by QV-24743 and QV-24830.
Fix scheduled to be released in:
Upgrade to the appropriate version when it has become available. Refer to the QlikView Release Notes for details once the versions have been released.
QV-24743 and QV-24830
Qlik Cloud and Qlik Sense Enterprise on Windows only render 100 bookmarks. If more than 100 bookmarks have been created and are being viewed, specific bookmarks will need to be filtered using the bookmark search.
Qlik Sense Enterprise on Windows
Qlik Cloud
HLP-15300
This Techspert Talks session covers:
Chapters:
Resources:
Qlik Cloud Reporting – Improving Table Presentation
How to send an Excel report as an attachment using Qlik Application Automation
Creating an Automation from Templates
Tips For Designing Application Automation Reporting Reports
Click here to see video transcript