When a user is deleted, any spaces, apps, scripts, and data connections they own will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Source: Reassigning ownership of spaces and resources (Qlik Cloud Documentation)

But even if the app is considered an Orphaned App, the owner can be changed in the Qlik Cloud Analytics Administration Console:

1. Open Qlik Cloud and open the menu
2. Access the Administration menu
3. Go to Content
   
   
   
   
4. Select the Apps tab
   
   
5. Filter by Deleted User in the Owner column
   
   
   
   Apps owned by Deleted Users will be listed.
   
   
6. Click the ... (ellipses) menu
   
   
   
   
7. Select Change Owner and change the ownership of the app

Environment

• Qlik Cloud Analytics

After an upgrade to QlikView September 2025 SR1, tasks defined in the QlikView Management Console using an external program fail.

The QlikView server's Windows Event log shows the following error:

Faulting application name: Qv.exe, version: 12.100.20100.0, time stamp: 0x692464ea
Faulting module name: ntdll.dll, version: 10.0.20348.4893, time stamp: 0xfd32fdb3
Exception code: 0xc0000005

Affected versions:

• QlikView September 2025 SR 1

Resolution

This is a known QV.exe defect (QCB-34453). Upgrade to QlikView September 2025 SR 2 or later releases.

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

Cause

Product Defect ID: QCB-34453

By Giacomo Brioschi, Principal Solution Architect, Qlik | Sathisan Vannadil, Senior Partner Solutions Architect, AWS | Sunil Yerkola, Senior Solutions Architect, ISV, AWS.

This guide walks you through the complete setup to bridge Amazon Quick and the Qlik MCP server, enabling real-time access to trusted Data Products with Qlik Trust Score for governed, AI-ready data, and insights and context from the Qlik Analytics Engine, all from within Amazon Quick.

Content

• What you'll need
• Step 1: Configure user roles for MCP access
• Step 2: Assign the new MCP role to users or groups
• Step 3: Create a new OAuth client for Amazon Quick
• Step 4: Add the Qlik MCP server as a connection in Amazon Quick
• Step 5: Create a new chat agent in Quick that uses the Qlik MCP server as an action
• Step 6: The power of Amazon Quick and the Qlik MCP server in action
• Troubleshooting
• Related Content

What you'll need

• An active AWS account
• Amazon Quick setup with user rights to create Connectors
• A Qlik Cloud tenant where you have Tenant Admin rights

Step 1: Configure user roles for MCP access

A Qlik tenant administrator must create (or update) a custom user role that grants the Qlik MCP permission. Without this, users will authenticate successfully but won't be able to execute any MCP tools.

1. In the Administration activity center, click Manage users.
2. Go to the Permissions tab and click Create new.
3. Assign a name to the role (e.g., MCP User) and under Features and actions > Agentic AI, set the MCP permission to Allowed.
4. Click Save.
   
   Setting the MCP permission to Allowed under Features and actions in a Qlik Cloud custom role
   

Step 2: Assign the new MCP role to users or groups

1. In the Administration activity center, click Manage users and go to the All users tab.
2. Click the three-dot menu (...) (A) on the right side of the user's row and select Manage roles (B).
   
   
   
   
3. Assign the MCP role to each user who needs access to the Qlik MCP server. Alternatively, you can assign the new role to a group of users.
   
   
   
   
4. Save your changes.

This can also be done from the Permissions tab. Use the Auto assign drop-down to give permission to all users in your tenant.

Space permissions and Section Access rules still apply. The MCP role grants access to the MCP server itself, but what each user can see and do through MCP is governed by their existing Qlik Cloud permissions. See Qlik MCP server access and permissions for details.

Step 3: Create a new OAuth client for Amazon Quick

The OAuth client authenticates and scopes user access when Quick connects to the Qlik MCP server. A tenant administrator must create an OAuth client for the integration. Once the OAuth client is ready, you can add the Qlik MCP server as a connection in Quick.

