By default, Qlik Replicate reads primary keys from source tables and creates target tables using those same keys. If you want to use an existing view that doesn’t share the same key columns, you can modify the replication process to define matching key columns and adjust the task settings to prevent it from reloading the target table.

In table transformations, use Set Key Columns > Use transformation definition to ensure the key columns match the target view.

But using Views as the target (instead of a table) will result in this error, as indexes cannot be applied to views.

[TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 1939 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Cannot create index on view 'PPHTRAN' because the view is not schema bound. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:5083)

Resolution

Target views behave differently from tables, but an internal parameter can be used to trigger a manual query. To achieve this, add the $info.query_syntax.create_index internal parameter and value to the SQL Server target endpoint.

1. Go to the  Endpoint connection
2. Switch to the Advanced tab
3. Click Internal Parameters
4. Add the following:
   
   • Parameter: $info.query_syntax.create_index
   • Value: select 1
     
     The SELECT 1 query itself has no effect, but it overrides the task behavior, preventing it from attempting to create a new unique index on the view, which is not supported.
     
     
     
     For more information about Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?

Internal Investigation ID(s)

SUPPORT-9276

Environment

• Qlik Replicate

Qlik Replicate 2025.11.0.285 could not read transaction logs properly for the SQL Server source endpoint, causing the following error:

[SOURCE_CAPTURE ]E: Bad Envelope : Lsn=00695591:01394baa:0009,operation=5,TxnId=0006:91821bb4,Tablename=COMMIT,PageId=0000:00000000,slotId=3,timeStamp=2026-02-25T06:20:03.890,dataLen=0, LCX=99, >Invalid data context / LCX Code encountered for TXN operation. [1020203] (sqlserver_log_processor.c:350) 00001580: 2026-02-25T07:35:09 [SOURCE_CAPTURE ]E: Internal error (specific information not available) [20014]

Resolution

Upgrade to Qlik Replicate 2025.11.0.437 to resolve the read issue for the transaction logs.

Internal Investigation ID(s)

SUPPORT-8946

Environment

• Qlik Replicate

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 

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

For the Qlik MCP FAQ, see Qlik Model Context Protocol (MCP) FAQ. 

What is Qlik Answers Agentic Analytics?

In February 2026, we launched our new agentic experience, which will enhance decision-making and improve productivity through a combination of assistants and agents running on a cutting-edge architecture. This initial release includes out-of-the-box agents for structured data analytics, unstructured knowledge, discovery of anomalies, and help and assistance. These agents take advantage of our foundational capabilities, including our data products and unique analytics engine, to execute complex, multi-step tasks in a trusted, scalable, and secure manner.

How will Qlik Answers evolve?

Qlik Answers is the primary AI assistant for people to interface with agentic AI. It will understand the intent of natural language questions and engage the underlying agentic framework to execute tasks, build responses, and take actions.

Qlik Answers now combines structured data analytics with unstructured content and general knowledge and reasoning from LLMs to deliver the most complete and relevant answers and insights, helping our customers improve decisions, productivity, and business outcomes in ways not possible before.

Looking ahead, as we build additional agents, such as prediction agents and pipeline agents, they will all be invoked through Qlik Answers. A broader set of agents is planned, all aimed at helping users get more value from their data and become more productive as Qlik continues to evolve.

What is the value to me as a customer?

With Qlik Answers now able to handle both structured and unstructured data, you can drive hundreds more informed decisions and actions each day. You can drive productivity through automation of a broad range of data and analytics tasks and workflows. And with plug-and-play simplicity, you can quickly deploy assistants in a matter of hours, reducing risk, speeding time-to-value, and future-proofing their investments in AI.

How much does the Qlik Answers cost?

For now, Qlik Answers 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, with additional capacity available for purchase as needed. 

There is currently no additional cost for structured data questions or task automation requests; a question is a question.

For additional details, refer to Pricing.

What if I have a valid subscription, but cannot use Qlik Answers yet?

