When using IBM DB2 for iSeries as a source in Qlik Replicate, the task may report a warning if journal receiver numbers are not continuous.

A typical warning message looks like:

[SOURCE_CAPTURE  ]W:  Journal entry sequence '2026' was read from journal receiver 'APSUPDB.QSQJRN0118'. The previous entry was read from receiver 'APSUPDB.QSQJRN0116'. Check if a receiver has been detached.  (db2i_endpoint_capture.c:1836)

Resolution

Qlik Replicate reports this condition as a warning only. There is no impact on task execution or data integrity:

• The task continues to run normally
• No journal entries are lost
• No data inconsistency is introduced

This warning can be safely ignored unless accompanied by other errors or abnormal task behavior.

Cause

On the IBM DB2 for iSeries side, 'Check if a receiver has been detached' can occur if, for example, the process is holding or locking the journal. This temporarily prevents the system from creating or attaching the next journal receiver. In such cases, a receiver number may be allocated but never successfully created, resulting in a gap in the receiver numbering.

This behavior is normal on IBM i and does not indicate a defect. The system assigns journal receiver numbers, but sequential continuity is not guaranteed. IBM i only guarantees that receiver numbers increase monotonically, not that every number will exist.

Internal Investigation ID(s)

00420963, 00423959

Environment

• Qlik Replicate
• IBM DB2 for iSeries all versions

At Qlik Connect 2026 I hosted a session called "Fast 15" with my top 10 visualization tips. Here's the app I used with all tips including test data.

Tip titles, more details in app:

• Product Catalogue
  How to make a product catalogue. Here's a variant with the new Pivot table using inline SVG images. The product images have been converted to Base64 and inlined within the inline SVG. The text is just positioned on top of the image.
• Table waterfall with subtotal and partial sum
  How to make table waterfall with add bars, and bars for subtotal and retro sum. Spreadsheet for layout, rangesum() and above() for offset and bar, master measures and SVG for waterfall.
• Switches revisited
  How to make a switch. Create a variable vSwitch set value to 0 Use the button, to toggle the variable, use action "set variable"
• Button examples
  How to style a button. Examples of button styles.
• Map with 3d bars
  How make 3d bar map point layer. Use a simple SVG with two rects: the bar and the shadow in Data URI with inline SVG. Added a top and base triangle for a little extra 3d effect.
• Rank box chart
  How to make a rank box chart. Use unicode boxes and repeat().
• Filter pane examples
  How to place a filter pane. Example of top panel, side panel and drawer style.
• Half Gauge
  How to make a multi half gauge. Use the map and two line layers.
• Pie chart value and percentage in the same label
  How to customize pie chart labels. Use dual() and number format measure expression.
• Line chart symbols
  How to add symbols in the line chart. Use dual and unicode symbols.
• Control chart with combo chart
  How to make a control chart with dynamic bounds. Use combo and measures for center, upper and lower bounds
• Formatting x-axis and keep field
  How to format the x-axis. Use dual and aggr.

I want to emphasize that many of the tips were discovered by others than me, I tried to credit the original author at all places when possible.

If you liked it, here's more in the same style:

• 24 days of visualization Season III, II, I
• Top 10 Tips Part X, IX, VIII, VII, VI, V, IV, III, II , I 
• Let's make new charts with Qlik Sense
• FT Visual Vocabulary Qlik Sense version
• Similar but for Qlik GeoAnalytics : Part III,  II, I

Thanks,
Patric

This article describes the diagnosis and resolution of a Qlik Data Gateway (repagent) service failure when installed in a non-default mount point (default is /opt and we installed using prefix keyword):

QLIK_CUSTOMER_AGREEMENT_ACCEPT=yes rpm -ivh  qlik-data-gateway-data-movement.rpm --prefix /data

The service entered a failed state after exhausting its systemd restart limit, caused by a stale process and PID file left over from a previous crash. This article covers root cause analysis, step-by-step resolution, and preventative measures.

The following symptoms were observed when the issue was reported:

• repagent service showing as 'failed' in systemctl status
• Service had restarted 5 times and hit the StartLimitBurst threshold
• All Qlik Replicate tasks were not processing
• Journal logs showed: 'Main process exited, code=exited, status=1/FAILURE'
• Subsequent start attempts failed with: 'New main PID does not belong to service, and PID file is not owned by root. Refusing.'

From the systemctl status output: 

Active: failed (Result: exit-code) since Wed 2026-04-15 21:16:53 BST
Main PID: 3220 (code=exited, status=1/FAILURE)
repagent.service: Start request repeated too quickly.

