You may encounter this issue that unable to connect to Azure SQL Database after enabling TLS v1.2 on the database side, and gives an error when executing the task on the Talend management Console side.

java.sql.SQLException: Reason: Login failed due to client TLS version being less than minimal TLS version allowed by the server.

Resolution

When using the MSSQL components in Talend Studio, Qlik Talend components support 2 kinds of driver (explicit choice to make). The open source one JTDS or the official Microsoft jdbc driver.

It is recommended to use the official MSSQL driver to ensure greater compatibility. The jTDS is not recommended but can still be supported and this driver in a “deprecated” status,  Keep this possibility to use this driver for users who want to use it and for whom it remains compatible with their databases.

There are two solutions for this issue as belows

Solution 1

The jTDS driver prior 1.2 does not support TLS v1.2. Please use the official JDBC driver from Microsoft (switch to the official MSSQL driver to ensure greater compatibility).

• https://learn.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server
• ways-to-install-external-modules-into-Talend-Studio

Solution 2

Add ssl=require to the end of the JDBC connection URL (ex: jdbc:jtds:sqlserver://my-example-instance.c656df8582985.database.windows.net:1433;ssl=require), or in "Additional JDBC parameters" field of  MSSQL components and then re-publish the job and run on Talend management Console.

Cause

The open source  jTDS driver, specifically earlier versions like 1.2, does not natively support TLS 1.2. This can lead to connection failures when connecting to SQL Server instances that enforce TLS 1.2, such as Azure SQL Managed Instances or on-premises servers configured to require TLS 1.2 for security reason. 

Related Content

publish-jobs-to-Talend-Cloud

Environment

• Talend Studio 
• Talend Cloud 

Qlik Insight Advisor performs slowly. No errors are logged.

Resolution

To optimize performance,

• Review what fields you have available for analysis: Enabling a custom logical model 
• Review the business logic to improve performance using the following guide: What is Insight Advisor and business logic?

For additional performance or optimization questions, head over to the Qlik App Development forum, where your knowledgeable Qlik peers and our active Support Agents can better assist you.

Environment

• Qlik Insight Advisor

Leasing a license to the QlikView Desktop client with a custom user fails. 

Resolution

To set up QlikView to lease a license to a custom user, allow license leasing for DMS mode:

1. On the Windows Host running QlikView Desktop, browse to  C:\Users\USERNAME\AppData\Roaming\QlikTech\QlikView
2. Open the settings.ini in a text editor of your choice (as administrator)
3. Add the following parameter and value:
      
             SupportLeaseLicenseForDMSMode=1
   
   See How to change the settings.ini in QlikView Desktop for details.
4. Open the QlikView AccessPoint using QlikView Desktop and lease a license
   
   See How to lease a license in QlikView with DMS mode enabled for reference. 

If adding SupportLeaseLicenseForDMSMode=1 does not work:

1. On the QlikView server, browse to /ProgramData/QlikTech/
2. Rename the LicenseService folder to, for example, LicenseService_old
3. Open the QlikView Management Console
4. Navigate to System > License > Choose your QlikView Server's license
5. Click Apply License 
6. Open the QlikView AccessPoint using QlikView Desktop and lease a license
   
   See How to lease a license in QlikView with DMS mode enabled for reference. 

Internal Investigation ID(s)

QV-24037

Environment

• QlikView

This article will outline how to successfully change the service account running Qlik Sense. 

Contents:

• Account Requirements: What the account needs access to.
• Prep work
• Changing Qlik Sense dependencies
• Change the service account
• External Dependencies
• Video Demonstration
• Related Content

Account Requirements: What the account needs access to.

1. Certificates
   • Access to the certificate(s) for the site
2. Files and file shares
   • Access to the installation path for Qlik Sense
   • Access to %ProgramData%
   • Access to C:\Program Files\Qlik
   • Access to the Service Cluster share
3. Access to external systems as data sources, e.g.
   • Databases
   • UNC shares to QVDs, CSVs, etc

Note: Many of the file level permissions would ordinarily be inherited from membership to the Local Administrators group. For information on non-Administrative accounts running Qlik Sense Services see Changing the user account type to run the Qlik Sense services on an existing site.

Prep work

Record the Share Path. Navigate in the Qlik Management Console (QMC) to Service Cluster and record the Root Folder.

 

 

 

Changing Qlik Sense dependencies

1. Stop all Qlik Sense services
2. Ensure permissions on the Program Files path (this should be provided by Local Administrator rights):
   1. Navigate to the installation path (default: C:\Program Files\Qlik)
   2. Select the Sense folder > Right Click > Properties > Security > Edit > Add
      1. Lookup the new service account
      2. Ensure that the account has Full control over this folder
3. Ensure permissions on the %ProgramData% path (this should be provided by Local Administrator rights):
   1. Navigate to the installation path (default: C:\ProgramData\Qlik)
   2. Select the Sense folder > Right Click > Properties > Security > Edit > Add
      1. Lookup the new service account
      2. Ensure that the account has Full control over this folder
4. Ensure access to the certificates used by Qlik Sense
   1. Start > MMC > File > Add/Remove Snap-In > Certificates > Computer Account > Finish
      1. Go into Certificates (Local Computer) > Personal > Certificates
      2. For the Qlik CA server certificate (under Certificates (Local Computer) > Personal > Certificates)
         • Right Click on the Server Certificate > All Tasks > Manage Private Keys > Ensure that the new service account has control
      3. If using a third party certificate, do the same
5. Ensure access to the Service Cluster path used by Qlik Sense
   1. Start > Computer Management > Shared Folders > Shares > Select the Share path
   2. Right click on the Share Path > Properties > Share Permissions > Add the new service account to have full control
   3. Open Windows File Explorer and navigate to the folder (e.g. C:\Share) > Right click on the folder > Security > Edit > Add the new service account to have full control
6. Ensure membership in the Local Groups that Qlik Sense requires:
   1. Start > Computer Management
   2. Navigate to Local Users and Groups > Local Groups
   3. Add the new service account as a member of:
      • Administrators (if using this configuration option)
      • Performance Monitor Users
      • Qlik Sense Service Users

Change the service account

1. Swap the account for all Qlik Services except the Qlik Sense Repository Database Service.
   1. Open the Windows Services Console
   2. Locate the services
   3. One by one open the Properties of the Service and change the accountover by using the Windows services control panel
2. Start all Qlik Sense Services
3. Access the QMC to validate functionality, preferably as a previously configured RootAdmin
4. Access the Data Connections section of the QMC
5. Toggle the User ID field and change the data connections used by the License and Operations Monitor apps to use the new user ID and password:
   
   
   
   
6. Add the RootAdmin role to the new service account*
   1. QMC > Users
   2. Filter on the new UserID > Edit
   3. Add RootAdmin role
      
      *If this account is not existing yet in Qlik Sense, you would need to try to connect to the Hub/QMC with this new account first, in order to be able to see it in QMC>Users.
      
      
7. Execute the License Monitor reload task
8. Inspect the configured User Directory Connectors and change the User ID and password combination if previously configured.

External Dependencies

1. Go into the QMC > Data Connections section and inspect all Folder data connections to determine all network shares that the service account needs access to. Either change them yourself or alert the necessary teams to provide both Share and NT level access to these shares.
2. Inspect all Data Connections and ensure that none use the old Service account and password. Follow up with necessary teams to provide access to data sources that used the old credentials.

Video Demonstration

Related Content

How to change the share path in Qlik Sense (Service Cluster) 

Microsoft will deprecate Change Data Capture (CDC) components by Attunity. See SQL Server Integration Services (SSIS) Change Data Capture Attunity feature deprecations | microsoft.com for details.

Will this affect Qlik Replicate? 

Resolution

This announcement does not affect Qlik Replicate. It is only relevant to the product "Change Data Capture (CDC) components by Attunity".

Microsoft distributes and provides primary support for this product. Qlik Replicate's functionality will remain the same.

Environment

• Qlik Replicate

Beginning with Qlik Sense Enterprise on Windows 2024, Qlik has extended CSRF protection to WebSockets. For reference, see the Release Notes.

In the case of mashups, extensions,and or other cross-site domain setups, the following two steps are necessary: 

1. Add additional response headers. These headers help protect against Cross-Site Forgery (CSRF) attacks.
2. Change the applicable code in your mashup or extension.

Content

• Add the Response Headers
• Adapt your Mashup or Extension code
• Workflow
• Verification

Add the Response Headers

The three additional response headers are:

Access-Control-Allow-Origin: https://localhost:8080
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: qlik-csrf-token

Localhost and port 8080 are examples. Replace them with the appropriate hostname. Defining the port is optional. 

If you have multiple origins, seperate them by comma.

Example:

For more information about adding response headers to the Qlik Sense Virtual proxy, see Creating a virtual proxy. Expand the Advanced section to access Additional response headers.

Adapt your Mashup or Extension code

In certain scenarios, the additional headers on the virtual proxy will not be enough and a code change is required. In these cases, you need to request the CSRF token and then send it forward when opening the session on the WebSocket. See Workflow for a visualisation of the process.

An example written in Enigma.js is available here:

• Authentication: Qlik Sense JSON Web Token (JWT) 
• Code Sample 

The information and example in this article are provided as-is and are not directly supported by Qlik Support. More assistance can be found on the Qlik Integration forum. Professional Services are available to help where needed.

Workflow

Workflow

Verification

To verify if the header information is correctly passed on, capture the web traffic in your browser's debug tool.

Environment

• Qlik Sense Enterprise on Windows November 2024 and later

A binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with:

General Script Error

or

Binary load fails with error Cannot open file

Before Qlik Sense Enterprise on Windows November 2024 Patch 8, the Qlik Engine permitted an unsupported and insecure method of binary loading from applications managed by Qlik Sense Enterprise on Windows.

Due to security hardening, this unsupported and insecure action is now denied.

Binary loads of Qlik Sense applications require a QVF file extension. In practice, this will require exporting the Qlik Sense app from the Qlik Sense Enterprise on Windows site to a folder location from which a binary load can be performed. See  Binary Load and Limitations for details.

Example of a valid binary load:

Binary [lib://My_Extract_Apps/Sales_Model.qvf];

Example of an invalid binary load:

"Binary [lib://Apps/777a0a66-555x-8888-xx7e-64442fa4xxx44];"

Environment

• Qlik Sense Enterprise on Windows November 2024 Patch 8 and any later releases

When querying the /api/v1/apps endpoint in Qlik Cloud Analytics, the results also include Scripts, Data Flows, and Table Recipes.

Is there a way to see only the apps?

Example output:

{                   
  "attributes": {
    "_resourcetype": "app",
    "createdDate": "2025-08-27T06:31:14.767Z",
    "custom": {},
    "description": "",
    "dynamicColor": "",
    "encrypted": true,
    "hasSectionAccess": false,
    "id": "54b3b705-f00f-48ce-bbff-2497926f79e0",
    "isDirectQueryMode": false,
    "lastReloadTime": "",
    "modifiedDate": "2025-08-27T06:31:15.215Z",
    "name": "THIS IS ACTUALLY A TABLE RECIPE",
    "originAppId": "",
    "owner": "auth0|omitted",
    "ownerId": "omitted",
    "publishTime": "",
    "published": false,
    "thumbnail": "",
    "usage": "SINGLE_TABLE_PREP"
  },
  "create": [
    {
      "canCreate": true,
      "resource": "sheet"

...

Resolution

This is working as designed. From the Qlik Cloud Analytics perspective, Scripts, Data Flows, and Table Recipes are considered apps. 

To recognize them, the “usage” attribute needs to be checked:

"usage": “ANALYTICS” → apps
"usage": "SINGLE_TABLE_PREP" → table recipes
"usage": "DATA_PREPARATION" → scripts
"usage": "DATAFLOW_PREP" → data flows

Environment

• Qlik Cloud Analytics

When creating a Log Stream Staging task in Qlik Replicate, Qlik Enterprise Manager (QEM) may report an Express license restriction:

Express license: Running a task with 'Log Stream Staging' is not supported [1021616]

This can happen if the wrong license was registered in Qlik Enterprise Manager. Checking and re-registering the correct license in Qlik Enterprise Manager fixes the problem.

Resolution

To resolve this issue, re-register the correct Replication Management license in Qlik Enterprise Manager (QEM):

1. In Qlik Enterprise Manager, click the Gear (Settings) icon.
2. Select the Licenses tab.
3. Open the Replication Management sub-tab.
4. Verify the license properties. If they do not match the expected license (for example, the expiration date differs from other environments), click Register License.
5. Paste in the correct license text and register it.
6. Confirm that the license details update correctly.

Cause

Qlik Enterprise Manager maintains its own licenses for different modules (Replication Management and Replication Analytics). In this case, the incorrect license was applied under the Replication Management module for the prod Qlik Replicate server. As a result, Qlik Enterprise Manager interpreted the environment as running with an Express license.

Environment

• Qlik Enterprise Manager
• Qlik Replicate

Qlik supports connecting to SAP HANA DATABASE using Qlik's QvOdbcConnectorPackage. This assumes that the SAP HDBODBC Driver has been installed on the Qlik system.

To connect to the HANA Database using ODBC drivers:

1. Open the ODBC Data Sources from your system and check if the HDBODBC driver is installed:
   
   
   
   

2. If the drivers are missing, install SAP HANA CLIENT (see SAP HANA AND QLIK VIEW/SENSE | community.sap.com for details)

3. From ODBC Data Sources > USER DSN, select HDBODBC and complete your configuration

4. In Qlik Sense, use the created ODBC DSN to create a new connection

Environment

• Qlik Sense Enterprise on Windows

The new Straight Table was moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one.

This article aims to answer any frequently asked questions around this switch, beginning with:

• The old table will not be removed anytime soon. It will continue to work until further notice. We encourage you to subscribe to the Qlik Support Blog and What's New in Qlik Cloud to stay ahead of updates.
• The old table will not be updated further. Use the new table to benefit from future improvements.
• We monitor your feedback and will improve the functionality of the new table.

FAQ

What improvements does the Straight table come with?

Here are some examples:

• Grid styling
• Totals styling
• Pagination or virtual scroll
• Scrollbars outside of the table
• Add, delete many fields at the same time
• Cell font family, size and color styling
• Font styling by expression
• Column width options pixels, percentages
• Chart exploration, end user can pick dimensions and measures
• Header on/off
• Zebra striping
• Null value styling
• Selection info in export
• Totals in export
• Titles in export
• Cyclic dimension controls in dropdown

Will the old table be removed?

No, the old table will continue to work in the foreseeable future. Any changes will be notified in advance. Regardless, we highly recommend upgrading your tables as soon as possible to enjoy the new Straight Table's new functions. 

How do I convert to the new table?

The easiest way to convert your tables is to drop the new table chart onto the old one.

1. First, copy the old table
2. Edit the sheet that includes the Table
3. Open the Charts pane
4. Drag the Straight table over your table
5. Choose Convert to: Straight table

The new table looks different and offers more functionality that must be enabled to be used.

When will the old table be deprecated?

Not anytime soon, it will be a soft fade out. The new Straight Table will be the preferred choice for all new applications, and we anticipate many will upgrade to benefit from new functionality. Over time, the usage of the old table will diminish until most applications are using the new table anyway.

Will this affect Qlik Sense Enterprise on Windows?

Qlik Sense Enterprise on Windows will have the table feature aligned with Qlik Cloud Analytics in a future release.

I’m not happy with X and Y of the new table, will that be changed?

We’re closely monitoring feedback on the new table and are dedicated to creating the best possible experience, including improvements to accessibility. We are committed to accessible standards so people with disabilities can use our products. Printing, the tables should, of course, print in as consistent a manner as possible. As for usability, we aim to enable experienced users to reach functionality quickly, while also not overwhelming new users.

Originally, the old table was identified as table (retired). We removed the (retired) label.

Environment

• Qlik Analytics

This article provides the steps needed to successfully upgrade Qlik Replicate installed on a Windows Cluster.

Environment:

• Qlik Replicate 2021.5 upgrade to 2021.11
• Qlik Replicate upgrade 2021.11 to 2022.5 or 2022.11

Resolution

1. Stop all tasks. Note that some tasks could take up to 20 minutes or more to stop. Monitor the process before you continue.
2. Assuming we are on Active Node A: from the Cluster Manager, take the Attunity Replicate Server and Attunity Replicate UI server Offline
3. Take a backup of all your task definitions on Node A:Qlik Replicate Command Line Console as Administrator
4. Run:

   repctl -d "YOUR_DATA_DIRECTORY_PATH" exportrepository

   Example: ~Program Files\Attunity\Replicate\bin> repctl -d "S:\Programs\Qlik\Replicate\data" exportrepository
   This example writes the backup to the Replication_Definition.json file.
    
5. Back up your data directory by copying it to a folder location outside the Qlik Replicate directories. You can skip copying the \logs subfolder.
6. On Node A: verify the installed version of Attunity Replicate. This can be done by reviewing the program installed through the Windows Add/Remove programs feature. Note: attempting to “upgrade” with an identical version will lead to Attunity Replicate being uninstalled.
7. Verify what account the Attunity (or Qlik) Windows Services are run with. Note the account credentials (username and password). After the upgrade, the account may have been switched back to Local System and the account credentials will need to be entered again. 
8. On the active node: perform the upgrade by running a newer version of the Qlik Replicate executable.
   • Right-click on the executable and run as administrator.
   • Follow the on-screen instructions.
9. On Node A:
   • Verify that the Qlik Replicate Server and Qlik Replicate UI Server are stopped in the Cluster Manager
   • Verify that the Qlik Replicate Server and Qlik Replicate UI Server are stopped in the Windows Services 
10. Move the Cluster service (this is the role that manages your share drive/Qlik service/and client access point) to another node (Node B in our example). This is going to move the shared drive and service to the other node (Node B).
11. On Node B: run the same upgrade as previously done on Node A, repeating steps 8 to 9.
12. Repeat the upgrade steps on any additional nodes. 
13. Verify the account running the Attunity Replicate Services on all nodes, changing the account back to the account which was used before the upgrade (see step 7).
14. From the Windows Cluster, bring the Attunity Replicate Server and Attunity Replicate UI Server back online.
15. Resume the tasks. Note: resume tasks at a rate of five (maximum) at a time until all have been launched.

The Show Fields (A) checkbox in the Selections Tool (B) will always be disabled by default if Master Dimensions are defined. This is true for both Qlik Cloud Analytics and Qlik Sense Enterprise on Windows and is working as designed.

Behavior may have been different in previous versions of Qlik Sense Enterprise on Windows due to a defect.

Internal Investigation ID(s)

SUPPORT-5549

Environment

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows

The Qlik Analytics Migration Tool provides a structured and repeatable process for migrating analytics assets to Qlik Cloud. It enables teams to define migration plans, validate each step, and coordinate across roles to ensure secure and accurate execution.

Content

• Core Capabilities
• What Makes the Tool Different
• Why Move to Qlik Cloud
• How to Get Started
• Qlik Analytics Migration Tool (Quick Video Demo)

Core Capabilities

• Migrate Qlik Sense Client-Managed apps, streams, users, groups, data files, data connections, and much more
• Preserve content ownership, access rights, and user-generated content such as apps, private and community sheets, as well as bookmarks through dynamic user mapping
• Automatically rewrite load scripts to reflect updated cloud data connections and paths
• Configure structured plans and jobs to manage projects at scale
• Enable multi-user access to support collaboration and phased execution
• Log, validate, and roll back migration steps as needed
• Partially supports QlikView and Qlik NPrinting migrations to reduce redevelopment

What Makes the Tool Different

• Designed from real-world experience and refined for enterprise use
• Fully branded, hardened, and extended since acquisition
• Supports phased and repeatable execution across migration stages
• Adjusts load scripts and metadata automatically during migration
• Maintains user identity, private content, and access policies

Why Move to Qlik Cloud

Qlik Cloud provides continuous innovation, centralized governance, and integrated AI that is not available in on-premises environments. Customers migrating to Qlik Cloud immediately benefit from:

• Qlik Predict for AI-driven forecasting and predictions built into dashboards
• Qlik Answers for intuitive, natural language search and explanation
• Continuous cloud-native feature delivery with automated upgrades
• Real-time access to governed and streaming data sources
• Simplified DevOps, reduced infrastructure management, and tighter security control

How to Get Started

• Download the Qlik Analytics Migration Tool from Qlik's Download page. 
  
  
  
  
• Review full documentation at Qlik Analytics Migration Tool overview | Help.qlik.com 

Qlik Analytics Migration Tool (Quick Video Demo)

Learn More, Ask Questions, Share Experiences

The Qlik Community is the central place to get answers, exchange ideas, and collaborate with peers using the Qlik Analytics Migration Tool. Whether you're preparing for a full environment shift or running phased pilots, we encourage you to share your approach and learn from others moving to Qlik Cloud in the Move to Cloud forum.

Environment

• Qlik Cloud

This article explains how the Qlik Sense app button component can be used to send custom parameters directly to the automation without requiring a temporary bookmark. This can be useful when creating a writeback solution on a big app as creating and applying bookmarks could take a bit longer for big apps which adds delays to the solution. More information on the native writeback solution can be found here: How to build a native write back solution.

Contents

• Button configuration
• Automation configuration
• Limitations
• Related Content

Button configuration

1. In this example, we'll use an app that contains car sales opportunities from Salesforce. The straight table, the variable input dropdown, and the native button are important for this example.
   

   
   

2. Start editing the sheet and go to the button configuration section, set the action to "Execute automation" and specify the automation that should run when the button is clicked. If your automation isn't shown, you can copy and paste the automation id.
   
   
   
   
3. Additional input parameters can now be added through the "Add parameter" button.
   
   

   

4. Parameters require a key and a value, it's possible to use Qlik Expressions as input for the value. These expressions are evaluated when the button is clicked.
   
   
   
   
5. After adding the parameters, use the "Copy input block" button to copy the all parameters that will be sent to the automation to your clipboard.
   
   
   
   

Automation configuration

1. If you want anyone who can access the button to be able to run the automation, then set the automation's run mode to "Triggered".

   If you want to limit this to a specific group of users, you can leave the automation in Manual run mode and place it in a shared space that this group of users can access. More information about this is available here: Introducing Automation Sharing and Collaboration. Make sure to disable the Run mode: triggered option in the button configuration.

   
2. Right-click in the automation canvas and select "Paste Block(s)" to add the Inputs block to the automation. Connect the new Inputs block to the Start block. Apart from the default parameters, you'll also find your custom parameters as Inputs in the block.
   
   

   

3. You can now reference the custom parameters from the button in other blocks in the automation by selecting the output from the Inputs block.
   
   
   
   
   

    

Limitations

1. The maximum payload size when triggering an automation is 32kb. When using the GetCurrentSelections expression, every field value will be sent to the automation. This could exceed the 32kb limit. Use the temporary bookmark solution as described in this article instead: Native writeback solutions.
2. Other automation limitations are available here: Platform limitations.
3. More info on configuring the native button can be found here: Creating buttons.

Related Content

• Creating buttons
• Native writeback solutions

Environment

• Qlik Cloud
• Qlik Application Automation

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

A deployed 8.0.1 Talend Administration Center instance is bundled with Apache Tomcat 9.0.91. This Tomcat version has been flagged as being impacted by CVE-2025-24813.

Resolution

At this time, CVE-2025-24813 does not apply to the Talend Administration Center (TAC) webapp. The reason Talend Administration Center is not impacted at this time, is because Tomcat installed with Talend Administration Center has disabled the "Writes enabled for the default servlet" option (disabled by default); A prerequisite for being suspectable to an attack would be to have that setting enabled.

While the Talend Administration Center webapp itself is not impacted by the CVE, if users desire to remove those vulnerable jars removed from security scans (whether due to preference, security audit, or other considerations), users have the following options to pursue:

• If the current Tomcat instance that hosts Talend Administration Center 8.0 is version 9.0.x, users can upgrade Tomcat to 9.0.100 or higher.
• If the current Tomcat is using 10.1.34 or a prior version, users can upgrade Tomcat to at least 10.1.40 (or higher) and patch the TAC instance to QTAC-969.

Please note if users plan to upgrade Talend Administration Center from TPS-5552 or earlier (Using Tomcat 9) to QTAC-969 or higher for TAC 8.0, the recommended path would be to  deploy both Apache Tomcat 10.1.40 (or higher) and Java 17 to address this release. (One recommended option is to completely reinstall Tomcat & Talend Administration Center with the new installer and point to the new DB).

If users manually deploy Tomcat 10.1.40 (or a later version) alongside the Talend Administration Center to an instance, and wish to verify that the aforementioned flag(s) are disabled, kindly inspect the "web.xml" file located in (<Root Folder>/apache-tomcat/conf). Proceed to approximately lines 124-135, and examine the following configuration for the "org.apache.catalina.servlets.DefaultServlet":

<servlet>
    <servlet-name>default</servlet-name>
    <servlet-class>
          org.apache.catalina.servlets.DefaultServlet
    </servlet-class>
    <init-param>
        <param-name>readonly</param-name>
        <param-value>false</param-value>
    </init-param>
    <load-on-startup>1<load-on-startup>
</servlet>

The example shown above illustrates that the value is set to "false", signifying that it is write-enabled. If users want that functionality disabled, change the "param-value" flag to false, save the changes, and subsequently restart Tomcat (either via the start/stop bat/sh script, or with the service).

Internal Investigation ID(s) 

QTAC-918

Environment

• Talend Administration Center 8.0.1

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

Monthly monitoring of the data volume used in Qlik Cloud (Data for Analysis) is essential when using a capacity-based subscription.

This data is accessible in the Qlik Cloud Administration Center Home section:

For an overview of how the Data for Analysis is calculated, see Understanding the subscription value meters | Data for Analysis; its calculation considers the size of all resources on each day, and the day with the maximum size is treated as the high-water mark, which is then used for billing purposes. 

However, you may sometimes notice that the usage does not decrease as expected, even after reducing your app data. In such cases, it is recommended to review unused or rarely reloaded apps, as the previous app reload size may still be used for the calculation.

Resolution

To review the detailed usage, you can use a Consumption Report.

1. Distribute a consumption report; see Distributing detailed consumption reports | help.qlik.com for details on how to achieve this.
2. Review your data usage on the Data for Analysis sheet.
3. If you observe unexpected usage in apps, such as apps with reload infrequently, the is possible that the size is carried over from the previous reload.

To prevent the previous reload size from being carried over into the following month in similar use cases (specifically for apps that are not actively in use), a possible workaround is to reload apps using small dummy data to update the previous reload size of the apps.

Note that while offloading QVD files to, for example, S3 incurs no cost, any subsequent reload of those QVDs into Qlik Cloud will be counted toward Data for Analysis. Users should carefully evaluate whether this approach is beneficial.

Cause

Example case:

1. Extract external data into an app during reload.
2. Store the data as QVD files, and save the files outside Qlik Cloud (such as AWS S3).
3. Drop the source tables from the data model at the end of the script.
4. Reload completes; the final data model contains no tables.

The app is reloaded only once a month (or even less frequently) for the purpose of creating QVD files. At the end of the script, all tables are dropped, and the final app size is empty.

In this scenario, the usage of Data for Analysis won't be reset in the following month since it takes into consideration the size of loading the app. Therefore, the loading size continues to be charged in the next month as a previous reload.

Environment

• Qlik Cloud Analytics

If a Qlik Sense Enterprise on Windows script log reaches 1GB in size, the last line will state:

The file has reached its maximum size

Resolution

Redesign the app to generate a smaller script log if possible.

Cause

Product limitation.

Environment

• Qlik Sense Enterprise on Windows