Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
A scheduled reload using Qlik Data Gateway fails with the following error:
Internal error. (Connector error: Unknown reason:. Connector process started but gRPC server failed to initialize after 3 attempts (DirectAccess-1500)) The engine error code: EDC_ERROR:22013
Manual reloads may work as expected, but scheduled reloads continue to error out.
The error indicates a resource shortage.
Increase the Qlik Data Gateway VM server CPU and RAM to meet the system requirements. See System prerequisites for details.
The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.0.0.
Content
Improvement / Defect | Details |
SHEND-2273 |
|
QCB-28706 |
Upgraded PostgreSQL version to 14.17 to address the pg_dump vulnerability (CVE-2024-7348). |
SUPPORT-335 | Upgraded PostgreSQL version to 14.17 to address the libcurl vulnerability (CVE-2024-7264). |
QB-24990 | Fixed an issue with upgrades of PostgreSQL if Qlik Sense was installed in a custom directory, such as D:\Sense. |
Improvement / Defect | Details |
SHEND-1359, QB-15164: Add support for encoding special characters for Postgres password in QPI | If the super user password is set to have certain special characters, QPI did not allow upgrading PostgreSQL using this password. The workaround was to set a different password, use QPI to upgrade the PostgreSQL database and then reset the password after the upgrade. This workaround is not required anymore with 1.4.0 QPI, as 1.4.0 supports encoded passwords. |
SHEND-1408: Qlik Sense services were not started again by QPI after the upgrade | QPI failed to restart Qlik services after upgrading the PostgreSQL database. This has been fixed now. |
SHEND-1511: Upgrade not working from 9.6 database | In QPI 1.3.0, upgrade from PostgreSQL 9.6 version to 14.8 was failing. This issue is fixed in QPI 1.4.0 version. |
QB-21082: Upgrade from May 23 Patch 3 to August 23 RC3 fails when QPI is used before attempting upgrade. QB-20581: May 2023 installer breaks QRS if QPI was used with a patch before. |
Using QPI on a patched Qlik Sense version caused issues in the earlier version. This is now supported. |
You can also click Copy link - this will show a warning that the bookmark needs to be published. When confirming the warning, the bookmark will be automatically published.
If the share option is not available or if users who should see the bookmarks cannot find it, verify that Sense has not been set up with Security Rules that disallow sharing or access to specific objects. See the attached document for details.
Loading MS Access data (.accdb file) using generic ODBC (via Data Gateway) in Data Manager fails with the following error:
Failed to add data
Data could not be added to Data manager. Please verify that all data sources connected to the app are working and try adding the data again.
The Direct Access ODBC Connector log reads:
Message=Error in HandleJsonRequest for method=getRawScript,
exception=Exception, error=ODBC Wrapper: Unable to execute SQLForeignKeys:
[Microsoft][ODBC Driver Manager] Driver does not support this function.
internalError=True
Use the Data Load Editor to load MS Access data.
Loading file-based Access DBs through ODBC to a modern BI tool is not recommended, specifically with larger files. These are likely to underperform during the loading process.
This error indicates the MS Access ODBC driver doesn’t support the SQLForeignKeys ODBC function. However, retrieving the table foreign keys is essential for Data Manager (as opposed to Data Load Editor).
SUPPORT-4446
A Talend Spark Stream Job configured with Yarn cluster mode and Kerberos enabled is encountering issues and failing to execute, presenting the following errors:
YarnClusterScheduler- Lost executor 3 on me-worker1.xxx.co.id: Unable to create executor due to Unable to register with external shuffle server due to : java.lang.IllegalStateException: Expected SaslMessage, received something else (maybe your client does not have SASL enabled?)
jaas.conf content =
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/tmp/adm.keytab"
principal="cld_adm@XXX.CO.ID"
doNotPrompt=true;
};
KafkaClient {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/tmp/adm.keytab"
principal="cld_adm@XXX.CO.ID"
doNotPrompt=true;
};
The external shuffle service within YARN is configured to mandate SASL authentication; however, the Spark executor is either improperly configured to use SASL or is transmitting an incompatible message.
Common causes includes:
This error results in the executor's failure to register with the shuffle service, prompting the YarnClusterScheduler to mark it as lost.
Ensure that the external shuffle service is enabled, and that the SASL settings are in accordance with YARN's configurations:
spark.authenticate true
( #not necessary
spark.network.crypto.enabled true
spark.network.crypto.saslFallback true
)
The new Straight Table was moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one.
This article aims to answer any frequently asked questions around this switch, beginning with:
Here are some examples:
No, the old table will continue to work in the foreseeable future. Any changes will be notified in advance. Regardless, we highly recommend upgrading your tables as soon as possible to enjoy the new Straight Table's new functions.
The easiest way to convert your tables is to drop the new table chart onto the old one.
The new table looks different and offers more functionality that must be enabled to be used.
Not anytime soon, it will be a soft fade out. The new Straight Table will be the preferred choice for all new applications, and we anticipate many will upgrade to benefit from new functionality. Over time, the usage of the old table will diminish until most applications are using the new table anyway.
Qlik Sense Enterprise on Windows will have the table feature aligned with Qlik Cloud Analytics in a future release.
We’re closely monitoring feedback on the new table and are dedicated to creating the best possible experience, including improvements to accessibility. We are committed to accessible standards so people with disabilities can use our products. Printing, the tables should, of course, print in as consistent a manner as possible. As for usability. we aim to enable experienced users to reach functionality quickly, while also not overwhelming new users.
This article aims to help you facilitate the most effective way to collaborate with Qlik Support. It defines your responsibilities as a partner, including reproducing issues, performing basic troubleshooting, and consulting the knowledge base or official documentation.
For the Qlik Talend guide, see Partner Guide: How to Prepare and Collaborate with Qlik Talend Technical Support.
Before contacting Qlik Data Analytics Technical Support, partners must complete the steps outlined in Qlik Responsible Partner Duties and should review the OEM/MSP Support Policy to understand the scope of support and the expectations on Partners.
Content
Identify which Qlik product, environment, product configuration, or system layer is experiencing the issue.
For example, if a task fails in Qlik Sense Enterprise on Windows, try running it directly in Qlik Sense Management Console to determine whether the problem is transient. Also, try running a different task to determine whether the problem is task-specific.
Similarly, if a reload fails in one environment (e.g., Production), inform the customer to try running it in another (e.g., Test) to confirm whether the issue is environment-specific.
Always include the exact product name, version, and patch (or SR) the customer is using.
Many issues are version-specific, and Support cannot accurately investigate the issue without this information.
If the product the customer is using has reached End of life (EOL), please plan the upgrade. If the issue can be reproducible on the latest version, please reach out to us so that we can investigate and determine whether it's a defect or working as designed.
For End of Life or End of Support information, see Product Lifecycle.
Partners are expected to recreate the customer’s environment (matching versions, configurations, and other relevant details) and attempt to reproduce the issue.
If you do not already have a test environment, please ensure one is set up. Having your own environment is essential for reproducing issues and confirming whether the same behavior occurs outside of the customer’s setup.
In addition, please test whether the issue occurs in the latest supported product version. In some cases, it may also be helpful to test in a clean environment to rule out local configuration issues. If the issue does not occur in the newer version or a clean setup, it may have already been resolved, and you can propose an upgrade as a solution.
See the Release Note for the resolved issues.
Regardless of whether the issue could be reproduced, please include:
While pasting a portion of the log into the case comment can help highlight the main error, it is still required to attach the entire original log file (using, for example, FileCloud).
Support needs the full logs to understand the broader context and to confirm that the partial information is accurate and complete.
It is difficult to verify the root or provide reliable guidance without full logs.
Additionally:
Please do not simply forward or copy and paste the customer’s inquiry.
As a responsible partner, you are expected to perform an initial investigation. In your case submission, clearly describe:
Sharing this thought process:
Even if the issue remains unresolved, outlining what you already tried helps Support move forward faster and more effectively.
Attach all relevant files you received from the customer and personally reviewed during your investigation, as well as all relevant files you have used when reproducing the steps.
Providing both the customer’s files and your reproduction files allows Support to verify whether the same issue occurred under the same conditions, and to determine if the problem is reproducible, environment-specific, or isolated to the customer's configuration.
This includes (but is not limited to):
All support cases must be submitted using your official partner account, not the customer's account.
If you do not yet have a partner's account, contact Qlik Customer Support to request access and to receive the appropriate onboarding.
Review the support policy and set the case severity properly. See
Qlik Support Policy and SLAs
This template helps guide you on what to include and how to structure your case.
What happened? When did it happen? Where did it happen?
Clearly describe the event, including:
Only include what is needed based on the case type.
Examples:
List the files you have included in the case and what each one is.
Explain what investigation was done before contacting support.
Examples:
Thank you! We appreciate your cooperation in following these guidelines.
This ensures that your cases can be handled efficiently and escalated quickly when necessary.
Question
After moved migrated GitHub from on-premises to cloud and so switched from credential login to SSO, is there a way to authenticate Talend Studio to GitHub using SSO login? If using personal access tokens (PATs), is it on the security risk?
So far Talend Studio cannot SSO directly to GitHub, it can use a workaround with PATs or SSH keys, and thereby also be more secure than without SSO.
How a personal access token can be authorized for SSO
This link above explains how a personal access token can be authorized for SSO. So using a username and PAT from Studio to login to GitHub. GitHub allows granular permission controls for PATs and SSO authorization further mitigates security risks. Developers will need considerable rights.
How an ssh key can be authorized for SSO
You can do much the same with SSH keys
When attempting to connect to a GitHub repository from Talend Studio, encountered an error with the following message:
"git-upload-pack not permitted on 'https://github.com//.git'"
Common Symptoms:
Error:org.eclipse.jgit.api.errors.TransportException
Message:username or password are not correct
GitHub Desktop and Git Bash access may still work
Can successfully access other GitHub repositories
This issue is caused by a missing Single Sign-On (SSO) authorization on the GitHub Personal Access Token (PAT) being used.
When a GitHub organization enforces SAML SSO, all PATs must be explicitly authorized for use by the organization. If this step is skipped or the organization has changed its SSO enforcement, Git operations like git-upload-pack
will be denied — even if the PAT has the correct scopes.
To address the issue, please verify and reauthorize Single Sign-On (SSO) for your GitHub Personal Access Token (PAT) by following these step-by-step instructions:
Optional: Test via Git Bash
Run:
git clone https://user:PAT@github.com/<org>/<repo>.git
If SSO is not configured, you will receive a message:
Your organization has enabled or enforced SAML SSO...
Qlik Talend Cloud: 'git-receive-pack not permitted' error while creating a project
Using Qlik-CLI to export an app without the '--exportScope all' parameter fails with the error:
Error: 400 - Bad Request - Qlik Sense
This is observed after an upgrade to Qlik Sense Enterprise on Windows November 2024 patch 10 or any later version. The error is intermittent and the export may succeed if executed several times.
Reviewing the output shows Status: 201 Created, followed by the error after retrieving the app from the temporary download path:
> qlik qrs app export create "dbb1841d-f3f6-4a49-b73f-0a24cc003b1b" --exportScope all --output-file "C:/temp/App3.qvf" --insecure --verbose
Insecure flag set, server certificate will not be verified
POST https://sense/jwt/qrs/app/dbb1841d-f3f6-4a49-b73f-0a24cc003b1b/export/e237e6c8-d367-45d3-9eff-9f191b3f1ef5?exportScope=all&xrfKey=4B21426C21AE6B85...
Status: 201 Created
{
"exportToken": "e237e6c8-d367-45d3-9eff-9f191b3f1ef5",
"appId": "dbb1841d-f3f6-4a49-b73f-0a24cc003b1b",
"downloadPath": "/tempcontent/f8deec7c-5ab4-4462-879b-38990febbd1b/Test.qvf?serverNodeId=ae6a7f27-1abd-439e-b4da-0a0b0f4a3e61",...
}
GET https://sense/jwt/tempcontent/f8deec7c-5ab4-4462-879b-38990febbd1b/Test.qvf?serverNodeId=ae6a7f27-1abd-439e-b4da-0a0b0f4a3e61&xrfKey=4B21426C21AE6B85...
Status: 400 Bad Request
400 - Bad Request - Qlik Sense
Error: 400 - Bad Request - Qlik Sense
This is being investigated by Qlik as SUPPORT-3800.
Delete the content of the cookie store ( ~/.qlik/.cookiestore) when the error occurs.
In Windows, this can be found in %USERPROFILE%\.qlik\.cookiestore
A batch job can be created to automate the deletion.
This is caused by an incorrect cookie handling by Qlik-CLI. While exporting the app, the responses include the Set-Cookie header, but qlik-cli fails to update the cookie store with the new cookie.
When passing parameters from postman to a talend services, tRestRequest component is receiving null response.
Review the schema of the tRestRequest component to ensure the Comment field is appropriately assigned.
In REST API Mapping section, by default, if you leave the Comment field empty, the parameter is considered as a Path parameter.
There are some parameters missing/misconfiguring in the Comment field of tRestRequest component and you need to define what type of parameter it is in the Comment field of the schema.
Below is a list of supported Comment values:
empty or path corresponds to the default @PathParam,
query corresponds to @QueryParam,
form corresponds to @FormParam,
header corresponds to @HeaderParam.
matrix corresponds to @MatrixParam.
multipart corresponds to the CXF specific @Multipart, representing the request body. It can be used only with POST and PUT HTTP methods.
https://help.qlik.com/talend/en-US/components/8.0/esb-rest/trestrequest
Question I
Which Apache Tomcat Versions are affected by Apache Tomcat Vulnerability CVE-2025-24813 and the impact?
Apache Tomcat Vulnerability CVE-2025-24813 is Remote Code Execution and/or Information disclosure and/or malicious content added to uploaded files via write enabled Default Servlet
Affected Apache Tomcat version
How Impact
The original implementation of partial PUT used a temporary file based on the user provided file name and path with the path separator replaced by ".".
If all of the following were true, a malicious user was able to view security sensitive files and/or inject content into those files:
If all of the following were true, a malicious user was able to perform remote code execution:
Question II
On which Apache Tomcat versions this Vulnerability is fixed and currently Talend Supported Apache Tomcat versions?
Vulnerability is fixed with the following Apache Tomcat versions
Talend Supported Apache Tomcat Versions
Regarding of Talend Help Documentation: compatible-web-application-servers
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-24813
Apache Tomcat Vulnerabilities
When attempting to build a set of items (jobs, routes, services, etc) from a parent project with a reference project, Maven and the P2 may only see the items in the parent. Additionally, there may be errors of certain items (child jobs, routines, etc) missing during different stages of the build; such as (but not limited to the following):
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project <project_name>: Could not resolve dependencies for project org.example.<project_name>.job:<job_name>:jar:0.1.0: The following artifacts could not be resolved: org.example.<reference_project>.joblet:<joblet_name>:pom:0.1.0 (absent)
When the YAML or Pipeline scripts being used with the orchestrator, Talend CICD may need to be modified, so that the parent and reference projects are checked out and copied into one folder. This process may depend on the orchestrator used (such as Jenkins/Cloudbees, Azure DevOps, Gitlab Actions, etc); for specific information, please check with your DevOps team for specific commands and process.
In short, the process should look similar to the following:
Most YAML or Pipeline scripts are setup to pull and checkout from one repository/branch; however, if a Reference Project is being used, it does require that repository/branch also be pulled down. If the reference project is not copied into the same folder as the parent project, Maven/Talend may only see the parent project checked out without reference project.
A user can enable failure notifications for automations in their profile settings. Reference: Notifications
However, if the user is not the owner of an automation hosted in a shared space, they will not receive the expected notification.
Only the automation owner will be alerted.
This behaviour is different than the one for application reloads, where tenant admins and people with permissions on a shared space can also be notified.
This is a current limitation.
To provide Qlik with input on this limitation and suggest changes, head to Qlik's ideation portal, which our product teams actively monitor.
A user can enable failure notifications for automations in their profile settings. Reference: Notifications
However, despite the automation failing several times, only the original notification of the first failure is delivered.
This is as designed.
Since automations can be run every 30 seconds, we want to avoid spamming the user with notifications. We therefore have a 6-hour window after a failure during which the user will not receive another alert.
Another can be sent after six hours.
Qlik plans to reduce the window from 6 hours to 1 hour. No estimated time for this change is known yet.
Qlik is updating the Qlik Talend Nexus repository. The changes will be rolled out in a phased approach.
The expected impact of Phase One (deployed July 16th) is:
Qlik Talend Studio:
Qlik Talend Administration Center
Multiple options exist:
This article will be updated with additional information as the second phase is announced (estimated time not yet available).
Question
After upgrading Talend Administration Center (TAC) to TPS-5612 (R2024-12) or later, why do the four MetaServlet commands createBranch, branchExist, createTag and deleteBranch not work as before and throw the error like below?
{"error":"Unknown command 'branchExist'","returnCode":2}
With the release of Talend Administration Center patch TPS-5612, project references and Git access have been removed from Talend Administration Center to improve the performance.
The following elements have been removed:
This is documented in the change notes here: https://help.qlik.com/talend/en-US/release-notes/8.0/r2024-12-administration-center
In the Talend Management Console Cloud production environment (Remote Engine v2.13.x), task executions are repeatedly failing with the error:
"Connection reset by peer`at `org.talend.remote.jobserver.client.JobSenderClient.sendJob".
Increase the value of "MAX_ARCHIVES_DIR_SIZE" in RE/etc/org.talend.remote.jobserver.server.cfg to accommodate larger job archives and prevent further upload failures.
For example
Changing the following value from 100G to 300G, up to your requirement
org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ARCHIVES_DIR_SIZE=100G The default is 100 G
org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ARCHIVES_DIR_SIZE=300G
Based on interpretation of RE logs and data, the "Connection reset by peer "error originates from JobLimitException. Specifically, the "MAX_ARCHIVES_DIR_SIZE" limit defined in RE/etc/org.talend.remote.jobserver.server.cfg file has been reached, which causes the job upload request to be rejected on FILE_SERVER_PORT 8004.
The obvious JobLimitException error message looks like:
Caused by: org.talend.remote.jobserver.commons.utils.io.JobLimitException: Current upload of job archive will exceed the allowed size of archive directory of: '107374182400' (configured in org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ARCHIVES_DIR_SIZE)
Since the error "Connection reset by peer "message is not directly indicative of this root cause, it is necessary to search for relevant keywords in RE/data/log to determine whether any of the following job size limits have been exceeded:
* `MAX_JOB_FILE_SIZE`
* `MAX_UNZIPPED_SIZE`
* `MAX_ZIPPED_ENTRIES`
* `MAX_ZIP_NAME_LENGTH`
* `MAX_UNZIPPED_FOLDER_NAME_LENGTH`
* `MAX_UNZIPPED_FILE_NAME_LENGTH`
* `MAX_ZIP_DEPTH`
Talend Studio Can't retrieve any project from Cloud when connects to TMC, a warning appears stating that:
"Can't retrieve any project from Cloud, please ask for help from the administrator."
The user who is connecting to TMC has not been assigned any projects.
Assign this user to projects within TMC. For a detailed process, please refer to this Assigning users to projects documentation.
Qlik Talend Cloud: Unable to connect Talend Studio to Talend Cloud with SSO enabled