After upgrading to Qlik Sense Enterprise on Windows May 2023 (or later), the Qlik Sense Repository Service may cause CPU usage spikes on the central node. In addition, the central Engine node may show an increased average RAM consumption while a high volume of reloads is being executed. 

The Qlik Sense System_Repository log file will read:

"API call to Engine service was successful: The retrieved 'StaticByteSize' value for app 'App-GUID' is: 'Size in bytes' bytes." 

Default location of log: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\[Server_Name]_System_Repository.txt

This activity is associated with the ability to see the Base memory size in the Qlik Sense Enterprise Management Console. See Show base memory size of apps in QMC.

Resolution

The feature to see Base memory size can be disabled. This may require an upgrade and will require downtime as configuration files need to be changed.

Take a backup of your environment before proceeding.

1. Verify the version you are using and verify that you are at least on one of the versions (and patches) listed: 
   
   
   • May 2023 Patch 13
   • August 2023 Patch 10
   • November 2023 Patch 4 
   • February 2024 IR
     
2. Back up the following files:
   
   
   • C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   • C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
     
     *where C:\Program Files can be replaced by your custom installation path.
     
     
3. Stop the Qlik Sense Repository Service and the Qlik Sense Dispatcher Service
   
4. Open and edit the capabilities.json with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   2. Locate: "enabled": true,"flag": "QMCShowAppSize"
   3. Change this to: "enabled": false,"flag": "QMCShowAppSize"
   4. Save the file  
5. Open and edit the repository.exe.config with a text editor (using elevated permissions)
   1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   2. Locate: </appSettings>
   3. Before the </appSettings> closing statement, add:
      <add key="AppStaticByteSizeUpdate.Enable" value="false"/>
   4. Save
6. Start all Qlik Sense services
7. Verify you can access the Management Console

If any issues occur, revert the changes by restoring the backed up files and open a ticket with Support providing the changed versions of repository.exe.config, capabilities.json mentioning this article. 

Related Content

Show base memory size of apps in QMC

Internal Investigation:

QB-22795
QB-24301

Environment

Qlik Sense Enterprise on Windows  May 2023, August 2023, November 2023, February 2024. 

An SQL Server backup file is considered striped if it consists of multiple files or if it was generated from multiple files appended into a single bak file.

This means the backup files will contain the same LSNs for each of those files.

Qlik Replicate cannot process these multiple files with the same LSN.

The following error will occur when Qlik Replicate encounters striped backup files:

00012300: 2025-11-04T20:22:28:558929 [SOURCE_CAPTURE ]E: do_log_processing_direct(...) 2 multiple family members (=stripes) encountered in backup set while only 1 can be handled. [1020440] (sqlserver_log_processor.c:4685)

Resolution

Skip the LSN and start from another LSN or timestamp. Note that this will lead to a data gap for the LSN that was skipped.

You can also choose to do a full reload.

Cause

Striped backups are a result of SQL Server configurations. Please consult with your DBA on backup configurations.

Environment

• Qlik Replicate

With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User,  and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.

Here are two scenarios:

I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).

In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.

If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.

II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License  for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.

A QlikView Server or a Qlik Publisher software can be activated in two ways:

1) Using a legacy method with 16-digit QlikView license key and the corresponding control number

2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model

If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.

Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales 

Environment:

• QlikView 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
   

Related Content:

• How to Apply an unified Signed License Key for QlikView and Qlik Sense
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)

Unable to resume Qlik Replicate tasks due to the error below:

00020080: 2023-08-16T13:55:07 [SOURCE_CAPTURE ]I: Start processing new RESETLOGS_ID 'xxxxxxxxx' that does not still have archived Redo logs (oradcdc_thread.c:430)

Resolution

The internal parameter supportResetLog is currently set to true. When a failover happens, the redo log ID will be reset to zero.

• With supportResetLog set to true, Qlik Replicate will search from zero when it cannot find the next redo log.
• With supportResetLog set to false, Qlik Replicate will keep searching for the next redo log until it appears or the task times out. This setting resolved the "Start processing new RESETLOGS_ID 'xxxxxxxxx' that does not still have archived Redo logs" error. 

To set the Internal Parameter:

