Qlik Sense Connectors are missing from the Data source except few REST connectors.

Resolution

Solution 1

Repair Qlik Sense with the Qlik Sense Setup file (identical version).

Solution 2

1. Obtain a copy of the folder "C:\Program Files\Common Files\Qlik\Custom Data\" from a different, but working Qlik Sense Enterprise on a Windows environment (identical version). A test installation can be set up to obtain it.
2. Replace the files/folders with the copied version. This action needs to be carried out on all nodes if it is a multi-node environment.

Solution 3

Encryption keys:

• Verify if the Encryption keys are present in the User's directory.
• Check if you have multiple encryption keys stored in the User's directory.
• Delete and recreate the Encryption keys using Setting an encryption key

Encryption keys will be stored in either "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\" Or "C:\Users\{sense service user}\AppData\Roaming\Qlik\Keys\"

Cause

• The Connector folders or executables are corrupted or deleted.
• Connector folders or executables are being scanned and removed from their path. Therefore, it is mandatory to exclude Qlik folders if any scanning software is present on Qlik Sense Windows machines. For more information about exclusions, please refer to the document titled Qlik Sense Folder And Files To Exclude From Anti-Virus Scanning
• Encryption Keys are either deleted or corrupted.

Related Content

Qlik Sense ODBC Connectors are no longer available after an Upgrade - Error Message Unknown Connection Type. QvOdbcConnectorPackage.exe

An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet

Environment

• Qlik Sense Enterprise on Windows 

***Changes must be made to all Qlik servers that will not be provided with internet access.***

For servers not connected to the internet, they may be prompted with a pop-up error when browsing in the Hub or in the Data Load Editor with the following errors:

• The Hub has continuous bubbles while loading forever
• The Hub is stuck on the initial loading bar

Browser Debug tools may display the following error in the console:

Cause:

This was originally defined as an issue with the Qlik Sense DataMarket connector executable, which is cryptography signed for authenticity verification, and the .NET Framework's verification procedure when launching an executable includes checking OCSP and Certificate Revocation List information, which means fetching it online if the system doesn't have a fresh cached copy locally.

Even without the QlikData Market being in use, the solutions provided can be deployed when encountering issues with Qlik Sense Enterprise Windows servers that have no internet access. Internet access is recommended.  
 

Resolution

Only deploy one of the below options.

Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade. 

Option 1:

1. Stop all Qlik Sense services on all nodes
2. Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config
   1. If there is an empty <runtime/> tag, change it to

      <runtime>     
           <generatePublisherEvidence enabled="false"/>  
      </runtime>

   2. If there is no <runtime/> tag, add the below anywhere above the closing </configuration> tag.

      <runtime>
          <generatePublisherEvidence enabled="false"/> 
      </runtime>

   3. If the <runtime> section has existing content, add generatePublisherEvidence.

      <runtime>
        <some other key="value"/>
        <generatePublisherEvidence enabled="false"/>
      </runtime>

      Example:
      
3. Save machine.config
4. Repeat on all nodes (if applicable)
5. Start services on all nodes

In a Windows multi-node deployment, the App Distribution Service (ADS) distributes apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS. The service is installed on every node. However, Qlik Sense does not have load balancing for ADS, meaning if not all nodes have access to the apps, distribution may fail. See App Distribution from Qlik Sense Enterprise to Qlik Cloud fails when distributed from RIM NODE.

If you wish to disable app distribution from certain nodes:

1. Log on to Qlik Sense node on which you wish to disable App Distribution.
2. Stop the Qlik Sense Dispatcher Service.
3. Open the "C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf" file with Notepad or any text editors.
4. Find the  [appdistributionservice] section and the[hybriddeploymentservice] section. 
5. Disable both by setting it to Disabled=true.
   

   [appdistributionservice]
   Disabled=true
   Identity=Qlik.app-distribution-service
   DisplayName=App Distribution Service
   ExePath=dotnet\dotnet.exe
   UseScript=false
   
   [hybriddeploymentservice]
   Disabled=true
   Identity=Qlik.hybrid-deployment-service
   DisplayName=Hybrid Deployment Service
   ExePath=dotnet\dotnet.exe
   UseScript=false​

6. Save the file.
7. Restart the Qlik Sense Dispatcher Service.

Environment

• Qlik Sense multi-cloud environments. Any versions.

After updating the license, connecting to the Talend Administration Center fails with:

You are using # DI users, but your license allows only #, please contact your account manager.

Resolution

Two solutions exist.

Deactivate Unused Users via Security Account

