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 applying the Oracle July 2024 patch, the following error will be seen when working with compressed tables:
[ASSERTION ]W: A compressed row cannot be parsed for table (oradcdc_parse.c:2640)
The error leads to missing records.
Qlik is actively working on a fix to address the issue caused by the Oracle July 2024 patch. If you have not yet upgraded and plan to, consider waiting until a fix is available for Qlik Replicate. We expect one by the end of week 39.
Only Oracle instances with compressed tables are affected.
If you are uncertain whether or not you are using compressed tables, run the following query:
select owner, table_name, COMPRESSION,COMPRESS_FOR from dba_tables where compression='ENABLED'
If waiting is not an option, please upgrade to Qlik Replicate 2023.11.724 and log a ticket with support if you encounter problems with compressed tables post-upgrade.
Oracle July 2024 Patch with compressed tables. It is being investigated as RECOB-8914 by Qlik.
Qlik Enterprise Manager (QEM) analytics show the error:
could not open file base/16394/16500: No such file or directory.
Qlik Enterprise Manager analytics data is stored in the Postgres database from your Repository connection. The data is stored as tables and retrieved by QEM. This error refers to the table's Postgres base file being missing.
The base files indicated in the error message will need to be restored either through:
Consult your Postgres DBA for the procedures.
If no backups are available, then the Repository connection needs to be initialized to recreate all the tables. All previous Analytics data will be deleted and recreated.
Postgres upgrades and maintenance may cause missing base files. Best practices include stopping the Qlik Enterprise Manager collector before maintenance and always backing up your database to ensure changes can be reverted if undesired behavior occurs.
After an upgrade of Qlik Replicate (2022.5 to 2023.11), tasks using a PostgreSQL source see truncations for the varchar column when running a full load.
The following is logged in the source_unload logging component:
[SOURCE_UNLOAD ]V: Value for (varChar column) was truncated. bind type: -8, data len: 14 (14, after truncation: -2), bind len: 0, statement:
Add the Internal Parameter unboundedVarcharMaxSize on the Postgres Aurora source endpoint and set it to 8000.
If you are using Logstream setup, please add unboundedVarcharMaxSize on the Postgres Aurora source endpoint in both the Logstream Parent task and child task.
To resolve the issue:
The Internal Parameter has unexpectedly changed between Qlik Replicate 2022.5 and 2023.11. This only affected Postgres Aurora.
While unboundedVarcharMaxSize had a default value of 8000 in 2022.5, it is now set to -1 for Postgres Aurora by default.
RECOB-8644
The HubSection_Home resource filter in Qlik Sense refers to the button which allows a user to navigate back to the Hub from inside of an application.
Default ruleset:
If an administrator should want to disable this functionality for their users, for example, if the application is embedded into another page. Then they will want to disable the default rule named HubSections.
The result with this rule disabled is as follows for the end user:
The result of this change will disable this functionality for all users. If an administrator wants to provide this functionality to a select set of users then the administrator can create a new rule in this schema:
Customer policy adopted injection via the reverse proxy of the Content Security Policy header for security reasons.
The policy adopted is basic: default-src 'self'
Opening the QlikView AccessPoint or Qlik Sense Hub may fail or the AccessPoint may only render partially.
The Browser Debug tools will provide more insight:
QlikView
Qlik Sense Enterprise on Windows
The Header Content Security Option contains a string of rules that informs the browser which resource/code is trusted to be loaded, executed rendered.
More details on the argument could be found here:
https://www.w3.org/TR/CSP3/ ,
For QlikView Accesspoint a first example is to use Content-Security-Policy: "default-src 'self' 'unsafe-inline' data: ;" ; (note that using 'unsafe-inline' option could be unsafe in a the proxy injection scenario when the client will brose a different site , you could/evaluate to use instead the sha256-hashcode version )
Further option could be necessary if for example you have QlikView Extension Object ( Server and Document Extensions) that are using external resources downloaded from CDN locations;
In this case the troubleshoot is the same use F12/Development Tools to check the resource that violates the policy and ad an exclusion.
QlikView Access Point Shows "Loading Content" Indefinitely,
What is CSP (Content-Security-Policy) and How does it Relate to Qlik?
Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.
The behaviour began after an upgrade of Qlik Sense Enterprise on Windows.
This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.
Enable QmcTaskTableCacheDisabled.
To do so:
Upgrade to the latest Service Release and disable the caching functionality:
To do so:
NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.
Should the issue persist after applying the workaround/fix, contact Qlik Support.
After upgrading to Qlik Sense Enterprise on Windows May 2024 or newer, exporting a sheet or visualization to a PDF leads to a blank PDF output. The same export worked as expected before the upgrade.
This affects deployments running Windows 2012 R2, a version of Windows no longer supported by Qlik Sense Enterprise on Windows. It is incompatible with the current reporting_web_renderer.exe resource used by the Printing service.
Upgrade the server to a supported operation system and test again.
Microsoft dropped support for Windows 2012 R2 in January of 2023. The last version of Qlik Sense Enterprise on Windows which supported Windows 2012 R2 was Qlik Sense May 2023.
The eclipse OSGi framework was unable to promptly identify the installed CommandLine module.
To resolve this issue, a retry mechanism should be implemented to ensure its functionality.
Add -Dinstall.org.eclipse.equinox.p2.transport.ecf.retry=10 after mvn command.
mvn org.talend.ci:builder-maven-plugin:8.0.16:generateAllPoms \
-Dtalend.studio.p2.update='/opt/Patch_20240621_R2024-06_v1-8.0.1' \
-Dlicense.path='/opt/license' \
-Dinstaller.clean=true \
-Dstudio.error.on.component.missing=false \
-Dinstall.org.eclipse.equinox.p2.transport.ecf.retry=10 \
-s ${TALEND_SETTINGS_XML}
QlikView and Qlik Sense load either missing or additional zeros, compared to the values in the data source.
For example data like in the below script is loaded with incorrect leading zeros.
LOAD * Inline [
F1, F2
1, a
01, b
02, c
2, d
];
On the second row the leading zero is missing, and on the fourth row, there is an unexpected additional leading zero.
QlikView
Qlik Sense Enterprise on Windows
Qlik Cloud
The observed behaviour is a part of fundamental Qlik engine functionality and data compression technique.
In short, this means that Qlik interprets and associates loaded data by best effort. As part of Qlik optimization and compression technique the same reoccurring value in a field is stored on the first occurrence only, and the following occurrence reference to the first (stored) value. This means that two values with identical numerical representation can not be stored with two different textual presentations in the same field in Qlik.
Please keep in mind that all numerical values in Qlik act as dual values. This means that they have an underlying numerical value that is used for calculations, and a textual formatted value which is the value seen in charts or as calculations results.
In the example below four rows of data are loaded. In the field F1 there are four different value.
LOAD * Inline [
F1, F2
1, a
01, b
02, c
2, d
];
Identical numerical values are associated with the same textual presentation value in Qlik . For this reason, it is not possible to store the same numerical value with different textual presentation values.
One way to resolve this is to format the values as text by using Text() during reload.
LOAD
text(F1) as F1,
F2
Inline [
F1, F2
1, a
01, b
02, c
2, d
];
This will result in the visual values looking identical to the data source.
NOTE: Value formatted with Text() will not have underlying numerical values, hence calculations on these values is not possible.
Talend Managemnet Console supports SingleSignOn(SSO) and integrates with several SSO platforms. In this exercise, you will activate SSO by linking your TMC with Okta which is a third-party enterprise-grade identity management service, built for the cloud, but compatible with many on-premises applications.
Check your email inbox and click on the confirmation link to activate the Okta Account
Connect to your Okta organization and add Talend Cloud as a new SSO-enabled application.
The TalendCloudDomainName attribute indicates your Talend Cloud domain. You can find the domain name in the Domain field of the Subscription page of your Talend Management Console. The NameId Format attribute indicates the email address format.
Once you set and Create the Talend Cloud SAML application, you can see the Icon created in OKTA My Apps
And TADA! You are connected to Talend. Check that your user has the roles and types you have set.
You must have the Security Administrator role in Talend Management Console and have the metadata file obtained from the SSO provider
Free Trial OKTA Account
Talend Management Center
creating-talend-cloud-application-in-okta
When customer is trying to connect to Mysql 8 DB on Talend 8 R2024-05 it is giving the below error:
===============
javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
at java.base/sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:842)
at java.base/sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:821)
===============
Customer is using MySQL Driver: mysql-connector-java-8.0.12.jar
It seems that it is a bug with the MySQL driver. It looks like sql drivers 8.0.16 and below are affected.
https://bugs.mysql.com/bug.php?id=93590
https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-16.html
https://bugs.mysql.com/bug.php?id=93590
https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-16.html
Expect font not appearing in NPrinting Pixel Perfect PDF reports.
By Default, there are two fonts that can be selected in Pixel Perfect reports that will show the Chinese Characters,
Most of the other languages will not show the characters.
In the Pixel Perfect Editor, simply switch to MS Gothic font
Chinese, Japanese ,German, Spanish, Portuguese languages will now appear in the PDF format report export.
This article provides an overview of how to manage users using Qlik Application Automation. This approach can be useful when migrating from QlikView, or Qlik Sense Client Managed, to Qlik Sense Cloud when security concerns prevent the usage of Qlik-CLI and PowerShell scripting.
You will find an automation attached to this article that works with the Microsoft Excel connector. More information on importing automation can be found here.
Content
In this example, we use a Microsoft Excel file as a source file to manage users. A sheet name, for example, Users, must be added and this must also be provided as input when running the automation. The sheet must also contain these headers: userId, Name, Subject, Email, Roles, Licence, and Flag.
Example of sheet configuration:
If users are to be created the Flag column must be set to create. If users are to be deleted, there's no need to include roles, but Flag must be set to delete.
Add the List Rows With Headers block from the Microsoft Excel connector to read the values that have been configured in the Excel sheet.
When running the automation you must provide input to the automation, this includes the name of the worksheet to read data from. You also need to specify the first and last cell to read data from, as well as if users are to be created or deleted. Example :
Input | Value |
Worksheet Name | Users |
Excel Start Cell | A1 |
Excel End Cell | G5 |
Mode | Create |
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 manage space membership (users)
This article supplements documentation that requires changes to the Qlik Sense Engine Settings.ini. No settings are provided in this article.
[Settings 7]
Key=Value
If you are looking to modify the Qlik Sense Desktop client settings.ini:
Qlik Enterprise Manager (QEM) fails to monitor Qlik Replicate.
The following issues can be observed:
Possible error messages:
This is a known issue and Qlik is actively working on a patch. Please review the release notes for QB-26321 and QB-27571 for updates.
QB-26321 and QB-27571
QB-26321 and QB-27571
"RestConnectorMasterTable" General Script Error in statement handling
RestConnectorMasterTable:
20200826T102106.344+0000 0088 SQL SELECT
20200826T102106.344+0000 0089 "name",
20200826T102106.344+0000 0090 "value"
20200826T102106.344+0000 0091 FROM JSON (wrap off) "contactCustomData"
20200826T102106.344+0000 0092 WITH CONNECTION (
20200826T102106.344+0000 0093 URL " ",
20200826T102106.344+0000 0094 HTTPHEADER "Authorization" "**Token removed for security purpose**"
20200826T102106.344+0000 0095 )
20200826T102106.967+0000 General Script Error in statement handling
20200826T102106.982+0000 Execution Failed
20200826T102106.986+0000 Execution finished.
Qlik Sense Enterprise on Windows
To be able to catch the exact error and mitigate the issue they need to apply our recommended best practices for error handling in Qlik scripting using the Error variables
Error variables
Script control statements
Set to ErrorMode=0 it will ignore any errors and continue with the script. You can use the IF statement to retry the connection or move to another connection for a few attempts and then it will change it to ErrorMode=1 and fail or just disconnect on its own.
A sample script is located here, but further options can be added from the Help links already provided.
Qlik-Sense-fail-and-retry-connection-sample-script
Note: QlikView scripting is the same in these functions for Qlik Sense unless otherwise stated, but there are some very helpful items in the links.
Best-Practice-Error-Handling-in-Script
Error with the fetch of the token with the rest call. If the number of rows in a table doesn't match or is less than expected, trigger the script to throw an error and have it try to load the table again for more records, or if the count is off, do a Loop until returns the correct number.
QB-3164
Three requirements need to be met in order to allow Anonymous users access to the Hub:
Useful information:
By default, anonymous access is disabled. The steps provided require a restart of the Proxy service after completion.
Anonymous users will need to have a license rule available for them which gives them either an Analyzer Capacity License or a Login Access Token. The instructions in this article will focus on Analyzter Capacity Licenses.
You can use the default Everyone stream, which has already been set up for anonymous access, or create your own.
We will create two rules. One to allow logged in (authenticated) users access and publishing permissions. One to allow anonymous user access, but no publishing permissons. Note that based on your requirements, this may need to modified.
We are now ready to test access.