Resolution

To restore the service, first verify the SELinux config is set to SELINUX=disabled and SELINUXTYPE=minimum:

vi /etc/selinux/config

# This file controls the state of SELinux on the system. 
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these three values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=minimum

If not, make the changes as per above and reboot the box. Then continue using a root user:

1. Identify the stale process.
   
   cat /home/qlik/gateway/movement/data/repagent.pid
   
   This file will have the running pid number
   
   ps -ef | grep 1234
   
   This confirmed PID 1234 (agentctl) was still running as an orphan process under the qlik user.
   
   
2. Kill the stale process.
   
   sudo kill -9 1234
   
   This force-killed the orphan agentctl process and its child processes.
   
   
3. Remove the stale PID file.
   
   rm -f /home/qlik/gateway/movement/data/repagent.pid
   
   
4. Reset the failed service state.
   
   sudo systemctl reset-failed repagent
   
   This cleared the systemd failure counter, allowing the service to be started again.
   
   
5. Start the service.
   
   sudo systemctl start repagent
   
   sudo systemctl status repagent
   
   
6. The service returned to an active (running) state successfully.

Confirmed resolution output:

Active: active (running) since the current date
Main PID: 10391 (agentctl)
Tasks: 93

Cause

There are two root causes.

Stale Orphan Process (Primary Blocker)

When the repagent service originally crashed, it left behind an orphan process (PID 4082) that continued running independently of systemd. When systemd attempted to restart the service, it detected the stale PID file pointing to PID 4082, which it refused to adopt because it was not owned by root. This caused every restart attempt to fail with a 'protocol' error.

SQLite Native Library Warning (Secondary)

The journal also showed a secondary warning related to the System.Data.SQLite native library pre-loader failing to check the code base for assemblies loaded from a single-file bundle. This is a known .NET runtime compatibility warning and does not directly cause the service failure, but may indicate a .NET version mismatch worth monitoring.

System.Data.SQLite: Native library pre-loader failed to check code base
System.NotSupportedException: CodeBase is not supported on assemblies
loaded from a single-file bundle.

Environment

• Qlik Talend Cloud

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

A reload task in QlikView fails with the following error in the task log:

Error The sourcedocument failed to save.. Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. || at QlikView.Doc.SaveAs(String _FileName, Int16 _Format) || at QVBWrapper.Document.Save(ILogBucket i_LogBucket, String i_SaveAsFileName)

This may be caused by an active virus scan locking the relevant files, or an invalid alert configured on the task.

• QlikView

Virus Scan

Ensure that QlikView file locations (.qvw, qvd, etc..) are excluded from active virus scans. See QlikView Folder And Files To Exclude From Anti-Virus Scanning .

Invalid Alerts

Remove or edit the alerts configured on the document.

Alerts can be configured in the Distribution task. To verify:

• Open the QlikView Management Console
• Go to Documents > Source Documents
• Locate the failing document/task.
• Open the document/task
• Navigate to the Distribute tab
• Go to the Notify tab.
• Uncheck Send notification e-mail to recipients 
• Make sure, there is enough disk space to save the QVW

For additional troubleshooting steps and root causes, see QlikView: Checklist For Reload/Publisher Task Failure.

After completing the initial database configuration steps, the go to db config page link is removed from the Qlik Talend Administration Login page. See Updating parameters after the configuration is finalized for details.

Can the steps be repeated and the link re-enabled? 

Resolution

The Database configuration parameter named configuration.dbadmin.enable is set to false once you finalize the configuration on the Qlik Talend Administration login page.

To update the parameters configured on the Configuration and Database configuration pages, you must edit the configuration.properties file in the <TalendAdministrationCenterInstallationDirectory>/apache-tomcat/webapps/org.talend.administrator/WEB-INF/classes folder:

1. Open configuration.properties in an editor
2. Locate the configuration.dbadmin.enabled= parameter and set it from false to true 
   
   
   
   
3. Save the changes
4. Restart the Qlik Talend Administration Center services

5. Log in; the link will be accessible again

Environment

• Qlik Talend Administration Console

The App capability enabling Insight Advisor in hub is disabled without user action. 

Environment

• Qlik Sense Enterprise on Windows May 2025 and earlier versions

Resolution

The issue is caused by SUPPORT-7049, which has been resolved in the following versions and any subsequent releases:

• Qlik Sense November 2024 Patch 26
• Qlik Sense May 2025 Patch 17
• Qlik Sense November 2025 Patch 7

Upgrade to the latest available version and then manually reenable the Insight Advisor:

1. Navigate to \Program Files\Qlik\Sense\ServiceDispatcher, and open services.conf in a text editor.
2. Find the section [nl-app-search.parameters] and add the following parameter to its list:
   
   --preserve-iac-status=true 
   
   
   
   
3. Restart the Qlik Sense Service Dispatcher

Internal Investigation ID(s)

SUPPORT-7049

Importing a Qlik Replicate task with a name longer than 32 characters leads to the import failing with the following error:

SYS-E-HTTPFAIL, Failed to import task

Environment

• Qlik Replicate, version 2025.11

Resolution

Qlik Replicate has a task name limit of 32 characters, as documented in Qlik Replicate | Adding tasks. This validation can be overridden when importing a task starting with Qlik Replicate version 2025.11 SP04.

To override the validation, upgrade to 2025.11 SP04 or later and add the enforceTaskSettingsValidation feature flag:

1. Open the Qlik Replicate Console
2. Change to the Server settings using the drop-down arrow
   
   
   
3. Scroll down and open the More Options menu tab
   
   
   
   
4. Insert enforceTaskSettingsValidation (A) and click Add (B)
   
   
   
   
5. Set the value to Off
   
   
   
6. Save the settings. No restart of the services is required.

Qlik Replicate can now import tasks with names longer than 32 characters. 

Internal Investigation ID(s)

• RECOB-11132

Environment

• Qlik Replicate, version 2025.11

The Qlik Sense on Windows Content Monitor is intended for Qlik Administrators. Its purpose is to monitor and analyze your Qlik Sense content, including app usage, resource consumption, and data sources. This helps with governance, optimization, and identifying unused content.

Requirements

• Platform: Qlik Sense Enterprise on Windows
• Version: November 2025 onwards 
• Availability: Bundled with installation from version November 2025 onwards
• If you are running previous versions of Qlik Sense Enterprise on Windows, the Content Monitor is also available on Qlik's Downloads page here: Content Monitor (download page)
  • This must be manually installed, and a weekly reload is recommended.
  • The downloaded version is supported from Qlik Sense version Feb 2020.

Core Documentation

All technical details can be found in the two attached documents. These are your primary resources.

Qlik Sense Content Monitor User Guide

• • What it covers: A detailed, sheet-by-sheet explanation of the entire app. It describes what every KPI, chart, and table means for sections like "Weekly Summary," "Snapshot," "Applications," "Sessions," "Task Executions," "File Inventory," and "Infrastructure."

  • Use Case: 

    • Guiding a customer on how to read and interpret the data.

    • Answering customer questions like, "What does the 'Session Concurrency' sheet show?" or "How do I read the 'File Inventory' sheet?"

  • See the attached Qlik Sense Content Monitor User Guide

Configuration Guide

• • What it covers: This is the primary guide for setup and reload issues. It contains:

    • Detailed definitions for all script parameters (e.g., vCentralNodeHostName, vVirtualProxyPrefix, vServerLogFolder).

    • Performance tuning options (e.g., vFileScanMaxDuration, vAppRetrievalLoop, exclusion lists).

    • A "Trial Mode" section is used for troubleshooting initial reload failures.

    • A "Troubleshooting" section.

  • Use Case:

    • New installations.

    • Troubleshootings.

    • Tuning performance for long reloads.

  • See the attached Qlik Sense Content Monitor Configuration Guide

Environment

• Qlik Sense Enterprise on Windows

This article provides answers to the most frequent questions asked about Qlik MCP.

For the more general Qlik Answers FAQ, see Qlik Answers Agentic Analytics FAQ.

How do I troubleshoot my connection to the LLM I’m using?

Qlik Model Context Protocol (MCP) server integrates Qlik Cloud into your LLM workflow, allowing you to work with Qlik Cloud using your LLM without having to leave your LLM. Connection issues will often be tied to misconfiguration.

• Before you begin, review Deploying and administering Qlik MCP server and Connecting to the Qlik MCP server
• If you are using ChatGPT, verify that you are on the correct ChatGPT plan (see Connecting to ChatGPT)
• Typically, OAuth authentication issues with your client will be caused by:
  • Incorrect Remote MCP server URL (<your tenant URL>/api/ai/mcp)
  • Wrong Client ID
    

    Qlik MCP does not support clients with Client Secrets.

• If an error code is returned, reconnect; if reconnecting does not resolve the issue, submit the code returned by MCP to your LLM vendor for further troubleshooting

How do I troubleshoot my app if I am not getting the answers I expect?  

In a case where you do not get the response you expect based on the sources, or you receive an error:

• Ask again in case of an error (see the appendix for possible error codes)
• Rewrite the prompt (see Best practices for chatting with Qlik Answers)

Has your app been prepared for Qlik Answers?

• Best practices for preparing applications for Qlik Answers
• Writing master item descriptions for Qlik Answers

How much does the Qlik MCP cost?

For now, Qlik MCP will continue to be priced based on current models for the number of questions asked. You get capacity at corresponding levels in Standard, Premium, and Enterprise editions, as well as Qlik Sense Enterprise SaaS. There is currently no additional cost for structured data questions or task automation requests; a question is a question.

Use of the MCP server consumes questions when Qlik is accessed using Tool Calls. A Tool Call is a request made by the LLM to interact with Qlik's capabilities, such as, but not limited to, querying databases, calling APIs, or performing computations. These are typically visible in the LLM's log.

For Qlik's MCP server, 5 Tool calls consume 1 question. More questions may be purchased for expanded use cases.

See Pricing and the Qlik MCP server product description for details.

Qlik’s pricing does not include your chosen LLM subscription or usage, which will need to be paid separately.

Does Qlik MCP work with my existing Qlik apps?

Yes. Qlik MCP works on top of existing Qlik Sense applications and uses the same data, logic, and security model.

But to get the best experience, apps should be prepared beforehand:

• Best practices for preparing applications for Qlik Answers
• Writing master item descriptions for Qlik Answers

What capacity limitations do we need to consider?

Your Qlik Cloud subscription determines the quota of questions asked by users. If you are licensed for Qlik Answers, both MCP and Qlik Answers will use your monthly question capacity. See Administering Qlik MCP server. 

What happens when we reach a capacity limit?

Question capacity quotes are per month and reset every month. When you hit your limit, users can no longer ask questions until the next month. Overage is only allowed, depending on your subscription. For more information, see Qlik MCP server product description.

For more information on overage, see Overage. 

How do we turn off features?

Features can be turned off for individual users through user scopes.

1. Go to your Administration Center
2. Go to Manage Users
3. Switch to the Permissions tab
4. Click User Defaults and change the scope as required

See Control access to AI features.

A Loop and Reduce task created in the Qlik Sense Application Management Console (AMC) will only display its settings and parameters to the original task creator. Other users are unable to view any details. 

For more information about AMC, see: AMC - Application Management Console, an alternative to the QMC for large Enterprise environments.

Example:

User A, who created the task, sees:

User B only sees the following:

Resolution

Create a new Security Rule in the Qlik Sense Management Console to allow the desired user(s) to see all content. For more information about Security Rules, see Security rules.

Example Security Rule:

• Name: AMC - Access
• Resource Filter: SharedContent_*
• Action: Read
• Conditions: ((user.name="USERSNAMEHERE"))
  This defines which users you would like to be able to view all of the Shared Content.
  
• Context: Only in Hub 
  
  
  

Environment

• Qlik Sense Enterprise on Windows 

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

By default, Qlik Talend Data Catalog will not be able to trace the lineage of Qlik Talend Studio jobs that use dynamic components such as tDBJava. To extract lineage correctly, there are multiple steps that need to be followed. Below is an example where the JavaRow lineage fails to show because Talend Data Catalog is not able to parse the lineage of tJavaRow and instead creates duplicate columns, unintentionally splitting the lineage for each column:

Requirements

The following versions are required to trace lineage for complex Qlik Talend Studio components:

• Qlik Talend Studio R2025-04
• Qlik Talend Data Catalog 2026-02-10

Steps

1. In Qlik Talend Studio, confirm you have a complex component that will require advanced lineage tracing. In the example job below (MySqlToMySql_tJava) the tJavaRow component is included.
   
   
   
   
2. In Qlik Talend Studio, navigate to Project Settings (A) > Job Settings (B) and verify that Disable Lineage (C)is not checked for Qlik Cloud:
   
    

   

    
   If this setting is not available to you in Studio due to using an on-prem or local connection, then in the Qlik Talend Studio directory, edit the .ini file:
   
   -Dtalend.lineage.enabled=true 
   
   Example: Talend-Studio-win-x86_64.ini
   
    

   -vm
   C:\Talend\Studio-QTC\zulu17.48....
   -vmargs
   -Xms512m
   -Xmx1536m
   -Dfile.encoding=UTF-8
   -Dtalend.lineage.enabled=true
   -XX:+UseG1GC
   -XX:+UseStringDeduplication
   -XX:MaxMetaspaceSize=512m
   --add-modules=ALL-SYSTEM

   
   
    