Alternatively, you can use OAuth Dynamic Client Registration (DCR), which allows an LLM client to register itself automatically with Qlik Cloud, without the tenant administrator needing to create an OAuth client in advance.

For more information, see how to connect to the Qlik MCP server and how to create OAuth clients for LLM clients in our online help.

Amazon Quick supports two OAuth client types for User authentication: Web (server-side, browser-based redirect flow) and Native (client-side, PKCE-based flow without a backend secret). Choose the one that best fits your security requirements and use case. The following section describes the Web configuration as an example.

1. In your Qlik Cloud tenant, navigate to the Administration activity center.
2. Go to OAuth and click Create new.
3. For the Client type, select Web.
4. Enter a name for the OAuth client (e.g., Amazon Quick MCP) and optionally add a description.
5. Under Scopes, select user_default and mcp:execute.
   
   
   
   Optionally add offline_access to reduce re-authentication frequency to once every 30 days from the default 6-hour expiry.
   
   
6. Under Add redirect URLs, enter the authentication callback URL for Quick as a redirect URI: https://{region}.quicksight.aws.amazon.com/sn/oauthcallback. Replace {region} with your AWS Region (for example, us-east-1).
   
   
   
   
7. Click Create.
8. Immediately copy the Client ID and Client Secret; you'll need both in the next step to configure the integration on the Amazon Quick side, and the secret won't be shown again.

Important, tenant admin must connect first: according to Qlik documentation, the tenant administrator has to be the first user to connect and authenticate with any new MCP client. This establishes tenant level trust between Quick and the Qlik OAuth app. Until the admin completes this first connection, other users' connection attempts will fail. Make sure the admin completes the Quick side integration (Step 4) and authenticates before rolling out access to other users.

Step 4: Add the Qlik MCP server as a connection in Amazon Quick

This step is performed in Amazon Quick, not in Qlik Cloud.

In this final configuration step, you will create an Amazon Quick connection to the Qlik MCP server to access your trusted data foundation. Once this is completed, you will be able to use your Amazon Quick Chat Agents to invoke the available tools to retrieve insights from Qlik. Instructions for adding a remote MCP server connection in Quick will depend on the Quick integration UI.

At a high level:

1. Sign in to Amazon Quick using your web browser.
2. Go to More on the sidebar menu, select Connectors, and click Model Context Protocol within the list of supported connectors.
3. On the Create integration screen, enter the Name and Description for your Qlik MCP integration. For the MCP server endpoint, enter the URL of the Qlik MCP server as https://{your-tenant-hostname}.{your-tenant-region}.qlikcloud.com/api/ai/mcp, as shown in the screenshot below, and make sure to replace {your-tenant-hostname} and {your-tenant-region} with the hostname and region of your Qlik Cloud tenant.
   
   
   
   
4. Choose Next once you're done.
5. In the following Authenticate screen, select User Authentication as the Authentication method, Custom user based OAuth as the Auth Configuration, and enter the following details:
   1. Enter the Client ID and Client Secret that you previously copied from the Qlik OAuth client you created in Step 3. If you chose Native as the OAuth client type, leave Client secret empty.
   2. Token URL allows a client to perform an OAuth flow with Qlik to obtain a token set. Enter your token URL as https://{your-tenant-hostname}.{your-tenant-region}.qlikcloud.com/oauth/token, replacing your-tenant-hostname and your-tenant-region with the hostname and region of your Qlik Cloud tenant. 
   3. The Authorization URL is the URL that the MCP server uses to retrieve the authorization token. Enter your Authorization URL as https://{your-tenant-hostname}.{your-tenant-region}.qlikcloud.com/oauth/authorize, again replacing the tenant hostname and region placeholders.
      
      
      
      
6. Click Create and Continue.
7. Authenticate by signing into your Qlik Cloud tenant when prompted.
8. Click Approve to authorise Quick to access your Qlik Cloud data.

   Data sharing notice: by clicking Approve, you enable the Qlik MCP server to share your Qlik Cloud data with Amazon Quick. Quick is not managed by Qlik, and your data will be stored and processed under AWS's control. Check your organisation's AI data sharing policies before proceeding.

   
   
   