1. Go to the Oracle Source Endpoint
2. Switch to the Advanced tab
3. Click Internal Parameters
4. Add:
   
   Parameter: supportResetLog
   Value: uncheck the box (set to false) 
   
   
   
   For more information on Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?
   
   
5. Save and exit. The change will take effect once the tasks using this endpoint are stopped and resumed.

Environment

• Qlik Replicate
• Oracle Database as a Source

The goal of this article is to address the upcoming changes announced by Marketo regarding the deprecation of authentication via the access_token query parameter, which will no longer be supported after January 31, 2026. For further details, please refer to: Using an Access Token | Marketo Developer Guide.

Marketo specificities: "If your project uses a query parameter to pass the access token, it should be updated to use the Authorization header as soon as possible. New development should use the Authorization header exclusively".

The Stitch Marketo integration (V2) already handles authentication using access tokens, as outlined in Marketo’s documentation. Specifically, Stitch includes a Bearer token in the Authorization header of its API calls. This approach complies with Marketo’s authentication requirements, so no additional configuration is needed on your end.

For reference, please visit the integration's repository | github.com.

During the extraction process of your HubSpot integration, the following error was encountered:

requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url <CustomURL>

...

Giving up on request after {} tries with url {} and params {}

Resolution

This error may be transient. However, if it is recurring frequently enough to disrupt your workflow, please reach out to Qlik Support.

Cause 

The HubSpot API is having issues processing the amount of data compiled based on the request sent by Stitch.

Environment

• Stitch 

A space owner can edit apps owned by other users, but cannot edit the scripts. The option to access the Data Load Editor is not present:

Resolution

Explicitly assign the Can edit data in applications space role. See Working in shared spaces | help.qlik.com for details.

Cause

The Owner role implicitly gives access to all other actions on the space except this one. This is designed to prevent owners from accidentally accessing another user's script without them or another space manager taking explicit responsibility.

Environment

• Qlik Cloud Analytics

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor, License Monitor, and Content Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor, License Monitor, and Content Monitor

The Operations Monitor loads service logs to populate charts covering the performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor. 

• Basic information can be found in Operations Monitor | help.qlik.com
• Detailed descriptions of sheets and visualizations are accessible in the About the Operations Monitor story available from the app overview page under Stories

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

• Basic information can be found in License Monitor | help.qlik.com  
• Detailed descriptions of sheets and visualizations are accessible in the About the License Monitor story available from the app overview page under Stories

The Content Monitor loads from the APIs and logs to present key metrics on the content, configuration, and usage of the platform, allowing administrators to understand the evolution and origin of specific behaviors of the platform.

• Basic information can be found in Content Monitor | help.qlik.com  
• Each sheet in the Content Monitor includes an About text box to describe its content. 
  

All three apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor | Content Monitor (download page). Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

The existing 'has restricted view' space role can export data to Excel. If you do not wish for users with the 'has restricted view' space role to be able to export data, you will need to edit the User Default role to deny download for all users, and then create a custom role that allows it for specific users and groups.

Steps

1. Go to the Administration activity center
2. Go to Manage users
3. Go to Permissions 
4. Click User Default 
   
   
   
   
5. Expand Content Types
6. Expand Applications
7. Set In-app content download to Not Allowed 
8. Click Confirm 
   
   

   This has now changed the default user behavior across the tenant. Users will no longer be able to download in-app content.

9. Back in the Permissions view, click Create New
   
   
   
   

   This creates a new role that you will need to assign to any users who should have the permission to download in-app content.

10. Name your New Role, then expand Content Types
11. Expand Applications
12. Set In-app content download to Not Allowed 
13. Click Confirm
    
    
    
    
14. Assign users or groups to the new custom role 
    
    See Assigning security roles and custom roles to users for details.

There is no function to restrict downloading by apps or spaces.

Related Content

• Assigning security roles and custom roles
• Permissions in User Default and custom roles
• 'In-app content download' permission: Additional details
• Assigning security roles and custom roles to users

Environment

• Qlik Cloud Analytics

The following two items were deprecated in June 2025:

• Developer role
• Enable API keys toggle