Since launch, Qlik Answers has been rolled out across regions, and the process is still ongoing. If you have Standard, Premium, and Enterprise editions, check if your region already supports it (see Supported regions).

If it is not yet available to you, then:

• MCP is already available to you regardless, see Deploying and administering Qlik MCP server 
• Be on the lookout for an in-product message alerting you once your tenant has access

Do I have to be a Cloud customer to use it?

Yes, you must be a Qlik Cloud customer to use Qlik Answers. Qlik Answers is built on cloud-native technologies, specifically large language models (LLMs) that require significant compute resources and specialized infrastructure, and there is no mechanism to deploy these technologies in an on-premises environment.

However, you don’t have to fully migrate their analytics environment or documents to the cloud in order to take advantage of Qlik Answers. Qlik's roadmap aims to enable support for analytics apps that were pushed to the cloud, at which point unstructured documents can be indexed where they reside. The current target release date for this feature sits within Q2 of 2026.

Will I get both Qlik Answers and Insight Advisor?

No. You will use either Qlik Answers or Insight Advisor, not both at the same time.

Qlik Answers represents the AI-first experience going forward. When a tenant chooses Qlik Answers, that becomes the primary way users interact with analytics. Insight Advisor is not available in parallel within the same tenant.

This is a deliberate choice to avoid duplicated experiences, inconsistent results, and user confusion.

Will Qlik Answers become available on premises?

No. Qlik Answers is cloud only.

There are no plans to bring Qlik Answers to on-premises environments. The product relies on cloud native AI services, managed infrastructure, and continuous model evolution.

What happens to Insight Advisor? Is it going away?

Insight Advisor is not being discontinued.

If you remain on Insight Advisor, you can continue using it. However, within a tenant, you must choose between Insight Advisor and Qlik Answers. You cannot run both experiences side by side.

What happens to the business logic we already built in Insight Advisor?

The most important and relevant business logic is preserved when moving to Qlik Answers.

That said, Qlik Answers is built for a newer generation of AI-driven analytics. In many cases, customers will find they no longer need to manually build or maintain the same level of logic, because the system handles more of that automatically.

The value is not in recreating everything exactly as it was, but in moving to a simpler, more capable experience.

What is the difference between Qlik Answers and Qlik MCP?

This is essentially a buy vs build decision:

• Qlik Answers is a fully managed, out-of-the-box solution. It features AI agents specifically
  designed to take advantage of our unique capabilities, including our analytics engine.
  
  Everything is preconfigured, secured, monitored, and continuously improved. Customers can start using it immediately without worrying about infrastructure, model selection, or orchestration.
  
  It’s an easy, plug-and-play solution.
  
  
• Qlik MCP is for customers who want to build and customize themselves. It is aimed at broader AI initiatives and assistants, allowing organizations to build on top of Qlik’s trusted data and analytics foundation. It’s designed for technically advanced teams that want to integrate their own models, customize deeply, and manage their own AI stack.
  
  Essentially, it’s “APIs for AI.” 
  
  
• If you want speed, simplicity, and support, Qlik Answers is the right choice. If you want full
  control and customization, and to build and operate it yourself, MCP is the right path.

What AI models does Qlik Answers use?

Qlik Answers is built on AWS Bedrock and currently utilizes Anthropic Claude models. The specific model versions vary by agent function and are continuously evaluated and updated based on performance, accuracy, latency, and cost optimization.

Our Model Selection Philosophy:

Qlik maintains flexibility in model selection to continuously improve the user experience as AI technology evolves. Different agents within the Qlik Answers architecture may use different models optimized for their specific tasks (e.g., semantic understanding, code generation, reasoning).

Can I bring my own AI model to Qlik Answers?

No. Not at this stage.

Qlik Answers is a managed experience with curated models and configurations. Customers who want to use their own models or bring custom AI stacks should use MCP instead.

Does Qlik Answers work with my existing Qlik apps?

Yes. Qlik Answers 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

Does it respect master items and business logic?

