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.
A talend job did run fine in the past two years, however, recently it was running slowly for several hours and freezes occasionally.
The job does not have much complicated sunjobs and it reads a file row by row, and for each row, checks the record type and sends the row to one of two possible output files.
When trying to process a file with less than 30.000 lines, It loads about 1000 lines and then seems to freeze for several minutes, then loads another batch of lines, and so on. This issue doesn't reproduce on a newly created job (Duplicated one)
After made an investigation on thread dump, the real time statistics was blocking the job and the problem seems to be appearing from the Statistics Monitor. It is suggested disable stats and logs both from Studio and Talend Administration Center sides using the below steps and re-run the job.
Studio Side
Disable Stats and Logs for Job level
Studio--> Designer -->Job-->Stats&Logs--> Disable the below check boxes.
We already have a global option in Studio >Preference>Talend>Run/Debug for Project Level
Talend Administration Center side
Job Conductor page--> Statistics-->disabled
Job won't open Socket and send message to Studio/Job Server when Statistics is disable and no matter disable it on job or project level, need to re-deploy jobs to Job server.
Checked the Thread dump and identified the below blocked threads:
org.talend.administrator.statistics.business.RealtimeTaskLoader->ExecStatisticsMonitor
The blocked threads indicate the problem occurs while retrieving the statistics and logs and the space and performance for this job is getting less and slower after it has been working for a while.
When a user is deleted, any spaces, apps, scripts, and data connections they own will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Source: Reassigning ownership of spaces and resources (Qlik Cloud Documentation)
But even if the app is considered an Orphaned App, the owner can be changed in the Qlik Cloud Analytics Administration Console:
Security issues in Qlik Sense Enterprise for Windows have been identified, and patches have been made available. If the vulnerabilities are successfully exploited, these issues could lead to a compromise of the server running the Qlik Sense software, including unauthenticated remote code execution (RCE).
This issue was discovered by Qlik during internal security testing and no reports of it being maliciously exploited have been received.
All versions of Qlik Sense Enterprise for Windows prior to and including these releases are impacted:
Using the CVSS V3.1 scoring system (https://nvd.nist.gov/vuln-metrics/cvss), these issues are rated HIGH.
(CVE-pending) QB-29918, QB-29750 Remote Code Execution (RCE) via Connectors
Severity: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H 8.8 (High)
Unprivileged users with network access may be able to create connection objects that trigger the execution of arbitrary EXE files on Qlik Sense Enterprise for Windows.
(CVE-pending) QB-29586, QB-29864, QB-29482, QB-29802 - Broken Access Control (BAC)
Severity: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H 7.5 (High)
Unprivileged users with network access to Qlik Sense for Windows installation may be able to execute remote commands that could cause high availability damages, including high integrity and confidentiality risks.
Customers should upgrade Qlik Sense Enterprise for Windows to a version containing fixes for these issues. Fixes are available for the following versions:
All Qlik software can be downloaded from our official Qlik Download page (customer login required).
Question
What changes are made to the seat allocation after a license renewal?
If the number of seats or users will decrease after a license renewal, the admin user will receive an email that asks to de-allocate the exceeding seats within 14 days, and a reminder 7 days after.
At the end of the 14 days, the seats will be de-allocated automatically starting from the least recent accesses.
All of this info is included in the email received by the admin user.
You can find further details on these seats allocation in tmc-account-license-info
Including details on what's considered admin seat within Talend Management Console.
When using Kafka as a target in a Qlik Replicate task, the "Control Table" name in target is created in lower case, for example the Apply Exception topic name is "attrep_apply_exceptions" (if auto.create.topics.enable=true is set in Kafka broker config/server.properties file), This is the default behavior.
In some scenarios, you may want to use the non-default topic name or topic name in upper case etc to match the organization naming standards rule. This article describes how to rename control table topics' name.
In this article, we will use the topic name "attrep_apply_exceptions" as an example. You can customize below control topics using the same process:
The same way works for more generic level , not only for Kafka target endpoint. In generic level we may rename other metadata eg "target_schema" too.
Kafka topic names cannot exceed 255 characters (249 from Kafka 0.10) and can only contain the following characters:a-z|A-Z|0-9|. (dot)|_(underscore)|-(minus)
More detailed information can be found at Limitations and considerations.
The safest topic name length is 209 (rather than 255/249).
Qlik Replicate (versions 2022.11, 2023.5 and above)
Kafka target
case #00010983, #00108779
Generate a record to attrep_apply_exceptions topic for Kafka endpoint
With the new inclusion of the Get Chart Image block in the Qlik Reporting connector in Qlik Application Automation, you now have more options to notify a group of users with more in-depth data and charts using Slack, Microsoft Teams, and email.
This article will guide you in sending your first chart image to Slack with Qlik Application Automation.
It explains a basic example of a template configured in Qlik Application Automation for this scenario.
You can make use of the template which is available in the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send a Chart Image to Slack' or 'Embed a chart image in an email' in the search bar, and clicking the Use template option.
For guidance on sending charts via Microsoft Teams and mail, go to the "Next Steps" section at the end of this article.
You can download examples of the automations from this article: Send-chart-image-to-slack.json, Send-chart-image-to-outlook.json, Send-chart-image-to-mail.json, Send-chart-image-to-microsoft-teams.json
Warning: Whenever the “Get Chart Image” block is to be used, we advise you to only use it with temporary bookmarks or pre-existing persistent bookmarks.
If the condition block outcome evaluates to false:
Gmail does not support embedding base64 encoded images due to security constraints. To work around this, we advise sending the chart image as an attachment through the Send Mail block in the Mail connector if you use a Gmail account.
See Gmail blocking small embedded inline images in email template for details on the restriction.
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
This article explains how to simply set up JWT authentication using Qlik Sense default certificates and test it.
Click here for Video Transcript
In order to integrate your solution with Qlik Sense using JWT authentication, you will need to pass in your code the JWT token in the authorization token for the first request to Qlik Sense so that a session is created.
It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:
{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false
Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.
This problem occurs when the Mail.Send permission has not been configured in the app registration.
More information about the Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).
The Replicate Connect Service does not start, leading to the Qlik Replicate IMS source endpoint failing to pull data from IMS.
Verify what program is blocking irpcd.exe executable from launching, such as an anti-virus or threat protection program and enable an exception for irpcd.exe.
The irpcd.exe executable is quarantined by an anti-virus or similar threat protection program and cannot be started.
Upgrading Qlik Data Transfer fails with the following error in the installation logs:
Something went wrong while upgrading Qlik DataTransfer. The following error appears in the log file: 0x80070570 = ERROR_FILE _CORRUPT
If the installation still fails:
0x80070570 = ERROR_FILE _CORRUPT indicates a damaged or otherwise corrupt installation file. This can be caused by the file itself being damaged or an underlying issue with the file system.
Question I
Will the method to upgrade to Java 17 be the same as: upgrading-java-for-talend-remote-engine when a Remote Engine is already installed (from lower version like 8 or 11)?
The method is not the same for Java 17. Starting from Remote Engine version 2.13, it requires Java 17.
The document is only valid for Remote Engine versions 2.12 or lower.
From Remote Engine versions 2.13 and up, it will be required to re-install the Remote Engine.
Question II
Will the method of setting up Java 17 in Talend Studio remain the same as: setting-compiler-compliance-level ?
The answer is YES .
Question III
How will Camel components in route be used?
It is a matter of dependency management. Once Studio will be upgraded to 8.0.1-R2025-02 (Java 17/Camel 4), any newly created routes or existing routes will depend on Camel 4 so
appropriate libraries will be used at build/run time (either installed in Studio with update, or downloaded).
It is the same for all route components. It will be pretty transparent for the final user.
Question IV
Where is Camel 4 bundled?
Camel 4 libraries are either installed in Studio, or downloaded. OSGi features for Camel 4 are also pre-installed in Talend Runtime.
Either users deploy routes as Microservices and Camel 4 dependencies are packaged in fat Jar at build time or users deploy in Talend Runtime and the container (which new version will be delivered in Feb. 2025) includes all pre-installed Camel 4 features.
Additionally, the Remote Engine has nothing to do with Camel 4.
If you are looking for more information about Java 17 Migration Guide, please refer to this KB article
Qlik-Talend-Products-Java-17-Migration-Guide
Route(OSGI-based) service design facing child Job bundle jar (child bundle was introduced by cTalendJob in Route design), encounters the error "Unable to resolve root : missing requirement" after being deployed to Runtime. However, Route runs smoothly in Studio debug run mode.
The Runtime logs provide insightful error messages as detailed below:
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=TestBasicRoute-feature; type=karaf.feature; version="[0.1.0,0.1.0]"; filter:="(&(osgi.identity=TestBasicRoute-feature)(type=karaf.feature)(version>=0.1.0)(version<=0.1.0))" [caused by: Unable to resolve TestBasicRoute-feature/0.1.0: missing requirement [TestBasicRoute-feature/0.1.0] osgi.identity; osgi.identity=org.example.route.TestBasic; type=osgi.bundle; version="[0.1.0,0.1.0]"; resolution:=mandatory [caused by: Unable to resolve org.example.route.TestBasic/0.1.0: missing requirement [org.example.route.TestBasic/0.1.0] osgi.wiring.package; filter:="(osgi.wiring.package=@BundleConfigImportPackage@)"]]
at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.400.jar:?]
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve TestBasicRoute-feature/0.1.0: missing requirement [TestBasicRoute-feature/0.1.0] osgi.identity; osgi.identity=org.example.route.TestBasic; type=osgi.bundle; version="[0.1.0,0.1.0]"; resolution:=mandatory [caused by: Unable to resolve org.example.route.TestBasic/0.1.0: missing requirement [org.example.route.TestBasic/0.1.0] osgi.wiring.package; filter:="(osgi.wiring.package=@BundleConfigImportPackage@)"]
at org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341) ~[org.eclipse.osgi-3.18.400.jar:?]
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve org.example.route.TestBasic/0.1.0: missing requirement
The child bundle JAR is lacking the 'lib' and 'osgi-info' folders. Additionally, the custom Maven files ('pom.xml', 'pom-parent.xml', 'pom-bundle.xml', and 'pom-feature.xml') are outdated, which contravenes the Studio's default dependency settings during the compilation and packaging processes.
Updating an Excel Worksheet using Qlik Application Automation leads to Microsoft Excel reporting a 503 error.
A 503 (Service not Available) error indicates the target system, in this case Microsoft Excel, cannot handle the calls due to high frequency. To overcome this, a retry mechanism would need to be implemented in your automation, adding robustness in front of those errors.
Attached to this article is a sample automation demonstrating how to handle these errors in the Excel block and implement retry logic when it fails.
Third-party bottleneck.
TAC tasks are hanging on "Running" status for a long time in Job Server, and it does not end.
Analysis
This issue can be identified by long duration of task execution time and it can be seen from the large time gap between the job end time and the task end time.
Usually, the time gap between the job end time and the task end time are small if there are no problems occurring.
Please check and try the following points.
It is most likely that there are network connection issues (because of network infrastructure, VPN, etc)between the Talend Administration Center and the execution server (Job Server).
One possible situation may be the following: After the task is run by the Job Server, the execution result should be sent to the Talend Administration Center normally. If there is a connectivity problem between the Talend Administration Center and the Job Server, then the execution result will not be sent to the Talend Administration Center, which causes this problem.
You can access Qlik Sense demo apps from https://demos.qlik.com/.
If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.
If you are looking to download demo apps:
After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed.
The Qlik Sense System_Repository log file will read:
"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes."
Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt
This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.
The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.
Take a backup of your environment before proceeding.
If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article.
Show base memory size of apps in QMC
QB-22795
QB-24301
Qlik Sense Enterprise on Windows May 2023, August 2023, November 2023, February 2024.
When using Qlik Sense behind a reverse proxy, environment.user.ip is always the IP of the reverse proxy instead of the end user client.
Environments:
This is a product limitation.
A feature request (SHEND-225) has been logged but there is no information if and when the feature will be implemented yet.
Unable to Execute Talend job query after Talend Remote Engine and JAVA version 17 upgrade in PROD.
The Same query was running fine before on Java 11 version but after Java upgrade to 17, it is unable to run the particular query and same jobs are failing due to below error
The original query inside hive tDBInput component has no grammar issue.
Execution failed with code 1 and error Job stopped with errors or unable to run. Exception in component tDBInput_4 (Outbound_File_Creation_Type_1) org.talend.sdk.component.api.exception.ComponentException: (java.sql.SQLException) [Amazon][HiveJDBCDriver](500051) ERROR processing query/statement. Error Code: 40000, SQL state: TStatus(statusCode:ERROR_STATUS, infoMessages:[*org.apache.hive.service.cli.HiveSQLException:Error while compiling statement: FAILED: ParseException line 1:3328 missing EOF at 'JOIN' near ')':17:16, org.apache.hive.service.cli.operation.Operation:toSQLException:Operation.java:335, org.apache.hadoop.hive.ql.reexec.ReExecDriver:compileAndRespond:ReExecDriver.java:126,
Try the setting "UseNativeQuery=1" in JDBC connection URL property to enable the use of Native query option.
For example:
jdbc:hive2://localhost:10000/foundation;AuthMech=2;UseNativeQuery=1
This parameter specifies whether the driver transforms the queries emitted by applications.
1: The driver does not transform the queries emitted by applications, so the native query is used.
0: The driver transforms the queries emitted by applications and converts them into an equivalent form in HiveQL.
If the application is Hive-aware and already emits HiveQL, then enable this option to avoid the extra overhead of query transformation.
As HiveQL is using parameter "UseNativeQuery=0" by default, which means it will transform query inside JDBC before sending to HS2 , and the introduced false optimization query will cause the problem.
Qlik Replicate tasks using DB2 LUW Source Endpoint experience latency when consuming data.
Verify if the DB2 LUW configuration for the DB2 instance of the Source endpoint has its configuration parameters LOGMETHOD1 and LOGMETHOD2 set to a backup device location.
This would indicate the DB2 Log Reader Agent is loading the transaction logs from a backup device which will add overhead to the task using this DB2 Source Endpoint.
To correct the condition you can set the DB2 parameter by the DBA Overflow Log path from NULL to archive_log_path. See overflowlogpath - Overflow log path configuration parameter for more information.
This path can point to a local disk on the DB2 server for optimal access to the DB2 transaction logs.
First log archive method:
(LOGARCHMETH1) = VENDOR:/opt/simpana/Base64/libDb2Sbt.so
Second log archive method:
(LOGARCHMETH2) = DISK:/db2/P10/alternate_logpath/
Overflow log path:
(OVERFLOWLOGPATH) = archive_log_path
This is the result of the DB2 Log Reader Agent, which Qlik Replicate calls using the DB2 API and from which we access the transaction logs from DB2. In a setup in which LOGMETHOD1 is pointing to a backup device, the DB2 Log Reader Agent loading the transaction logs will lead to overhead and ultimately latency.