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.
This article provides a guide on how to configure a Qlik Sense Enterprise on Windows Virtual Proxy with OIDC authentication.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
QlikView QVD files contain lineage information of the stored data.
QlikView any version
The lineage information can be found in the QVD file XML header and might look like below, with connection details and the SQL statements used during reload.
How to decrypt a heavily encoded SAML message.
If you have set up the Identity Provider to encrypt the SAML assertion, then in order to see what it contains for troubleshooting, you will need to decrypt it.
Qlik Sense Enterprise on Windows , all versions
It is important to understand the 3 below concepts when using SAML.
A SAML AuthnRequest is:
A SAML assertion (The assertion is a section in the SAML response) is:
* It must be the private key in clear text, not protected by a passphrase. A protected private key will begin with -----BEGIN ENCRYPTED PRIVATE KEY----- while a clear text private key will begin with -----BEGIN RSA PRIVATE KEY----- In order to decrypt a private key, you can use the command: openssl rsa –in enc.key -out dec.key You will be asked to enter the passphrase for your private key. Please note that openssl must be installed and you should run this command from the command prompt in the folder where the binary for openssl is installed. |
Scheduled tasks will fail in Qlik Sense, if the App contains Section Access while could be working fine from the script editor.
Investigating the log file <Servername>_System_Engine.txt shows a warning message similar to:
WARN domain System.Engine.Engine 89 6ac41964-2910-4a17-9162-c40119b2d3d6 domain\qliksense System: DetermineAccess: Failed to access the following document af18ffcb-6b60-4546-9fa5-f385172eebec with the user: 0 sa_scheduler 20181126T181325.903+0100 6864 7120 eaa1c5c2-1850-40cb-a490-0e6158df82b0 af18ffcb-6b60-4546-9fa5-f385172eebec 20181126T181055.000+0100 6ac41964-2910-4a17-9162-c40119b2d3d6
On the script log you will see:
Execution Failed
Execution finished.
Qlik Sense Enterprise on Windows governs access to resources (such as Apps) through the Repository Service. An account for each service is created in the PostgreSQL database during setup, such as the sa_scheduler account above. For the Scheduler to be able to access the App during reload, this account must be added into Section Access, not the account running the actual service.
See also the help documentation:
"The INTERNAL\SA_SCHEDULER account user is required to enable reload of the script in a Qlik Management Console task." Managing security with section access
The following requirements must be met:
Section Access; LOAD * INLINE [ ACCESS, USERID ADMIN, INTERNAL\SA_SCHEDULER ];
Qlik Talend Cloud establishing a connection to SAP using the Extractor Endpoint fails with:
Status(StatusCode="Internal", Detail="SYS-E-HTTPFAIL, Failed to load dynamic endpoint properties. SYS,GENERAL_EXCEPTION,Failed to load dynamic endpoint properties,Failed to find endpoint type 'SAPExtractor' from endpoint server 'Local' Failed to find endpoint type 'SAPExtractor' from endpoint server 'Local' XXXX, HTTP request failed, Failed to connect using Data Movement gateway local_repsrv. Verify the status in Management Console > Data gateways is "Connected" and then retry the operation.").
systemctl stop repagent
sudo su
systemctl start repagent
systemctl status repagent
repagent.service - Qlik Data Gateway - Data Movement
Loaded: loaded (/etc/systemd/system/repagent.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2025-03-25 14:18:57 GMT; 11min ago
Process: 176787 ExecStop=/opt/qlik/gateway/movement/bin/repagent stop (code=exited, status=0/SUCCESS)
Process: 176944 ExecStart=/opt/qlik/gateway/movement/bin/repagent start (code=exited, status=0/SUCCESS)
Main PID: 177014 (agentctl)
Tasks: 0 (limit: 49025)
Memory: 28.0K
CGroup: /system.slice/repagent.service
‣ 177014 /opt/qlik/gateway/movement/bin/agentctl -d /opt/qlik/gateway/movement/data service host -b
Mar 25 14:18:53 RHEL8.domain.local systemd[1]: Starting Qlik Data Gateway - Data Movement...
Mar 25 14:18:53 RHEL8.domain.local su[176967]: (to qlik) root on none
Mar 25 14:18:53 RHEL8.domain.local su[176967]: pam_unix(su-l:session): session opened for user qlik by (uid=0)
Mar 25 14:18:57 RHEL8.domain.local su[176967]: pam_unix(su-l:session): session closed for user qlik
Mar 25 14:18:57 RHEL8.domain.local systemd[1]: Started Qlik Data Gateway - Data Movement.
Missing Sapjco3.jar and libsapjco3.so files in the /opt/qlik/gateway/movement/endpoint_srv/endpoints/SAP directory.
CC-16456
Creating ODBC or OLE DB connections in the Data Manager fails while using Qlik Sense Enterprise on Windows November 2024.
The DSN list is not shown:
The connection screen loops with a spinning progression wheel:
This is caused by SUPPORT-1177 and SUPPORT-1180, which have been fixed in Patch 9 (release expectation: May 2025). Review the Release Notes for details at patch publication.
Use the Data Load Editor to create a new ODBC or OLE DB connections.
Product Defect ID(s): SUPPORT-1177, SUPPORT-1180
Do Qlik Products support the use of Standalone Managed Service Accounts (GMSA)?
At this time, QlikView, Qlik Sense Enterprise on Windows, and Qlik NPrinting do not support the use of managed service accounts.
For general service account requirements, see:
QlikView Service Account Requirements
Qlik Sense Sevice Account Requirements
Qlik NPrinting user account requirements
Qlik Sense Enterprise on Windows
Qlik NPrinting
QlikView
A security issue in a version of Qlik Alerting Windows has been identified. This issue was resolved in a later patch, which is already available. If the vulnerability is successfully exploited, it could lead to unauthorized access to the Qlik Alerting application.
Qlik Alerting Windows July 2023 Service Release 1
Using the CVSS V3.1 scoring system (https://nvd.nist.gov/vuln-metrics/cvss), this issue is rated CRITICAL.
CVE-Pending (QB-24808) Authentication bypass
Severity: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8 Critical)
An unprivileged user with network access to the Qlik Alerting Server is able to bypass basic authentication.
Customers should upgrade to Qlik Alerting July 2023 Service Release 2 or higher.
All Qlik software can be downloaded from our official Qlik Download page (customer login required).
Open Qlik Office 365 SharePoint connector and select "Can Authenticate" and the press the green button "Authenticate"
You will be redirected to a Microsoft login page that should look similar to the following picture:
If azure grants access, the Qlik Webconnector application will generate a code as the following one:
Testing (With NON administrator rights)
If a basic (Non admin) user tries to auth the following message would appear in azure:
In order to fix this the administrator needs to grant access to the users.
Once the administrator granted access to the user the message that should appear is the following one:
When attempting to create a datasource that enables routes/services to access an Azure-based SQL Server with AD Authentication, the datasource may fail to connect. Despite providing the necessary ms__auth.dll to Runtime (either through the service or etc folder) and windows, the tesb log may still display the following error message:
"Failed": "com.microsoft.sqlserver.jdbc.SQLServerException:Failed to load MSAL4J Java library for performing ActiveDirectoryPassword authentication.
In many cases, the reason for this error is due to Runtime not having the specific library installed within it. Although they are very similar, Azure-based SQL Instances do require specific dependencies that may not be found with the regular Microsoft SQL JDBC drivers. This may affect those users who have a Runtime instance at or newer than the R2024-06 Patch.
To address this issue, please follow these steps:
If the datasource or task is still encountering connection issues, kindly contact Qlik Support.
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.
With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User, and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.
I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).
In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.
If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.
II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.
A QlikView Server or a Qlik Publisher software can be activated in two ways:
1) Using a legacy method with 16-digit QlikView license key and the corresponding control number
2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model
If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.
Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales
How are sessions counted in Qlik Sense?
The following are examples of how sessions are counted within Qlik Sense.
Sessions will be terminated after the currently configured Session timeout in the Qlik Sense Proxy.
If the Qlik Sense engine or Proxy are terminated or crash, Sessions are ended right away.
Once the maximum number of parallel user connections (5) is reached, this will be documented in the AuditSecurity_Repository log. To identify if this is the issue, review the relevant log and review how the user is interacting with the system.
The log is stored in:
C:\Programdata\Qlik\Sense\Log\Repository\Audit\AuditSecurity_Repository.txt
The related message reads:
Access was denied for User: 'Domain\USER', with AccessID '264ff070-6306-4f1b-85db-21a8468939b5', SessionID: 'e3cd957b-a501-4bec-a3f8-d35170a73efa', SessionCount: '5', Hostname: '::1', OperationType: 'UsageDenied'
Troubleshoot too many sessions active in parallel
Qlik Sense April 2018 and later- Service account getting "You cannot access Qlik Sense because you have no access pass"
The QlikView Services can be set up to either use the local QlikView Administrators Group, or Digital Certificates. The Service Account has specific requirements.
The two options during installation are Use digital certificates and Use QlikView Administrators Group.
Authenticate communication between QlikView servers using digital certificates and SSL. This alternative is recommended in environments where not all servers have access to a common Windows Active Directory or when the security provided by certificate authentication is required. Note that digital certificates are only supported by Windows Server 2008 R2 and later.
Authenticate communication between QlikView services based on membership in the local Windows group QlikViewAdministrators. This alternative can be used in environments where all servers that are part of the QlikView installation can authenticate using a common Windows Active Directory.
Regardless of the option chosen, the service account used to run the services has to be:
Note: GMSA (Standalone Managed Service Accounts) are not supported for Qlik products
If your Qlik Sense Enterprise on Windows version is not compatible with the QSR database.
This may occur if:
An incorrect version of Qlik Sense Enterprise on Windows in a multi node environment will trigger a database migration to this version. The result is that the Qlik Sense Repository service fails to start with the error:
Fatal exception during startup Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.↵↓An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext
As database migration started which had caused database corruption, you need to revert back to the old database backup to resolve this issue or contact Qlik Support for assistance.
QB-8813
Qlik Sense Enterprise on Windows all versions
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
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
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