Yes. Master measures and dimensions are always prioritized. If business logic exists, Qlik Answers uses it rather than creating new calculations.

Does it generate charts automatically?

Yes. Qlik Answers generates appropriate visualizations such as KPIs, bar charts, or time-based charts depending on the question.

How does security work in Qlik Answers?

Qlik Answers inherits and enforces Qlik's established security model without exception. All existing security rules, section access configurations, and row-level security policies apply automatically.

Key security principles:

• Users only see data they are authorized to access
• Section access restrictions are enforced
• Application-level permissions control which apps users can query

Field-level security (if implemented) is respected in all analyses.

No additional security configuration is required. Organizations with complex security requirements can continue using their existing Qlik security implementations with confidence.

Can different users get different answers to the same question?

Yes, if their access rights differ. Answers are always scoped to the user’s permissions.

Do I need to prepare my data differently?

While no special data preparation is required beyond standard Qlik Sense data modelling best practices, the apps themselves should be prepared beforehand to give you the best experience possible:

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

Does Qlik Answers support follow-up questions?

Yes. Qlik Answers understands conversational context, allowing users to refine or continue their analysis.

Does Qlik Answers support multiple languages?

At its initial GA release, Qlik Answers is optimized and fully supported for English language queries and responses.

While the underlying large language models have multilingual capabilities and may be able to process queries in other languages with varying degrees of accuracy, non-English language support is not officially validated, documented, or supported by Qlik at this time.

Additional language support is planned for future releases based on demand and regional priorities.

Does it replace analysts or data teams?

No. It accelerates analysis and reduces repetitive work but does not replace human expertise or decision-making.

Can I limit which apps are available to Qlik Answers?

Yes. Only enabled and indexed applications are available.

Does it work across multiple apps?

Not in the current GA release. Qlik Answers operates within the context of a single Qlik Sense application per query. Multi-application query capabilities are planned for a future release.

What scopes do I need to be able to ask questions?

If you want to ask questions in an app, you just need the ‘Data analysis’ scope. If you plan on asking questions to an assistant, you need the ‘Data analysis’ and ‘Search knowledge base’ scopes.

What is the risk of Cross-Region Inference?

Cross-region inference has minimal risks as the data still stays within the AWS Virtual Private Network. The only difference here is that the LLM call gets processed in a different region due to GPU availability.

What about the speed of responses?

We have made a deliberate design decision to prioritize the quality of answers and insights over the speed of responses. In general, Qlik provides a far richer reasoning process and answer than competing products, and this results in a longer response time. We are planning to improve and optimize this, as well as introduce a faster mode for simpler questions in the future.

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

Qlik Answers always references its sources in detail. To begin troubleshooting, check the citations, which will show:

• The app used
• The fields and expressions used to build the visualization
• The knowledge base used
• The text chunks being referenced

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

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. 

What functional limitations do we need to consider?

• See Qlik Answers Limitations.
• Qlik Answers will work with one app or assistant at a time. It does not search through all apps. 

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.

If you have previously enabled the feature, the entirety of Qlik’s Agentic Analytics can easily be turned off again by configuring AI features in Qlik:

1. Go to your Administration Center
2. Go to Settings
3. Go to the Tenant tab
4. Toggle Enable cross-region inference in AI features in Qlik

See Enable cross-region inference.

Appendix 

Error codes

These error codes should only be used to reference what is an expected error. Retry if you receive any of these errors.

Retry and Processing Errors

• DAA-001: Retry limit exceeded.
• DAA-002: Maximum duplicate processing attempts exceeded.

App and Document Errors

• DAA-007: App ID not found in swarm.
• DAA-008: Failed to retrieve the document.
• DAA-009: Invalid App ID.
• DAA-010: App not indexed for answers.

Chart and Sheet Errors

• DAA-016: Failed to create chart.
• DAA-017: Unexpected error while adding chart.
• DAA-018: Sheet creation failed.

Expression and Hypercube Errors