1. Log in to Qlik Talend Administration Center using a Security Administrator or the default security account.
   
   For information about the default security account, see Change the default password used to configure the database for details. 
2. After logging in, navigate to Settings > Users and deactivate any unused or excess users

Modify Users Directly in Qlik Talend Administration Center Database

1. Access the Qlik Talend Administration Center database directly
2. Locate the user table and review existing users:
   • Identify unused users
   • Verify user types against the new license
3. Update user types to comply with license constraints (e.g., change DQ to DI) or delete unnecessary users

License downgrade behavior: When downgrading licenses (for example, from DQ seats to DI seats), user configurations must also be updated.

• Users previously assigned as DQ must be manually changed to DI
• Failure to update the user type may cause access issues or license mismatches

Cause

The issue occurs due to a mismatch between the number or type of users defined in the system and those allowed by the updated license.

• The Available Users section reflects:
  • The number of users currently created under active licenses
  • The total number of users permitted by those licenses
• After a license update:
  • If the user type and/or user count exceeds the new license limits, the system triggers the error
  • Qlik Talend Administration Center functionality is restricted until the discrepancy is resolved

About User Types and License Seats

In Qlik Talend Administration Center, users are assigned different license seat types depending on their access rights and functional domain.

The main user/license types are:

• DI (Data Integration / ESB user)
  Used for Data Integration and ESB-related activities.
• DQ (Data Quality / Data Management user)
  Used for Data Quality and data stewardship tasks.
• MDM (Master Data Management user)
  Used for Master Data Management domain.
• NPA (No Project Access)
  Users with no project-level access.

For more information regarding license types and features for users, see What domains can you work in depending on your user type and license.

Environment

• Qlik Talend Administration Center

When reaching out to Qlik Support for Qlik Talend Cloud pipeline and data integration issues, you may be asked to provide additional information and logging.

This list is meant to serve as an index for the guides on obtaining requested logs:

1. Tenant ID and URL: Find your Qlik Cloud Subscription ID and Tenant Hostname and ID
2. Data movement gateway repagent and repsrv logs: Troubleshooting Data Movement gateway
3. Export the data pipeline and replication project:
   • Exporting and importing data pipelines
   • Exporting and importing replication projects
4. Export task diagnostics package (only available for Landing and Replication tasks): Qlik Cloud: How to collect Diagnostics Package for Integration Projects
5. Task events log: How to download task event JSON files from Qlik Talend Cloud

Environment

• Qlik Talend Cloud

This article documents how to download the Network Integrations logs to troubleshoot issues occurring with Open Lakehouse in Qlik Talend Cloud.

For information on what permissions are required to view and configure Network Integrations, see Permissions | Network integrations.

To download the logs:

1. Open the Administration Center
2. Navigate to Lakehouse Clusters
3. Click the ellipses menu (...) to the right of the desired integration
   
   
   
   
4. Click View Logs 
   
   

Environment

• Qlik Talend Cloud

To view general project information, click on the (i) icon left of the Show tasks button:

There you will find:

• Project name as the header
• Created date of the project 
• Owner or creator of the project
• Space
• Use case or type of project (data vs replication)
• Data platform
• Connection or target connection used by the project
• Project Id or unique ID that can be requested by Qlik Support during troubleshooting

To view general task information, click on the (i) icon in the top left corner of the task page:

There you will find all of the same information as for the project information (including Created), except the Data task runtime Id which is another unique ID that Support can request for troubleshooting.

Environment

• Qlik Talend Cloud

A Qlik Sense app has been deleted from the Qlik Sense Management Console and needs to be restored.

! Deleting Qlik Sense application from Qlik Management Console (QMC) is generally an irreversible process. Restoring the applications is only possible if a previous backup exists. The delete process removes all files from the configured file share. See Creating a file share (Help.com).

If a backup of the files exists, proceed with the documented steps.

Note that these steps can also be applied when restoring and importing from one Qlik Sense environment to the other. 

Information on server migration has also be posted to Qlik Community: Qlik Sense Migration Part1: Migrating your Entire Qlik Sense Environment. If assistance is needed, Qlik Consulting would need to be engaged. Qlik Support cannot provide walk-through assistance with server migrations outside of a post-installation and migration completion break/fix scenario.

Resolution:

To successfully restore Qlik Sense Application to the Qlik Sense environment, you must ensure backup strategy using your backup software tool for your shared folder, where Qlik Sense Application files are stored.

! If no backups of files are available, no restoration will be possible. 
 

Restore process:

1. Find the App filename

You can find the filename (APP_ID) in the AuditActivity_Engine log.
This log is by default stored in: \\<rootShare>\Log\Engine\Audit\ by default.

An example showing App id followed by App name follows:


492    20.4.2.0    20180521T180500.118+0200    QlikServer1    0ccd5e9f-e020-4b76-a84d-144bdf903765    20180521T180500.112+0200    12.145.3.0    Command=Reload app;Result=0;ResultText=Success    0    0    2290    INTERNAL    sa_scheduler    d296b870-da06-4311-bacc-038992b1c954    c047d8a7-148c-4ea6-97f2-10290e706cd7    License Monitor    Engine    Not available    Doc::DoReloadEx    Reload app    0    Success    0ccd5e9f-e020-4b76-a84d-144bdf903765
 

2. Add extension ".qvf" to the app file

This will make the file readable and importable. 

• Navigate to the file on disk.
• Right-click and click rename 
• Add .qvf as a file extension
• Confirm any warnings that the file may not be accessible any more after renaming

3. Import the App

• Open the Qlik Sense Management Console
• Go to Apps
• Locate and click Import 

•  Locate the file on disk
• Click Open

• Rename the App to the original name

4. App has been imported and received a new APP_ID

You can now locate the app in the shared folder with a new App ID.

5. Find the proper stream where the app resides

6. Go to section "APPS" select the app, hit "Publish"

Click Publish  

The Publishing dialogue:
 

 

7. Hit "Ok", the app is being published - IMPORTED back

8. The confirmation message should now print as Successful in the App list.

Content

• Chapters
• Environment overview
• Zabbix Server set-up
• Clone the Zabbix docker repository
• Setting up environment variables
• Re-link compose.yaml to our preferred compose file
• Logging in for the first time
• Zabbix Agent installation on Windows Server
• Zabbix Server Configuration
• Adding the first Server
• Importing Qlik Sense Enterprise for Windows templates
• Linking templates to hosts
• Engine Healthcheck Monitoring with HTTP Agent example
• Steps to configure a new HTTP Agent for QSE Health monitoring
• Defining the Virtual Proxy prefix for Zabbix HTTP Agent
• Resources & Links

Chapters

• 01:33 - Why use Zabbix
• 02:35 - Architecture for demo
• 03:41 - Downloading the installer
• 04:36 - Installing Zabbix Server
• 08:37 - Installing the Zabbix agent
• 12:17 - Applying Qlik specific templates
• 14:28 - Reviewing Qlik-specific Dashboards
• 16:49 - Configuration details
• 18:42 - How to create a dashboard
• 20:30 - Q&A: Can Zabbix run on Windows?
• 21:16 - Q&A: Is Zabbix supported by Qlik?
• 21:36 - Q&A: Can this monitor data capacity?
• 22:45 - Q&A: Can the Zabbix agents affect performance?
• 23:20 - Q&A: Can it monitor bookmark size?
• 24:02 - Q&A: Can this monitor amount of data being used?
• 24:19 - Q&A: Can this monitor sheets, and objects in apps?
• 24:49 - Q&A: Is there a similar tool for Cloud?
• 25:36 - Q&A: Would this work with QlikView?
• 26:11 - Q&A: Does this read the app data?
• 26:26 - Q&A: Can this help measure how long to open an app?

The information in this article and video is provided as is. If you need assistance with Zabbix, please engage with Zabbix directly.

Environment overview

The environment being demonstrated in this article consists of one Central Node and Two Worker Nodes. Worker 1 is a Consumption node where both Development and Production apps are allowed. Worker 2 is a dedicated Scheduler Worker node where all reloads will be directed. Central Node is acting as a Scheduler Manager.

Zabbix Server set-up

The Zabbix Monitoring appliance can be downloaded and configured in a number of ways, including direct install on a Linux server, OVF templates and self-hosting via Docker or Kubernetes. In this example we will be using Docker. We assume you have a working docker engine running on a server or your local machine. Docker Desktop is a great way to experiment with these images and evaluate whether Zabbix fits in your organisation.

Clone the Zabbix docker repository

This will include all necessary files to get started, including docker compose stack definitions supporting different base images, features and databases, such as MySQL or PostgreSQL. In our example, we will invoke one of the existing Docker compose files which will use PostgreSQL as our database engine.

Source: https://www.zabbix.com/documentation/current/en/manual/installation/containers#docker-compose

git clone https://github.com/zabbix/zabbix-docker.git

Setting up environment variables

