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

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

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

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

Notifications have been set up for Performance/Resources on a task, but the Latency exceeds and Clear notification values cannot be changed.

Resolution

Upgrade to Qlik Replicate version 2025.5.0.308 PR02.

Cause

UI defect. 

Environment

• Qlik Replicate version 2025.5.0.134

Click here for Video Transcript

The Qlik Sense Virtual Proxy has two different authentication options by default: Forms and Windows Authentication. The Windows Authentication Pattern setting determines which one is used. 

The setting is accessed through the Qlik Sense Management Console > Virtual Proxies > [Virtual Proxy] > Authentication

See Figure 1:

When a client connects to Qlik Sense, the browser sends a User-Agent string to as part of the standard connection process.

The Qlik Sense Proxy service reads this string and checks for the presence of the value found in Windows Authentication Pattern. If the string is present windows authentication is used and if the browser supports NTLM the user may be automatically logged in. If the automatic login fails they will get a pop-up asking for username and password.

If the Windows Authentication Pattern value is not found then we fall back to forms authentication where instead we use a form and always require a username and password for login.

The default value for Windows Authentication Pattern is "Windows", which is present in all windows browser user-agent strings. If you change it to say Chrome or Firefox instead only those browsers will be offered Windows authentication. If you want to use Windows Authentication on all browsers try setting it to another string found in all user-agents (besides Windows), for example, "Mozilla".

Related Content:

• Integrated Windows Authentication (IWA) with Qlik using Internet Explorer, Chrome and Firefox 
• Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub 
• Qlik Sense Enterprise on Windows Default Authentication Module 
• Qlik Sense and Authentication

You may encounter this error that unable to import csv files into Talend Data Preparation Datasets which gives Import Error and the oauth authenticaiton failed message.

Log 

2025-08-13 14:04:21.403 ERROR [user ] 1678370 --- [nio-9999-exec-3] o.t.d.exception.TDPExceptionController   : An error occurred. Error : org.talend.dataprep.exception.TDPExceptionFlowControl: Sorry, an unexpected error occurred and we could not complete your last operation. You can continue to use Data Preparation | Context : {} 
2025-08-13 14:04:21.416 ERROR [user ] 1678370 --- [nio-9999-exec-5] o.t.d.exception.TDPExceptionController   : An error occurred : {cause=null}

org.talend.dataprep.exception.TDPException: 500 Internal Server Error from GET http://1.2.3.4:9999/datasets/9d69c531-b630-4c5e-b2ca-b9cb73f7910d/content
    at org.talend.dataprep.processor.ExceptionsConfiguration$ExceptionsConversions.lambda$doWith$1(ExceptionsConfiguration.java:109)
    at org.talend.dataprep.conversions.BeanConversionService.convert(BeanConversionService.java:189)
    at org.talend.dataprep.command.GenericCommand$ErrorHandler.getTDPExceptionFromDTO(GenericCommand.java:546)
    at org.talend.dataprep.command.GenericCommand$ErrorHandler.apply(GenericCommand.java:519)
    at org.talend.dataprep.command.GenericCommand$ErrorHandler.apply(GenericCommand.java:495)
    at org.talend.dataprep.command.GenericCommand.executeCall(GenericCommand.java:253)
    at org.talend.dataprep.command.GenericCommand.execute(GenericCommand.java:265)
    at org.talend.dataprep.dataset.adapter.DataInventoryClient.getDataSetContent(DataInventoryClient.java:263)