9. In Manage Tools & Permissions, you can list the tools available for read and write operations, and in the final section, Publishing the connection, you have the option to share this connection with your team members, e.g., with users or a group of users who can access the Qlik MCP server via Amazon Quick.
   
   In this example, the connection has been shared with a group called Qlik Test.
   
   
   
   
10. Click Publish to create the connection.
11. If the integration creation has been successful, you should be able to see the list of actions (tools) available within the connector, as shown in the snapshot below:
    
    
    
    For a complete list of Qlik tools available, see Qlik MCP tools | help.qlik.com.

Step 5: Create a new chat agent in Quick that uses the Qlik MCP server as an action

With the connector in place, the tools that the Qlik MCP server provides are now available within Amazon Quick. Chat Agents in Amazon Quick help users explore data, analyse information, and take actions through open-ended natural language conversations, now including Qlik's capabilities. Agents are configured with specific goals, knowledge sources, and connected tools, and can evolve from simple question answering to orchestrating complex workflows. You can use chat agents to:

• Generate content and provide answers through natural language conversations
• Analyse and summarise information from connected spaces, dashboards, topics, datasets, and uploaded files
• Invoke actions to perform predefined steps for consistent, repeatable outcomes

For more information, see Create, customize, and deploy AI-powered chat agents in Amazon Quick | docs.aws.

Let's explore together how to create an Agent in Amazon Quick that uses the Qlik MCP server connection.

1. When you are in Amazon Quick, go to More on the left sidebar and click Chat Agents, then select Create a chat agent from the central part of the UI.
   
   
   
   
2. Describe in your own words how you want the agent to behave; Amazon Quick will use that to automate the setup for you. This step is optional and can be skipped in favour of manual configuration.
3. In the Configure chat agent window, make sure that within Actions, the Qlik MCP integration connection configured in Step 3 of this guide is linked; otherwise, link it manually.
4. Once you're done, click Launch chat agent.
   
   

Step 6: The power of Amazon Quick and the Qlik MCP server in action

Now you're ready to harness the full power of Qlik's trusted Data Products and Analytics Engine within Amazon Quick workflows through the newly created agent. What once required switching between tools can now happen in a single, unified experience.

Troubleshooting

Problem: Non-admin users can't connect
Likely root cause: Tenant admin hasn't completed first connection yet (see note in Step 3)

Problem: OAuth callback fails
Likely root cause: Region placeholder in the redirect URL doesn't match your Quick instance's actual region

Problem: User connects but can't access specific apps or data
Likely root cause: Space permissions or Section Access rules are restricting access; this is by design

Problem: The user is not able to use Qlik tools from the Amazon Quick Chat Agent
Likely root cause: Make sure the Qlik MCP server connection is added to the Chat Agent's available actions

Related Content

• Deploying and administering Qlik MCP server
• Qlik MCP server access and permissions
• Connecting to the Qlik MCP server
• OAuth2 clients Qlik Cloud supports
• Integration demo

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external data sources and tools.

Connecting Perplexity to the Qlik MCP server means you can get Perplexity’s real-time web search and reasoning alongside Qlik’s governed analytics data in a single conversation, or have it take action to manage operations within your Qlik Cloud tenant.

What you'll need

• A Qlik Cloud tenant with the MCP server enabled by a tenant administrator. Review Deploying Qlik MCP server for a tenant for details.
• A Perplexity Pro, Max, or Enterprise account (accurate at time of writing). If using an enterprise account, you must have permission to create new connectors, or ask an administrator to help.
• Tenant administrator access in Qlik Cloud to create an OAuth client.

How the Qlik MCP server works

A short orientation before touching any settings:

• The MCP server URL follows the pattern https://<your tenant URL>/api/ai/mcp.
• All connections are user-bound: access tokens are scoped and time-limited, and data access is enforced by the same access controls as when a user uses the interface directly.