Here you can modify environment variables as needed, to change things like the Stack / Composition name, default ports and many other settings supported by Zabbix.

cd ./zabbix-docker/env_vars
ls -la #to list all hidden files (.dotfiles)
nano .env_web

In this file, we will change the value for ZBX_SERVER_NAME to something else, like "Qlik STT - Monitoring". Save the changes and we are ready to start up Zabbix Server.

Re-link compose.yaml to our preferred compose file

./zabbix-docker folder contains many different docker compose templates, either using public images or locally built (latest and local tags).

You can run your chosen base image and database version with:

docker compose -f compose-file.yaml up -d && docker compose logs -f --since 1m

Or unlink and re-create the symbolic link to compose.yaml, which enables managing the stack without specifying a compose file. Run the following commands inside the zabbix-docker folder to use the latest Ubuntu-based image with PostgreSQL database:

1. unlink compose.yaml
2. ln -s ./docker-compose_v3_ubuntu_pgsql_latest.yaml compose.yaml
3. Start the Zabbix stack in detached mode with docker compose up -d

If you skip the -d flag, the Docker stack will start and your command line will be connected to the log output for all containers. The stack will stop if you exit this mode with CTRL+C or by closing the terminal session. Detached mode will run the stack in background. You can still connect to the live log output, pull logs from history, manage the stack state or tear it down using docker compose down.

Pro tip: you will be using docker compose commands often when working with Docker. You can create an alias in most shells to a short-hand, such as "dc = docker compose". This will still accept all following verbs, such as start|stop|restart|up|down|logs and all following flags. docker compose up -d && docker compose logs -f --since 1m would become dc up -d && dc logs -f --since 1m.

Logging in for the first time

• By default, the Zabbix Web GUI will be exposed on ports 80/443
• Using tools like Portainer makes Docker stack management easier

Use the IP address of your Docker host: http://IPADDRESS or https://IPADDRESS.

The Zabbix server stack can be hosted behind a Reverse Proxy.

The default username is Admin and the default password is zabbix. They are case sensitive.

Zabbix Agent installation on Windows Server

Download link: https://www.zabbix.com/download_agents, in this case download the Windows installer MSI.

1. Run the installer .msi
2. Leave components unchanged
3. Hostname = your machine hostname, we will have to use the same hostname when adding a Host in Zabbix Server.
4. Zabbix server IP/DNS: IP address or DNS name of your Zabbix Server
5. Agent listening port, the same port will be used when when adding a Host in Zabbix Server.
6. Enable "Add agent location to the PATH" for convenience in the command line
7. Finish installation

Zabbix Server Configuration

Adding the first Server

After Agent is installed, in Zabbix go to Data Collection > Hosts and click on Create host in the top right-hand corner. Provide details like hostname and port to connect to the Agent, a display name and adjust any other parameters. You can join clusters with Host groups. This makes navigating Zabbix easier.

Fig 1: Adding a Host

 

Note: Remember to change how Zabbix Server will connect to the Agent on this node, either with IP address or DNS. Note that the default IP address points to the Zabbix Server.

Importing Qlik Sense Enterprise for Windows templates

In the Zabbix Web GUI, navigate to Data Collection > Templates and click on the Import button in the top right-hand corner. You can find the templates file at the following download link:

LINK to zabbix templates

Linking templates to hosts

Once you have added all your hosts to the Data Collection section, we can link all Qlik Sense servers in a cluster using the same templates. Zabbix will automatically populate metrics where these performance counters are found. From Data Collection > Hosts, select all your Qlik Sense servers and click on "Mass update". In the dialog that comes up, select the "Link templates" checkbox. Here you can link/replace/unlink templates across many servers in bulk.

Select "Link" and click on the "Select" button. This new panel will let us search for Template groups and make linking a bit easier. The Template Group we provided contains 4 individual templates.

Fig 2: Mass update panel

Fig 3: Search for Template Group

Once you Select and Update on the main panel, all selected Hosts will receive all items contained in the templates, and populate all graphs and Dashboards automatically.

To review your data, navigate to Monitoring > Hosts and click on the "Dashboards" or "Graphs" link for any node, here is the default view when all Qlik Sense templates are linked to a node:

Fig 4: Host Dashboards

 

Fig 5: Repository Service metrics - Example

Engine Healthcheck Monitoring with HTTP Agent example

We will query the Engine Healthcheck end-point on QlikServer3 (our consumer node) and extract usage metrics from by parsing the JSON output.

Steps to configure a new HTTP Agent for QSE Health monitoring