• DAA-024: Expression builder (v2) error.
• DAA-025: Hypercube length exceeded.

Semantic Search Errors

• DAA-030: No related data found in semantic search.
• DAA-031: Error while fetching semantic search results.
• DAA-032: Not enough relevant assets found in search.
• DAA-033: Validation error during semantic search.

Access Verification Errors

• DAA-050: Missing access control context.
• DAA-051: HTTP error occurred during access control request.
• DAA-052: Access control request timed out.
• DAA-053: Connection error during access control request.
• DAA-054: Access control privilege denied.
• DAA-055: Unexpected error in access control process.

You can select a sheet to the landing page of the app by setting a default bookmark.

When you open the app, the expected landing page may not be displayed.

As well, when you open a sheet with a sheet action, the action might not get triggered.

Environment

• Qlik Sense Enterprise SaaS
• Qlik Sense Business

Resolution

The session needs to be terminated.

1. Close the browser or all opened tabs.
2. Wait for 30 minutes.
3. Log in to the tenant and open the app.

Cause 

The default bookmark with selection and landing sheet as well as sheet actions are applied once per session.

Qlik Sense SaaS keeps the session up to 30 minutes after closing the tab or tabs.

Related Content 

Setting a default bookmark to create an app landing page

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

ErrorCode.11041 occurs when opening up an App
ErrorCode.11043 occurs when creating a Database connection in the data load editor.

The two symptoms will correlate with the Qlik Sense system having a restricted or no internet connection.

Qlik connectors are cryptographically signed for authenticity verification. The .NET framework verification procedure used for this signing includes checking OCSP and Certificate Revocation List information, which are fetched from an online resource if the system doesn't have a cached local copy. These requests will timeout due to a lack of access to online resources in environments with restricted, slow or no internet connection. Due to the authenticity check failure, the connector will not run, and the app reload fails.

 

Resolution:

Edit the .Net Framework's machine.config file

1. Stop all QS services on all nodes
2. Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config
   
   Change (or add) the <runtime/> tag to reflect: 
   

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

   If the <runtime> section looks different, modify it to:
   

   <runtime>
     <OTHER CONFIGURATION="YOU VALUES">
       <...>
     <generatePublisherEvidence enabled="false"/>
   </runtime>​

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

NOTE1: Changes to machine.config affects all software using the .NET framework feature.

NOTE2: 3rd party connectors might be compiled for 32-bit platforms.
In such case repeat steps above for the 32-bit version of the machine.config file;
C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config
 
 

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

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

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

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

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

Resolution:

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

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

Restore process:

1. Find the App filename

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

An example showing App id followed by App name follows:


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

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

This will make the file readable and importable. 

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

3. Import the App

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

•  Locate the file on disk
• Click Open

• Rename the App to the original name

4. App has been imported and received a new APP_ID

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

5. Find the proper stream where the app resides

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

Click Publish  

The Publishing dialogue:
 

 

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

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

Previous versions of Microsoft SQL Server do not support a dedicated JSON data type.

For later versions, Microsoft announced the introduction of a native JSON data type (along with JSON aggregate functions). This new data type is already available in Azure SQL Database and Azure SQL Managed Instance, and is included in SQL Server 2025 (17.x).

SQL Server 2025 (17.x) became Generally Available (GA) on November 18, 2025.

At this time, the current Qlik Replicate major releases 2025.05/2025.11 do not support SQL Server 2025 or its native JSON data type yet.

Environment

• Qlik Replicate all versions
• SQL Server 2025 on-premises
• Azure SQL Database and Azure SQL Managed Instance (which share the same engine as SQL Server 2025)

Common Errors Observed if the table contains a JSON column in SQL Server 2025

SQL Server endpoint with SQL Server 2025 as the source

During the endpoint connection ping test, you may encounter:

SYS-E-HTTPFAIL, Unsupported server/database version: 0.
SYS,GENERAL_EXCEPTION,Unsupported server/database version: 0