2025-08-13 14:04:38.385 ERROR [user ] 1678370 --- [nio-9999-exec-4] o.t.d.exception.TDPExceptionController   : An error occurred. Error : org.talend.dataprep.exception.TDPExceptionFlowControl: ACL_NOT_FOUND.MESSAGE | Context : {entityId=689c39066827013844aa11d1} 
2025-08-13 14:04:38.393  WARN [user ] 1678370 --- [or-http-epoll-8] o.t.dataprep.sharing.SharingWebClient    : Sharing client error with : 404 Not Found from GET http://1.2.3.4:9999/sharing/v1/sharingset/preparation_folder/689c39066827013844aa11d1 
2025-08-13 14:04:38.621  WARN [user ] 1678370 --- [nio-9999-exec-2] o.t.d.cache.MultiTenantKeyGenerator      : No Current tenant in the context we can't add the tenantId into the cache key 
2025-08-13 14:04:38.991 ERROR [user ] 1678370 --- [io-9999-exec-10] o.t.d.exception.TDPExceptionController   : An error occurred. Error : org.talend.dataprep.exception.TDPExceptionFlowControl: ACL_NOT_FOUND.MESSAGE | Context : {entityId=689c39066827013844aa11d1} 
2025-08-13 14:04:38.993  WARN [user ] 1678370 --- [or-http-epoll-8] o.t.dataprep.sharing.SharingWebClient    : Sharing client error with : 404 Not Found from GET http://1.2.3.4:9999/sharing/v1/sharingset/preparation_folder/689c39066827013844aa11d1 
2025-08-13 14:04:39.826  WARN [user ] 1678370 --- [nio-9999-exec-1] o.t.d.cache.MultiTenantKeyGenerator      : No Current tenant in the context we can't add the tenantId into the cache key

2025-08-13 14:05:00.316 ERROR [user ] 1678370 --- [nio-9999-exec-4] o.t.d.exception.TDPExceptionController   : An error occurred. Error : org.talend.dataprep.exception.TDPExceptionFlowControl: ACL_NOT_FOUND.MESSAGE | Context : {entityId=3168a305-05d1-41ee-9c9e-b43f18c49c96} 
2025-08-13 14:05:00.319  WARN [user ] 1678370 --- [or-http-epoll-9] o.t.dataprep.sharing.SharingWebClient    : Sharing client error with : 404 Not Found from GET http://1.2.3.4:9999/sharing/v1/sharingset/dataset/3168a305-05d1-41ee-9c9e-b43f18c49c96 
2025-08-13 14:05:00.513 ERROR [user ] 1678370 --- [io-9999-exec-10] o.t.d.exception.TDPExceptionController   : An error occurred. Error : org.talend.dataprep.exception.TDPExceptionFlowControl: ACL_NOT_FOUND.MESSAGE | Context : {entityId=3168a305-05d1-41ee-9c9e-b43f18c49c96} 
2025-08-13 14:05:00.516  WARN [user ] 1678370 --- [or-http-epoll-9] o.t.dataprep.sharing.SharingWebClient    : Sharing client error with : 404 Not Found from GET http://1.2.3.4:9999/sharing/v1/sharingset/dataset/3168a305-05d1-41ee-9c9e-b43f18c49c96 
2025-08-13 14:05:01.684 ERROR [user ] 1678370 --- [nio-9999-exec-6] o.t.d.d.s.a.synchronous.SchemaAnalysis   : Unable to analyse schema for dataset 3168a305-05d1-41ee-9c9e-b43f18c49c96. 
org.springframework.web.client.HttpClientErrorException$Unauthorized: 401  on GET request for "http://localhost:8187/artifacts/t_default/lastVersion": "{"status":401,"title":"Unauthorized"}"
    at org.talend.tsd.maven.publisher.controller.ApiClient.invokeAPI(ApiClient.java:579)
    at org.talend.tsd.maven.publisher.controller.api.ArtifactsApi.lastVersionWithHttpInfo(ArtifactsApi.java:95)
    at org.talend.tsd.maven.publisher.controller.api.ArtifactsApi.lastVersion(ArtifactsApi.java:57)
    at org.talend.tsd.dictionary.provider.service.IndexVersionsCache.getLastVersionFromProducer(IndexVersionsCache.java:43)
