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.
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.
This is a Python example to call the Qlik Sense Engine API.
Here is a simple script using the websocket-client module to call the Engine API. Note that the Qlik Sense virtual proxy is set to header authentication.
import websocket import ssl import json header_user = {'header_user': 'user1'} ws = websocket.create_connection("wss://qlikserver1.domain.local/hdr/app/", sslopt={"cert_reqs": ssl.CERT_NONE},header=header_user) ws.send(json.dumps({ "handle": -1, "method": "GetDocList", "params": [], "outKey": -1, "id": 1 })) result = ws.recv() while result: result=ws.recv() y = json.loads(result) print(y) ws.close()
Example of results:
{'jsonrpc': '2.0', 'method': 'OnConnected', 'params': {'qSessionState': 'SESSION_CREATED'}} {'jsonrpc': '2.0', 'id': 1, 'result': {'qDocList': [{'qDocName': 'test1', 'qConnectedUsers': 0, 'qFileTime': 0, 'qFileSize': 176418, 'qDocId': '9b428869-0fba-4ba5-9f94-901ae2fdf041', 'qMeta': {'createdDate': '2018-11-29T09:28:40.588Z', 'modifiedDate': '2018-12-17T15:13:56.860Z', 'published': True, 'publishTime': '2018-12-17T15:13:56.782Z', 'privileges': ['read', 'offlineaccess'], 'description': '', 'dynamicColor': '', 'create': None, 'stream': {'id': 'aaec8d41-5201-43ab-809f-3063750dfafd', 'name': 'Everyone'}, 'canCreateDataConnections': False}, 'qLastReloadTime': '2018-11-29T09:30:42.121Z', 'qTitle': 'test1', 'qThumbnail': {}}]}}
In certain scenarios, it is necessary to create additional Windows local accounts for Qlik Replicate and Qlik Enterprise Manager to provide a user the minimum required access level.
This article outlines the steps to add a Windows local account in the built-in Guests group.
#00048742
Gold Client BW is a versatile solution designed to streamline day to day business activities. Gold Client BW helps reduce the need of full system refreshes, provides the ability to copy queries and hierarchies to non-Production systems, and aids in troubleshooting production support issues. The Gold Client BW tool will save time, reduce manual effort, and allows users focus on what matters most.
Usage examples of Gold Client BW are listed below:
After upgrade from QlikView 12.40, it is no longer possible to connect to some Generic LDAP servers.
Current distributions fail and setting up a new connection results in wrong username and password.
LDAP connector changes to comply with new Microsoft security settings. If an outdated LDAP server is deployed it may be necessary to revert to the previous settings.
From R2024-05, Java 17 will become the only supported version to start most Talend modules, enforcing the improved security of Java 17 and eliminating concerns about Java's end-of-support for older versions. In 2025, Java 17 will become the only supported version for all operations in Talend modules.
Starting from v2.13, Talend Remote Engine requires Java 17 to run. If some of your artifacts, such as Big Data Jobs, require other Java versions, see Specifying a Java version to run Jobs or Microservices.
Content
Qlik Talend Module | Patch Level and Version |
Studio | Supported from R2023-10 onwards |
Remote Engine | 2.13 or later |
Runtime | 8.0.1-R2023-10 or later |
For Windows users, please follow the JDK installation guide (docs.oracle.com).
For Linux users, please follow the JDK installation guide (docs.oracle.com).
For MAC OS users, please follow the JDK installation guide (docs.oracle.com).
When working with software that supports multiple versions of Java, it's important to be able to specify the exact Java version you want to use. This ensures compatibility and consistent behavior across your applications. Here is how you can specify a specific Java version on the following products (such as build servers, shared application server, and similar):
For Studio users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps:
-vm
<JDK17 HOME>\bin\server\jvm.dll
For Remote Engine (RE) users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
For Runtime users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
If Runtime is not running as a service:
With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option.
To use Talend Administration Center with Java 17, you need to open the <tac_installation_folder>/apache-tomcat/bin/setenv.sh file and add the following commands:
# export modules export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
Windows users use <tac_installation_folder>\apache-tomcat\bin\setenv.bat
Follow the steps below to configure the JobServer to use the new Java version.
Navigate to the JobServer Configuration:
Go to the <JobServerRootDir>\conf directory, where <JobServerRootDir> is the path to your Talend JobServer installation.
Open the Configuration File for Editing:
Locate the TalendJobServer.properties file and open it with a text editor of your choice.
Set the Java 17 Executable Path:
Find the line dedicated to the Job launcher path within the file. You will modify this line to point to the Java 17 executable.
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH="C:\\Program Files\\Java\\jdk-17\\bin\\java.exe"
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/usr/lib/jvm/java-17-openjdk/bin/java
Replace the example paths with the actual path where Java 17 is installed on your system. Ensure to point directly to the Java executable within the bin directory of your JDK installation.
Save Your Changes:
After editing, save the TalendJobServer.properties file.
Restart Talend JobServer:
For the changes to take effect, restart your Talend JobServer.
After completing these steps, Talend JobServer will utilize Java 17 for executing Jobs, ensuring compatibility with the latest Java version supported by Talend modules.
For Java 17 users, Talend CICD process requires the following Maven options:
set "MAVEN_OPTS=%MAVEN_OPTS% --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
For Java 17 users, Talend CICD process requires the following Maven options:
export MAVEN_OPTS="$MAVEN_OPTS \ --add-opens=java.base/java.net=ALL-UNNAMED \ --add-opens=java.base/sun.security.x509=ALL-UNNAMED \ --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
<name>TALEND_CI_RUN_CONFIG</name> <description>Define the Maven parameters to be used by the product execution, such as: - Studio location - debug flags These parameters will be put to maven 'mavenOpts'. If Jenkins is using Java 17, add: --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED </description>
Overview
Enable your Remote Engine to run Jobs or Microservices using a specific Java version.
By default, a Remote Engine uses the Java version of its environment to execute Jobs or Microservices. With Remote Engine v2.13 and onwards, Java 17 is mandatory for engine startup. However, when it comes to running Jobs or Microservices, you can specify a different Java version. This feature allows you to use a newer engine version to run the artifacts designed with older Java versions, without the need to rebuild these artifacts, such as the Big Data Jobs, which reply on Java 8 only.
When developing new Jobs or Microservices that do not exclusively rely on Java 8, that is to say, they are not Big Data Jobs, consider building them with the add-opens option to ensure compatibility with Java 17. This option opens the necessary packages for Java 17 compatibility, making your Jobs or Microservices directly runnable on the newer Remote Engine version, without having to go through the procedure explained in this section for defining a specific Java version. For further information about how to use this add-opens option and its limitation, see Setting up Java in Talend Studio.
Procedure
c:\\Program\ Files\\Java\\jdk11.0.18_10\\bin\\java.exe
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=c:\\jdks\\jdk11.0.18_10\\bin\\java.exe
ms.custom.jre.path=C\:/Java/jdk/binMake this modification before deploying your Microservices to ensure that these changes are correctly taken into account.
Reloads fail with error:
A reload fails with:
Requested endpoint could not be provisioned due to failure to acquire a load slot: Your version of Direct Access gateway is no longer supported. Go to 'Data gateways' in the Management Console to download the latest version (DirectAccess-0001)
Upgrade Qlik Data Gateway - Direct Access to a supported version.
If you are already on a supported version of Qlik Data Gateway, rerun the reload. Likely, the services were still initializing when the issue occurred.
This message can occur when the Qlik Data Gateway version is not supported
Or it could also be caused if the services are starting when the request is sent, causing the version being misreported. This is usually an isolated issue with very few reload failures.
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.
Introduction
Qlik Cloud offers a number of distribution and reporting capabilities. From in-app download, Data Alerts, and Subscriptions, to enterprise report distribution, there are many ways to produce and delivery analytics to stakeholders.
Administrators may be interested in seeing, or analyzing, the result of activity for these capabilties. This post is intended to offer some insight on a number of event types found in Management Console > Events as it relates to reporting and distribution use cases on Qlik Cloud. The post was created in response to some common questions from customers.
Disclaimer:
Interactive reporting/distribution events are found by filtering within the Management Console > Events on the Event Type = com.qlik.v1.reporting-service.audit
Ad hoc download events surface when a user is working within an application and downloading a produced file to their local system. This activity has the tags "sense-dialog.download".
{ "data": [ { "id": "6696d14047e1fa3e821fc21f", "contentType": "application/json", "data": { "appIds": [ "09eea519-a69c-456e-8790-ef0bacc42310" ], "endTime": "2024-07-16T20:00:00.752237504Z", "reportId": "a1e65f7f-d6ef-4e4d-b619-23574a8c87d8:0", "requestId": "a1e65f7f-d6ef-4e4d-b619-23574a8c87d8", "startTime": "2024-07-16T19:59:59.468816403Z", "success": true, "tags": [ "sense-dialog.download" ], "templateType": "sense-data-1.0", "traceId": "f71cdbe3dfabc79acd1e73b9d4648176", "version": "1.0.0" }, "eventId": "1d7e3ab7-dc80-427c-bbdb-19bbfedf", "eventTime": "2024-07-16T20:00:00.756Z", "eventType": "com.qlik.v1.reporting-service.audit", "eventTypeVersion": "1.0.0", "source": "com.qlik/reporting-service", "tenantId": "<tenant>", "userId": "uzWYcE_cOycXMWhuD6BlRKH82I2dI-J8", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/6696d14047e1fa3e821fc21f" }, "self": { "href": "https://<tenant>/api/v1/audits/6696d14047e1fa3e821fc21f" } } }
Event variants:
Object (chart) data download
Attribute |
Value |
Description |
templateType |
Sense-data-1.0 |
Data export (XLS) |
Object (chart) image download
Attribute |
Value |
Description |
templateType |
Sense-image-1.0 |
Image export (PDF, PNG) |
Sheet download
Attribute |
Value |
Description |
templateType |
Sense-sheet-1.0 |
Sheet export (PDF, PNG) |
Story download
Attribute |
Value |
Description |
templateType |
Sense-story-1.0 |
Story export (PDF) |
Tabular reporting, on-demand download
Attribute |
Value |
Description |
templateType |
Sense-excel-template-1.0 |
Tabular report run on-demand. This is a metered event against the monthly Qlik Reporting Service allocation for the tenant |
These events surface when a user schedules a file to be deliver to their inbox via email. This activity has the tags "Subscription.execution".
{ "id": "66969fee79c1c5c9c01f221d", "contentType": "application/json", "data": { "appIds": [ "09eea519-a69c-456e-8790-ef0bacc42310" ], "endTime": "2024-07-16T16:29:34.075307903Z", "reportId": "a5d1aa11-25f3-4400-add4-f4f637dca380:0", "requestId": "a5d1aa11-25f3-4400-add4-f4f637dca380", "startTime": "2024-07-16T16:29:03.860783997Z", "success": true, "tags": [ "subscription.execution" ], "templateType": "composition-1.0", "traceId": "78edb521626993b692a89a52535ad946", "version": "1.0.0" }, "eventId": "37030b7a-af9e-4313-84a8-b397bd0a", "eventTime": "2024-07-16T16:29:34.079Z", "eventType": "com.qlik.v1.reporting-service.audit", "eventTypeVersion": "1.0.0", "source": "com.qlik/reporting-service", "tenantId": "<tenant>", "userId": "6437fea62c33a33f8e579163", "links": { "Self": { "Href": "https://<tenant>.us.qlikcloud.com/api/v1/audits/66969fee79c1c5c9c01f221d" }, "self": { "href": "https://<tenant>.us.qlikcloud.com/api/v1/audits/66969fee79c1c5c9c01f221d" } } }
Subscription to Chart
Attribute |
Value |
Description |
templateType |
sense-image-1.0 |
Subscription to a single object Image file |
Subscription to Sheet
Attribute |
Value |
Description |
templateType |
composition-1.0 |
Subscription to a multi-sheet file |
Subscription to Sheet (legacy event)
Attribute |
Value |
Description |
templateType |
Sense-sheet-1.0 |
Subscription to a single sheet Image file |
Related: Subscriptions reports are produced by a task - the task event information is found with the event type = com.qlik.sharing-task.executed with attribute
{ "id": "66969fee79c1c5c9c01f2222", "contentType": "application/json", "data": { "appId": "09eea519-a69c-456e-8790-ef0bacc42310", "createdDate": "2024-05-17T16:30:26Z", "creatorId": "658079d5374a6c533936afa8", "description": "", "enabled": true, "expiry": "", "insightLink": "", "name": "US Sales Overview and Product Details", "ownerId": "658079d5374a6c533936afa8", "resourceId": "66478621f5cee84514946139", "resourceLink": "", "resourceType": "sharing-task", "sharingTaskType": "sheet-sharing", "sheetCount": 2, "spaceId": "", "thumbnail": "/api/v1/sharing-tasks/66478621f5cee84514946139/executions/latest/files/", "transports": null }, "eventId": "1f725851-2526-4aaa-9387-ac5d19fb", "eventTime": "2024-07-16T16:29:34Z", "eventType": "com.qlik.sharing-task.updated", "eventTypeVersion": "1.0", "source": "com.qlik/sharing", "tenantId": "<tenant>", "userId": "", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/66969fee79c1c5c9c01f2222" }, "self": { "href": "https://<tenant>/api/v1/audits/66969fee79c1c5c9c01f2222" } } }
These events surface when a user selects the share > image and enters an email address of their choice. An email will be sent containing an image of the chart in the users session to the entered recipient(s).
{ "id": "6696e3a747e1fa3e822422a7", "contentType": "application/json", "data": { "appIds": [ "09eea519-a69c-456e-8790-ef0bacc42310" ], "endTime": "2024-07-16T21:18:31.797924952Z", "reportId": "0385f4fa-c0a5-4fa9-a5e6-550b48d4b652:0", "requestId": "0385f4fa-c0a5-4fa9-a5e6-550b48d4b652", "startTime": "2024-07-16T21:18:28.350152565Z", "success": true, "tags": [ "share.execution" ], "templateType": "sense-image-1.0", "traceId": "9c0695b2802a7e1957adde8571d80b46", "version": "1.0.0" }, "eventId": "e4bc1bea-d433-49f2-8ef4-4f8329f6", "eventTime": "2024-07-16T21:18:31.802Z", "eventType": "com.qlik.v1.reporting-service.audit", "eventTypeVersion": "1.0.0", "source": "com.qlik/reporting-service", "tenantId": "<tenant>", "userId": "658079d5374a6c533936afa8", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/6696e3a747e1fa3e822422a7" }, "self": { "href": "https://<tenant>/api/v1/audits/6696e3a747e1fa3e822422a7" } } }
Share an image
Attribute |
Value |
Description |
templateType |
Sense-image-1.0 |
image |
Related: Sharing of images are executed by a one-time task - the task event information is found with the event type = com.qlik.sharing-task.created.
{ "id": "66953c96e5a6921af0723fea", "contentType": "application/json", "data": { "creator": "658079d5374a6c533936afa8", "notification": { "resourcetype": "chart", "trigger": "onetime-tasks" }, "recipientCount": 1, "transports": [ "Email" ] }, "eventId": "2fe569ff-c25e-4437-bc9e-315ac0ffd7fb", "eventTime": "2024-07-15T15:13:26Z", "eventType": "com.qlik.sharing.created", "eventTypeVersion": "1.0", "source": "com.qlik/sharing", "tenantId": "<tenant>", "userId": "", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/66953c96e5a6921af0723fea" }, "self": { "href": "https://<tenant>/api/v1/audits/66953c96e5a6921af0723fea" } }
Report (file) production events are found by filtering within the Management Console > Events on the Event Type = com.qlik.v1.reporting-service.audit.
Advance sheet/object composition reports are produced with the reporting execution type composition-1.0 from one of two sources - Qlik Application Automation or Public API.
For associated task information with reports produced from Qlik Application Automation use the associated task history view within Qlik Application Automation. Qlik Cloud has no additional visibility of events produced by integrated systems that use the public.api.
{ "id": "6696ce0079c1c5c9c02b4b01", "contentType": "application/json", "data": { "appIds": [ "1af4b714-2775-4953-83b8-987c0774c5c6" ], "endTime": "2024-07-16T19:46:08.764518686Z", "reportId": "5be4a6a3-ef5f-4c6c-b017-282c961cb358:0", "requestId": "5be4a6a3-ef5f-4c6c-b017-282c961cb358", "startTime": "2024-07-16T19:45:49.67199137Z", "success": true, "tags": [ "automation.execution" ], "templateType": "composition-1.0", "traceId": "3d4186dfc1ca6aabbd53186a50b4b455", "version": "1.0.0" }, "eventId": "1112234b-eb09-4669-9428-4a6b50d9", "eventTime": "2024-07-16T19:46:08.772Z", "eventType": "com.qlik.v1.reporting-service.audit", "eventTypeVersion": "1.0.0", "source": "com.qlik/reporting-service", "tenantId": "<tenant>", "userId": "658079d5374a6c533936afa8", "links": { "Self": { "Href": "https://<tenant>.us.qlikcloud.com/api/v1/audits/6696ce0079c1c5c9c02b4b01" }, "self": { "href": "https://<tenant>.us.qlikcloud.com/api/v1/audits/6696ce0079c1c5c9c02b4b01" } } }
Qlik Application Automation - reports
Attribute |
Value |
Description |
tags |
automation.execution |
Use of the report block in an automation triggers this call and uses the template type composition-1.0. This is a metered event against the Qlik Reporting Service |
Public API - reports
Attribute |
Value |
Description |
tags |
public.api |
Public api use of the reporting service template type composition-1.0 method is a metered event against the Qlik Reporting Service |
Tabular reports are produced during authoring, task execution, on-demand or even api.
{ "id": "668ea84a3b6614357241c921", "contentType": "application/json", "data": { "appIds": [ "09eea519-a69c-456e-8790-ef0bacc42310" ], "endTime": "2024-07-10T15:27:06.093116069Z", "reportId": "41957445-f17b-499b-b65a-695619337e55:0", "requestId": "41957445-f17b-499b-b65a-695619337e55", "startTime": "2024-07-10T15:26:48.879380599Z", "success": true, "tags": [ "reporttask.execution" ], "templateType": "sense-excel-template-1.0", "traceId": "30b27fec6e342c3c204bf194e2d25498", "version": "1.0.0" }, "eventId": "430146ea-5c0c-42cc-bd4f-687de440", "eventTime": "2024-07-10T15:27:06.097Z", "eventType": "com.qlik.v1.reporting-service.audit", "eventTypeVersion": "1.0.0", "source": "com.qlik/reporting-service", "tenantId": "<tenant>", "userId": "uzWYcE_cOycXMWhuD6BlRKH82I2dI-J8", "links": { "Self": { "Href": "https://<tenant>.us.qlikcloud.com/api/v1/audits/668ea84a3b6614357241c921" }, "self": { "href": "https://<tenant>.us.qlikcloud.com/api/v1/audits/668ea84a3b6614357241c921" } } }
Tabular reporting - task execution
Attribute | Value | Description |
tags | reporttask.execution | Execution by the sharing service. This is a metered event against the Qlik Reporting Service |
Tabular reporting - Qlik add-in preview
Attribute | Value | Description |
tags | excel-addin.download | Preview/download from the xls-addin. This is a metered event against the Qlik Reporting Service |
Tabular reporting - public api execution
Attribute | Value | Description |
tags | Public.api | Generation from a direct api call. This is a metered event against the Qlik Reporting Service |
Tabular reporting, on-demand download
Attribute |
Value |
Description |
templateType |
Sense-excel-template-1.0 |
Tabular report run on-demand. This is a metered event against the monthly Qlik Reporting Service allocation for the tenant |
The users referenced in the audit event varies on a number of factors.
A report task execution can be better understood by filtering within the Management Console > Events on the Event Type = com.qlik.reporting-task.summary.created
{ "id": "6692c82bfc781165f388f0f0", "contentType": "application/json", "data": { "appId": "e9318b86-eef4-40dc-9209-56d563aeaf51", "createdDate": "2023-11-13T19:32:31Z", "creatorId": "uzWYcE_cOycXMWhuD6BlRKH82I2dI-J8", "description": "", "distributionchannels": [ "email" ], "emailRecipientDisabledExternalCount": 0, "emailRecipientDisabledInternalCount": 0, "emailRecipientEnabledExternalCount": 1, "emailRecipientEnabledInternalCount": 4, "emailRecipientsCount": 5, "enabled": true, "error": "", "expiry": "", "failedExecutions": 4, "hassectionaccess": false, "id": "655279cf9b65ec9d88e5e475", "insightLink": "", "name": "PL Value Report", "ownerId": "uzWYcE_cOycXMWhuD6BlRKH82I2dI-J8", "reportingServiceEventId": "e890b0f5-6a5c-4ca7-b0c7-4450e07f02af:0", "resourceId": "655279cf9b65ec9d88e5e475", "resourceLink": "", "resourceType": "reporting-task", "sharingTaskExecutionId": "6692c821827ec440bf7f5278", "sharingTaskOwnerId": "uzWYcE_cOycXMWhuD6BlRKH82I2dI-J8", "sharingTaskType": "template-sharing", "spaceId": "6552705a2d187abbfe607291", "status": "FAILED", "successfulExecutions": 1, "taskExecutionId": "6692c821827ec440bf7f5278", "thumbnail": "", "transports": [ "email" ], "typeOfSpace": "shared", "workflowId": "" }, "eventId": "414731b1-15cf-4413-8eb3-fe77f98c", "eventTime": "2024-07-13T18:32:11Z", "eventType": "com.qlik.reporting-task.summary.created", "eventTypeVersion": "1.0", "source": "com.qlik/reporting-task", "tenantId": "<tenant>", "userId": "", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/6692c82bfc781165f388f0f0" }, "self": { "href": "https://<tenant>/api/v1/audits/6692c82bfc781165f388f0f0" } } }
EmailRecipientsCount | The email recipient counts reflect attempted emails sent (see Mail Transport below) |
SuccessfulExecutions |
The number of unique reports created as part of the task - this would be the increment to the Qlik Reporting Service metric. |
Failedexecutions |
The number of failed report creation executions for any reason as part of the submitted task structure. Failures are not counted in the Qlik Reporting Service. |
For those that make use of the Qlik Reporting Service with the integrated report task capability within a Qlik Sense App, a deeper understanding of the related events will be helpful. For a Report Task there are two pre-execution checks:
The net of these pre-checks is that it is not possible to do a reliable sum-check on recipients vs reporting-service events.
Data Alert events are found by filtering within the Management Console > Events on the Event Type =com.qlik.alerting-task.execution-summary.created.
Note that the Data Alert feature is designed to automatically produce a CSV attachment if the number of rows meeting the event are greater than a certain number (refer to feature documentation for the more). There is no tracking of this CSV file, it is produced within the Alert service.
{ "id": "66963df32ea1bb46a72a930b", "contentType": "application/json", "data": { "alertId": "664785f7f5cee8451494610c", "alertName": "Quarterly YOY Performance", "summary": { "accessMode": "TARGET_ACCESS", "alertId": "664785f7f5cee8451494610c", "alertName": "Quarterly YOY Performance", "complete": true, "disabledRecipientsCount": 0, "failedExecutionsCount": 1, "failedExecutionsRecipientsInfo": [ { "alertingTaskRecipientErrors": [], "userId": "ugzEPnk6mF9_iRFoGF7NUmX3CIYXUO6H" } ], "ownerId": "658079d5374a6c533936afa8", "successfulExecutionsCount": 3, "tenantId": "5rTVZhiekEho5Om7w3bdyfGtmwX8BumO", "totalRecipientCount": 4, "workflowId": "308d069c-acaf-456a-b9a1-0a42d2876e0b" }, "tracking": { "alertId": "664785f7f5cee8451494610c", "workflowId": "308d069c-acaf-456a-b9a1-0a42d2876e0b" } }, "eventId": "335b25c5-1fe0-4302-9241-89bfde4d", "eventTime": "2024-07-16T09:31:31Z", "eventType": "com.qlik.alerting-task.execution-summary.created", "eventTypeVersion": "1.0", "source": "com.qlik/alerting", "tenantId": "<tenant>", "userId": "", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/66963df32ea1bb46a72a930b" }, "self": { "href": "https://<tenant>/api/v1/audits/66963df32ea1bb46a72a930b" } } }
Another event that may be relevant to distribution use cases like Subscriptions, Tabular Reporting or Data Alerts is the transport event found by filtering within the Management Console > Events on the Event Type = com.qlik.transport-response.email.sent. The event indicates that a connection was made and the payload was passed to the SMTP service. This event has no knowledge of any SMTP service processing of the payload.
{ "id": "66969fef2ea1bb46a740a013", "contentType": "application/json", "data": { "accepted": [ "6437fea62c33a33f8e579163" ], "connectionFailed": false, "failure": false, "message": "250 Ok: queued as gYcCT7j0RVWVG1Rov1RxXQ", "rejected": [], "requestId": null, "serviceProvider": "classicSMTP", "smtpResponseCode": 250, "tracking": null }, "eventId": "iqyjh8tg1Kgb9EeBgKrwcCuY3voqHrgz", "eventTime": "2024-07-16T16:29:35.035Z", "eventType": "com.qlik.transport-response.email.sent", "eventTypeVersion": "1.0", "source": "com.qlik/transport", "tenantId": "<tenant>", "userId": "", "links": { "Self": { "Href": "https://<tenant>/api/v1/audits/66969fef2ea1bb46a740a013" }, "self": { "href": "https://<tenant>/api/v1/audits/66969fef2ea1bb46a740a013" } } }
A Qlik Account is required to access Qlik portals, software downloads and full access to Qlik.com site resources.
To connect your account to your corporation (accessing product downloads, etc.) the email address domain must match the corporate domain.
The email address cannot be changed after account creation.
A confirmation code has been sent to your email address. You will need the code in the final step.
Please note that in the current and previous Qlik Sense versions it is not possible to download data from the Dynamic Views objects. However it is planned to release this feature in the August 2021 version (on Windows only).
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.
Qlik Customer Portal is currently experiencing login issues. After self-registration, some customers are unable to login to Qlik Customer Portal using their Qlik Account.
We are actively mitigating the issue. We will update this article when fully resolved.
If you need to create a Support Case or contact Support, please contact us through our Support Chat either here on Community, or on Customer Portal (login not required).
When chatting with support, let us know you are experiencing a login trouble with Customer Portal, and please provide the email associated with your Qlik Account.
External users connected through JWT are unable to create ODAG apps from a template. Internal users are able to create apps as expected.
Browser development tools report the following error:
"msgCode": "ODAG-ERR-1143", "replacements": { "appId": "TEMPLATE-APPID", "err": { "name": "RequestError", "message": "The request returned an unexpected result.", "status": 400, "headers": { "cache-control": "private, must-revalidate, max-age=0", "date": "TIMESTAMP", "expires": "TIMESTAMP" }, "body": { "link": {}, "errors": [ { "message": "Bad Request", "status": 400 } ] } } } } ] } } }, "retentionTime": 0, "validation": { "contents": [ "Failed to copy the app: TEMPLATE-APPID", ….. "
A matching error (ODAG-ERR-1143) can be found in the Qlik Sense OdagService logs in C:\Programdata\qlik\sense\log\OdagService\TIMESTAMP.log.
An ODAG Service limitation prevents the duplication of ODAG App templates if the user contains the ‘|’ (pipe) character.
Review JWT integration to avoid "|" (pipe) characters in the username used to identify users on Qlik Sense.
Product Defect ID: QB-27979
Upgrading Qlik Sense Enterprise on Windows does not automatically upgrade the bundled PostgreSQL version. New versions of PostgreSQL are only deployed during a new install. This means upgrading to, for example, Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.
For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:
Content:
The information in this article is provided as-is and to be used at your own 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 process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.
It is highly recommended to test this process in a test environment to get familiar with it.
The first step is to upgrade your environment to Qlik Sense Enterprise on Windows. This article was originally written for May 2021, but can be applied to any version. Follow the required steps and recommendations for an upgrade for your version. Example: August 2023.
Once the upgrade is done make sure your Qlik Sense site is completely operational.
At this point, you have an operational Qlik Sense site running on your new version of Qlik Sense Enterprise on Windows. However, the bundled PostgreSQL is still on version 9.6 or 12.5, depending on the originally installed version.
The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.
You will now need to uninstall Qlik Sense from the central node following these instructions.
During the uninstall:
Now that Qlik Sense Enterprise on Windows is uninstalled on the central node, you will reinstall it as a result will deploy either a bundled PostgreSQL 14.8 (August 2023 and later) or a bundled PostgreSQL 12.5 (May 2021 to May 2023). Instructions available here (choose your version).
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.
You now have a clean Qlik Sense Enterprise on Windows deployed on your central node with PostgreSQL 14.8 or 12.5. You now need to restore your environment to retrieve all your configurations and apps.
Please follow the Restoring a Qlik Sense site (including the certificates).
Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;
pg_restore: warning: errors ignored on restore: 1
Once the environment is restored, you should be able to start your central node and rim nodes successfully.
Qlik Sense Enterprise on Windows May 2021 and later
This article provides step-by-step instructions for implementing Azure AD as an identify provider for Qlik Cloud. We cover configuring an App registration in Azure AD and configuring group support using MS Graph permissions.
It guides the reader through adding the necessary application configuration in Azure AD and Qlik Sense Enterprise SaaS identity provider configuration so that Qlik Sense Enterprise SaaS users may log into a tenant using their Azure AD credentials.
Content:
Throughout this tutorial, some words will be used interchangeably.
The tenant hostname required in this context is the original hostname provided to the Qlik Enterprise SaaS tenant.
Copy the "value of the client secret" and paste it somewhere safe.After saving the configuration the value will become hidden and unavailable.
In the OpenID permissions section, check email, openid, and profile. In the Users section, check user.read.
Failing to grant consent to GroupMember.Read.All may result in errors authenticating to Qlik using Azure AD. Make sure to complete this step before moving on.
In this example, I had to change the email claim to upn to obtain the user's email address from Azure AD. Your results may vary.
While not hard, configuring Azure AD to work with Qlik Sense Enterprise SaaS is not trivial. Most of the legwork to make this authentication scheme work is on the Azure side. However, it's important to note that without making some small tweaks to the IdP configuration in Qlik Sense you may receive a failure or two during the validation process.
For many of you, adding Azure AD means you potentially have a bunch of clean up you need to do to remove legacy groups. Unfortunately, there is no way to do this in the UI but there is an API endpoint for deleting groups. See Deleting guid group values from Qlik Sense Enterprise SaaS for a guide on how to delete groups from a Qlik Sense Enterprise SaaS tenant.
Qlik Cloud: Configure Azure Active Directory as an IdP
A third-party certificate was configured in the Qlik Sense Proxy, but is not being used.
The connection is not private" NET::ERR_CERT_COMMON_NAME_INVALID may be displayed on HUB access.
Qlik Sense Enterprise on Windows uses self-signed and self-generated certificates to protect communication between services, as well as user web traffic to the hub and management console. It is possible to use a third-party-issued SSL certificate to protect client web traffic. Using the self-signed certificate will cause a certificate warning to be displayed in the web browser (such as Google Chrome or Internet Explorer).
If the third-party certificate for the Qlik Sense Proxy Service is not fully compatible with Qlik Sense or it does not have the correct attributes and cyphers, the Qlik Sense Repository Service will revert to using the default certificates. The following error may occur in the Proxy Security logs:
Example: C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\HOSTNAME_Security_Proxy.txt
No private key found for certificate 'CN=qliksense.domain.com' ([CERTIFICATE THUMBPRINT HERE]) Couldn't find a valid ssl certificate with thumbprint [CERTIFICATE THUMBPRINT HERE] Reverting to default Qlik Sense SSLCertificate Set certificate 'CN=qliksenseserver1.domain.com' ([CERTIFICATE THUMBPRINT HERE]) as SSL certificate presented to browser
In order for Qlik Sense Enterprise to correctly recognize the third-party certificate as valid, the certificate will have to meet the following requirements:
Note: Root and Intermediate CA certificates need to be correctly installed. Should any be missing, Qlik Sense proxy will not use the server certificate and will revert back to using the self-signed certificate instead.
Certificates that are known to work well with Qlik Sense have the following attributes:
How to: Change the certificate used by the Qlik Sense Proxy to a custom third party certificate
Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product. This article aims to provide information on where to find information about them or where to download them.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Cloud.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud App Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Reload Analyzer.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Access Evaluator.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
This article shows how to use the Qlik Application Automation Monitoring App. It explains how to set up the load script and how to use the app for monitoring Qlik Application Automation usage statistics for a cloud tenant.
For more information and to download the app and usage instructions, see Qlik Application Automation monitoring app.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
The Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.
Disclaimer: Encrypted communication between PostgreSQL database and Qlik Sense services is a supported setup. This article provides general guidance on how to enable encryption on PostgreSQL database server, but local adjustment must be applied to comply with local IT requirements. Please be aware that Qlik Support can not help setting up Database Traffic Encryption, while Qlik Consulting Services may be utilized for deployment implementation.
Qlik Sense supports database traffic encryption using SSL/TLS, but it is not enabled by default. The Qlik Sense installer cannot use SSL encryption for establishing a connection to PostgreSQL. When SSL encryption is enabled, the installer does not recognize any already installed PostgreSQL databases, and as a consequence, installation cannot be completed. Password security and local IT policy around certificate need to be considered before enabling database encryption, as the implementation includes manual configuration of the Qlik Sense deployment.
Qlik recommends that the configuration in this section is performed by someone with sufficient skills in PostgreSQL database configuration.
This article covers two scenarios for enabling Database Traffic Encryption;
Upgrades: Prior to Qlik Sense Enterprise August 2022 release, the Qlik Sense installer cannot use SSL encryption for establishing a connection to PostgreSQL. So any upgrades will fail unless you are upgrading to August 2022 and later. Prior to upgrading, disable the encryption. You can enable it again after the upgrade is complete.
See Unable to upgrade Qlik Sense with missing 'SenseServices', 'QSMQ', and 'Licenses' database for respective capabilities.
Always take a complete backup of Qlik Sense deployment before altering system configuration, to allow restoring a working state in case of disaster.
These scenarios apply the default Qlik Sense signed certificate to encrypt traffic for a PostgreSQL database. Qlik Sense signed certificate is commonly only fully trusted by Qlik Sense nodes, which means other usage may not comply with local IT policies. It is recommended that a fully trusted certificate is used when applying encrypted database traffic for production environments. Consult the local IT department for details on retrieving a fully trusted certificate.
This scenario assumes a standard Qlik Sense installation, where the Qlik Sense Repository Database is installed on the Qlik Sense central node as part of the Qlik Sense installation.
This scenario assumes a custom Qlik Sense installation, where Qlik Sense is configured to use a dedicated PostgreSQL database as its Repository Database.