MS-CDC endpoint with Azure SQL Database as the source

Since the Azure SQL Database version is always 14.x, the version check succeeds. However, Azure SQL DB already uses the SQL Server 2025 kernel, the task later fails during runtime with:

[SOURCE_CAPTURE  ]T:  Failed to set ct table column ids for ct table with id '1021246693'  (sqlserver_mscdc.c:2968)
[SOURCE_CAPTURE  ]T:  Failed to get change tables IDs for capture list [1000100]  (sqlserver_mscdc.c:3672)
[SOURCE_CAPTURE  ]E:  Failed to get change tables IDs for capture list [1000100]  (sqlserver_mscdc.c:3672)

Resolution

No workaround can be provided until support has been introduced.

According to the current roadmap, support for SQL Server 2025 and the native JSON data type is planned for the upcoming major release: Qlik Replicate 2026.5.

No date or guaranteed timeframe can yet be given. The support planned for 2026.5 is an estimate.

Internal Investigation ID(s)

00419519

This article explains how to implement SAML for NPrinting with Azure as the IdP.

Environments:

Qlik NPrinting 

To implement Azure SAML in Nprinting, the following needs to be done:

1. Create your own application in Azure from this menu and choose a name for it.
   
   
   
   

2. Generate a Metadata XML file 
   
   Federation Metadata XML: Download
   
   

3. Configure SAML in NPrinting and upload your metadata file 
   
   See instructions on the following link: Confguring SAML
   
   Below is an example of a working metadata file with only the needed fields, the simpler is to copy the corresponding elements (Azure EntityID, certificate for signing, SingleSignOnService for HTTP-POST and HTTP-Redirect) from the IdP metadata file downloaded from Azure and paste it into the corresponding parts of the code.
   
   Then save the file as .xml and upload it to NPrinting:
   

   <?xml version="1.0"?>
   <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata" entityID="https://sts.windows.net/b26e23cf-787a-40e8-9d17-f0c9f9ad0821/">
     <IDPSSODescriptor xmlns:ds="http://www.w3.org/2000/09/xmldsig#" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
       <KeyDescriptor use="signing">
         <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
           <ds:X509Data>           
   <ds:X509Certificate>MIIC8DCCAdigAwIBAgIQFUUu6ZQHg5FJ...Ud8tf9A/4A6+2SZm34gf8gcVPTXT/a</ds:X509Certificate>
           </ds:X509Data>
         </ds:KeyInfo>
       </KeyDescriptor>    
   <SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://login.microsoftonline.com/b26e23cf-787a-40e8-9d17-f0c9f9ad0821/saml2"/>
   <SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://login.microsoftonline.com/b26e23cf-787a-40e8-9d17-f0c9f9ad0821/saml2"/>
     </IDPSSODescriptor>
   </EntityDescriptor>​

   
   Alternatively, when you upload the Azure metadata file as is to NPrinting, check the Webengine log file to remove unwanted tags from the Azure metadata file (As there are many tags that are not supported by Azure, it may take some time)
   
   
4. In Azure, configure your Enterprise application created in step 1
   
   The fields that need to be filled in on the Azure side are the 2 below, others are optional.
   
   Identifier (Entity ID):  The Entity ID set up in NPrinting in step 3
   Reply URL (Assertion Consumer Service URL): The correct value can be found in the SP metadata file downloaded from NPrinting
   
   
   
   
5. Make sure you give the correct permissions to the Azure AD users you want to authorize to connect with SAML
   
   
   
   The settings is now completed and SAML authentication should work.
   
   

Potential Troubleshooting Steps

• Remember that the user that logs in must already exist in NPrinting identified by either his email address or DOMAIN\Username (Based on the settings in step 3).
  
  If the authentication fails, the error will be logged in the web engine logs in C:\Programdata\Nprinting\Logs\.
  
  