The deprecation notice was communicated in an Administration announcement and documented on our What's New in Qlik Cloud feed. See Developer role and API key toggle deprecated | 6/16/2025 for details.

What products are affected by the removal of the role and toggle?

• Qlik Cloud Analytics
• Qlik Talend Cloud

What actions do I need to take?

To replace the deprecated built-in role, migrate your users away from the Developer role to a Custom Role with the required permissions (Manage API Keys).

To create and assign a replacement custom role:

1. In the Administration activity center, go to Manage users
2. On the Permissions tab, select Create new
3. Name the role using your organization's naming convention
4. Set Manage API keys to Allowed
5. Assign the role to users or groups who previously had the deprecated role
6. Remove the deprecated role from those users or groups

For additional reading on the Managed API Keys (set to Not allowed by default), see Permissions in User Default and custom roles | Permission settings — Features and actions.

When will the deprecated items be removed?

The Developer role and Enable API keys toggle will be removed in the coming weeks in line with the original announcement aiming for the end of 2025.

What will happen if we fail to migrate?

Once the Developer role has been removed, users who have not been updated to use the “Manage APK keys” = Allow permission will:

• Be unable to access the API keys UI in Profile > Settings
• Find their API keys disabled, resulting in 3rd-party integrations failing

API keys are not deleted from Qlik Cloud and will automatically be re-enabled once a user has been assigned the required Manage API Keys permissions.

To resolve this, a Tenant Administrator needs to act as outlined in What action do I need to take?

Environment

• Qlik Cloud Analytics
• Qlik Talend Cloud

Qlik Replicate SQL Server target faces the following truncation error:

Failed sending row to table SS.TABLE1
RetCode: SQL_SUCCESS SqlState: 22001 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server]String data, right truncation

Resolution

Increase precision enough for the target SQL Server column. This can be achieved in the Qlik Replicate UI transform tab in table settings, or by modifying it directly in the target DB:

ALTER TABLE [SS].[TABLE1]
ALTER COLUMN [AA] NUMERIC(9,4) NOT NULL;
ALTER TABLE [SS].[TABLE1]
ALTER COLUMN [BB] NUMERIC(12,4) NOT NULL;

Troubleshooting and Cause

Checked column precision control/transfer to target, the target precision is too small, which could not hold the numbers from the source, and causes the error.

==source ibm ==
UUBTCPP AA 19 DECIMAL 5
UUBTCPP BB 20 DECIMAL 8

DECIMAL(p) floating point

When you define a column with the DECIMAL(p) data type, it has a total of p (< = 32) significant digits. DECIMAL(p) has an absolute value range 10^-130 - 10^124.

DECIMAL(5,0): Could store a 5-digit whole number like (12345) or (-99999).
DECIMAL(5,5): Could store a number like 0.12345 or 0.00001

==target sqlserver ==
[AA] [numeric](7, 4) NOT NULL,
[BB] [numeric](8, 4) NOT NULL,

3-digit integer at maximum and 4-digit float --> (7,4)
4-digit integer at maximum and 4-digit float -->(8,4)

For example, the source column AA value=99999 , but the target can only hold a 3-digit integer, which will trigger the truncate mechanism. 

Environment

• Qlik Replicate

Creating a connection to Azure Databrics using Azure OAuth authentication mechanism fails with the error:

Code verification failed: Error making token request. An error occurred while sending the request

Resolution

1. Follow the steps in Create a Databricks connection, specifically Databricks configuration for OAuth.
2. Follow the steps in Configure an OpenID Connect OAuth application from Microsoft Entra app gallery | learn.microsoft.com.
3. Verify the following have been allowed on the Azure side:
   • https://login.microsoftonline.com/..../oauth2/authorize 
     You can verify the complete URL using your browser developer tool.
   • https://connector.qlik.com/auth/oauth/v2.htm/

Environment

• Qlik Sense Enterprise on Windows
• Qlik Cloud Analytics

The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.1.0.

Content

• What's New
• 2.1.0 September 2025 Release Notes
• Known Limitations (2.1.0)
• 2.0.0 May 2025 Release Notes
• Known Limitations (2.0.0)
• 1.4.0 December 2023 Release Notes
• Known Limitations (1.4.0)
• 1.3.0 May 2023Release Notes
• Known Limitations (1.3.0)
• 1.2.0 Release Notes

