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.
Custom QVX connectors stopped working after upgrading to Qlik Sense Enterprise on Windows November 2024.
After selecting Select Data in the Data Load Editor, the Select Data dialog window will display the following message and not proceed:
Please wait – analyzing the selected data
This worked as expected in previous versions of Qlik Sense Enterprise on Windows.
This issue is related to a defect (SUPPORT-998, QCB-30758) reported in Qlik GeoAnalytics Plus November 2024, which was resolved in Qlik Sense November 2024 Patch 6.
See the relevant release notes for details.
QB-30758 | Geo Analytics: After upgrade to Qlik Sense Nov 2024 the GA Plus connection hangs | After upgrading to Qlik Sense November 2024, the Geo Analytics Plus connection would indefinitely show "Please wait - analyzing the selected data". This was due to an issue in the field selection dialog which has been fixed. |
SUPPORT-998, QCB-30758
Qlik Talend Data Integration Data Movement Gateway supports connecting to a DB2i Source Endpoint using SSL. This article documents the step-by-step requirements to set up an ODBC connection to an iSeries with SSL enabled.
For general information about Qlik Data Movement Gateway, see Qlik Data Gateway - Data Movement.
$ cd /opt/qlik/gateway/movement/drivers/bin
$ ./install db2iseries
chmod 755 ibmi.conf
chmod 755 AS400-7CA.txt
[DB400]
Description = SSL-enabled IBM i DSN
Driver = IBM i Access ODBC Driver
#System = as400-7.iSeries.com
System = 127.0.0.1
[root@RHEL8 ~]#sudo stunnel /etc/stunnel/ibmi.conf
[root@RHEL8 ~]# isql -v DB400 IVAN IVAN+---------------------------------------+
SQL> SELECT REMOTE_ADDRESS, REMOTE_PORT, LOCAL_PORT_NAME, LOCAL_PORT, JOB_NAME FROM QSYS2.NETSTAT_INFO Where LOCAL_PORT = 9471
Before you can start using Qlik Sense Desktop, you need to authenticate yourself against a Qlik Sense Enterprise server. You need to have a working network connection to enable authentication.
The following requirements need to be met:
After you have been authenticated once, internet access is not required to continue using Qlik Sense Desktop. However, you have to re-authenticate yourself if thirty days have passed since you last authenticated.
Qlik Sense Desktop
Qlik Cloud
Qlik Sense Enterprise on Windows
Qlik Sense Business
Starting Qlik Sense Desktop | Qlik Sense on Windows Help
Starting Qlik Sense Desktop | Qlik Cloud Help
Configuring Qlik Sense Desktop authentication link
How to authenticate Qlik Sense Desktop against SaaS editions
How to authenticate Qlik Sense Desktop against a Qlik Sense Enterprise on Windows server
Running a Talend Job using a key pair authentication for Snowflake fails with the exception:
Starting job Snowflake_CreateTable at 09:21 19/07/2021. [statistics] connecting to socket on port 3725 [statistics] connected Exception in component tDBConnection_2 (Snowflake_CreateTable) java.lang.RuntimeException: java.io.IOException: Missing Keystore location at edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable.tDBConnection_2Process(Snowflake_CreateTable.java:619) at edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable.runJobInTOS(Snowflake_CreateTable.java:3881) at edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable.main(Snowflake_CreateTable.java:3651) [FATAL] 09:21:38 edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable- tDBConnection_2 java.io.IOException: Missing Keystore location java.lang.RuntimeException: java.io.IOException: Missing Keystore location at edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable.tDBConnection_2Process(Snowflake_CreateTable.java:619) [classes/:?] at edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable.runJobInTOS(Snowflake_CreateTable.java:3881) [classes/:?] at edw_demo.snowflake_createtable_0_1.Snowflake_CreateTable.main(Snowflake_CreateTable.java:3651) [classes/:?]
The Keystore path is not configured correctly at the Job or Studio level before connecting to Snowflake on the metadata and using the same metadata connection in the Jobs.
To use key pair authentication for Snowflake, they Keystone settings must be configured in Talend Studio before connecting to Snowflake.
Perform one of the following options.
Update the appropriate Studio initialization file (Talend-Studio-win-x86_64.ini,Talend-Studio-linux-gtk-x86_64.ini,or Talend-Studio-macosx-cocoa.ini depending on your operating system), with the following settings:
-Djavax.net.ssl.keyStore={yourPathToKeyStore} -Djavax.net.ssl.keyStoreType={PKCS12}/{JKS} -Djavax.net.ssl.keyStorePassword={keyStorePassword}
Update the Keystore configuration in Studio SSL preferences with the required Path, Password, and Keystore Type.
Add the Key Alias to the Snowflake metadata.
Update the tSetKeystore components in your Job, if you plan to run the Job when the target execution is local, Remote Engine, or JobServer (the versions do not matter). Before selecting the Key Pair option for the tSnowflakeConnection component, configure the key pair authentication on the Basic settings tab of the tSetKeystore component:
Select JKS from the TrustStore type pull-down list.
Enter " " in the TrustStore file field.
Clear the TrustStore password field.
Select the Need Client authentication check box.
Enter the path to the Keystore file in double quotation marks in the KeyStore file field.
Enter the Keystore password in the KeyStore password field.
Talend Remote Engine Heart Beat is failing hourly with 'GOAWAY received' error and the karaf.log shows below:
2024-08-01T10:16:58,638 | ERROR | pool-28-thread-1 | JAXRSUtils | 469 - org.apache.cxf.cxf-rt-frontend-jaxrs - 3.6.2 | | Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
2024-08-01T10:16:58,638 | WARN | pool-28-thread-1 | PhaseInterceptorChain | 467 - org.apache.cxf.cxf-core - 3.6.2 | | Interceptor for {http://pairing.rt.ipaas.talend.org/}PairingService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
Caused by: java.io.IOException: /<IP>:<port>: GOAWAY received
This could also be a possible solution when the following error is also showing in the log:
Caused by: java.io.IOException: HTTP/1.1 header parser received no bytes
heartbeat.interval=60 (by default)
with heartbeat.interval=65
org.apache.cxf.transport.http.forceVersion=1.1
Do not set heart interval to more than 180 seconds(3 mins). If Talend Cloud does not receive a heartbeat from the Remote Engine for more than 3 mins, it will show the Remote Engine's status as unavailable.
The connection to the server pair.xx.cloud.talend.com is kept during 60 seconds and Heartbeat.interval > 60 seconds allows to close this connection and prevent "GOAWAY received" error message.
For more information about heartbeat concept and heartbeat interval, please refer to documentation:
Monitoring-remote-engine-health
Internal Jira Case ID: TMC-4122
To disable all current triggers in a QlikView distribution environment, modify the Trigger.xml.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Support has collected a number of resources helpful for the implementation of Qlik Sense Version Control functionality.
Qlik Partner Solutions:
The tFtpGet component is unable to filter and download the necessary file according to the designated filemask. In the FTP UI tool, the file is listed and displayed with uppercase characters. However, when using the same uppercase-based filemask to filter the file, no file is downloaded.
The file was saved in lowercase, but it appears in uppercase when viewed through the FTP client UI. This inconsistency between the saved filename and its displayed version in the UI indicates a case-mismatch issue in the FTP system.
To resolve this issue, adjust the character case in the Filemask settings. Alternatively, enable the "Use Perl5 Regex Expression as Filemask" option to create a new filter that disregards case sensitivity. (This can be achieved by using "/i" in the Perl5 Regex Expression, which enables case-insensitive pattern matching, allowing "A" to match "a".)
Some Qlik Replicate tasks intermittently show a high amount of false latency. Latency may be observed at random times and will then immediately be gone again. Stopping and resuming the task may resolve the issue.
This is often observed when the Qlik Replicate server is out of sync with the time on the source and target endpoint servers.
Resolve the time sync issue.
Time is out of sync between servers.
Your jobs maybe failing in 30s with an error below from Talend Management Console.
org.talend.remote.commons.exception.ClientServerException: TimeOutInterruptor has interrupted the socket stream, timeout has been reached
org.talend.remote.commons.exception.ClientServerException: org.talend.remote.commons.exception.ClientServerException: TimeOutInterruptor has interrupted the socket stream, timeout has been reached
All jobs can be impacted by that and happen at any time.
As this issue is caused by timeout issue during file transferring in Qlik Talend Remote Engine, it can be resolved by excluding the Remote Engine folder from Antivirus Scanning or Firewall. Please double check your Antivirus Software and Windows defender.
Or if above solution does not help, please try to increase the timeout value by following below steps:
cd <RE_FOLDER>\system\org\talend\jobserver\org.talend.remote.jobserver.client\8.0.x.yyyymmdd_xxxx_patch
jar xvf org.talend.remote.jobserver.client-8.0.2.20240904_0703_patch.jar job_server_client.properties
inflated: job_server_client.properties
JobServerClient.conf.timeout=300000 -→ increase this to the time desired in milliseconds.
jar uf org.talend.remote.jobserver.client-8.0.2.20240904_0703_patch.jar
job_server_client.properties
From Karaf logs, the issue occurs due to timeout issue during file transferring in Talend Remote Engine, where the default timeout is set to 30 seconds in the existing system.properties
The socket related errors in context of ClientServerException + TimeOutInterruptor indicate there is a networking related congestion that prevents opening socket connections, which could also hint to an exhaustion of the network.
Internal Jira ID: TMC-1915
Creating a tenant in a specific region using either Automation or the available API fails.
The API call returns:
"Forbidden" error (status 403)
The Automation block for Application Automation - Platform operations → Create Tenant is restricted to a different region.
Create a region-level OAuth client for the specific region. For instructions, see Create a region level M2M OAuth2 client.
It is necessary to have a dedicated OAuth client for each region.
Saving an edited task in Qlik Cloud may lead to the error:
Unable to save task
Analyzing the issue with the browser's developer tools, we see that the error 500 Internal Server Error is returned. For tips on how to use developer tools, see Save network web traffic (HAR/XML file) and console logs from the browser's developer tools.
To resolve the issue, we remove the connection to the corrupt cron job, then set the task to its correct schedule:
There was a problem with the task's cron job in Qlik Cloud.
This article outlines the steps for CICD P2 zero install for pipeline using Maven and provides command examples.
mvn org.talend.ci:builder-maven-plugin:8.0.19:install -Dtalend.studio.p2.update= https://update.talend.com/Studio/8/updates/R2024-12 -Dlicense.path='/home/use1/cicd/license8 -s C:\app\apache-maven-3.9.0\conf\maven_settings.xml
mvn org.talend.ci:builder-maven-plugin:8.0.18:generateAllPoms -Dtalend.studio.p2.update='https://update.talend.com/Studio/8/updates/R2024-12' -Dfilter.include.dependencies=true -Dgeneration.type=local -e -X -s /home/wguo/cicd/maven_settings.xml -Dcodes.compile.failOnError=false -Dlicense.path='/home/use1/cicd/license8' -Dinstall.org.eclipse.equinox.p2.transport.ecf.retry=10 -Dstudio.error.on.component.missing=false
mvn -X clean deploy -U -f /home/user1/ws/project1/poms/pom.xml -Dlicense.path='/home/use1/cicd/license8' -Dtalend.studio.p2.update= https://update.talend.com/Studio/8/updates/R2024-12 -Dpackaging=zip -Dgeneration.type=local -Dinstall.org.eclipse.equinox.p2.transport.ecf.retry=10 -s /home/wguo/cicd/maven_settings.xml -DaltDeploymentRepository=dmt-releases::default:: http://s.ap.abc.net:8081/repository/dmt-releases/ -DaltSnapshotDeploymentRepository=dmt-snapshots::default:: http://s.ap.abc.net:8081/repository/dmt-snapshots/ -DaltReleaseDeploymentRepository=dmt-releases::default:: http://s.abc.net:8081/repository/dmt-releases/
For Windows-based CICD host machines, use the --define "xxx=yyy" option instead of -Dxxx=yyy to circumvent parameter passing failures.
Additionally, you can filter and specify which project items to generate in order to make the POM generation faster. For further details, please refer to Filtering project items | Talend Software Development Life Cycle Best Practices Guide Help.
In Qlik Sense, when there is a commented out portion of the script, if "//" is deleted and the script is saved, all the text will turn black and all syntax highlighting will be lost. If pages of the script are toggled between, a message that says "we have disabled syntax highlight to maintain performance" appears and the highlighting will come back but if previous steps are followed again,commenting will also be disabled again.
This is working as designed.
It is the current solution for dealing with deeply nested if statements. In many cases these deeply nested if blocks will cause real performance issues (crashing the browser). The best practice is to not use nested ifs when possible. The commenting/uncommenting works because we count the levels. Pretty sure 10 levels deep we trigger the perf warning. So if they comment out one and it's only 9 it won't complain.
Qlik Answers is Qlik's personalized AI assistant that generates on-point answers from your own trusted business content. See this article to learn how to get started with Qlik Answers
This connector unlocks new powerful use cases like indexing new data ad-hoc and taking your action oriented automations to the next level by including unstructured insights. This article explains how the Qlik Answers connector in Qlik Application Automation can be used.
Article contents
This connector does not require additional configuration to authenticate, it will automatically connect to the automation owner's Qlik account. Whenever blocks of this connector are executed, they will use that account.
For this connector's first release, we will introduce blocks that can re-index knowledge bases and ask questions to an assistant. We will deliver more blocks in future releases, do not hesitate to request new blocks through Ideation.
This use case focuses on ad-hoc updates to the knowledge base. The creation and initial configuration of a knowledge base should happen through the Qlik Answers UI as described here:
Once your knowledge base is configured and you've set up a data connection to a cloud storage location, you can then use Qlik Application Automation to add specific files to the Cloud Storage location and trigger a re-indexing. This could be useful in scenarios when you only want to index specific records that might depend on a context.
For this use case, you can use the blocks Add Data Source To A Knowledge Base and Sync Knowledge Base Data Source. The below example will fetch incidents from ServiceNow, store them in a Dropbox folder and then add the Dropbox folder as a data source to a Knowledge Base in Qlik Answers. After this, the data source will be synced to the knowledge base index.
By using the blocks Create Thread and Execute Synchronous Prompt, you can ask questions from an assistant to enrich other messages that are sent through automations with unstructured insights. In the below example, these blocks are added to the existing "Notify your team on Microsoft Teams based on a measure" template that can be found in the template picker:
Don't ask a question immediately after indexing. Asking a question should be done after the knowledge base has completed indexing successfully.
Environment
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.
After applying the Oracle July 2024 patch, the following error will be seen when working with compressed tables:
[ASSERTION ]W: A compressed row cannot be parsed for table (oradcdc_parse.c:2640)
The error leads to missing records.
Only Oracle instances with compressed tables are affected.
R&D addressed the compression warning and also another missing insert events.
Before rolling out the fix in production, always first test in UAT or other pre-release environments.
If you are uncertain whether or not you are using compressed tables, run the following query:
select owner, table_name, COMPRESSION,COMPRESS_FOR from dba_tables where compression='ENABLED'
Oracle July 2024 Patch with compressed tables.
RECOB-8914 by Qlik.
The QlikSenseUtil comes bundled with Qlik Sense Enterprise on Windows. It's executable is by default stored in:
%Program Files%\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
Qlik Sense Util is no longer supported as a backup and restore tool. For the officially supported backup and Restore Process, see Backup and Restore.
If an issue occurs with the existing Data Gateway and only the Gateway of the source connection is changed, the following error will be thrown when the task is resumed:
Failed to send proxy request
REPLICATE-AGENT-SERVICE-22: Gateway coordinates are modified. The source connection was changed to use a different gateway resource, and therefore your data asset cannot continue running. You can either revert the connection to the previous gateway resource or recreate the data asset.
Stop the task, run a prepare, then resume the task.
The data asset has been modified and cannot continue running on a different gateway.
The problem occurs when applying a valid SLK to QlikView. When clicking Apply License, the following error is shown:
Error when applying license: Post "https://license.qlikcloud.com/v1/definitions/signed": net/http: invalid header field value for "Authorization"
This error occurs when the license code is copied with line break characters. Those are considered as part of the license, invalidating the code.
To resolve the problem, copy the license code in a text file editor and manually remove the line break characters. Then copy the correctly formatted string to activate the license.
When removing the line breaks, verify that no other characters are deleted.
Example of an incorrectly and correctly formatted key:
Qlik Replicate offers a powerful logging feature when its level is set to "Trace" or "Verbose". Instead of directly writing to log files, detailed information is first stored in memory. This is particularly useful for troubleshooting unpredictable errors.
In case of a problem, Qlik Replicate captures the complete picture by writing the in-memory log to disk, including events leading up to and following the error. This strategy proves effective when dealing with issues that lack obvious causes, allowing for deeper analysis and faster resolution.
This article provides step-by-step instructions for Storing trace and verbose logging in memory.