We will be using a new Anonymous Access Virtual Proxy set up on each node. This Virtual Proxy will only Balance on the node it represents, to ensure we extract meaningful metrics from the Engine and we won't be load-balanced by the Proxy service across multiple nodes. There won't be a way to determine which node is responding, without looking at DevTools in your browser. You can also use Header or Certificate authentication in the HTTP Agent configuration.

Once the Virtual Proxy is configured with Anonymous Only access, we can use this new prefix to configure our HTTP Agent in Zabbix.

Defining the Virtual Proxy prefix for Zabbix HTTP Agent

In the Zabbix web GUI, go to Data collection > Hosts. Click on any of your hosts. On tabs at the top of the pop-up, click on Macros and click on the "Inherited and host macros" button. Once the list has loaded, search for the following Macro: {$VP_PREFIX}. This is set by default to "anon". Click on "Change" and set Macro value to your custom Virtual Proxy Prefix for Engine diagnostics, and click Update. The Virtual Proxy prefix will have to be changed on each node for the "Engine Performance via HTTP Agent" item to work. Alterantively, you can modify the MACRO value for the Template, this will replicate the changes across all nodes associated to this Template.

To make this change at the Template level, go to Data collection > Templates. Search for the "Engine Performance via HTTP Agent" and click on the Template. Navigate to the Macros tab in the pop-up and add your Virtual Proxy Prefix here to make this the new default for your environment. No further changes to Node configuration are required at this point.

The Zabbix templates provided in this article contain the following Engine metric JSONParsers:

• Memory: Allocated, Committed, Free, Total Physical
• Calls, Selections
• Saturation status (true/false)
• Sessions: Active/Total
• Users: Active/Total

These are the same performance counters that you can see in the Engine Health section in QMC.

Stay tuned to new releases of the Monitoring Templates. Feel free to customise these to your needs and share with the Community.

Resources & Links

• Zabbix home page
• Zabbix Installation from containers documentation
• Zabbix Docker repository on GitHub
• Install Docker Engine on Ubuntu

Environment

• Qlik Sense Enterprise on Windows

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor, License Monitor, and Content Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

You can automate daily distribution of the latest app using the Capacity consumption app deployer template in Qlik Automate.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

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:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all 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.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor, License Monitor, and Content Monitor

The Operations Monitor loads service logs to populate charts covering the 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. 

• Basic information can be found in Operations Monitor | help.qlik.com
• Detailed descriptions of sheets and visualizations are accessible in the About the Operations Monitor story available from the app overview page under Stories

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

• Basic information can be found in License Monitor | help.qlik.com  
• Detailed descriptions of sheets and visualizations are accessible in the About the License Monitor story available from the app overview page under Stories

The Content Monitor loads from the APIs and logs to present key metrics on the content, configuration, and usage of the platform, allowing administrators to understand the evolution and origin of specific behaviors of the platform.

• Basic information can be found in Content Monitor | help.qlik.com  
• Each sheet in the Content Monitor includes an About text box to describe its content. 
  

All three apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor | Content Monitor (download page). Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

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.

The Monitoring & Administration Topic Group

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.

Monitoring & Administration 

Other Apps

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.

According to the Qlik Cloud Platform document, Qlik leverages our cloud providers for backups to maintain copies of content for 30 days.

Can I restore one of those backups?

No, those backups cannot be restored. They are kept for disaster recovery purposes (see Disaster recovery/backup and recovery) and encompass entire regions. 

It's therefore not possible to recover a tenant's previous stage.

It's the tenant admin's responsibility to make sure that copies of the content are regularly backed up on any platform of choice for easy restoration. See Qlik Cloud Administration: Backup Responsibilities for details. 

Environment

• Qlik Cloud Analytics

In some instances, when a user shares a single app using the Share > Invite or Share > Manage Access option, the entire space is shared as well. 

Resolution

There are two possible root causes. Both are triggered by the user not having the correct permissions to share an app, but having permissions to share the space. In this instance, the system defaults to sharing the whole space. 

Qlik is working on an improvement to clarify what you are sharing, meaning you will be alerted you are sharing the space in the future. 

The two scenarios:

• Sharing applications via fine-grained access control is disabled in the User default or for the user.
  
  This affects all spaces.
  
  
  
  To resolve this, either enable it globally or create a custom role that allows the use of fine-grained access control. See Managing custom roles.
  
  
