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.
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.
When Qlik Data Gateway Direct Access is implemented, sometimes as the workload increases post-implementation, customers may experience general stability issues. We suggest a basic health check to address the more well-known problems and stabilize your gateway implementation.
This article outlines three
A high number of disconnects can cause reload disruptions. Some important disconnects will be recorded in the DirectAccessAgent logs. While a low volume of disconnects is expected and will typically recover within a few seconds, a high number of entries in the logs are indicative of a problem.
We suggest initiating an internal investigation if more than ten disconnects are found per day.
Search for “[ERROR] Connection to”, sample:
[Service ] [ERROR] Connection to <mytenant>.us.qlikcloud.com:443 failed
If the amount of disconnections is high, we suggest to refer to articles:
ODBC connector crashes can impact concurrent reloads if Process Isolation is not enabled. We suggest customers who experience crashes in their logs enable Process Isolation and configure Dump file creation.
Process isolation for ODBC connector can be confirmed in the C:\ProgramData\Qlik\Gateway\configuration.properties. ODBC_PROCESS_ISOLATION_MODE, will be set to None if disabled, and set to Load if enabled.
It can also be verified using the logs. The ODBC logs named odbc-connector_logs.txt, odbc-connector_logs.txt.1 from 1 to n. If isolation is enabled, the files includes a port number, for example odbc-connector_logs_49156.txt where 49156 would represent a port number.
To identify whether there are crashes or not in your DAG (Direct Access Gateway) and proceed to enable Process Isolation we suggest reviewing Qlik Data Gateway - Direct Access - ODBC Crashes.
Other cause of issues would be due to misconfiguration of third-party drivers, the details are outlined in Qlik Data Gateway Direct Access Data Preview long metadata requests.
Keep in mind that these recommendations are additional validations to the Best Practices and System Prerequisites documented in our Help Site:
Best Practices and System Requirements may not have been fully met.
Advanced options is not visible when editing a sheet. This can happen on a specific app even if the option was present before.
You can activate the "Show Sheet Header" option in the app settings to make the "Advanced option" button visible again.
For some reasons, the "Show Sheet Header" could be deactivated in an app. "Advanced Options" is invisible when this happens, because it is located in the sheet header that is removed. The app looks like this in editing mode:
This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.
If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.
Content
This document covers the following scenario:
Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.
These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8).
No further steps are required.
If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version
Changing the Database Superuser Password without Qlik Sense Installed
It is common to override Talend Studio jars with external/new jars, as demonstrated in the documentation page titled "Customizing the Maven URI for External Module Deployment".
However when trying to override a jar with another jar that is already installed in Studio, you will get in the error below. In the example below, the goal is to replace all references to Snowflake JDBC 3.13.30 with Snowflake 3.13.29. Both drivers are already installed in Studio/exist in the .m2 folder.
To get to the window above, navigate to Window | Show View in Talend Studio and choose Modules:
Open the Module view in the bottom, click on the Maven URI/component you want to customize and click the "..." button.
To point all references of Snowflake JDBC from version 3.13.30 to 3.13.29, remove the value of the Module File, check the Custom MVN URI, and enter the path of the existing module into the URI field. Below is an example that demonstrates the addition of the complete maven path for the Snowflake 3.13.29 driver.
NOTE: This change will affect all components that reference the jar. In the example below, 11 components utilize Snowflake JDBC 3.13.30. If you confirm the aforementioned selection, all 11 components will switch to using JDBC 3.13.29. It is not possible to selectively update specific components that rely on 3.13.30 to use 3.13.29, all 11 references will change.
Once you click the "OK" button, all references will change. As demonstrated below, all modules that were previously pointing to 3.13.30.jar will now use the Maven URI for 3.13.29.jar.
If the module needs to be reverted, simply return to the same window and uncheck "Custom Maven URI".
You are experiencing with the following error when connecting to Talend Administration Center
org.talend.administrator.common.exception.DBException: The database "{database URL}" is currently unreachable
Investigating for problems that makes the TAC application not connect to the database properly.
Please check the following points:
When the error occurs, it means that there is a problem in the connection between TAC application and the database.
After merging feature branches into the main branch in Talend Studio, several Jobs are not displayed correctly. Some Jobs are missing, while others contain incorrect files. Additionally, when importing Jobs with the same ID into Talend Studio, the following error message is displayed.
The 2 following items have the same ID, please unselect one of them:
Upon comparing the properties files of two Jobs, it was discovered that both Jobs contain the same ID. Talend Studio is unable to import Jobs with the same ID.
Please do not attempt to manually change the ID as it may lead to other dependency issues. Instead, follow the steps below to import these two Jobs that have the same ID.
Are you looking to download your purchased Qlik Products or download a Trial? All supported on-premise Qlik Products can be downloaded from Qlik's Product Download Site.
To access the Download Site, you need an active QlikID. You will be able to see all products your account is eligible for.
You can access the Download Page directly here, or navigate to it from the Community Home page:
This shows the download page with the Latest release and patch preselected.
Unsupported versions are not available for download. See Product Lifecycle for details on what versions have reached end of support.
Alternatively, instead of selecting your product directly, you can also search all available columns:
If you encounter issues with the download site, start a chat with us and we will be able to help you right away.
Click here for video transcript
When an ODBC connector crash occurs in Qlik Data Gateway — Direct Access, other concurrent reloads may be impacted following the original crash. This will specifically be the case if Process Isolation is not enabled.
To verify if there are ODBC connector crashes:
Multiple connector crashes can have a big impact on the stability of the Direct Access Gateway.
Enable Process Isolation as documented in Mitigating connector crashes during reload.
Some crashes can occur due to malformed queries, refer to the
If there are other crashes without traces that could explain their nature, enable dump file creation, collect the dump files and necessary information for DAG cases and contact Qlik Support.
When embedding a sheet in an iFrame, the "full screen" toggle button for Qlik Sense native chart objects is missing. This feature is present at the sheet level in the hub
Full Screen toggle button is available at the sheet level in the hub
The same feature is missing, once a sheet is added in an iFrame (Single Configurator)
This is a known limitation.
An improvement task has been created (Jira task VIZ-103) and an idea is available on our Ideation Platform.
To check the current status or to add your vote, head over to the idea: full screen for iframe and embed
QB-4967
VIZ-103
When publishing a Job from Talend Studio, configured with a Nexus Artifact Repository, the following error is shown:
java.io.IOException: org.eclipse.aether.deployment.DeploymentException: Failed to deploy artifacts: Could not transfer artifact xxxx from/to xxxx (xxxx): transfer failed for xxxx, status: 503 Repository offline
Please check your Talend Artifact Repository and set the status to online.
The Status of 503 Repository offline means that the Talend artifact repository is offline.