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.
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
The conclusions in this article were reached in collaboration with cjgorrin from the European Commission's Joint Research Centre Qlik Sense team.
With Qlik Sense's new feature, Chart-level scripts, the Replace prefix replaces all values in the HC1 table with a calculated value defined by the script.
Based on the Qlik Sense online documentation, using the attached CHART LEVEL SCRIPT_REPLACE RESIDENT load.qvf, we would expect the table to display the correct result regardless if an as (alias statement) is used or not.
Example One: Even if "as" is not used in the REPLACE statement, the error Load statement with star ('*') not supported in hypercube is displayed.
REPLACE LOAD
MyDim1,
MyDim2,
MyMeasure1,
MyMeasure2
RESIDENT HC1;
Example Two: If "as" is used in the REPLACE statement, no error is displayed but all rows are loaded with the same values. The values should remain unchanged.
REPLACE LOAD
MyDim1 as MyDim1,
MyDim2 as MyDim2,
MyMeasure1 as MyMeasure1,
MyMeasure2 as MyMeasure2
RESIDENT HC1;
This issue is caused by QB-27902, which will be resolved in an upcoming release of Qlik Sense Enterprise on Windows. Monitor the Release Notes for details.
REPLACE LOAD when used in a dynamic chart-level script is using only one row for the source data regardless of the actual number of source rows. It also incorrectly added rows to the chart.
QB-27902
Opening a QlikView document using the QlikView Desktop's Open in Server... functionality fails with the following error:
This document is a duplicate.
A QVW file cannot be opened if there is a QVF file with the same name.
Upgrade to QlikView 12.90 SR1 or any later version.
Change the extension to .qvw (lowercase) or .qvf
QV-25371
Affectioned versions:
Google Workspace can be used as a SAML identify Provider for Qlik Sense Enterprise on Windows, facilitating a single sign-on solution. In this article, we will cover how to perform a quick setup using Qlik Sense Enterprise on Windows September 2020.
To begin setting up SAML, we need to set up a new Virtual Proxy.
This concludes the setup!
To test, access the Qlik Sense hub using the prefix defined in the setup. In our case, the URL is: https://qlikserver2.domain.local/saml
You will be redirected to a Google Account signing page.
Existing limitations of Microsoft SQL Server (MS-CDC) as a source for Qlik Replicate are documented in MS-CDC Limitations and considerations (help.qlik.com).
This article aims to provide additional context to some of the listed limitations.
Question: The AR_H_USER header column is not supported (link). Does it mean all AR_H_USER headers can not be used when using MS-CDC for replication?
Answer: AR_H_USER is a header, the limitation means this header is not available to be used in the target table when Using MS-CDC for replication.
Question: MS-CDC Change Tables with fixed size columns (including NCHAR and CHAR data), the sum of which exceeds 8060 bytes, are not supported. (link) Are varchar(max) columns included in this limitation?
Answer: Varchar(max) columns are not included in the 8060bytes limitation for fixed-size columns.
Question: RENAME TABLE will not be captured and Table-level DDLs are not supported. (link) Does it mean when Qlik Replicate receives DDL changes it will work for the first DDL statement and the task will stop and we have to rename the CT table manually?
Answer: All DDL changes including RENAME TABLE, alter column, etc. are not supported. The table will be suspended. The quickest workaround is to disable MS-CDC on the table, drop the CT table and re-enable MS-CDC. If you need to keep the ct table history, the other workaround is to manually fix ct table to reflect the DDL changes.
Loading a data file from OneDrive may fail with the following error:
Cannot open the following file: 'Failed on attempt 1 to GET. (unauthenticated, Unauthenticated). Check to confirm that the file is available and that you have permission to access it.
Not all users are affected.
This is caused by QB-26980. This defect was resolved in Qlik Cloud during a September update.
If you encounter the problem in Qlik Sense Enterprise on-premise, upgrade to the the Qlik Sense Enterprise on Windows November 2024 release or any later version.
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 with the ID QB-26980 for reference.
This involves a request to a pre-authenticated download URL and uses the Range header: Partial range downloads
The Unauthenticated error is explained as The caller is not authenticated. For more information, see Detailed error codes (learn.microsoft.com).
To help Qlik customers manage costs more effectively, Qlik has developed the Qlik Snowflake Monitoring application, designed to provide invaluable insights about your Snowflake costs, usage, inventory, security, performance and contract utilization. This app utilizes Qlik's Associative Engine to connect directly to your Snowflake instance and reveal insights from Snowflake's detailed metadata, offering valuable information that traditional query-based tools and Snowflake's own reports are unable to provide.
Leveraging Qlik Application Automation, and Data Alerts, you can:
*Minor configuration is required on first run to create the required data connections.
Content:
This automation template is a fully guided installer/updater for the Qlik Snowflake Monitor. Leverage this automation template to easily install and update this application. The application itself is community-supported; and it is provided through Qlik’s Open-Source Software GitHub and thus is subject to Qlik’s open-source guidelines & policies.
For more information, refer to the GitHub Repository.
If the monitoring app was installed manually (i.e. not through the application automation installer), then the app will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring application and check their versions. This is because the application is tagged with ‘QCS - QSM - {App Name}’ and ‘QCS – QSM - {Version}’ during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.
The Qlik Snowflake Monitor requires two connections, one to your Snowflake instance to feed the data for your analytics, and one REST connection to the qlik-oss repository to run a version check on the monitor.
You will need to create a custom User, Role and Warehouse on your snowflake tenant. This is to ensure this user and role can see the monitoring details and can be monitored.
For Authentication, this setup is defaulted to username & password.
Finally, you need to name the connection as follows:
If you wish to use an alternative authentication method, please follow the documentation accordingly on both Snowflake & Qlik.
The REST connection is used to fetch version details from the GitHub repository. On reload it will look for the the latest released version in github and check this against the version you have installed. You can later use this in ‘Part Three’ to create an alert when updates to the application are available. To create a REST connection the following information is required:
Once these two connections have been set up, you can reload the application. The application has been created to accommodate Snowflake tenants of all sizes. If you have a small tenant, you will find the initial run of the load script can take around 30 minutes, and for larger tenants this can be over an hour or two. Subsequent runs will utilize cached QVDs that update daily to reduce reload times each subsequent day.
If a new release of the application is made, occasionally a full reload of data is required, but generally, if the data schema is unchanged the existing QVDs will be maintained. This is through the use of versions in the names of the QVDs used to store the data.
The application has the following two variables:
To create a new Data Alert for updates to the monitoring app, follow these steps:
The Qlik Snowflake Monitor can be easily installed by following these steps above. If you wish to find out more, check out this Ometis blog post and this Ometis Webinar to get a run through of the analytics this application can offer.
If you face any issues, please use the GitHub and raise an issue through the repository.
Unable to generate personal access token in TMC and shows error "Token creation has failed" in TMC
Talend Cloud users can generate up to five access tokens. So as an administrator, you can view the name, owner, creation date and last date used for each token generated on the account. You can delete tokens individually or by group.
It is recommended to delete unused and old tokens to increase the system security.
Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product. This article aims to provide information on where to find information about them or where to download them.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Cloud.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud App Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Reload Analyzer.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Access Evaluator.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
This article shows how to use the Qlik Application Automation Monitoring App. It explains how to set up the load script and how to use the app for monitoring Qlik Application Automation usage statistics for a cloud tenant.
For more information and to download the app and usage instructions, see Qlik Application Automation monitoring app.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
The Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.
Logs not showing up in TMC when a task is running on Remote Engine.
The payload of the generated metrics was exceeding the file size limit.
Most common error log:
com.fasterxml.jackson.databind.JsonMappingException: Invalid UTF-8 middle byte 0x70
at [Source: (ByteArrayInputStream); line: 1, column: 24553] (through reference chain: org.talend.observability.common.model.CloudEvent["data"]->org.talend.observability.common.model.MetricSet["metrics"]->java.util.ArrayList[42])
To address the issue and eliminate the error logs effectively , please follow these steps:
An existing User Directory Connector (UDC) stopped working.
The following error is displayed:
The User Directory Connector (UDC) is not configured because the following error occurred. Setting up connection to LDAP root node failed. Check log file
Configuring an identical connector with the same parameters on another server is working fine.
When starting a sync, the following exception is thrown in the User Repository logs:
Repository.UserDirectoryConnectors.LDAP.GenericLDAP.GenerateUserQuery(String[] toFilterOn)?? at Repository.UserDirectoryConnectors.LDAP.GenericLDAP.SyncUsers(String[] usersToFilterOn)?? at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)?? at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)????Exception rethrown at [0]: ?? at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)?? at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed,
LDAP filter strings are stored for UDC. If the LDAP filter is removed from the database (by using pgadmin, for example), leaving the string as a null value rather than an empty string, the Qlik Sense Services will not be able to correctly interact with the UDC anymore.
Adding alternative measures or dimensions to a chart is expected to immediately update the chart. However, Qlik Sense May 2024 requires a page refresh before any changes are reflected correctly.
Earlier versions of Qlik Sense are not affected.
This is caused by QB-26786.
Refresh the page.
Upgrade to Qlik Sense Enterprise on Windows November 2024 or any later versions.
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-26786 for reference.
A third-party security scan detects HSTS as not being enabled in Qlik Replicate or Qlik Enterprise Manager, even if it has been correctly set up.
Example software used which returned a false fail: VAM Vulnerability Assessment/CUB
Manually verify if HSTS is set up:
application-message:OK
application-status:200
cache-control:no-cache, no-store
content-length:12
content-type:application/json; charset=utf-8
date:Tue, 13 Aug 2024 01:33:36 GMT
server:Microsoft-HTTPAPI/2.0
strict-transport-security:max-age=31536000; includeSubDomains
x-content-type-options:nosniff
x-xss-protection:1; mode=block
As Qlik Replicate and Qlik Enterprise Manager do not use IIS, some third-party tools cannot successfully verify HSTS.
00298442
"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.
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
Talend Studio does not start and displays an error message:
An error has occurred. see the log file /studio/configuration/xxxxxxxx.log
The log files read:
!MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini). at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595) at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
Cached values.
To clear cached values and recreate certain configurations:
If the issue persists, create a backup of your workspace, then switch to a new empty workspace and try to pull your projects again.
The documentation of Talend Data Catalog v8.1 states that:
In fact, HA deployment is only available on the MM most advanced edition as the license stored in the shared database must be enabled to support both the Active and Passive servers (obviously on different host ids).
To be more precise, only the "Advanced Plus" version (the Data Governance version in v8.1) supports HA mode.
Talend Data Catalog High Availability Considerations
By default, Qlik Replicate control tables like attrep_apply_exceptions or attrep_status are created in lower case. If you would like for those tables to be created in UPPERCASE on Snowflake as a target, please see below.
Starting in version 2021.5 service pack 02, there is an internal parameter called setIgnoreCaseFlag which if checked or set to true, will set the QUOTED_IDENTIFIERS_IGNORE_CASE to true.
Thus, letters in double-quoted identifiers are stored and resolved as uppercase letters.
For reference: https://docs.snowflake.com/en/sql-reference/parameters.html#quoted-identifiers-ignore-case
You can search for setIgnoreCaseFlag in the Advanced tab -> Internal Parameters for the Snowflake Target endpoint.
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.
Preparing a storage task fails with the following error:
Failed to prepare Data Task
Job finished with error. SQL compilation error: Object already exists as TABLE
The error will only occur if a task name includes Japanese Katakana characters. It does not fail when using English as the preferred language; only when using Japanese.
This issue was caused by RECOB-8643 and has been resolved in the Qlik Data Gateway version 2024.5.7, along with any later releases.
See the Release Notes for details.
RECOB-8643
Upgrading Qlik Sense Enterprise on Windows (on-prem) fails. Reviewing the installer log files (see How To Collect Qlik Sense Installation Log File ) shows:
Error! Validation of: C:\Program Files\Qlik\Sense\\Client\1130.68f106588cb51d5970a9.js.LICENSE.txt failed: Could not find file 'C:\Program Files\Qlik\Sense\Client\1130.68f106588cb51d5970a9.js.LICENSE.txt'.
The environment previously used the Qlik PostgreSQL Installer to upgrade its bundled PostgreSQL database.
Verify if old Qlik Sense patches remained installed:
If the Uninstall option does not work, manually uninstall it instead:
A defect was observed if the Qlik PostgreSQL installer was previously used and old patches were not correctly removed by the installer. See the May 2023 Release Notes for QPI.
The error message appears when the installer is looking for the file which is no longer exists in the new version of the Qlik Sense.
Upgrading Qlik Sense Repository Database using the Qlik PostgreSQL Installer
Qlik Sense Enterprise on Windows with Qlik PostgreSQL Installer used to upgrade PostgreSQL
Example: QPI was used to upgrade PostgreSQL on November 2022. November 2022 was then upgraded to February 2023.
QB-17862