2025-08-13 14:05:01.701 ERROR [user ] 1678370 --- [nio-9999-exec-6] o.t.d.exception.TDPExceptionController   : An error occurred : {} 
org.talend.dataprep.exception.TDPException: Sorry, an unexpected error occurred and we could not complete your last operation. You can continue to use Data Preparation
    at org.talend.dataprep.exception.TDPException.rethrowOrWrap(TDPException.java:63)
    at org.talend.dataprep.dataset.service.analysis.synchronous.SchemaAnalysis.analyze(SchemaAnalysis.java:109)
    at org.talend.dataprep.dataset.service.BaseDataSetService.analyzeDataSet(BaseDataSetService.java:112)
    at org.talend.dataprep.dataset.service.DataSetService.create(DataSetService.java:443)
Caused by: org.springframework.web.client.HttpClientErrorException$Unauthorized: 401  on GET request for "http://localhost:8187/artifacts/t_default/lastVersion": "{"status":401,"title":"Unauthorized"}"
    at org.talend.tsd.maven.publisher.controller.ApiClient.invokeAPI(ApiClient.java:579)
    at org.talend.tsd.maven.publisher.controller.api.ArtifactsApi.lastVersionWithHttpInfo(ArtifactsApi.java:95)
    at org.talend.tsd.maven.publisher.controller.api.ArtifactsApi.lastVersion(ArtifactsApi.java:57)
    at org.talend.tsd.dictionary.provider.service.IndexVersionsCache.getLastVersionFromProducer(IndexVersionsCache.java:43)
    at org.talend.tsd.dictionary.provider.service.DictionaryProviderFacade.getBy(DictionaryProviderFacade.java:17)
    at org.talend.dataprep.configuration.ExtendedDictionarySnapshotProviderImpl$ExtendedDictionarySnapshotImpl.<init>(ExtendedDictionarySnapshotProviderImpl.java:58)
    at org.talend.dataprep.configuration.ExtendedDictionarySnapshotProviderImpl.get(ExtendedDictionarySnapshotProviderImpl.java:47)
    at org.talend.dataprep.dataset.service.analysis.synchronous.SchemaAnalysis.analyze(SchemaAnalysis.java:84)
2025-08-13 14:05:01.711 ERROR [user ] 1678370 --- [or-http-epoll-8] o.t.d.d.adapter.DataInventoryClient      : Error when create dataSet Purview_ApplicationService-sample from content 
org.springframework.web.reactive.function.client.WebClientResponseException$InternalServerError: 500 Internal Server Error from POST http://1.2.3.4:9999/dataset/v1/datasets/
    at org.springframework.web.reactive.function.client.WebClientResponseException.create(WebClientResponseException.java:332)
    Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
Error has been observed at the following site(s):
    *__checkpoint ⇢ 500 INTERNAL_SERVER_ERROR from POST http://1.2.3.4:9999/dataset/v1/datasets/ [DefaultWebClient]