• If issues are found with the implementation, among other reasons the following may be related:
  1. The email address attribute needs to be the full URL path, not just “emailaddress”
  2. The XML from AD/idp needs to have reference to only one certificate
  3. Irrelevant information in the XML from the idp needs to be removed as NP does not support and can cause errors.

To start replication from a specific point in time on a MongoDB source, you will need to identify the oplog stream position (BSON Timestamp) corresponding to your target time and configure it in your Qlik Replicate task.

This article outlines the options available to you.

Prerequisites

• The MongoDB oplog is a capped collection, and entries are overwritten over time. Ensure your target timestamp is still within the current oplog window before attempting to start from it.
• Query the primary node or a secondary with sufficient oplog retention.
• The Qlik Replicate MongoDB user requires read access to local.oplog.rs.

Finding the stream position

Option One: Query the oplog directly (Recommended)

Connect to the primary node via mongosh and run:

db.getSiblingDB('local').oplog.rs.find().sort({ $natural: -1 }).limit(1).pretty()

This returns the most recent oplog entry. Look for the ts field in the output:

   {
     "ts": Timestamp(1741600200, 1),
     "op": "i",
     ...
   }

The ts value is your stream position. The first number is Unix epoch seconds; the second is the ordinal increment.

Option Two: Query the oplog by target timestamp

If you know the specific time you want to start from, you can filter the oplog directly to find the closest entry:

var t = new Timestamp(Math.floor(new Date("2026-03-10T11:30:00Z").getTime() / 1000), 1);
db.getSiblingDB('local').oplog.rs.find({ ts: { $gte: t } }).limit(1).pretty()

Replace the date string with your target time. This returns the first oplog entry at or after that timestamp, giving you the exact ts value to use.

Option Three: Use rs.status() for orientation

The rs.status() command returns the current replication position (optimeDate and optime.ts) for each replica set member:

rs.status()

This is useful for cross-referencing a wall-clock time to an approximate oplog position. Once you have an approximate position, use option two to pinpoint the exact ts value.

Option Four: Let Qlik Replicate log it for you

Start the task normally (without specifying a position) and allow Qlik Replicate to connect to the MongoDB oplog. Qlik Replicate will log the current stream position it reads from in the task log output, in the exact format it expects. You can then use that as a reference and template for entering positions manually in future tasks.

This is the safest way to confirm the correct position format for your version of Qlik Replicate before attempting a manual entry.

Configuring the stream position in Qlik Replicate

Once you have your stream position value:

1. Open your task and click the Run drop-down > Advanced Run Options
2. Under Tables are already loaded. Start processing changes from:, select Source change position (e.g. SCN or LSN):
3. Enter the stream position in the format Qlik Replicate expects

Note: We recommend using option four first to confirm the exact position format your version of Qlik Replicate expects for MongoDB, as this can vary. Entering the value in an incorrect format will cause the task to start from an unintended position.

Environment

• Qlik Replicate

Connecting to an SFTP server using username and password authentication fails with the error:

Too many bad authentication attempts! 
com.jcraft.jsch.JSchException: 11 Too many bad authentication attempts!

Resolution

The issue is caused by the password containing a backslash (\). A backslash is treated as a control or escape character and must be escaped accordingly. If not handled correctly, a control or escape character in a password can cause connection or authentication errors.

Either remove the backslash (\) or replace it with a double backslash (\\) to escape it properly.

Example:

Previous, failing password: Test\123
Updated password: Test\\123

Environment

• Qlik Talend Cloud
• Qlik Talend Data Integration

When attempting to export data to .csv or as a Straight Table from a Vizlib Pivot Table object in Qlik Cloud Analytics, the following error message is displayed:

An error occurred during export. Please try again later.

Even small datasets will not export.  

This issue is not seen with this object in Qlik Sense Enterprise on-premise, but may occur with an app migrated to or published to Qlik Cloud from the on-premise install.

Resolution

Upgrade the Vizlib Pivot Table to version 3.17.3 or higher in all environments, then reload the affected app.

Cause

