The reload task fails with a message like this in the document log:

or

           2017-11-10 10:16:48 0454       WHERE isnum(Sequence#)
            2017-11-10 10:16:48      Error: Field 'Sequence#' not found
            2017-11-10 10:16:48      Execution Failed
            2017-11-10 10:16:48      Execution finished.

or
 

Sequence# field not found in 'lib://SHARE/Repository/Trace/SERVERNAME_Synchronization_Repository.txt' 

The steps below apply where it cannot find any field. The field that cannot be found includes but is not limited to CounterName, ProxySessionID.

Environment:

• Qlik Sense Enterprise on Windows and Qlik Sense Monitoring apps

Cause:

QLIK-35804: Occasionally when Qlik Sense services stop, they do not fully write to the logs in the expected format. 

Resolution:

Services need a restart

Restart the Qlik Sense services 

Last stop of services did not write logs in the expected format

Modify the License and Operations Monitor apps such that it will continue parsing logs even if it fails to fully parse a particular log.

1. When logged in to the server, import a new copy of the problematic app from C:\ProgramData\Qlik\Sense\Repository\DefaultApps (You will need to give it a new name, i.e. License Monitor (New))
2. Go to the Hub to the My Work section and open the application
3. Click on Open to go to the Data Load Editor
4. Go to the Run Logic section
5. It will initially look like below. For reference, the screenshots are from the Operations Monitor but the principle applies to the License Monitor as well even though the load script will look slightly different.
   
6. Wrap the section labelled working: with the following code:

   //begin ignoring errors parsing logs
   set errormode = 0;

   and 

   //end ignoring errors parsing logs
   set errormode = 1;

   This will look something like this:
   
   
7. Save the file
8. Reload from the Hub or QMC
   1. From the Hub: Click on the Load Data icon in the upper right hand corner
   2. From the QMC: Apps > Select the new License or Operations Monitor App > More Actions > Reload Now
9. Ensure that it has reloaded successfully
10. Delete the original License or Operations Monitor app
11. Rename the new copy, i.e. License Monitor (New) will be renamed to License Monitor
12. Publish the new app to the Monitoring Apps stream
13. Create a reload task to reload the new app. The default reload schedule for the default apps is to reload every hour, but you can set to this to be as frequent as your needs require.

Cannot log in to Qlik Talend Administration Center. Login fails with:

Error: 500, The call failed on the server; see server log for details

The log file reports:

ERROR SqlExceptionHelper - The MySQL server is running with the LOCK_WRITE_GROWTH option so it cannot execute this statement

Resolution

Expand cloud storage for MySQL or perform a data cleanup to free up the space required.

Cause

Cloud MySQL has reached the cloud storage quota during data writes. 

Environment

• Qlik Talend Administration Center

This article aims to explain the use of the dev:dump-create command. The output of the command creates a compressed file containing the latest logs, bundle, and feature statuses, along with a heap dump file. This can be used to help troubleshoot an ESB Runtime container.

To run the command:

1. Open the Runtime console.
   • If the service is already running, in the Runtime container's "bin" folder, run the "client" script.
   • If the Runtime is not active, run the "trun" script.
2. Execute this command: 
   

   dev:dump-create

   
   
   
   The execution may take a few seconds.
   
   If you want to exclude the head dump file, leading to a smaller file and quicker execution, use this optional flag:
   

   --no-heap-dump

   
   
   
   
3. A dump zip will be located in the main folder of the Runtime container:
   
   

The dump file includes:

• Latest logs: audit.log, em.log, tesb.log
• bundles.txt
• environment.txt
• features.txt
• heapdump.hprof (VisualVM can be used to view this file)
• memory.txt
• threads.txt

Related Content

• Dev Scope | Talend ESB Container Administration Guide 
• Github README for Karaf container

Environment

• Qlik Talend ESB

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.

The Qlik ODBC Connector Package log analyzer app is an easy-to-set-up app meant to assist in troubleshooting ODBC Connector issues for Qlik Sense Enterprise on Windows (on-prem).

This short guide documents how to configure and use the app in your own environment for both analysis and learning purposes. 

Content

• Requirements
• Setup
• App Content

Requirements

To get as much information as possible and leverage the app at its fullest, set the following two log settings in the QvOdbcConnectorPackage.exe.config file. The file is typically found in C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage.

• LoggingLevel set to ALL
• LogSQLStatements set to true
  
  

Setup

1. Download the Qlik ODBC Connector Package log analyzer app, either from the article directly or from our file share. 
2. Import the Qlik ODBC Connector Package log analyzer app to your Qlik Sense environment
3. Open the app from the hub
4. Go to the Data Load Editor 
5. Open the config tab
6. Define a lib connection for your ODBC connector package log file
   
   
   
   
   
7. Reload the Qlik ODBC Connector Package log analyzer app

App Content

The first sheet opens with aggregated information and KPIs.

What you will find here:

• Connector Package version
• ApplicationId: The applications using the ODBC Connector Package connectors
• Logging Level: The applied ODBC Connector Package logging level
• HostName
• Start time: The start timestamp of the logging
• End time: The end timestamp of the logging
• Date: The logged dates
• UserId: The logged user IDs
• Count of errors and Count of warnings: The number of logged errors and warnings
• Connector activity during the day: A chart showing during what time ODBC connectors have been used
• Connector activity by days: A chart showing during which days ODBC connectors have been used
• Max query data size reloaded: KPI showing the maximum data size reloaded by an executed query within a logged reloadID
• Max query reload time: KPI showing the maximum time of all the logged and executed queries
• Data source usage: A table showing the count of connections, count of used apps, count of errors, and the sum of the data size of all reloaded data by data source
• Command pipe: A list of all command pipes. Command pipes are the basis for an ODBC Connector Package activity. A command pipe is created every time the Data Load Editor is opened and the ODBC connections are loaded, as well as when a new ODBC connection is created, if a connection test is performed, and when data is previewed or reloaded. 
• RequestId: A command pipe can have different kinds of request IDs. For more details, see the Connector process details section.
• Num command pipes: The number of command pipes
• Number of apps: The total number of apps using some form of ODBC connection

The first sheet also shows additional details supplementing the initial charts and KPIs.

What you will find here:

• Connector process details: Filtering by a specific Command pipe allows for an overview of all messages and requests for that specific command pipe sorted by timestamp
• Database and connection string details: A table showing the type of data source, database version (if available), and the used connection string
• Overview of reload executions: A table showing which SQL statements have been executed in which request and command pipe. Also contains other details, such as timestamps, query time, reloaded data size, data source, rows fetched, etc...

The second sheet begins with a summary of errors and warnings.

What you will find here:

• A list of errors, warnings, and exceptions by command pipe and sorted by timestamp.
• The exact message and which app has been impacted

Following the error analysis, the app lists information about Advanced parameters and connection details.

What you will find here:

• The connection details are broken down by connection string parameters and can be filtered by command pipe. This allows you to review which reload used which connection string parameters and advanced parameters.

The last section of the second sheet displays table field details.

What you will find here:

• Data type information by executed SQL query, command pipe, application ID, and data source.

The Qlik ODBC Connector Package log analyzer app is provided as-is. No ongoing support will be provided by Qlik Support. For questions and to engage with your active Qlik peers on the subject, head over to Management & Governance.

Environment

• Qlik ODBC Connector Package
• Qlik Sense Enterprise on Windows

This article explains how to change the log level for the QvWebStorageProviderConnector in Qlik Sense Enterprise on Windows.

Always back up .config files before making changes.

To change the log level of your QvWebStorageProviderConnectorPackage to debug mode:

1. Browse to %Program Files%Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage
2. Locate deploy.config
3. Open deploy.config file in a text editor with elevated permissions (Administrator)
4. Locate the <LoggingLevel> section:
   

   <!-- Valid values: Off, Error, Warn, Info, Trace - We would recommend you have at least Error set.
   --> 
   <LoggingLevel>Info</LoggingLevel>

5. Change the field Info to Trace
   
   Example:

   <LoggingLevel>Trace</LoggingLevel>

6. Save the file
7. Restart all Qlik Sense services

Environment

• Qlik Sense Enterprise on Windows

Qlik Sense on-prem comes with an option to set a custom filter when creating a task. However, some custom filters are unable to be set with an error:

Value of Custom filter does not follow the correct pattern: [**-*****]

Example: 19-24 is acceptable, but 20-24, 21-24, 22-24, 20-23, 20,21,22,23,24 are not.

Resolution

This issue has been identified as a defect (ID QCB-29415), which is expected to be fixed in the Qlik Sense Enterprise on Windows November 2025 release.

Workaround:

Set multiple triggers for each hour.

Fix Version:

Qlik Sense Enterprise on Windows November 2025.

Environment

• Qlik Sense Enterprise on Windows, all versions leading up to November 2025

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes or contact support with the ID QCB-29415 for reference.

A scheduled Qlik Replicate task does not show up in the Executed Jobs list.

This is working as intended. The Executed Jobs tab will only show executed jobs that were scheduled to run once only. In other words, jobs scheduled to run periodically (e.g. Daily, Weekly, Monthly) will not be shown.

See Scheduling jobs.

Environment

Qlik Replicate 

After renaming a group used in the Identity Provider (IdP) set up with Qlik Cloud Analytics, the old group name continues to be listed in Qlik Cloud.

Users can log in without issues using the updated information.

Resolution

Use Qlik-CLI to remove the old group name.

Example command: 

qlik group rm <groupId>

See Delete group by ID for details.

Cause

Qlik Cloud retrieves all its information on groups from the IdP (Identity Provider), but does not delete old groups. Old groups can be removed using the API.

Renaming a group will be perceived by Qlik Cloud as a new group having been created. 

Environment

• Qlik Cloud Analytics

Can Qlik Cloud Analytics Community Sheets be unpublished using a Qlik Automate block or the Qlik REST API?

There is no unpublish sheet block in Qlik Automate, and a simple unpublish option cannot be done with the Qlik REST API.

To note:

• Duplciating a published sheet will create a private copy for the user who has unpublished it. It will only be visible to them.
• The sheet will need to be unpublished first, and ownership then needs to be transferred back to the original user. (Example: Set owner on an app object. The user must be the owner of the object)
• The published sheet behaviour in Qlik Sense is such that when published, it cannot be modified. You first need to unpublish the sheet before deleting.
• If the status or ownership of the sheet has not changed as expected: a new session will be created when the existing session is closed, either through inactivity or by the browser tab being explicitly closed (after around 120 seconds).

Environment

• Qlik Cloud Analytics

A task being run from the Qlik Sense Management Console fails with the error:

App already updating

The issue is typically only seen for specific apps and cannot be observed with new apps. 

Resolution

Restart all Qlik Sense services on the Central node. See Manual Start and Stop order of Qlik Sense services for details.

Cause

The task or app is queued within the manager schedule but has not completed successfully. 

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 and License 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.

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 and License Monitor

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. 

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.

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

Opening the QlikView Management Console (QMC) shows an orange banner across the top:

Lef expires DD/MM/YYYY

• QlikView any version

Expired Maintenance

Your maintenance support period has or is going to soon expire. Note that this can apply for both a QlikView Server license as well as a QlikView Publisher license. 

Review your LEF information for the following tag:

Perpetual License: 

• PRODUCTLEVEL;10;;2019-01-31
• PRODUCTLEVEL;30;;2019-01-31

Subscription License:

• TIMELIMIT;VALUE;2021-06-30;2022-06-30

To solve:

If you have not renewed your maintenance contract, this is expected and working as designed. Although the banner reads, the system remains working, but cannot be upgraded or supported by Qlik.

If your contract has been renewed, do the following:

1. Go to the QlikView Management Console
2. Navigate to System > Licenses
3. Choose your QVS@node/QMS@node  (check both)  and open the QlikView Server Licenses tab (Note: Be sure to check the Publisher license key as well.)
4. On the bottom, click: Update License from Server
   
   
   
   
5. Restart the QlikView services.

NOTE: 

• Be sure to check the Publisher license key as well.  If the Publisher LEF has expired it will also display the orange banner. You will need to update the License as well. 
• If the license has been extended with a time limit, example - TIMELIMIT;VALUE;;2022-05-21 the product will work until the mentioned time limit date  how ever the banner will still show the expired message in the management console, this is work as design.

Signed License Key applied

Another root cause may be a known issue with Signed key License on QlikView 12.40, or improper permissions assigned to Qlik Service Dispatcher. Product Defect ID(s): QV-17628

To solve:

If you are using version 12.40, note that there is a new service called Qlik Service Dispatcher. An admin account needs to be applied to resolve the issue. Qlik Management Service (QMS) may also need to be restarted as a workaround.

This issue is resolved in 12.50.

Erlang/Open Telecom Platform (OTP) has disclosed a critical security vulnerability: CVE-2025-32433.

Is Qlik NPrinting affected by CVE-2025-32433?

Resolution

Qlik NPrinting installs Erlang OTP as part of the RabbitMQ installation, which is essential to the correct functioning of the Qlik NPrinting services.

RabbitMQ does not use SSH, meaning the workaround documented in Unauthenticated Remote Code Execution in Erlang/OTP SSH is already applied. Consequently, Qlik NPrinting remains unaffected by CVE-2025-32433.

All future Qlik NPrinting versions from the 20th of May 2025 and onwards will include patched versions of OTP and fully address this vulnerability.

Environment

• Qlik NPrinting

The Qlik Sense Mobile app allows you to securely connect to your Qlik Sense Enterprise deployment from your supported mobile device. This is the process of configuring Qlik Sense to function with the mobile app on iPad  / iPhone.

This article applies to the Qlik Sense Mobile app used with Qlik Sense Enterprise on Windows. For information regarding the Qlik Cloud Mobile app, see Setting up Qlik Sense Mobile SaaS. 

Content:

• Pre-requirements (Client-side)
• Configuration (Server-side)
• Update the Host White List in the proxy
• Configuration (Client side)

Pre-requirements (Client-side)

See the requirements for your mobile app version on the official Qlik Online Help > Planning your Qlik Sense Enterprise deployment > System requirements for Qlik Sense Enterprise > Qlik Sense Mobile app

Configuration (Server-side)

Acquire a signed and trusted Certificate.

Out of the box, Qlik Sense is installed with HTTPS enabled on the hub and HTTP disabled. Due to iOS specific certificate requirements, a signed and trusted certificate is required when connecting from an iOS device. If using HTTPS, make sure to use a certificate issued by an Apple-approved Certification Authority.
Also check Qlik Sense Mobile on iOS: cannot open apps on the HUB  for issues related to Qlik Sense Mobile on iOS and certificates.

For testing purposes, it is possible to enable port 80.

(Optional) Enable HTTP (port 80).

1. Open the Qlik Sense Management Console and navigate to Proxies.
2. Select the Proxy you wish to use and click Edit Proxy.  
3. Check Allow HTTP 

Update the Host White List in the proxy 

If not already done, add an address to the White List:

1. In Qlik Management Console, go to CONFIGURE SYSTEM -> Virtual Proxies
2. Select the proxy and click Edit
3. Select Advanced in Properties list on the right pane
   
   

    

4. Scroll to Advanced section in the middle pane
5. Locate "Allow list"
   
   

    

6. Click "Add new value" and add the addresses being used when connecting to the Qlik Sense Hub from a client. See How to configure the WebSocket origin allow list and best practices for details. 
   
   

Generate the authentication link:

An authentication link is required for the Qlik Sense Mobile App.

1. Navigate to Virtual Proxies in the Qlik Sense Management Console and edit the proxy used for mobile App access
2. Enable the Client authentication link menu in the far right menu.
3. Generate the link.

NOTE: In the client authentication link host URI, you may need to remove the "/" from the end of the URL, such as http://10.76.193.52/ would be http://10.76.193.52 

Associate User access pass

Users connecting to Qlik Sense Enterprise need a valid license available. See the Qlik Sense Online Help for more information on how to assign available access types.
Qlik Sense Enterprise on Windows > Administer Qlik Sense Enterprise on Windows > Managing a Qlik Sense Enterprise on Windows site > Managing QMC resource > Managing licenses

• Managing professional access
• Managing analyzer access
• Managing user access
• Creating login access rules

Configuration (Client side)

1. Install Qlik Sense mobile app from AppStore.
2. Provide authentication link generated in QMC
   • Open the link from your device (this can be also done by going to the Hub, clicking on the menu icon at the top right and selecting "Client Authentication"), the installed application will be triggered automatically, and the configuration parameters will be applied.
   •  Enter user credentials for QS server

When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

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.

The default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:

1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)

   [globals]
   LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
   (...)
   MaxHttpHeaderSize=16384

2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.

Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows 

This article offers an example on how to set up a security rule matching to a role which is restricted to seeing only "License Management" in the Qlik Sense Management Console.

! The example is provided for demonstration purposes to explain a specific scenario. No support or maintenance is implied or provided. Further customization is expected to be necessary and it is the responsibility of the end administrator to test and implement an appropriate rule for their specific use case. For access to more tips and tricks, best practices, and ever-evolving creative solutions, we recommend joining us in our active Qlik Community.

Setup:

• Open the Qlik Sense Management Console and open the Security Rules menu
• Click Create new button

ServiceCluster_*,ServerNodeConfiguration_*,Engine*,Proxy*,VirtualProxy*,Repository*,Printing*,Scheduler*,User*,CustomProperty*,Tag_*,License*,TermsAcceptance_*,ReloadTask_*,UserSyncTask_*,SchemaEvent_*,CompositeEvent_*,QmcSection_License*,SystemRule_*

• Press Apply 

Expected outcome:

The user who is assigned to the LicenseAdmin role only has the privilege "License and tokens".

Related Content

• Qlik Sense Management Console sections grayed out and cannot be accessed 
• Security Rules: Control Access to sections in QlikSense Management Console