3. In Qlik Talend Studio, for the complex components (example: tJavaRow) open the component view and switch from Basic settings to Documentation.
   
   In Documentation, add all columns where lineage should be traced between the flags *** lineage start *** and *** lineage end ***.
   
   Below is an example for five columns:
   
   
    

   

    
   
    
   
   
   
   
   
   
    
   To clarify for the screenshot above, not all the code should be placed in Documentation. Only the necessary code to track the lineage of each column should be added, in this case, showing output_row.ColumnName = input_Row.ColumnName.
   
   
4. In the Run tab for Qlik Talend Studio, navigate to Advanced settings (A) > JVM Settings (B).
   
   Add the following flag (C) to generate the necessary JSON files for Talend Data Catalog:
   
   -Druntime.lineage.outputpath=<outputPath>(Example: -Druntime.lineage.outputpath=C:\Talend\TalendStudio\Lineage
   
   
   
    
5. Run the Qlik Talend Studio job and confirm the JSON is generated in the specified output path:
   
   
   
   
6. Create a new model in Qlik Talend Data Catalog using the Talend Data Integration bridge.
   
   Under the Miscellaneous parameters, include the following flags:
   
   
   1. -runtime.lineage: This should specify where the lineage folder resides. Note that the Project Path must be properly defined for this to work (example: CHRIS_PROJECT\MySQLToMySQL_tJava\01
   2. -runtime.lineage.components: Specifies the list of transformation components that will require the external runtime lineage log by providing a semicolon-separated list of <components type> themselves, optionally prefixed by their job name <job name>.<component type> 
      
      
      
       
7. Run the import for the model.
   
   Be sure to also create a Qlik Talend Data Catalog for your input and output components to get the full lineage. In the example being used, two SQL models were created for tDBInput and tDBOutput. Once all models are imported, be sure to add the database models as connections to your Qlik Talend model:
   
   
   
   
8. Open the Lineage for the specific job in the model. Here you will see all the lineage is included:
   
   
   
    

    

Environment

• Qlik Talend Studio
• Qlik Talend Data Integration

Upgrading Qlik Compose across multiple versions requires a specific upgrade path. See Qlik Compose December 2024 Initial Release Notes for details.

After an upgrade, following the steps from 2022.5 to 2023.11 and finally 2024.12, Qlik Compose returns a generic UI error during connection tests. 

UI ERROR
Unable to connect to the remote server

Reviewing the Qlik Compose server log reveals the Java process is failing to start entirely:

[INFO ] Java Server: .
[ERROR] Java Server: Error: Could not create the Java Virtual Machine.
[ERROR] Java Server: Error: A fatal exception has occurred. Program will exit.
[INFO ] Java Server: <JAVA_HOME>/lib/ext exists, extensions mechanism no longer supported; Use -classpath instead.
[WARN ] The Compose java server was restarted.
[ERROR] Java Server: Error: Could not create the Java Virtual Machine.
[ERROR] Java Server: Error: A fatal exception has occurred. Program will exit.

While the Qlik Compose server is running, the Java agent is down.

The details upgrade path followed was:

• 2022.5.0.2333 to 2023.11.0.1029, which was successful
• 2023.11.0.1029 to 2024.12.0.402, which was unsuccessful

Resolution

1. Stop the Qlik Compose services
2. Rename or remove the /ext folder in the Compose/java/lib/jre/lib directory
3. Start the Qlik Compose services

Cause

When the second hop was done, the installation recreated the /ext folder within Compose/java/lib/jre/lib with no files within. As Compose 2024.12 uses Java 17, it doesn’t support ext folder.

Environment

• Qlik Compose

This article documents the basic steps to configure the SAML integration between Qlik Sense Enterprise on Windows (Client-Managed) and Microsoft Entra ID. By connecting these two platforms, administrators can control which users are allowed to access Qlik Sense directly from Entra ID, provide users with seamless single sign-on using their Microsoft accounts, and manage identities from a centralized location.

If you are looking for instructions for Qlik Cloud Analytics, see How To: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP.

Content

• Prerequisites
• Step One: Adding the Qlik Sense Enterprise on Windows app to your ENTRA ID.
• Step Two: Assigning users to your Qlik Sense Enterprise Client-Managed app in ENTRA ID.
• Step Three: Configuring Microsoft Entra SSO
• Step Four: Configuring SSO Qlik Sense Enterprise client-managed virtual proxy
• Step Five: Testing SSO.

Prerequisites

To get started, you need the following items:

• A Microsoft Entra subscription. 
• A valid Qlik Sense Enterprise on Windows license.
• Along with Cloud Application Administrator, an Application Administrator can also add or manage applications in Microsoft Entra ID. For more information, see Azure built-in roles.

Step One: Adding the Qlik Sense Enterprise on Windows app to your ENTRA ID.

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
2. Go to Entra ID.
3. Select Enterprise Applications under the Manage part.
4. Click New Application.
5. In the search box, type Qlik Sense Enterprise Client-Managed and select the result.
6. Click Create and wait for the app to be successfully added to your application list.

Step Two: Assigning users to your Qlik Sense Enterprise Client-Managed app in ENTRA ID.

1. Open the created Qlik Sense Enterprise Client-Managed app, click on Users and groups on the left side.
2. Click + Add user/group.
3. Click None Selected under the Users.
4. Select the user or multiple users you want to permit to access Qlik Sense, then click Select.
5. Click Assign.
6. Click Refresh and verify that the target user is added with the Role assigned.

Step Three: Configuring Microsoft Entra SSO

1. Open the created Qlik Sense Enterprise Client-Managed app, and click Single sign-on on the left side.
2. On the Select a Single Sign-on method page, select SAML.
3. On the Set up Single Sign-On with SAML page, select the pencil icon for Basic SAML Configuration to edit the settings.
   
   
   
   
4. In the Identifier (Entity ID) textbox, type a URL using the pattern: https://<Fully Qualified Domain Name>.qliksense.com”
   
   This example uses the Qlik Sense Fully Qualified Domain Name https://qlikserver1.domain.local 
   
   
5. In the Reply URL textbox, type a URL using the pattern: https://<Fully Qualified Domain Name>:443{/virtualproxyprefix}/samlauthn/
   
   This example uses https://qlikserver1.domain.local:443/entrasaml/samlauthn/
   
   
6. In the Sign on URL textbox, type a URL using the pattern: https://<Fully Qualified Domain Name>:443{/virtualproxyprefix}/hub 
   
   This example uses https://qlikserver1.domain.local:443/entrasaml/hub
   
   
7. Click Save. 
   
   
8. Go to the Set up Single Sign-On with SAML page.
   
   
9. In the SAML Certificate section, find Federation Metadata XML, click Download, and save the file on your computer.
   
   

Step Four: Configuring SSO Qlik Sense Enterprise client-managed virtual proxy

All the following steps are taken in Qlik Sense Enterprise on Windows.

1. Open the Qlik Sense Management Console (QMC) as a root admin user or a user who has permission to create a virtual proxy.
2. Go to Virtual Proxies and click Create new (See Creating a virtual proxy for details).
3. If not already visible, activate the following Properties in the right-side menu: Identification, Authentication, Load Balancing, and Advanced.
   
    

   

4. Configure IDENTIFICATION as follows:
   • Description: Describe the purpose of the virtual proxy.
   • Prefix: Enter a unique name not yet used by any other virtual proxies; this value will be a part of the login URL for Qlik Sense.
   • Session inactivity timeout (minutes): Set how long a session can remain idle before it expires; once this limit is reached, the session becomes invalid and the user is automatically signed out.
   • Session cookie header name: Set a unique cookie name storing the session identifier after successful authentication.
     
     
     
      
5. Configure AUTHENTICATION as follows:
   
   • Anonymous access mode: This controls whether unauthenticated users can access Qlik Sense through this virtual proxy. The default setting is No anonymous user, which restricts access to authenticated users only. Leave it at the default.
   • Authentication method: Select SAML from the dropdown list, which will surface additional settings.
   • SAML host URI field: Enter the hostname that users will use to access Qlik Sense through this SAML proxy. This value should match the public URI of your Qlik Sense server.
   • SAML entity ID: Use the same value configured in the SAML host URI field.
   • SAML IdP metadata: Upload the identity provider metadata file previously downloaded from Microsoft Entra ID. Click Choose File and select the XML metadata file. 
   • SAML attribute user ID: Enter the attribute name or schema reference for the SAML attribute representing the UserID Microsoft Entra ID sends to the Qlik Sense server. Schema reference information is available in the Azure app screens post configuration. To use the name attribute, enter http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name.
   • SAML attribute for user directory: Enter the value for the user directory that's attached to users when they authenticate to Qlik Sense server through Microsoft Entra ID. Hardcoded values must be surrounded by square brackets []. To use an attribute sent in the Microsoft Entra SAML assertion, enter the name of the attribute in this text box without square brackets. In this example, we are using [domain].
   • SAML signing algorithm: Defines the certificate signing algorithm used by the service provider (Qlik Sense server). If your server uses a trusted certificate generated with Microsoft Enhanced RSA and AES Cryptographic Provider, consider changing the algorithm to SHA-256. In this example, SHA-1 is used.
   • SAML attribute mapping: Allows additional attributes (such as groups) to be passed to Qlik Sense for use in security rules. In this example, no additional attribute mapping is configured.
     
     
     
     
6. Configure LOAD BALANCING as follows:
   
   1. Click Add new server node.
   2. Then select the engine node (or nodes) that Qlik Sense should route user sessions to for load balancing and click Add to confirm your selection.
      
      
      
      
7. Configure ADVANCED as follows:
   
   
   • Host allow list: Define all hostnames that are permitted when connecting to the Qlik Sense server. Enter the hostname users will use to access the server.
     
     This value should match the SAML host URI, but without the https:// prefix.
     
     
     
      
   • Leave the other settings at their default values
     
     
8. Click Apply.
   
   
   
   The Proxy will be restarted. Click OK to confirm.
   
   
   
   
9. After the restart, locate the Associated items section in the menu and click Proxies.
   
   
   
   
10. Select the proxy node that will handle this virtual proxy connection in Qlik Sense, then click Link. Once the connection is established, the proxy node will appear in the list of associated proxies.
    
    
    
    
    
    
11. A Refresh QMC prompt appears. Click to confirm. Once the page reloads, open the Virtual proxies section and locate the newly created SAML virtual proxy in the list.
    
    
12. Select the entry, and the Download SP metadata button at the bottom of the screen will become active. Click this button to download and save the service provider metadata file for Qlik Sense.
    
    
    
    
13. Open the SP metadata file and review the entityID and AssertionConsumerService entries. These correspond to the Identifier and Reply URL fields in the Microsoft Entra ID application configuration. If the values in Entra ID do not match those in the metadata file, update the Domain and URLs section of the application configuration so they are aligned with the settings from Qlik Sense.
    
    
    
    

Step Five: Testing SSO. 

You can test the single sign-on setup either from the Microsoft Entra ID portal by selecting Test, or by navigating directly to the Qlik Sense sign-on URL and starting the login process from there.

The TDQRules qlikrules jar file is missing even after enabling the component in the feature manager.  

Resolution

This is caused by QTDQ-1404 and addressed in the 2026-04 release of Qlik Talend Studio. The issue is triggered by a space or special character in the install folder name.

Workaround:

Move or install Qlik Talend Studio in a different folder than the default \Program Files folder, and make sure that there is no blank space or special character in the new install path. 

Internal Investigation ID(s)

QTDQ-1404

Environment

• Qlik Talend Studio

Click here for Video Transcript

Note: The concept ’ UPSERT MODE’ and 'MERGE MODE' is not documented in the User Guide. i.e. it is not a word you can search for in the User Guide and is not a key word in the Replicate UI.

What they do:

UPSERT MODE: Change an update to an insert if the row doesn't exists on the target
MERGE MODE: Change an insert to an update if the row already exists on the target

How to set

Use MERGE MODE: i.e. configure the task under: task setting --> Error Handling --> Apply Conflicts --> ‘Duplicate key when applying INSERT:’ UPDATE the existing target record

Use UPSERT MODE: i.e. configure the task under: task setting --> Error Handling --> Apply Conflicts --> ‘No record found for applying an UPDATE:’ INSERT the missing target record

How they work:

Batch Apply and Transactional Apply modes:

There is a big difference in how these Upsert/Merge settings work depending of whether the task is in 'Batch' or 'Transactional' Apply mode.

Batch Apply mode:

Either option (Upsert/Merge) does an unconditional Delete of all rows in the batch, followed by an Insert of all rows.

Note: The other thing to note is that with this setting the actual update that fails is inserted in a way that may not be obvious and could cause issue with downstream processing. In batch apply mode the task will actually issue a pair of transactions (1st a delete of the record and then 2nd an insert) this pair of transactions is unconditional and will result in a "newly inserted row every time the record is updated on the source.

Transactional Apply mode:

Either option (Upsert/Merge) - the original statement is run and if it errors out then the switch is done (try and catch). 

Insert in transactional apply mode,  the insert statement will be performed in a "try / catch" fashion. The insert statement  will be run and only if it fails will it be switched to an update statement .

In transactional apply mode, the update will be performed in a "try / catch" fashion. The update will be run and only if it fails will it be switched to an insert statement . 

Gotchas:

1. If the table has added fields that are used/modified by a downstream process then there is a good chance that this will cause a problem.
2. Oracle table must have supplemental logging all column set
3. Masking of possible underlying issue - why was the record not there for an update or why was it there already for and insert
4. I want to caution you that there may be other missing records (from a failed insert) that were not captured and this setting will only bring over missing records if they are updated on the source. There could be many records still missing on the target.

Possible use case:

1. Missing values in some fields/missing rows on target. With Upsert/Merge set a "fake" update can be issued on the source (Update field1 = field1) without a where clause will force every row in the source to refreshed to the target ( without losing all the target data like a reload would)
2. Prevent a task from switching out of bulk apply due to errors 'Duplicate PK or Record not found (appliance targets could benefit from this)
3. Could help the CDC only task of split table environment - Separate Full Load / CDC design.

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.

Related Content

• Transformation: Target Lookup

Environment

Qlik Replicate 

What is the default user session timeout for Qlik Sense Business and Qlik Sense Enterprise SaaS? Can the session timeout for Qlik Cloud be changed?

The default (fixed) value is set to 30 minutes. This is controlled by SESSION_TTL.

It is not currently possible to adjust the session timeouts in the Qlik Cloud.

Environment:

Qlik Cloud 

NPrinting Initial Installation Fails with Error 0x080070643 (or similar)

Environment

• Qlik NPrinting all supported versions

Resolution

1. Ensure you have carefully reviewed and met the installation requirements. See Planning your deployment.
2. Ensure you have also carefully reviewed the companion NPrinting Product Release Notes (Release Notes) before installing.
3. The downloaded NPrinting install files must be in an 'unblocked' state
   
   
   
   
4. Ensure you have sufficient c:\drive space (NPrinting can only be installed on the c:\drive)
5. Antivirus software should be disabled 
6. The Windows Server hosting NP server is online to the internet (if offline, ensure all windows updates are performed 'before' attempting to install NPrinting server software)
7. The Windows Server hosting NPrinting has had all windows updates applied
8. The NP server computer is installed exclusively (no other Qlik Products or earlier versions of NPrinting (ie: NP 16) are installed or have been previously installed)
9. The Windows Server computer is a member of the same domain as the NPrinting Server service account
10. The intended NPrinting domain service user account used to install the NPrinting Server software 
    • is a member of the local administrators group Windows Qlik NPrinting Engine service administrator
    • has log on as a service > user rights assignment Windows Qlik NPrinting Server services administrator
    • is NOT restricted in any way by Active Directory group policy
    • is a member of the same domain as the NPrinting server computer

If any other version of NPrinting (ie NP 16 and earlier client server track) has been installed here previously or other unrelated software is installed, it would be recommended to reinstall Windows Server OS to ensure a clean start before installing NPrinting Server. (...or if this target Windows Server has been repurposed for use with NPrinting from some other function. It could already be damaged ie: damaged registry files).

*It is best to have a clean slate when installing Qlik NPrinting Server for the first time or if you suspect that the underlying Windows Server has become corrupted or damaged, or even when upgrading and Error 0x080070643 appears *

Related Information

• How to BackUp and Restore Qlik NPrinting Repositor... - Qlik Community - 1715863
• Qlik NPrinting Upgrade Steps and Best Practices
• Planning and Deploying NPrinting

On Red Hat Enterprise Linux v9.7, `OPENSSL_3.4.0' not found message may appear when running system commands. The message explicitly references Qlik Replicate's bundled libraries, which can make it look as though the error is a product issue.

For example, when running:

systemctl start areplicate

You may see:

systemctl: /opt/attunity/replicate/lib/libcrypto.so.3: version `OPENSSL_3.4.0' not found (required by /usr/lib64/systemd/libsystemd-shared-252.so)

This phrasing makes it clear that the error message itself points to Qlik Replicate’s libraries, while also explaining why someone might mistakenly think it’s a product defect.

Resolution

• If an error occurs, avoid running system commands inside Qlik Replicate’s environment.
• Do not source scripts such as arep_login.sh or include Qlik Replicate’s library path when executing commands that are unrelated to Qlik Replicate. This ensures that system tools use the correct libraries from /lib64 rather than the older bundled versions provided by Qlik Replicate.

Cause

Red Hat Enterprise Linux 9.7 ships with OpenSSL version 3.4 or newer, while Qlik Replicate (v2025.11.0.286) bundles its own OpenSSL libraries that only support versions up to 3.0.x. When the Qlik Replicate environment is activated, its library path (LD_LIBRARY_PATH) takes precedence, so system commands such as systemctl may load the older bundled libraries instead of the system’s /lib64 versions. This mismatch leads directly to the OPENSSL_3.4.0 not found error message.

Environment

• Qlik Replicate