What's New

• The PostgreSQL version used by QPI has been updated to 14.17
• An upgrade of an already upgraded external instance is now possible
• Support for an upgrade of the embedded 14.8 database was added
• Silent installs and upgrades are supported beginning with Qlik PostgreSQL Installer 1.4.0 and later. QPI can now be used with silent commands to install or upgrade the PostgreSQL database. (SHEND-973)

2.1.0 September 2025 Release Notes

Known Limitations (2.1.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.17. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.17. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

• QB-24990: Cannot upgrade PostgreSQL if Qlik Sense was installed in a custom directory such as D:\Sense. See Qlik PostgreSQL Installer (QPI): No supported existing Qlik Sense PostgreSQL database found.
• Rollback is not supported.
• Database size is not checked against free disk space before a backup is taken.
• QPI can only upgrade bundled PostgreSQL database listening on the default port 4432. Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• Cannot migrate a 14.8 embedded DB to standalone
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

1.3.0 May 2023 Release Notes

What Is the Hash of a Studio or TAC Patch?

When sharing a TAC (Talend Administration Center) or Studio patch with customers, some may request the hash value of the patch file.
This hash (Such as MD5, SHA-1, or SHA-256) is used to verify the integrity of the downloaded file, ensuring that the patch has not been corrupted or altered during transmission.

Purpose of the Hash

• Confirm the patch file is identical to the one provided by Qlik/Talend.
• Help customers validate the authenticity of the patch.
• Detect any tampering or incomplete downloads.

Where to Find the Hash

You can find the hash value of a patch (for instance, in the package provided by Qlik or from the build repository) as shown in the screenshot below:

It is the value of CheckSums

Environment

• Talend Data Integration 

Resolution

1. Download the Snowflake SSL Certificate
   
   
   1. Access your Snowflake account URL in a web browser (e.g., Chrome).
   2. Export the SSL certificate chain from the browser. This usually involves clicking on the padlock icon (A) in the address bar, then navigating to certificate details (B) and exporting (C) the certificates.
      
      
      
      
      
      
      
      
2. Import the Certificate into the Java TrustStore
   
   
   1. Identify the Java TrustStore: Determine which Java Runtime Environment (JRE) Qlik Talend is using. You can check this in the Qlik Talend Studio under Windows > Preferences > Java > Installed JREs. The cacerts file within the JRE's lib/security directory is the default TrustStore.  (Example: C:\Talend\Studio\zulu17.48.15-ca-jdk17.0.10-win_x64\lib\security\cacerts)
      
      
   2. Use the keytool utility: Open a command prompt and navigate to the bin directory of your JRE. Use the keytool command to import the downloaded Snowflake certificate into the cacerts file.
      
      
3. Use a Command Prompt to import the certificates
   
   Example commands:
   
   

   cd C:\Talend\Studio\zulu17.48.15-ca-jdk17.0.10-win_x64\lib\security

   keytool -import -trustcacerts -alias snowflakeCert -file  -keystore cacerts -storepass changeit

   
   Replace <path_to_downloaded_certificate> with the path to the certificate you downloaded (Example C:/User/Downloads/snowflake.cer).
   
   
4. Configure Qlik Talend for Custom TrustStore (if necessary)
   
   If you choose to use a custom TrustStore instead of the default cacerts, you will need to configure your Qlik Talend Job or Studio to use this custom TrustStore. 
   
   This typically involves setting Java system properties such as javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword in your Qlik Talend Job's advanced settings or in the Studio's JVM arguments.
   
   
   
   
5. Verify Network Configuration
   
   You can set the Qlik Talend Studio proxy settings either through the GUI by going to Windows > Preferences > General > Network Connections or by editing the .ini file in the installation directory for system-level or command-line settings. 
   
   The GUI method is for configuring connection settings within the Studio application, while the .ini method is useful for command-line execution or when the GUI option is unavailable.
   
   
   

Environment

• Qlik Talend Studio

By default, Qlik Enterprise Manager uses Single Sign-on through Windows Authentication to authenticate users with NTLM. Single Sign-on authentication can also be used with Kerberos, which does not require NTLM. If Kerberos authentication fails, it will default back to NTLM.

Qlik Enterprise Manager offers multiple authentication methods beyond NTLM and Kerberos. See Setting the login authentication method for details.

If Windows Authentication is used and NTLM is disabled, you will encounter the following error:

[ERROR] Test connection failed for server:XXXX. Message:'XXXX, The remote server returned an error:[ERROR] Test connection failed for server:XXXX. Message:'XXXX, The remote server returned an error: (401) Unauthorized.'..'.

Failure to connect to Qlik Replicate from Qlik Enterprise Manager (QEM) can be caused by various permission settings. See Minimum user access requirements for Qlik Replicate and Qlik Enterprise Manager for requirements.

If the required permissions are met, the next step would be to verify that NTLM is enabled on the Qlik Replicate server. 

NTLM is used with the Windows Authentication method, and if NTLM is disabled, then the user can not be authenticated, giving the (401) Unauthorized error.

For instructions on checking NTLM, please review this Microsoft documentation: How to enable NTLM 2 authentication 

Resolution

Enable NTLM authentication on the Operating System level.

Cause

NTLM authentication disabled.

Environment

• Qlik Replicate

During the extraction process of your Amazon Aurora MySQL integration, the following error was encountered:

Fatal Error Occurred - You are not utilizing binary logging.

Resolution

Amazon Aurora MySQL read replicas do not support binlog replication. The log_slave_updates parameter is not modifiable on Aurora read replicas, which means binlog replication cannot be enabled on these instances. This is mentioned in the Amazon Aurora MySQL RDS setup requirements | Qlik Stitch Documentation and further detailed in Amazon Aurora MySQL reference | docs.aws.amazon.com. 

If you encounter this error while connecting to the primary instance, please consult with your DBA and reach out to Amazon Support if needed. Aurora instances are managed by AWS and binlogs should be enabled by default.

Cause 

This happens when you set the integration to connect to a read replica instead of the primary instance.

Environment

• Stitch 

Question

How can we retrieve artifact information from Talend update website? For instance, for artifact "accessors-smart-2.4.11.jar", we can use the following URL to query its information: https://search.maven.org/solrsearch/select?q=a:accessors-smart+AND+v:2.4.11&rows=1&wt=json

Does Talend also offer a similar feature for its artifacts?

Answer

Talend update website is built on Nexus and utilizes the Lucene search API, as demonstrated in the following example:

https://talend-update.talend.com/nexus/service/local/lucene/search?a=accessors-smart&v=2.4.11

For further details on the Lucene search API, please refer to: Nexus Indexer Lucene Plugin REST API | repository.sonatype.org

Environment

• Talend Data Integration 

After upgrading to Qlik Talend Cloud Enterprise Edition R2025-08, some users reported that the tClaudeAIClient component was missing from the Talend Studio Palette.
Despite attempts to search for the component in the Palette or import it manually, they were unsuccessful.

Resolution

To restore the tClaudeAIClient component in Talend Studio, follow the steps below:

1. Open Talend Studio.
2. Navigate to Feature Manager by selecting "Help" > "Install Additional Packages" from the top menu or by using the shortcut icon for the Feature Manager on the Studio toolbar.
3. In the Feature Manager window, go to Components.
4. Locate EmbeddingAI under the available component families.
5. Select EmbeddingAI, then click Download or Install.
6. Once installation completes, restart Talend Studio.

After restarting, verify that the tClaudeAIClient component is available in the Palette under the AI family.

Cause 

The tClaudeAIClient component is a member of the AI family, which is offered through the EmbeddingAI optional feature. However, this feature may not be automatically installed or enabled by default, as it depends on the user's Studio configuration and feature synchronization settings.

Additional Notes

The EmbeddingAI package includes additional AI-related components beyond tClaudeAIClient.
If the component still does not appear after installation, ensure your Studio is synchronized with your Qlik Talend Cloud license and feature repositories.
For enterprise environments with restricted update policies, check with your Talend administrator to confirm access to optional feature downloads.

Environment

• Qlik Talend Cloud Enterprise Edition R2025-08 and later

• Talend Studio (Cloud or Local Installation)