This is not a Qlik issue, and is specific to complex apps with large data sizes and Vizlib Pivot Table version 3.14.0 or earlier. No Qlik limitation is involved.  

It appears that only export to Excel (.xlsx) was fully supported for such apps in Qlik Cloud with earlier Vizlib object versions.  

Note that downloading as an image or PDF from a Vizlib object remains unsupported.

Environment

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows

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.

To start replication from a specific point in time on a DB2 LUW source, you will need to identify the LSN (Log Sequence Number) corresponding to your target timestamp and configure it in your Qlik Replicate task.

There are several ways to obtain the LSN depending on your environment and access level.

Prerequisite

Ensure the DB2 archive logs covering your target LSN range are still retained and accessible on the server. If those logs have been pruned or moved off the system, Qlik Replicate will not be able to read from that position, and the task will error out.

How to obtain the LSN

Option One: db2pd (Recommended)

Run the following on the DB2 server to list active log files with their LSN ranges and timestamps:

db2pd -db <DBNAME> -logs

Sample output:

Log File         First LSN       Last LSN        Timestamp
S0001234.LOG     0x000123456789  0x000123ABCDEF  2026-03-10-11.30.00

Locate the log file whose timestamp range covers your desired start time and note the First LSN for that file. Convert the hex value to decimal before entering it into Replicate (e.g., 0x000123456789 = 1251004137353).

Option Two: db2flsn Utility

If you know the specific log file number and offset, you can translate it to an LSN using the db2flsn command-line utility:

db2flsn -db <DBNAME> -lsn <log_file_number>/<offset>

This is useful when you already know which log file corresponds to your target time. Convert the resulting hex LSN to decimal before entering it into Replicate.

Option Three: SQL Query (Current LSN)

To retrieve the current active LSN directly from the database:

SELECT CURRENT_LSN FROM SYSIBMADM.SNAPDB;

This returns the LSN at the moment the query is executed. Use this if you want to start replication from approximately "now" with a precise LSN anchor rather than relying on the task default. Convert the hex value to decimal before use.

Option Four: Let Qlik Replicate log it for you

By design, Qlik Replicate does not support starting CDC from a specific timestamp for a DB2 LUW source endpoint. This is a documented limitation in the Qlik Replicate User Guide.

However, when a DB2 LUW CDC task is first created and started, Replicate internally generates a file named DB2LUW_TIMESTAMP_MAP (a SQLite database) in the task's data folder. This file continuously maps processed LSN values to their corresponding timestamps each time the task runs. As a result, it provides a workaround to approximate a timestamp-based start position — by identifying the LSN that corresponds to the desired point in time and using that LSN to resume the task.

The only prerequisite for this approach is that the DB2 transaction logs covering the target time period must still be available and accessible on the source server.

Configuring the LSN in Qlik Replicate

Once you have your LSN value:

1. Open your task and click the Run drop-down > Advanced Run Options
2. Under Tables are already loaded. Start processing changes from:, select Source change position (e.g. SCN or LSN):
3. Enter the LSN in decimal format (e.g., 1251004137353)

DB2 tools typically display LSN values in hexadecimal. Please ensure you convert to decimal before entering the value in Qlik Replicate; the task will start from an incorrect log position.

Environment

• Qlik Replicate
• Qlik Talend Cloud

When asking the Qlik Answers Documentation Assistant a question and checking the source, it throws the following error:

Cannot access the source

Resolution

This issue occurs when the Assistant user accessing the Documentation assistant does not have permission to the source. For reference, when setting up a documentation assistant, there should be two spaces:

• Assistant Data: Managed space
• Assistants: Managed space

As the Knowledge base lives in the Assistant Data space, confirm that Can consume data and Can view permissions are set:

For more information, see Qlik Answers use case: Documentation assistant.

In addition, if the Documentation assistant is consuming data from a Direct Access Gateway, confirm that the Assistant users have the permission Can Consume Data for the space where the Direct Access Gateway is installed.

Environment

• Qlik Answers
• Qlik Cloud