Original Stack Trace:
2025-08-13 14:05:01.716 ERROR [user ] 1678370 --- [nio-9999-exec-3] o.t.d.exception.TDPExceptionController   : An error occurred : {} 
org.talend.dataprep.exception.TDPException: An error has occurred during the import.
    at org.talend.dataprep.dataset.adapter.DataInventoryClient.lambda$createDatasetFromContent$4(DataInventoryClient.java:292)
    Suppressed: [CIRCULAR REFERENCE: org.springframework.web.reactive.function.client.WebClientResponseException$InternalServerError: 500 Internal Server Error from POST http://1.2.3.4:9999/dataset/v1/datasets/]
Caused by: org.springframework.web.reactive.function.client.WebClientResponseException$InternalServerError: 500 Internal Server Error from POST http://1.2.3.4:9999/dataset/v1/datasets/
    at org.springframework.web.reactive.function.client.WebClientResponseException.create(WebClientResponseException.java:332)
    Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
Error has been observed at the following site(s):
    *__checkpoint ⇢ 500 INTERNAL_SERVER_ERROR from POST http://1.2.3.4:9999/dataset/v1/datasets/ [DefaultWebClient]

Oauth Authenticaiton Failed

org.springframework.web.client.HttpClientErrorException$Unauthorized: 401  on GET request for "http://localhost:8187/artifacts/t_default/lastVersion": "{"status":401,"title":"Unauthorized"}"

Resolution

1. Revise the client_secret value in iam/config/clients/dqdict-client.json with the correct value from oidc.semanticservice.secret in dq_dict/config/data-quality.properties

   oidc.semanticservice.secret=5yjRGCv-f5e15374fae358e1-Lp3Q

2. Restart IAM Server to take affect the change

Cause

Since Talend Data Preparation is connected with dq-dict service per schema analysis module, this issue is caused by DQ-Dictionary-IAM-setting and iam/config/clients/dqdict-client.json is configured improperly with wrong client_secret 

{"client_name" : "DQ Dict API Server", "application_type" : "web", "client_id" : "FqtrjyZu7hTsoQ", "client_secret" : "/5TG+15LvXy7DE49z+UdmSPdBhwVBUt8ptVSF2m0Dx5YN4+81PUjfBTv90TG4OSZezR98o5L/byb", "grant_types" : [ "password", "authorization_code" ] }

which is not aligned with the oidc.semanticservice.secret  in dq_dict/config/data-quality.properties

oidc.semanticservice.secret=5yjRGCv-f5e15374fae358e1-Lp3Q

Environment

• # Qlik Talend Data Preparation
• Talend Data Integration 

When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

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

The default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:

1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)

   [globals]
   LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
   (...)
   MaxHttpHeaderSize=16384

2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.

Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows 

The audit trail provides information about the operations executed in Qlik Enterprise Manager, including the login process. When using the FORM authentication method, the User column value is blank.

To find the corresponding username, you can use one of the following methods:

• Check the previous line; specifically, the line in which the Requested Action column shows Login. The login name can be found in the User column.
• Check the Payload column. Copy the URL and paste it into a web browser to retrieve the username. Below is an example:
  
  {"payload":{"$type":"FormLoginReq","username":"domain\\Administrator","password":""}}

Environment

• Qlik Enterprise Manager

When installed in Linux deployment server, those two folders are allocating a lot of space in - /opt partition.
- /opt/TalendRemoteEngine
- /opt/TalendRuntime-8.0.1-R2025-02-RT

How to purge and keep under control the space allocated in - /opt partition?

How To

Cleaning Talend Remote Engine (RE) Cache and Logs

1. Stop the Remote Engine.
2. Delete the following contents:
   1. Temporary files:
      <TalendRemoteEngine>/data/tmp
   2. Cache files:
      <TalendRemoteEngine>/data/cache
   3. Log files (delete based on your retention policy):
      <TalendRemoteEngine>/data/log
3. Restart the Remote Engine.

Cleaning Up KAR Files from Talend Runtime Server
Please follow the steps in this article to remove or clean up KAR files:
How to Remove / Clean Up KAR Files from Talend Runtime Server

Related Content 

For automated clean-up, refer to the following documentation: Understanding the Talend Remote Engine Clean-up Cycle

Environment

• Talend Cloud 
• Talend ESB 

Authenticating Qlik Sense Desktop against Qlik Sense Enterprise on Windows fails with:

Server authentication attempt failed.

Resolution

To identify the correct root cause, test the connection from the Qlik Sense Desktop client machine to the server.

1. Open Windows PowerShell (as an administrator)
2. Run the following command to test the connection against the Qlik Sense Enterprise on Windows server using port 443:
   
   Test-NetConnection -ComputerName <hostname> -Port 443
   
   

Depending on the results:

• If the test connection succeeds, the possible cause is an Authentication URI misconfiguration.
• The response Name Resolution failed indicates an issue with the hostname resolution or points to the hostname being incorrect
• The response TCP connection failed indicates a connection issue between the Qlik Sense Desktop host and the Qlik Sense Enterprise on Windows Server. In this case, retest with an IP address instead of the server name.

