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.
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
Testing a connection to Salesforce using the Qlik Salesforce connector fails with the error:
INVALID_LOGIN:Invalid username, password, security token; or user locked out
The Salesforce user login credentials (username, password, or security token) are incorrect.
When the list box is set to collapsed, its title size cannot be changed from the Styling tab. This is currently a product limitation.
An improvement is on Qlik's roadmap: VIZ-241
Updating Custom Properties in the Qlik Sense Hub or changing the script in the Data Load Editor, loading data fails with the error:
The request could not be completed due to a conflict.
The app saves regardless of the error.
Set AppStaticByteSizeUpdate.Enable to false.
By default, the setting AppStaticByteSizeUpdate.Enable in the repository.exe.config file is set to true. To change this:
SUPPORT-4002
Loading data from a QVD with a field containing NaN values will significantly affect the reload performance.
A testing scenario is attached in this article, using the Qlik Sense app app_nan.qvf and the QVD table_with_nan_value.qvd.
Scenario One
Observation Two
This has been investigated as SUPPORT-1818 and has been concluded to work as designed.
$numeric columns will be managed at the assembler level and not at the C++ level. That is correct and optimized since we expect numbers in that column.
When a NaN value appears, the assembler tries to decipher it, which takes time.
To work around this, transform the NaN values to Nulls on the data source side or before storing data in QVDs.
An example workaround can be found in How to change string to null() value (Qlik Community post).
SUPPORT-1818
A Windows authentication pop-up is shown when uploading or deleting files, prompting the user to sign in. Both the Data Manager and Data Load Editor are affected.
This occurs if:
Upgrade to November 2024 Patch 7 or any higher releases.
This is caused by QB-31249. The virtual proxy prefix was missing on requests related to /qrs/appcontent. As a result, a login dialog is displayed when uploading and deleting files. See Sense Enterprise on Windows release notes - November 2024 Initial Release to Patch 15 for details.
Three workarounds are available if an upgrade is not immediately possible.
Remove the Virtual Proxy Prefix
Add non-SSO users
Use a different file upload method
There are other methods to upload files, such as using Folders or other connectors. See Loading files from local and network file folders for an example.
Qlik Sense November 2024 Patch 7 or any higher releases.
Product Defect ID: QB-31249
In Job Conductor, Job log file cleaner is no longer occuring and resulting in files piling up and filling-up filesystem when installing Talend V8 R2025-01, executionLogs and generatedJobs are not cleaned as expected
Apply TAC R2025-04 and later patch to solve this issue.
It is a known jira issue that File cleaner doesn`t work as expected due to regexp matcher to escape file
Jira Issue: QTAC-966
Talend Administration Center is facing LDAP login failure with the error log
ERROR LoginHandler - LDAP user authenticate fail:
org.apache.directory.ldap.client.api.exception.LdapConnectionTimeOutException: MSG_04177_CONNECTION_TIMEOUT (2000)
For LDAP connection timeout, default: 2000 ms issue, please follow below steps to increase ldap.config.timeout value from configuration table in Talend Administration Center DB.
UPDATE `tacdb`.`configuration` SET `value` = '10000' WHERE (`key` = 'ldap.config.timeout'); Unit: "ms"
Potential Causes
How To Grant Users The Access To Data Model Viewer.
With default security rules and settings, users can not see the data model for published apps. However, we can achieve this by creating/updating security rules through the Qlik Sense Management Console.
This requires a rework of the ContentAdmin rule and will provide far more permissions to users than Option 1. See ContentAdmin for details on what a ContentAdmin is allowed to do.
To distribute Qlik Sense applications from on-premise to SaaS, you are trying to create a new deployment through the QMC section "Cloud Distribution"
When clicking on the Deployment setup, you are intermittently receiving an error:
You do not have the privilege to read content
When checking the Hybrid Deployment Service log located in %ProgramData%\Qlik\Sense\Log\HybridDeploymentService\Trace, you see errors when HDS tries to fetch a license from the repository.
397 20220217T094322.646+01:00 INFO qlikserver1 37 domain\SVC_QS "Request starting HTTP/1.1 GET https://localhost:5927/v1/license " 36644
400 20220217T094322.653+01:00 DEBUG qlikserver1 37 domain\SVC_QS Refreshing the license cache 36644
401 20220217T094322.654+01:00 DEBUG qlikserver1 37 domain\SVC_QS Getting a license from repository 36644
402 20220217T094322.670+01:00 WARN qlikserver1 33 domain\SVC_QS Could not get a license, statusCode = "Forbidden", reason = '"Forbidden"' 36644
403 20220217T094322.672+01:00 ERROR qlikserver1 33 domain\SVC_QS Error when getting a license: "Response status code does not indicate success: 403 (Forbidden)." 36644
Qlik Sense Enterprise on Windows
Log in to the server with the account running Qlik Sense services.
Open Internet Explorer and check the proxy configuration in settings > Internet options > connections tab > LAN settings.
Ensure the configuration is set correctly, according to your internal IT requirements.
Wrong proxy configuration set in the service account Windows profile.
QB-9173