• The user is a tenant admin, allowing them to share spaces, but is not the owner of the space and does not have Can Manage permissions.
  
  This affects specific spaces.
  
  To resolve this, grant the user Can Manage permissions on the space or make them the owner.

  While this is currently by design, Qlik plans to change this behaviour in the upcoming feature to make this action unnecessary.

Environment

• Qlik Cloud Analytics

Qlik Cloud includes robust disaster recovery and backup mechanisms for active tenant data. See Adaptive high-availability infrastructure for details.

However, this does not mean data that has been deleted by the customer is being retained. Any intentionally or accidentally deleted Qlik Cloud data cannot be recovered by Qlik. See Qlik Cloud Analytics: Is it Possible to Recover a Deleted App or Sheet?

To prevent data loss, customers are responsible for implementing their own backup strategy for any content that may be removed. This includes apps, sheets, and spaces within the Qlik Cloud environment.

How to Back Up Qlik Cloud Apps

There are several ways to back up Qlik Cloud content:

• Qlik Automate
• Qlik CLI
• Qlik REST APIs
• Third-party solutions

Qlik Automate

Qlik Automate supports the creation of workflows that regularly back up apps within Qlik Cloud. These workflows can, for example, be configured to export apps to external storage, synchronize content between spaces, or integrate with version control systems.

Here are some helpful resources to get started:

• CI/CD pipelines for Qlik Sense apps with automations and GitHub
• How to export a Qlik Sense app without data to an Amazon S3 bucket and import an app from a file on Amazon S3
• How to export Qlik Sense Apps from source to a target shared space using Qlik Application Automation

These automations can be tailored to meet organizational backup requirements and integrated into broader content management strategies.

Qlik CLI

Qlik CLI enables app exports using command-line tools.

For more information regarding Qlik CLI, please see this introduction on the Qlik Developer Portal.

With Qlik CLI installed, the “qlik app export <appId> [flags]” command can be used to export an app. More information about the command and its available flags can be found on its Qlik Developer Portal page.

Qlik REST APIs

The public Qlik REST APIs can be used to build a more customized, local solution.

Using the POST /api/v1/apps/{appId}/export endpoint returns a "Location" header with the download URL for the exported app.

Third-party solutions

External tools that integrate with Qlik Cloud can also be used to back up apps. Please note that third-party solutions are not supported by Qlik Support.

Environment

• Qlik Cloud

This article provides details about the new permissions available for Private automations, which will replace the previous Automation Creator role.

You can assign these permissions to a custom role or the User Default. More information about creating & managing custom roles is available here.

The existing Automation Creator role will be deprecated later in 2026.

Private automations

These permissions allow users to run and create automations in their personal space.

Shared automations

Earlier in 2025, we introduced the shared automation permission that allows users to run, create, and manage automations in shared spaces in which they have the correct permissions. More information about which space roles are required for the various automation actions is available here:

• Full & Professional users
• Analyzer users

Qlik Talend Cloud tasks do not offer logging at the task level for Storage and further downstream tasks. For those tasks, specifically, support may request Task Event files to troubleshoot various issues, which are especially helpful for troubleshooting downstream tables that are in error or not progressing as expected. Often the event files from the impacted task and its source or predecessor task will be requested.

In this article, we will guide you through how to download the event logs:

1. Navigate task's Monitor tab
   
    

   

2. Place the mouse cursor in the space between the Run button and the task status (such as Running, Completed, Stopped), then:
   
   
   • (on Windows) hold CTRL+ALT and double left-click the mouse
   • (on Mac) hold Command+Option and double left-click the mouse
     
      
      

     

      

3. The downloads will begin automatically and fetch four files:
   
   
   
   For some tasks, the following pop-up will appear. Unless instructed otherwise by Support, click OK:
   
    

   

Environment

• Qlik Talend Cloud

This article explains how to obtain a task schedule in the Talend Management Console, how to pause it, and how to resume it. All steps are performed using the API.

In the example, we use the following values:

• The Environment ID: 5b0431e2ee7c2b4082797c73
• Task ID: 698ba125c327f6c153585c67
• %TOKEN% is to be replaced by your actual bearer's token
• The API URL used in each example is set to the EU region, api.eu.cloud.talend.com. Update the region accordingly. 
• The schedule is set from: 1772628971000 to 1775220971000, which is the 3rd of March 2026 to the 3rd of April 2026 in milliseconds since January 1st 1970. Use epochconverter.com to convert date and time to epoch time. 

Content

• Getting a task schedule
• Pausing a task
• Resuming a task
• Pausing and resuming a plan

Getting a task schedule

First, we get the scheduling of a task. 