Authentication URI misconfiguration

If the authentication URI is incorrect:

1. On the Qlik Sense Enterprise on Windows Server, open the Qlik Sense Management Console
2. Go to Virtual Proxies
3. Verify the Client authentication link host URI; make the required changes
   
   Example: Ensure the Prefix is included in the URI
   
   
   
   
4. Authenticate the Qlik Desktop client

Hostname resolution issues

Hostname resolution issues may be caused by network issues. Contact your network admin for details.

There are options available in the authentication link URI configuration as well:

1. On the Qlik Sense Enterprise on Windows Server, open the Qlik Sense Management Console
2. Go to Virtual Proxies
3. Verify that the Client authentication link host URI uses the correct name; if the name is correct, change it from hostname to an IP address
4. Authenticate the Qlik Desktop client

Environment

• Qlik Sense Enterprise on Windows (all versions)

When you use VBA code (macro) in an Excel report, it won't be copied into the generated XLSM report.

Resolution

Fix Version

Upgrade to Qlik NPrinting February 2025 SR3.

Workaround

1. Log in to Web Console; the user will need the Admin role

2. In the top bar of the Qlik NPrinting Web Console, click Admin and Settings

3. Click the Report tab

4. Under PixelPerfect security, tick Enable script execution 
   
   
   

5. Click Update at the bottom right

Cause

Defect QCB-32502.

Internal Investigation ID(s)

QCB-32502

Environment

• Affected versions: Qlik NPrinting February 2025 from IR to SR2

This article briefly introduces how to perform a clean-up to restore mistakenly deleted features for a damaged Remote Engine, without reinstalling and pairing the entire engine.

Before you begin

Your Remote Engine version must be v2.12.14 onwards.

How To

Solution 1: Graceful clean-up to repair a damaged Remote Engine

1. Stop the engine and please follow documentation about  running the graceful shutdown process of Remote Engine.
2. Remove the <RE_installation>/data/cache folder and restart the engine.
3. Alternatively, if your engine was installed using an archive delivery and used to be started by one of start-up scripts from <RE>/bin, such as start, karaf, trun, or run, please execute that script with the clean option to restart your engine. For example,

   ./trun clean

   The graceful cleanup process automatically identified the missing features required by a paired engine and re-install them.

Solution 2: Clean Remote Engine Cache

1. Stop remote engine

2. Delete the content in tmp folder <RE_installation>/data/tmp

3. Delete the content in cache <RE_installation>/data/cache

4. Restart remote engine

Related Content 

For more information about graceful cleanup remote engine, please refer to Help Documentation

graceful-cleanup-upon-engine-start-to-clean-up-and-repair-damanged-engine

Environment

Talend Cloud 

After activating Stitch with SSO login using Azure, current users can log in without issue. However, new users added to the Azure AD cannot see Stitch.

Resolution

A new user must log in through the My Apps Portal:

1. Go to: https://myapps.microsoft.com
2. Sign in using the correct work account
3. Locate and click on the Stitch tile
4. The new user is now authenticated using Azure SSO

Trigger provisioning in Stitch and automatically create the user in Stitch (if configured correctly).

Other Identity Providers (Idps) function similarly. These are their respective URLs:

• Google Workspace
   https://accounts.google.com, then click the Google Apps menu
• Okta
  https://<your-company>.okta.com/app/UserHome 
• Onelogin
  https://<your-company>.onelogin.com/portal 
• PingFederate
  https://apps.pingone.com

Cause

Stitch uses Just-in-Time provisioning. 

This means that: A user is not created in Stitch automatically when added to Azure AD. Instead, a user is only provisioned in Stitch when they log in for the first time via SSO.

Environment

Stitch 