See Qlik MCP server for details.

Which OAuth client type should I use?

Before creating the OAuth client in Qlik Cloud, decide which client type fits your situation. For connecting Perplexity, the relevant choice is between Web and Native.

Web client (recommended for most organisations)

A Web client issues a client secret in addition to a client ID. The secret is stored server-side on Perplexity and is never exposed to the browser or end user. This makes it the more secure option: even if someone obtains the client ID, they cannot complete the OAuth flow without the secret.

Use a Web client when:

• You are rolling out the connector to a team or organisation and want an additional layer of credential protection.
• Your organisation’s security policy requires confidential client flows.
• You have an admin who can manage secret rotation if needed.

Copy the client secret at creation time. Qlik will not show it again. For a Web client, you will paste it into Perplexity during connector configuration.

Native client (lightweight public client)

A Native client does not use a client secret. It relies on the OAuth PKCE flow, which protects against code interception without requiring a shared secret. This is a valid and commonly used pattern for public clients.

Use a Native client when:

• You want the simplest possible setup with no secret to manage or rotate.
• Your organisation permits public client flows for internal tooling.

At a glance

Both client types work with Perplexity’s custom remote connector flow.

Step 1: Prepare the OAuth client in Qlik Cloud

The tenant administrator creates the OAuth client:

5. In the Qlik Cloud Administration activity center, go to OAuth and click Create new.
6. Select Web or Native as determined above.
7. Add the required scopes: user_default and mcp:execute.
   Optionally add offline_access to reduce re-authentication frequency to once every 30 days from the default 6-hour expiry.
8. For the redirect URL, enter Perplexity’s OAuth callback:
   
   
   • https://www.perplexity.ai/rest/connections/oauth_callback
   • For organisations on the Perplexity Enterprise subdomain, use https://enterprise.perplexity.ai/rest/connections/oauth_callback instead.
     
     See Adding Custom Remote Connectors for more details.
9. If using a Web client, copy the client secret immediately. Qlik will not show it again.
10. Note down the Client ID.

See Deploying Qlik MCP server for a tenant for details. 

Step 2: Add the connector in Perplexity

1. Go to Account settings > Connectors and click + Custom connector, then select Remote.
2. Fill in the required fields:
   • Name: Qlik Cloud (or your tenant name).
   • MCP Server URL: https://<your-hostname>.<your-region>.qlikcloud.com/api/ai/mcp
   • Authentication: OAuth 2.0. Enter the Client ID from step 1. For a Web client, also enter the Client Secret. For a Native client, leave the secret field blank.
   • Transport: Streamable HTTP.
3. Acknowledge the data-sharing warning and click Add.
4. Navigate back to the connector listing and find the new connector.
5. Click Add Connector on the connector card to start the Qlik OAuth flow, sign in to your Qlik Cloud tenant, and click Approve.

By clicking Approve, you are authorising the Qlik server to share your Qlik Cloud data with Perplexity, a third-party system not managed by Qlik. Check your organisation's AI data-sharing policies before proceeding.

If the Qlik MCP server supports OAuth discovery (via /.well-known/oauth-authorization-server), Perplexity can detect endpoints and scopes automatically, and you may not need to enter them manually.

Step 3: Enable the connector and test it

Toggle the connector on under Sources in a Perplexity thread. You can also type the connector name, and it’ll suggest adding it to the thread.

Try these example prompts to confirm the connection is working:

• “What apps are available in my Qlik Cloud tenant?”
• “Summarise the key metrics from [your data product name].”
• “What does [KPI name] look like this month compared to last?”

Organisation members can add custom remote connectors if admins have enabled them. Only admins can share a connector with the entire organisation, done from the Permissions screen in Enterprise settings.

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

Can I restore one of those backups?

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

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

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

Environment

• Qlik Cloud Analytics

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

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

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

How to Back Up Qlik Cloud Apps

There are several ways to back up Qlik Cloud content:

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