The following Qlik Talend API can be used to retrieve the executions scheduled in a time window using the "from" and "to" parameters: Get scheduled executions 

Get scheduled executions of all types

POST /orchestration/executables/events/search

Example: 

curl -v -X POST ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"environmentId\":\"5b0431e2ee7c2b4082797c73\",\"from\":\"1772628971000\",\"to\":\"1775220971000\"}" ^
https://api.eu.cloud.talend.com/orchestration/executables/events/search

The API returns a maximum of 100 entries by default. The parameter "offset" can be used to retrieve the next entries.

Example with "offset": 

curl -v -X POST ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"environmentId\":\"5b0431e2ee7c2b4082797c73\",\"from\":\"1772628971000\",\"to\":\"1775220971000\",\"offset\":100}" ^
https://api.eu.cloud.talend.com/orchestration/executables/events/search

To retrieve all the entries, increase the "offset" value to the total value returned by the call that is lower than the limit value.

Pausing a task

Next, we pause the task.

The following Qlik Talend API can be used to pause a task: Pause / Resume a Task

Pause / Resume a Task

PUT /orchestration/executables/tasks/{taskId}/pause

Example:

curl -v -X PUT ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"pause\":true,\"pauseContext\":\"Pause during the maintenance window\"}" ^
https://api.eu.cloud.talend.com/orchestration/executables/tasks/698ba125c327f6c153585c67/pause

Resuming a task

We now set the task to resume.

The following Qlik Talend API can be used to resume a task: Pause / Resume a Task

Pause / Resume a Task

PUT /orchestration/executables/tasks/{taskId}/pause

Example:

curl -v -X PUT ^
-H  "Content-Type: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"pause\":false}" ^
https://api.eu.cloud.talend.com/orchestration/executables/tasks/698ba125c327f6c153585c67/pause

Pausing and resuming a plan

To pause and resume a plan, the following Qlik Talend API can be used: Pause-Resume Plan executions

Pause-Resume Plan executions

PUT /orchestration/executables/plans/{planId}/pause

Environment

• Qlik Talend Cloud
• Qlik Talend Management Console

A newly created user in Talend Cloud may not receive the expected welcome email if the user was created in the Qlik Talend Management Console. 

Other email notifications are received correctly, such as when resetting an existing user account. 

Resolution

The issue is typically related to role permissions, email notification settings, or SSO configuration in the Qlik Talend Cloud Management Console.

1. Verify User Role Permissions
   
   The account used to create the new user must have the Infrastructure Administrator role. Without this role, the user creation may succeed, but notification emails will not be triggered.
   
   
2. Verify Email Notification Settings
   
   

   Ensure that the “User has been created” notification is selected:

   1. Log in to Talend Cloud Management Console
   2. Go to Profile preferences and then the Notifications option
   3. Confirm that “User has been created” is selected
      
      
      
      If this notification is not selected, no email will be sent when a new user is created.
      
      
3. Check SSO Configuration (Important)
   
   

   If Single Sign-On (SSO) is enabled for Talend Cloud, newly created users will not automatically receive activation emails.

   To trigger the notification email:

   1. Temporarily disable SSO. SSO can be disabled by navigating to the Qlik Talend Management Console > Users > Authentication
   2. After disabling SSO, create the user
   3. Click "Send Invitation” to activate the user account
   4. Once SSO is disabled and the invitation is sent, the notification email will be delivered correctly.

Related Content

• Talend Management Console email notifications 
• Enabling email notifications

Environment

• Qlik Talend Cloud
• Qlik Talend Management Console

Qlik Sense may be unable to access the Qlik Sense Management Console (QMC) and/or HUB. You will find below some guidance explaining how to troubleshoot those.

To start your troubleshooting you will need to clearly identify your issue: 

• Is the issue only regarding the HUB?
• Is the issue only regarding the QMC?
• Is the issue regarding both the QMC and the HUB?

In this troubleshooting guide we will talk about the third scenario where you are unable to open neither the Qlik Sense Management Console (QMC) and the HUB

As a second steps to identify your issue, you will need to answer the three following questions:

• Is this issue has started occurring after a fresh installation or an upgrade of the product without having worked before?
• Is this issue occurring on a random basis from time to time? 

We will discuss the following two scenarios below.

Below is a provided list of article containing specific root causes that that could help you after following the above steps: 

