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.
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:
There are problems occurring related to notifications, for example, the notifications are not being sent to E-mail.
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
This document explains how to manually setup custom connectors within Qlik Sense with Standard mode without legacy mode. More info under Legacy vs. Standard Mode in Qlik Sense: Explainer and Security Considerations
Pre-requisites:
After installing Qlik SAP Connectors on a Qlik Sense Enterprise Server, some connectors like Qlik SAP Report Connector, Qlik SAP Query Connector..., are not automatically installed. Thus, when migrating from a "QlikView environment" to "Qlik Sense Enterprise", those specific connectors need to be manually set in Qlik Sense.
Step 1:
After successful connection, click Create button
Step 2:
Step 3:
It should look like:
Step 4:
Step 4:
Optional Steps:
With the latest versions of QlikView and Qlik SAP Connector, you don't need to perform this step.
After upgrading to Talend 8.0.1, we are facing an issue when using phoenix-client-hbase-2.4-5.1.1.7.1.9.6-3.jar to connect to the Phoenix HBase by using JDBC.
This error is being thrown while trying to establish a connection
org.apache.phoenix.query.GuidePostsCacheProvider - Could not load/instantiate class org.apache.phoenix.query.DefaultGuidePostsCacheFactory
Searched for the phoenix-hbase-client jar file and the required classes are present in folder without missing jar issue.
This issue has been fixed from CDP side.
You need to apply for CDP patch fix and update Cloudera CDP version to 7.1.9 with hot-fix jars.
It is a known bug from upstream
https://issues.apache.org/jira/browse/PHOENIX-7290.
https://github.com/apache/phoenix/pull/1873/commits/78165aa4601ee49e572c3f75e99be7c7506737aa
Internal Jira Case: TBD-16676
The architecture of the integration at a High-level looks like this:
Qlik Sense Advanced Analytics integration is essentially an extension to Qlik Sense’s expression syntax, and as such it can be used in both Chart Expressions, and in Load Script Expressions.
With this new capability, we are now able to add syntax to a chart expression that tells Qlik Sense that particular expression should not be evaluated on the Qlik Sense server, but instead, all the information and data needed to calculate that expression should be sent via the server side extension on to the backend R system for calculation.
After the advanced analytic calculations are completed, the data is sent back to the Qlik Sense Server and to the client for visualization.
This video shows an example of how Qlik Sense connects to an R server for extending expression capabilities in Qlik Sense Apps while offloading the calculations to the R server engine.
Click here for Video Transcript
In order to start displaying a simple "Hello World" in Qlik Sense using a R-Script, we will do the following:
1. Have R & R-studio installed in your system. (RGui included with R for Windows can also be used) R can be downloaded at https://cloud.r-project.org/
2. We need a package in R to extend R functionality to applications via TCP/IP. The package name is "Rserve()"
Install the package using the below command in RStudio GUI:
install.packages('Rserve')
3. Now we need to invoke that library and start Rserve. In order to do so, execute the below scripts:
library(Rserve) Rserve()
4.The communication method from Sense to R is taken care using gRPC. R is not a supported language in gRPC by default.
So a possible solution for this is to develop a connector in any of the supported languages of gRPC. Qlik provides an open-source connector developed in C# which in turn access Rserve to be able to run R scripts.
qlik-oss/sse-r-plugin
Once you built the connector, start the SSEtoRserve.exe (ideally on the Rserve server itself)
Note: Qlik Support does not support this plugin directly. Inquiries should be submitted via GitHub under sse-r-plugin - Issues
5. Now we will have to configure the plugin:
Add the following line in the settings.ini file:
SSEPlugin=R,localhost:50051
The settings.ini is located in this location:
Add the following line in the settings.ini file:
SSEPlugin=R,localhost:50051
The settings.ini file is located in this location:
a. In the QMC, add a new Analytic Connection.
b. Restart the Qlik Sense Engine service.
Please refer to the screenshot below for creating a new connection.
Note: If the R-Plugin (SSEtoRserve.exe) was installed on the R-Server (where Rserve runs) or another machine, point to that machine name instead of 'localhost'. Also, in multi-node environments with multiple Qlik Sense Engines, even if the plugin was installed on the Central node, make sure to add the Central node's hostname instead of 'localhost' as the other Rim node Engine services need the correct DNS/Netbios name to reach the plugin.
6. Now Open a Qlik Sense App and add a KPI object in the sheet. This can be one of the Apps included with the plugin itself under <storage path>\sse-r-plugin-master\sense_apps
Note that the example apps also need data connections to be created to the data files included with these apps files in the above location.
7. Otherwise, a new app can be created and any data may be loaded for the SSE example below.
8. For the measure, add the following expression which contains an R-script:
R.ScriptEvalStr('paste(q$firstWord, q$secondWord);', 'Hello' as firstWord, 'World' as secondWord)
9. If everything is configured properly, the R-script shown in bold above should be executed fine and it should display a "Hello World" message.
R.ScriptEvalStr('paste(q$firstWord, q$secondWord);', Only([First Word]) as firstWord, Only([Second Word]) as secondWord)
Eight script functions are automatically added to the functionality of the plugin. What is needed to be covered on the plugin side to fulfill the functionality is to implement the EvaluateScript rpc function.
The syntax of these functions is:
<EngineSSEName>.<FunctionName>(Script [,Parameter...])
Where the Script is an R-Script to be evaluated & Parameter is the data sent from Qlik's end.
Here, we use the ScriptEvalStr function which accepts argument of type String & returns a String. The 'paste' function in R concatenates vectors after converting to character. We pass two data fields of type string from Qlik (First Word & Second Word). The R-script then references these data fields through the q dataframe (structure already taken care in R) (q$firstWord and q$secondWord). The script/function finally returns a String back to Qlik Sense.
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:
The Qlik Sense Engine allows for a Hard Max Limit to be set on memory consumption.
To be able to enforce "Hard max limit" the engine requires access to a specific endpoint in the Windows operating system API.
If the operating system blocks calls to this endpoint, then an attempt to use the configuration "Hard max limit" will fail, and the engine will instead operate according to the "Soft max limit" configuration.
Refer to the documentation provided by Microsoft fur forther information: "SetProcessWorkingSetSizeEx"
See Editing an engine - Qlik Sense for administrators for details.
To note:
Even with the hard limit set, it may still be possible for the host operating system to report memory spikes above the Max memory usage (%).
This is down to how the Qlik Sense Engine memory limit will be defined based on the total memory available.
Example:
The memory working setting limit is not a hard limit to set on the engine. This is a setting which determines how much we allocate and how far we are allowed to go before we start alarming on the working set beyond parameters.
QLIK-96872, HLP-17517
When using SAML or ticket authentication which started in Qlik Sense June 2019, some users belonging to a big number of groups see the error "Qlik Sense G3 Broker API" on the hub and cannot proceed further.
You may receive the following error when setting up the SAML virtual proxy: cachebust pending
Environments:
The only known workaround in the above versions is to reduce the number of groups sent in the SAML response or ticket request.
The fix for this defect is included in the following versions, but additional steps may be necessary:
All Versions
The default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.
Steps:
[globals]
LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
MigrationPort=4545
(...)
MaxHttpHeaderSize=65534
Note: Above value (16384) is an example. You may potentially need to put more depending of the total number of characters of all the AD groups to which the user belongs. The max value is 65534.
Other Related Articles:
https://community.qlik.com/t5/Official-Support-Articles/Error-431-when-trying-to-access-the-Qlik-Sense-Management/ta-p/1789124
QB-234.
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.
The Qlik Sense Repository Database (QSR) can be moved to a dedicated standalone PostgreSQL instance not hosted on the same machine as other Qlik Sense Services. It is also possible to move an already existing QSR from a local Sense install, to a dedicated PostgresSQL database.
Content:
Instructions for this might vary slightly. Please refer to the Qlik Online Help for details. We recommend watching this video.
Qlik Sense Enterprise server has a set of five databases. For more details visit Installing and configuring PostgreSQL on help.qlik.com.
1. The Qlik Sense repository database (QSR):
The QSR is the primary database in your Qlik Sense deployment.
2. The Qlik Sense services database (SenseServices):
The SenseServices database contains schemas for each of the Qlik Sense services and allows growth independently of the Qlik Sense Repository Database, while still sharing the same PostgreSQL instance and login role.
3. The Qlik Sense message queue database (QSMQ):
The QSMQ database provides a light-weight method of passing messages internally between services in Qlik Sense Enterprise. The NOTIFY and LISTEN functionality in PostgreSQL allows services to be notified about new messages that have been written to the messaging table.
4. The Qlik Sense logging database (QLogs): No longer supported after May 2021
The QLogs database centralizes logging by collecting log messages from all Qlik Sense nodes in your deployment and stores them in a PostgreSQL database.
5. The Qlik Sense license service database (Licenses):
The Licenses database is used to sync the assignments between the Qlik license backend and the local installation.
Follow How to change the shared path in Qlik Sense
Depending on the version, you need to backup different databases, on the current Qlik Sense central node hosting the Qlik Sense Repository Database service, follow the backup instructions to obtain a database copy of each Qlik Sense Database Present .
Example for February 2021 you need to backup the databases reported in section "Installing and configuring PostgreSQL"; referring to the Help site these are :
QSR , QSMQ , SenseServices , Licenses , if configured QLogs
On the dedicated remote postgresSQL host, perform a restore of the backed up Databases of previous point.
Execute steps in Moved Postgress database to new host, but some qliksense is still accessing the SenseServices old database; check if different version of article are present for different Qlik Sense version .
Starting from April 2019 new License Service implementation is using this database.
It will look like this:
repeat this for:
C:\Program Files\Qlik\Sense\NotifierService\install\Configure-Service.ps1
C:\Program Files\Qlik\Sense\AppDistributionService\Configure-Service.ps1
C:\Program Files\Qlik\Sense\HybridDeploymentService\Configure-Service.ps1
C:\Program Files\Qlik\Sense\MobilityRegistrarService\install\Configure-Service.ps1
C:\Program Files\Qlik\Sense\PrecedentsService\install\Configure-Service.ps1
C:\Program Files\Qlik\Sense\NLAppSearch\install\Configure-Service.ps1
there might come new services or disappear with new releases, please check in the C:\Program Files\Qlik\Sense\ folder for "Configure-Service.ps1" to find additional one in your version of Qlik Sense.
Note: If you have installed Qlik Sense in a different directory the Configure-Service.ps1 would have to be updated as in this example:
File: Configure-Service.ps1 Folders: Various (9 microservices)
Before:
11 | [string] $senseInstallPath
"$env:ProgramFiles\Qlik Sense",
After:
11
[string] $senseInstallPath = "D:\Qlik",
After successfully verifying your new setup, remove the Qlik Sense Repository service dependencies and the old Postgres database. This is done to avoid issues with future Upgrade of Environment.
In Multi-node scenario you need to repeat steps "Changing the Connection Strings to Databases" on all Rim nodes (QlikSenseUtil for Repository.exe.config and Configure-Service.ps1 for the micro services), and if required configure "Update the Qlik Logging Service Connection String" (note that is EOL with Qlik Sense Enterprise on Windows February 2022) .
This article describes how to resolve the NPrinting connection verification error:
x Qlik NPrinting webrenderer can reach Qlik Sense hub error
Logging out from Qlik Cloud Analytics leads to the error:
502 Bad Gateway
QB-29858 will be fixed in an upcoming Qlik Cloud Analytics update. Until then, refresh the page to resolve the 502 Bad Gateway error.
The information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QB-29858 for reference.
QB-29858
To retrieve the list of projects in TAC, use the following MetaServlet API command:
Command: { 'actionName': 'listProjects', 'authPass': 'admin', 'authUser': 'admin@company.com', 'onlyActive': true, 'onlyGit': false, 'withReference': false }
However, the above command will return multiple entries for the same project depending on the number of branches associated with it.
To obtain a unique count of project names, regardless of the number of branches the project has, set the parameter 'loadAllBranchAndTag' to false in the command, as shown below:
Command : { 'actionName': 'listProjects', 'authPass': 'admin', 'authUser': 'admin@company.com', 'onlyActive': true, 'onlyGit': false, 'withReference': false, ‘loadAllBranchAndTag’ : false }
Note: please make sure to apply the patch TPS-5611 before executing this metaservlet command.
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.
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 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).
A workaround is available to address the complications affecting extension and invalid visualization errors. This workaround can be applied before or after the upgrade. It has been tested successfully on all patches released on December 4th. The November 2024 release is not affected by the issue.
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.
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.