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.
Please, let us know if anyone has questions or concerns about enabling the email notifications.
Qlik Sense Mobile Client Managed & SaaS
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.
Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.
The behaviour began after an upgrade of Qlik Sense Enterprise on Windows.
This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.
Enable QmcTaskTableCacheDisabled.
To do so:
Upgrade to the latest Service Release and disable the caching functionality:
To do so:
NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.
Should the issue persist after applying the workaround/fix, contact Qlik Support.
This article explains how client-managed Qlik Sense sessions function and how to terminate them if needed.
Qlik Sense allows a maximum of five parallel sessions per user. Beginning with the sixth authentication attempt, the connection will fail until a session becomes available. By default, the duration of a session is 30 minutes, but this can be adjusted in the Qlik Sense Enterprise Management Console (see Virtual Proxy settings).
If the maximum session count has been reached, the user will encounter the error You cannot access Qlik Sense because you have too many sessions active in parallel.
The maximum number of sessions a user can have simultaneously cannot be changed.
Once the user is authenticated, a cookie named X-Qlik-Session is saved in their browser. If this session cookie header’s value is not transmitted, is destroyed, or modified between the end user’s browser and the Qlik Sense server, the user's session is terminated. The user is then logged out.
By default, the session will be destroyed after 30 minutes of inactivity. Closing the browser or tab itself will not immediately terminate the session but will continue the inactivity timer.
You can verify your session timeout value or configure it:
For more information see How to count sessions in Qlik Sense.
Qlik Sense admins may encounter the error message You cannot access Qlik Sense because you have too many sessions active in parallel. This often happens when they have Qlik Sense Hub open in one tab and Qlik Sense QMC in another.
The reason for reaching the maximum of five sessions is that the administrator is using the Qlik Sense service account to log into both Qlik Sense Hub and QMC. It’s important to note that the service account creates its own sessions in addition to those initiated by the user logging into the Hub or QMC.
Therefore, it is strongly recommended not to license the Qlik Sense service account for logging into the QMC, as logging into the QMC does not require a licensed user. By following this practice, you will likely avoid reaching the limit of five concurrent sessions.
For more information on the error and how to troubleshoot it, see:
If you do not want to wait for Qlik Sense to automatically delete a session after 30 minutes of inactivity, you have the option to manually terminate it the session and reconnect to Qlik Sense.
There are various methods for deleting sessions in Qlik Sense, each with its advantages and disadvantages. Below are a few examples:
To do this:
This prompts a restart of the proxy.
The advantage of this method is that you can perform it directly in the QMC without needing any third-party scripts or tools. However, the downside is that restarting the proxy service will delete sessions for all users.
The first step is to retrieve all user sessions from the available proxies and then delete them one by one. The advantage of this method is that you can delete individual user sessions without affecting the sessions of other users. However, the downside is that it requires technical knowledge to write the program that will list the user’s sessions and allow you to choose which sessions to delete.
Qlik-cli-utils (GitHub) is a collection of PowerShell scripts that enables you to automate certain tasks. With qlik-cli-utils, you can delete an individual user’s sessions without affecting the sessions of other users.
The advantage of this tool is that you can specify which user’s sessions you want to delete. However, the downside is that it operates via a command line without a graphical user interface (GUI), and you need to install Qlik-CLI (a PowerShell module obtained from GitHub) in addition to qlik-cli-utils. Deleting sessions is done one at a time, as shown in the image below.
Qlik Fix: How to fix "Too many sessions active in parallel"
Troubleshoot no access pass or too many sessions active in parallel on Qlik Sense hub
Qlik Sense can process a maximum of 1,048,576 (2^20) characters by row when loading data from a CSV file. If a row in the source CSV file is longer than this limit, Qlik Sense automatically breaks it to multiple rows in the loaded table.
This doesn't happen when loading another file format (like XML) or loading the same CSV file in QlikView.
To increase the maximum length, please set parameter LongestPossibleLine in Settings.ini file of Qlik Sense Engine to a higher value than 1048576.
See How to modify Qlik Sense Engine's Settings.ini for detailed instructions of changing parameters in Settings.ini.
Qlik Sense engine supports up to 512 Megabytes (512*1024*1024) as line length. Script reload can handle strings up to this length in a single data cell. However, when using the data selection wizard, such long string may break the web socket. Therefore, maximum string length is limited to 1,048,576 characters to avoid this web socket issue.
Relevant resources:
How to Access My Qlik Portal
Managing Your Subscription in My Qlik
Please do the following before requesting the change:
Areas that are particularly sensitive when you remove a user:
The purpose of this article is to provide details about enabling Full Load Passthru filter in Qlik Cloud Data Integration (QCDI) and get the selected data from the source during the initial load of the Landing or Replication Tasks.
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.
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' 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:
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.
It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:
{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false
Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.
This problem occurs when the Mail.Send permission has not been configured in the app registration.
More information about the Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).
This article gives an overview of the available blocks in the Jira connector in Qlik Application Automation. It will also go over some basic examples of retrieving issues by a specified project and creating an issue within a Jira account.
This connector supports CRUD operations(read, create, update, delete) for the following modules in Jira:
There are also a few generic blocks that could help to cover the other modules :
Authentication for this connector is based on the oAuth2 Protocol.
Let's now go over a few basic examples of how to use the Jira connector:
1. How to list issues from a specific project from a Jira account
2. To create a new issue:
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.
After exporting a Logstream parent task and changing its name, the import fails with:
SYS-E-HTTPFAIL, SYS-E-HTTPFAIL, Put full task failed. Task name: <task_name>
Alternatively, if you need two parent tasks:
Line 8: "target_names": ["logstreamnewname"],
Line 41: "target_name": "logstreamnewname",
Line 43: "database_name": "logstreamnewname"
Line 126: "name": "logstreamnewname",
Line 132: "path": "C:\\logstreamnewname",
The Parent Logstream task has wrongfully signalled a duplication of the target.
Sometimes the target default endpoint behavior does not meet our needs. This article is useful if we want to modify the default syntax.
For example, while MySQL is the target endpoint, Qlik Replicate creates a net changes table and uses it in batch apply mode. The net changes table is created with the default engine type "InnoDB" which has limitations while "MyISAM" and does not have the Row size too large limitation in MySQL.
The below steps demonstrate how to change the net changes table engine type from "InnoDB" (default) to "MyISAM". After the setup is done, Qlik Replicate will create the net changes table automatically with engine type "MyISAM".
From the Qlik Replicate computer where you want to import the task, open the Qlik Replicate command line console by doing the following:
From the Start menu, expand Qlik Replicate and then select Qlik Replicate Command Line.
A command-line console is displayed with the correct prompt for Qlik Replicate.
Alternatively, open a Windows Command Prompt using As Adinistrator and change to "<product dir>\Attunity\Replicate\bin" (default location)
repctl.exe getprovidersyntax syntax_name=MySQL > MySQL_MyISAM.jsonIf the DATA folder is non-default location, add option -d data_directory in the command.
command getprovidersyntax response:
[getprovidersyntax command] Succeeded
"provider_syntax": { "name": "MySQL", "query_syntax": {Modified:
"provider_syntax": {
"name": "MySQL_MyISAM",
"repository.provider_syntax": {
"name": "MySQL_MyISAM",
"query_syntax": {
repctl putobject data=MySQL_MyISAM
Do not add the additional suffix ".json" in the end of the command as this will cause the command to fail.
It is finally here: The first public iteration of the Log Analysis app. Built with love by Customer First and Support.
"With great power comes great responsibility."
Before you get started, a few notes from the author(s):
Chapters:
01:23 - Log Collector
02:28 - Qlik Sense Services
04:17 - How to load data into the app
05:42 - Troubleshooting poor response times
08:03 - Repository Service Log Level
08:35 - Transactions sheet
12:44 - Troubleshooting Engine crashes
14:00 - Engine Log Level
14:47 - QIX Performance sheets
17:50 - General Log Investigation
20:28 - Where to download the app
20:58 - Q&A: Can you see a log message timeline?
21:38 - Q&A: Is this app supported?
21:51 - Q&A: What apps are there for Cloud?
22:25 - Q&A: Are logs collected from all nodes?
22:45 - Q&A: Where is the latest version?
23:12 - Q&A: Are there NPrinting templates?
23:40 - Q&A: Where to download Qlik Sense Desktop?
24:20 - Q&A: Are log from Archived folder collected?
25:53 - Q&A: User app activity logging?
26:07 - Q&A: How to lower log file size?
26:42 - Q&A: How does the QRS communicate?
28:14 - Q&A: Can this identify a problem chart?
28:52 - Q&A: Will this app be in-product?
29:28 - Q&A: Do you have to use Desktop?
Qlik Sense Enterprise on Windows (all modern versions post-Nov 2019)
*It is best used in an isolated environment or via Qlik Sense Desktop. It can be very RAM and CPU intensive.
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.
Optimizing Performance for Qlik Sense Enterprise - Qlik Community - 1858594
Qlik Gold Client support cases can be opened on the Qlik Customer Portal. For effective communication with Qlik Support, always include all required information, go into detail when describing your problem, and provide all necessary supplementary material (such as log files).
To log the case:
How to Contact Qlik Support
How to View Cases in Support Portal
The Qlik NPrinting Engine cannot resolve requests for tasks which include Qlikview Entity reports that output to PDF or is not printing QlikView Entity reports to PDF.
An error is displayed when attempting to edit or print the QlikView Entity report:
Error: QlikView NPrinting PDF Printer not installed or not properly registered
Or the report fails silently while the following is printed in the Qlik NPrinting logs:
resolution aborted with exception System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.↵↓ at Tracker.PDFXChange.IPXCControlEx.get_Printer(String pServerName, String pPrinterName, String pRegKey, String pDevCode)↵↓ at Qlik.Reporting.Printers.QlikPdfPrinter.Win64PrinterFactory.get_Item(String pServerName, String pPrinterName, String pRegKey, String pDevCode
When you install Qlik NPrinting, the Windows service “Print spooler” must be up and running. If it is disabled, the Qlik NPrinting Printer will not be added during the installation. Similarly, if a separate PDF-XChange driver is installed, the Qlik NPrinting engine install will not install the QlikView NPrinting PDF-Printer.
NPrinting: PDF reports generation fails after disabling the Windows Spooler service
QB-14941
Creating a new git branch will persist unstaged changes from the current branch.
Replication Steps
This is a normal behavior in git. You can add these untracked changes to a git branch or remove these untracked changes before switching branch.
Due to untracked files are not monitored by git, so after switching branch, these files are still present in local file system. When Talend Studio loads jobs from local file system, the untracked changes will appear in the newly created branch in studio as well.
Internal Defect ID: TUP-44462
After a Qlik Replicate task was stopped to update parameters, the task will not start. A new task referencing the same source fails to fetch its tables and errors out with the following:
SYS-E-HTTPFAIL, SYS-E-HTTPFAIL, Command get_owner_list failed when creating the stream component...
SYS,GENERAL_EXCEPTION,SYS-E-HTTPFAIL, Command get_owner_list failed when creating the stream component..,SYS,GENERAL_EXCEPTION,Command get_owner_list failed when creating the stream component.,Failed getting stream handle create_stream_handle failed Command create_stream_handle failed when preparing component. ORA-12170: TNS:Connect timeout occurred
ORA-12170 is an Oracle connection error and is not caused by Qlik Replicate. Qlik Replicate will send a connection request through the Oracle client, which will establish a connection to the database based on the sqlnet.ora settings. ORA-12170: TNS:Connect timeout occurred indicates a timeout.
To resolve the error, update sqlnet.ora and increase the available timeouts.
A Qlik Replicate Log Stream task fails with the error:
Stream component 'st_0_T03ERP_TGT_QLK_LSS' terminated Cannot initialize subtask
Failed while preparing stream component 'st_0_T03ERP_TGT_QLK_LSS'. Error reading audit batch
Timeout while waiting to get data from audit file
Verify that sufficient disk space is available. Clear up space or increase the available quota, then:
A corrupted metastore.sqllite file. The file is created in the Log Stream target location (LogStream/audit_services directory) when a task is started. Most commonly disk space issues cause the file's corruption.
Please, let us know if anyone has questions or concerns about enabling the email notifications.
Qlik Sense Mobile Client Managed & SaaS