After upgrading a Studio instance to R2025-02 or migrating the project being opened, the read and write operations of all Jobs using tMSSql components degrades down to speeds that may create a significant impact on those affected jobs. Tests have been preformed with a simplified job that connects to a mssql database, execute a query, and exports those values to a CSV file.

The (migrated) job, once it begins to run, takes more than 5 minutes to execute; regardless if the job is ran locally, or remotely against a Jobserver or Remote Engine. If taking the same query from the job and running it directly against the SQL Server instance, for example with SQL Management Studio, the query takes less than 10 seconds.

Below are some screenshots showing the performance differences between opensourcejtds and mssqljdbc:

Resolution

You can apply the R2025-04 monthly patch, or a newer monthly patch, and the fix should be applied to both the components and all jobs affected (with a rebuild/republish).

Cause

The issue was identified as a bug, and has been fixed as of the R2025-04 Monthly Patch.

Related Content

For more information about the Issue and Fix, please refer to

• release-notes/8.0/r2025-04-studio-notable-fixes-and-known-issues
• patch-notes/8.0/r2025-04

Internal Investigation ID(s)

Internal Jira case ID: QAPPINT-1330

Environment

• Talend Studio 8.0.1
• Talend Data Integration 

The Feature Manager within Studio 8 is used for applying patches and installing new features that may not have been installed, depending on the Monthly Patch that is applied at that moment. There may be 1 or 2 URL's within the Update Settings itself (Eclipse update system is based on a system named "p2", and one or two P2 URL can define the full update). .