Qlik Automate

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

Here are some helpful resources to get started:

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

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

Qlik CLI

Qlik CLI enables app exports using command-line tools.

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

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

Qlik REST APIs

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

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

Third-party solutions

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

Environment

• Qlik Cloud

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.

Qlik Cloud automatically places applications on compute engines based on calculated metrics that determine the required resources. This automatic placement works well for most apps, but some require manual intervention.

Apps with large chart objects that generate large hypercubes can consume all available memory and crash. By pinning an app to a specific engine size, you control the minimum compute resources available for interactive consumption.

For details, see Assigning engines to improve application performance and Pin applications to engine sizes.

This article aims to clarify how reloads are handled for an app pinned to an engine, since assigning an engine concerns only the opening and consumption of apps by end users, not app reloads.

How reloads are handled:

• The optimization concerning app reloads is based on a similar concept: Qlik Cloud still automatically places applications on engines based on calculated metrics that determine the required resources.
• As a rule, the app will initially be placed on an engine based on the metrics of the last successful reload.
• If that engine is not sufficiently large, the reload will at first fail and then be moved to a larger one, where it will restart from scratch.
• This process is not made obvious to end users and administrators. The initial failures won't be noticed in logs or alerts, although analyzing the details might show a later "start time" than expected since only the successful run will be shown.
• The next time the task is run, it will automatically start on the larger engine.
  In rare scenarios, the calculated metrics might not reflect the required resources, and the behaviour could be erratic. In case of issues, do not hesitate to contact support with all the necessary information (appIds, taskIds, reloadIds, timestamps). 

Environment

• Qlik Cloud

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

Is Qlik NPrinting affected by CVE-2025-32433?

Resolution

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

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

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

Environment

• Qlik NPrinting

There are two different ways to check the patch version of your Qlik Talend JobServer:

• Log in to your Qlik Talend Administration Center (TAC) and navigate to Conductor (A) > Servers (B)
  
  The patch level can be found below the Server Version (C) column, as shown below.
  
  
  
  The version will not be listed for any JobServers that are disconnected from Qlik Talend Administration Center. 
  
  

• On the server that JobServer is installed, navigate to <JobServer>/agent

  • If the version of Talend JobServer is TPS-6002 (R2025-04) or higher, the patch level for JobServer can be found in the branding.properties file. 
    
    

  • If the branding.properties file is missing, then a lower version of Jobserver is being used. The full version can be found in <JobServer>/agent/lib and reviewing the org.talend.remote file extension name:
    
    Example: org.talend.remote.server-8.0.2.20250129_0823_patch indicates the patch level is R2025-01 (TPS-6002)
    
    

Environment

• Qlik Talend Administration Center

Qlik Software Windows executables (such as Qlik Talend Studio, Talend Installers, Qlik NPrinting) come with an embedded digital signature, which signals Windows (and any security software) that the executable has been verified.

The digital signature is typically valid for 2 to 3 years before requiring renewal.

However, when reviewing the signature, it may show that it was revoked by the issuer around April 28th of 2026, even though it should still be valid for another 6-12 months.

Consequently, security software may block any executable that does not have a valid or current digital signature, leading to users being unable to launch the installed Qlik software.

Resolution

While proceeding by bypassing the signature check is an option, it is not always a feasible workaround. Qlik is actively replacing the affected installation files with executables that include both the digital signature and a new (valid) countersignature. 

Re-downloading the installation package from the Qlik Download page will resolve the issue in most instances. 

• Qlik Sense Enterprise on Windows and Desktop May 2026 IR
• Qlik Sense Enterprise on Windows November 2024 Patch 28 (release expected May 27th)
• Qlik Sense Enterprise on Windows May 2025 Patch 20 (release expected May 27th)
• Qlik Sense Enterprise on Windows November 2025 Patch 10 (release expected May 27th)

Not all files have been replaced at this point. Specifically, major releases (IR) are still undergoing processing.