No Hub or QMC access after upgrade to Sense November 2017 or higher - recursive script
How to approach Qlik Sense Error 404 when access Hub/QMC
Qlik Sense: Cannot access QMC or Hub. Error in repository log: implementation not part of Windows FIPS validated cryptographic algorithms
Qlik Sense Installation successful but problem opening QMC/HUB
Can't access Qlik Sense QMC or HUB using local service account
Cannot open Qlik Sense Management Console or hub after upgrade - RootFolder and AppFolder are not defined at startup 
Qlik Sense Management Console (QMC) and Hub are not accessible and connection to QRS Database times out after 90 seconds 

Resolution

General verification

Before starting to investigate deeper into the issue you need to apply some basic steps to troubleshoot:

• Verify general network connectivity. Qlik Sense relies on the usage of WebSockets, which may be blocked. See How to troubleshoot web socket issue for Qlik Sense? for details. 
• Are you following the minimal requirements (Please make sure you select the correct version). 
• Are the Qlik Sense services up and running? => Try to start and restart them to see if it comes back up and running. (You might need to wait a few minutes before the services become operational)
• Are you using the correct URL to access the Qlik Sense Management (QMC) and HUB? => You can try to access them connected remotely to the Qlik Sense Server by accessing the URL https://localhost/qmc or https://localhost/hub. If this works you might have a DNS and/or a network issue.
• Do you have connectivity to the Qlik Sense Server from the machine you are attempting to connect?  Verify with a network ping and/or telnet to Qlik Sense on the relevant ports. Please see How To Check Open Ports Using PowerShell and the relevant version help site.  

The issue has started occurring after a fresh installation or an upgrade of the product without having worked before

If after checking the above points you still experience issues, you need to know that to start properly, the Qlik Sense Management Console will need to have few services properly working: 

• The Qlik Sense Repository Database
• The Qlik Sense Repository Service
• The Qlik Sense Dispatcher
• The Qlik Sense Proxy

To verify if those services are actually functioning correctly, you will need to check their logs.
Start by looking into the Qlik Sense Repository logs stored by default in C:\Programdata\Qlik\Sense\Log\Repository\Trace\Servername_System_Repository.txt. (You might want to restart the services before looking into this log to get fresh information)

If the Qlik Sense Repository Database and Service starts correctly you are basically looking at the following string in this logs (It might take few minute to initialize after a service restart)
Startup phase completed

If you do not find this string in the logs, then you will likely need to search for the first ERROR and/or WARN showing in this logs. You can then grab the content of the message and search it in our knowledge base

However if you find this string in the logs, the next step is to check the Qlik Sense Proxy logs stored by default in C:\Programdata\Qlik\Sense\Log\Proxy\Trace\Servername_System_Proxy.txt
Once again we would recommend to restart the Qlik Sense Proxy Service before looking into the logs to get fresh information.

In this log you might see few errors at the beginning saying
When contacting https://localhost:4242/    No connection could be made because the target machine actively refused it 127.0.0.1:4242
Could not contact local repository to retrieve local server node configuration    No connection could be made because the target machine actively refused it 127.0.0.1:4242

Those will be expected since the Qlik Sense Proxy service will try to connect to the Qlik Sense Repository Service, so as long as the startup phase is not completed for the Qlik Sense Repository service you will keep getting those events in the logs.
Basically if the Qlik Sense Proxy service is starting correctly you should expect the following event in the logs: 

Proxy is running

As for the Qlik Sense Repository if you do not find this string in the logs, then you will likely need to search for the first ERROR and/or WARN showing in these logs. You can then grab the content of the message and search it in our knowledge base.

E.g. Here is an example of the types of error you can get in the Qlik Sense logs: 

Proxy will NOT be listening to port 443, likely bound by another process An attempt was made to access a socket in a way forbidden by its access permissions.

The above steps should help you to investigate the root cause of your issue for this scenario.

The issue occurs on a random basis from time to time

In the following scenario we are more looking into an environment issue such as network connectivity, resource overload, ...
The first step would be to check the Qlik Sense Repository Service and Proxy logs as described above to find any relevant ERROR and/or WARN that could explain the root cause. 

Then you can start looking into the Windows Event logs (Application and System) to find any problem at a system level around the time you are getting this issue.

Below are common causes/events that you could find in those logs: 

• Memory starvation Windows successfully diagnosed a low virtual memory condition?
• Network issue The network link is down.  Check to make sure the network cable is properly connected

Those types of event require often to involve your system and/or network and/or virtualization team for further troubleshooting.

In addition you can run a performance monitor to check the resource consumption on your machine following How to log CPU and memory with Microsoft Performance Monitor on a windows 2012 Server (PerfMon)