Base URL: Original 8.0.1 content, which contains additional features and dependencies are not included in the default Studio instance (https://update.talend.com/Studio/8/base)

Update URL: Incremental updates which contain new/improved functionalities along with fixes (For example, https://update.talend.com/studio/8/updates/R2025-07v2/).

All Talend Studio Releases before R2024-05 must have the P2 Base URL, which is set by default to: https://update.talend.com/Studio/8/base

If the Studio instance(s) are in an air gapped environment, or a connection to above URLs (or in general) to our update site is not possible from where Studio is installed on, this article briefly introduces how users can work around these network issues in offline mode to update Talend Studio manually.

Offline or Manual Update Process

Updating older Studio 8.0.1 Patch releases to a target Patch Release prior to R2025-05

If the Studio instance(s) are in an air gapped environment, or a connection to above URLs (or in general) to our update site is not possible from where Studio is installed on, this article briefly introduces how users can work around these network issues in offline mode to update Talend Studio manually.

1. Download P2 repo archive
   The P2 Base can be obtained from either the TMC Downloads Page (within the "Continuous Integration (CI) for cloud" section) for cloud customers; For On-Prem Customers, at the bottom of the license email (Providing Download Links for the Modules), there is a section titled "Local update sites for installation without internet:". There is a link to download a zip file that includes the Full P2 Repository, which is called:
   

   Talend_Full_Studio_p2_repository-2021109_1610-V8.0.1.zip

2. To point the settings for the url to the archive file that is on the instance, please use the below format:
   

   jar:file:/<path to archive on disk>/Patch_20240621_R2024-03_v1-8.0.1.zip!/

   The extra / at the beginning and end as well as the !

    

Updating older patch releases of Studio 8.0.1 to target Patch Release R2024-05 or later

If the target Patch release for the Studio in question is R2024-05 or higher, the patch archive will act as both Base_URL and Update_URL; as the P2 base now has shifted to the specific patch being applied.

For all more recent patch releases, Studio will only need to use the above format for the Update_URL; additionally, users can follow alternatives instructions on Qlik's patch release notes, which will translate to the same format by the application:

1. Obtain the patch zip file from Qlik Support

2. Create a folder named "patches" in the Studio installation directory and copy the patch .zip file to this folder.

3. Restart the Studio instance.

4. If the Studio instance supports installing features using the Feature Manager wizard, log in to a project desired, and navigate to the wizard to proceed with the patch installation. Otherwise, click OK when prompted to install the patch.

Environment

Talend Studio 

By default, the touch screen function cannot be disabled in Qlik Sense Enterprise on Windows. It is enabled whenever the client recognizes a touch-enabled device, such as a mobile phone or tablet. 

It can be disabled manually by the user, but not globally on the server.

To disable Touch Screen mode manually:

1. Click the three dots (ellipsis) in the top left corner
2. Toggle Touch  Screen Mode on or off
   
   

An idea has been created to gather demand on allowing this feature to be disabled on server/administration level. See Option to Disable Touch Screen or toggle Touch Screen off on server side.

Environment:

Qlik Sense Enterprise on Windows 

It is possible to disable touch screen options entirely in, for example, mashups. 

A mashup can send information to the client that sends a fixed device type,  which modifies the UI accordingly.

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

Example:

// Sets device type, which modifies the UI accordingly.
// The device type is automatically detected if it is not manually set.

@function
// String describing the device type.
@param {'auto'|'touch'|'desktop'} deviceType

@example
qlik.setDeviceType('desktop');

 More information could be found on the help site: setDeviceType method

If Qlik NPrinting tasks do not complete and will only continue if the operating system is restarted, review the Qlik NPrinting log files for the following error:

io: read/write on closed pipe

This error indicates the Windows Operating System is damaged (after a faulty restart, a failed upgrade, or similar root causes).  

Resolution

Reinstalling Qlik NPrinting will not be sufficient to resolve the error. The Operating System will need to be reinstalled. 

Example solution:

1. Take a backup of your Qlik NPrinting database; see Backup and restore Qlik NPrinting for details.
2. Store the backup in a location off the current server
3. Reinstall Windows
4. Restore your Qlik NPrinting database; see Backup and restore Qlik NPrinting for details.

Environment

• Qlik NPrinting

To decrypt the Qlik Talend Data Integration (QCDI) verbose task log files:

1. Open the Qlik Talend Data Integration Project in the Web UI
2. Navigate to your project in the Qlik Talend Data Integration (formerly QCDI) browser interface
3. Locate the Task Name
   1. Go to the Tasks tab
   2. Click on the ... (ellipsis) button next to the relevant task
   3. Select View task logs
      
      
      
      
   4. Identify the unique task name (example: TASK_aRBItFnknSU0vR5LX0AgkA)
      
      
      
      
4. SSH into the Linux Gateway machine using the qlik user and log in
5. Navigate to the movement/bin Directory:
   cd /opt/qlik/gateway/movement/bin
6. Source the Qlik Talend Data Integration environment:
   source arep_login.sh
7. Decrypt the Task Log File by running the repctl dumplog command:

   repctl dumplog "/opt/qlik/gateway/movement/data/logs/TASK_aRBItFnknSU0vR5LX0AgkA.log" log_key="/opt/qlik/gateway/movement/data/tasks/TASK_aRBItFnknSU0vR5LX0AgkA/log.key" > "/opt/qlik/gateway/movement/data/logs/TASK_aRBItFnknSU0vR5LX0AgkA_Decrypted.log"

   In the example command, replace TASK_aRBItFnknSU0vR5LX0AgkA with your actual task name.
   
   
8. (Optional) Compress and download the decrypted Logs
   
   To bundle and download the decrypted logs:

   tar -czf decryptedLogs.tar.gz TASK_aRBItFnknSU0vR5LX0AgkA_Decrypted.log reptask_TASK_aRBItFnknSU0vR5LX0AgkA__250806061702_Decrypted.log

   Then, download decryptedLogs.tar.gz from the Linux gateway and send it to Qlik Support.

Related Content

How to Decrypt Qlik Replicate Verbose Task Log Files

Environment

• Qlik Talend Data Integration (QCDI)

A JWT token will continue to function normally even if the user it was originally created with has been deactivated. The token remains valid irrespective of the user's status.

For more information, see:

• JWT authentication
• Qlik Sense: How to set up JWT authentication 

Environment

• Qlik Sense Enterprise on Windows