To prevent this from recurring, Qlik has updated its digital signing processes.

If your product is not available on the Qlik Download page (such as Qlik Talend Studio), contact Qlik Support to receive the newly compiled executable (R2024-05 through R2026-05). 

Cause

The revocation of the digital signature was due to identifying a countersignature that did not have a timestamp set. 

Internal Investigation ID(s)

ITSYS-16864

Environment

• Qlik Products

After an admin invited a user to a Qlik Cloud tenant, the user never received the invitation email.

How can this be resolved quickly?

Resolution

There are several possible reasons for a user not to receive their expected invite email, such as temporary glitches with the recipient's mail server, a spam filter capturing the invite, or even a simple accidental deletion of the invite.

However, an invited user does not actually need the invitation email to access the tenant. They can log in to the tenant after the invite was sent, regardless of whether or not they received the email.

To get a user you previously invited into your Qlik Cloud tenant:

1. Request that the user access the tenant's URL (example: https://TENANT.REGION.qlikcloud.com)
2. They are redirected to the login panel
   • If the user already has a Qlik account with the same email used for the invitation, ask the user to log in
   • If the user doesn't have a Qlik account with the same email used for the invitation, ask them to sign up for one, which will redirect them to https://register.myqlik.qlik.com/
     
     
     
     For instructions, see How to Register a Qlik Account.
     
     
   • Once the user has successfully logged in, they can use the tenant as normal.

Environment

• Qlik Cloud Analytics

After upgrading to Microsoft Windows Server 2025, the installed Qlik Sense Enterprise on Windows patch version is no longer visible in the Installed Updates summary.

In previous Windows Server versions, navigating to Control Panel > Programs and Features > Installed Updates displayed the patch version. 

Changes in Windows Server 2025 affect how installed updates are displayed in the Control Panel. This does not indicate a failed installation.

You can verify what patch version of Qlik Sense Enterprise on Windows you have installed by retrieving it from the Windows registry. Alternatively, see What version of Qlik Sense Enterprise on Windows am I running?

Resolution

The registry key including the patch version is:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\QlikSenseEnterprisePatch

You can query the registry using PowerShell.

Administrator privileges are required to access the Registry or to run the recommended PowerShell script.

Option One: Use Get-QlikSensePatchInfo.ps1 

We recommend using the attached Get-QlikSensePatchInfo.ps1 script. 

1. Download Get-QlikSensePatchInfo.zip and extract it
2. Run Get-QlikSensePatchInfo.ps1
3. The script will return:
   • DisplayName: Patch name
   • DisplayVersion: Patch version number
   • UninstallString: Uninstall command

Example output:

DisplayName : Qlik Sense May 2025 Patch 17
DisplayVersion : 14.231.29
UninstallString : "C:\ProgramData\Package Cache\c70a85bf-ecb8-4772-affb-80f28a97bdcb\Qlik_Sense_update.exe"

Option Two: Query the registry manually

1. Open a PowerShell command line with elevated permissions
2. Run the following PowerShell command:
   

   Get-ItemProperty "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\QlikSenseEnterprisePatch" |
   Select-Object DisplayName, DisplayVersion, UninstallString​

Environment

• Qlik Sense Enterprise on Windows
• Windows Server 2025

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

Resolution

Solution 1

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

Solution 2

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

Solution 3

Encryption keys:

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

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

Cause

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

Related Content

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

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

Environment

• Qlik Sense Enterprise on Windows 

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

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

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

Resolution

Only deploy of the listed options.

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

Option 1:

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

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

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

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

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

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

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

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

If you wish to disable app distribution from certain nodes:

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

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

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

Environment

• Qlik Sense multi-cloud environments. Any versions.

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

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

Resolution

Two solutions exist.

Deactivate Unused Users via Security Account

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

Modify Users Directly in Qlik Talend Administration Center Database

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

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

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

Cause

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

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

About User Types and License Seats

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

The main user/license types are:

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

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

Environment

• Qlik Talend Administration Center