After upgrading Qlik Sense Enterprise on Windows (example: February 2024 to November 2024), the Data Load editor fails to load.

The error:

Connection lost. Make sure that Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working.

Error Code: 16

The console log reads:

Error during WebSocket handshake: Unexpected response code:431

Resolution

Adjust the MaxHttpHeaderSize as documented in Qlik Sense Client Managed: Adjust the MaxHttpHeaderSize for the Micro Services run by the ServiceDispatcher.

Cause

The console error 431 means Request Header Fields Too Large in HTTP.

Related Content

Qlik Sense Enterprise on Windows: Error Code 16 or Error Code 1003 while working on or opening a Qlik Sense app 

Environment

• Qlik Sense Enterprise on Windows

Images included in an Excel worksheet may appear stretched or use the wrong aspect ratio when previewed in an Excel report or after being distributed in an on-demand reporting task.

This affects charts imported by Qlik Sense as well as static images and shapes. 

Resolution

To fix the affected Qlik Reporting template, change the body font currently used in the Excel template to a supported font family:

1. Create a new Excel workbook or open an existing Excel template using Office Web or Excel
   Desktop
2. For each Excel worksheet contained in the Workbook, click on the worksheet’s top left
   corned or press Ctrl-A to select all the cells.
3. In the Excel ribbon bar, under the Home menu, choose a supported body font
   
   Supported fonts:
   
   
   • Andale Mono
   • Arial (Bold, Italic, Bold Italic)
   • Arial Black
   • Calibri (Bold, Italic, Bold Italic)
   • Calibri Light (Italic)
   • Cambria (Bold, Italic, Bold Italic)
   • Candara (Bold, Italic, Bold Italic)
   • Comic Sans MS (Bold)
   • Consolas (Bold, Italic, Bold Italic)
   • Constantia (Bold, Italic, Bold Italic)
   • Corbel (Bold, Italic, Bold Italic)
   • Courier New (Bold, Italic, Bold Italic)
   • Georgia (Bold, Italic, Bold Italic)
   • Impact
   • Times New Roman (Bold, Italic, Bold Italic)
   • Trebuchet (Bold, Italic, Bold Italic)
   • Verdana (Bold, Italic, Bold Italic)
   • Webdings
   • WenQuanYi Zen Hei
     
     More fonts could be supported in the future.
     
     
4. After changing your font, double-check the size of images added to the template (both static
   images and dynamic Qlik Sense charts). Font modification may have altered the image; if necessary, resize or re-add the image.

To prevent other related symptoms, set the main display zoom level to 100% when creating and editing an Excel template on the Windows platform. Note that this is a Windows OS setting and not the Zoom set within the Excel App.

Cause

An unsupported font is used in the current Qlik Reporting template. 

Internal Investigation ID(s)

SUPPORT-3842, QCB-32146

Environment

• Qlik Cloud Analytics
• Qlik Reporting

Opening QlikView Documents from the AccessPoint directly in the QlikView Desktop leads to the document being launched with the wrong (AJAX) client.

Previously, documents would automatically launch with qvp:// and use the Desktop client as the default.

Clicking the View details link lists only three clients:

Ajax client, Internet Explorer plugin, Mobile client

Previous versions would list the QlikView desktop client:

Resolution

This behavior was changed between 12.70 and 12.80. To reenable the previous default:

1. Open QlikView Desktop
2. Go to Settings
3. Go to User Preferences
4. In the License section, click Clear License Information
5. Close the QlikView Desktop
6. Open a Windows File Explorer and go to %USERPROFILE%\AppData\Roaming\QlikTech\QlikView
7. Open settings.ini
8. Modify the settings.ini by adding the line SupportLeaseLicenseForDMSMode=1 below the [Settings 7] section
   
   Example:
   
   [Settings 7]
   SupportLeaseLicenseForDMSMode=1
   .... other settings ....
   
   
9. Save the changes to the settings.ini
10. Open QlikView Desktop and open the AccessPoint; any documents will now open directly with QVP://accesspoint/path/documents.qvw.

If the steps did not succeed:

• Verify that you cleared the license beforehand
• Verify if SupportLeaseLicenseForDMSMode=1 is still present in %USERPROFILE%\AppData\Roaming\QlikTech\QlikView\settings.ini
  The settings.ini file may have been overwritten by a different version of QV.exe that was active while the changes were made. If this is the case, close all QV.exe instances and repeat the steps.

Internal Investigation ID(s)

QCB-32143

Environment

• QlikView 12.80 and later

The central proxy virtual proxy cannot be deleted and virtual proxy prefix are unique per proxy.

Environments:

• Qlik Sense Enterprise on Windows 

Resolution:

In order to change to remove the prefix for a different virtual proxy to use another authentication method by default:

1. in the QMC, go to "Virtual proxies" > "Central proxy (default)"
2. Modify the virtual proxy prefix to the desired string
3. Click "Apply" in order to save
4. Go back to "Virtual proxies", double-click on the virtual proxy that you want to make default in order to edit it.
5. Remove the virtual proxy prefix
6. Click "Apply" in order to save

Note: If the virtual proxy made default is using SAML authentication, the SAML Assertion Consumer Service URL will also need to be updated in the Identity Provider configuration.

You may be experiencing a pattern of the Binlog error like below when extracting data from MySQl Integrations in Stitch.

Fatal Error Occurred - Binlog has expired for tables

The problem always stems from how did you configured certain parameters in your AWS RDS instance due to a lack of explicit specification.

As MySQL Integrations can be configured with AWS RDS instances, for MySQL integrations that are configured in this way, it means the requirements for the Binary Log Retention Period differs from that of standalone MySQL instances and this can cause issues if the Binary Log Retention Period is incorrectly or insufficiently configured.

Resolution

The Binary Log Retention Period should be configured to a value of 168 hours or 7 days. 
Running call

call mysql.rds_set_configuration('binlog retention hours', 168)

or

call mysql.rds_set_configuration('binlog retention hours', 7) 

will fix the issue.

Cause

The Binary Log Retention Period is controlled by AWS RDS which functions differently and independently of a standalone MySQL instance.

If the Binary Log Retention Period is set to 0, this will cause issues.

Related Content

There is a RDS specific stored procedure that governs bing log retention beyond traditional MySQL parameters given in the case.

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-stored-proc-configuring.html

Environment

• Talend Cloud 
• Qlik Stitch

Cannot log in to Qlik Talend Administration Center. Login fails with:

Error: 500, The call failed on the server; see server log for details

The log file reports:

ERROR SqlExceptionHelper - The MySQL server is running with the LOCK_WRITE_GROWTH option so it cannot execute this statement

Resolution

Expand cloud storage for MySQL or perform a data cleanup to free up the space required.

Cause

Cloud MySQL has reached the cloud storage quota during data writes. 

Environment

• Qlik Talend Administration Center

When doing a false migration update, you want a new branch based on the good commit id to start again. 

This article briefly introduces how to create a New Branch from a Commit before the faulty Migration Update

How to

1. Install Git Bash (if not already installed)
   https://git-scm.com/downloads
2. Identify the correct commit to revert to
   • Open the commit history of the affected file, for example:
     http://abc.com/project/talend.project
   • Look for the commit where the productVersion was updated, and find the commit SHA-1 id right before the false commit from the commit history.
   • Find the SHA-1 hash of the last good commit before the incorrect migration.
3. Create a new branch from that commit and sync it to Git server
   Run the following commands in your terminal:

   git clone http://abc.com/project.git
   cd project
   git checkout -b newBranchName <sha1-of-good-commit>
   git push -u origin newBranchName

These above steps will create and push a new branch starting from the commit just before the incorrect migration was introduced.

Environment

• Talend Studio 
• Talend Data Integration 

When running extractions in Shopify that involve requesting a large quantity of data, encountered a ServerError.

This is notably seen during initial/historical data extractions.

Cause

Too much data is being requested from Shopify and it creates a Sever Error because Shopify is unable to process the large amount of data via their API.

Resolution

When this error arises, Stitch Subject Matter Experts have the capability to adjust a tuning parameter labeled "Results Per Page". If you encounter this error, it is advisable to consult with a Stitch Subject Matter Expert to establish an appropriate value for this parameter and thereby resolve the issue.

Environment

• Qlik Stitch

Qlik Sense uses HTTP,  HTTPS, and WebSockets to transfer information to and from Qlik Sense.

The attached Webscoket Connectivity tester can be used to verify protocol compliance, indicating if a network policy, firewall, or other perimeter device is blocking any of the required connections.

If the tests return as unsuccessful, please engage your network team. 

The QlikSenseWEbsocketConnectivtyTester is not an officially supported application and is provided as is. It is intended to assist in troubleshooting, but further investigation of an unsuccessful test will require your network team's involvement. To run this tool, the Qlik Sense server must have a working internet connection.

Environment:

Qlik Sense Enterprise on Windows 

For Qlik Sense Enterprise on Windows November 2024 and later:

Since the introduction of extended WebSocket CSRF protection, using the WebSocket Connectivity tester on any version later than November 2024 requires a temporary configuration change.

1. Open the Proxy.exe.config stored in C:\Program Files\Qlik\Sense\Proxy\
2. Locate

   <add key="WebSocketCSWSHCheckEnabled" value="true"/> 

3. Change it to

   <add key="WebSocketCSWSHCheckEnabled" value="false"/> 

4. Restart the proxy
5. Run the WebSocket Connectivity tester
6. Revert the change

How to use the Websocket Connectivity Tester

1. Download the attached package or download the package from GitHub: https://github.com/flautrup/QlikSenseWebsocketConnectivityTester
2. Unzip the file
3. Login to the Qlik Sense Management Console
4. Create a Content Library
   
   
   1. Go to Content libraries 
   2. Click and Create New
   3. Name the Content Library: WebSocketTester
   4. Verify and modify the Security Rule
      
      Note that in our example, any user is allowed to access this WebSocketTester.
      
      
      
      
   5. Click Apply
      
      
5. Click Contents in the Associated items menu
6. Click Upload
7. Upload the QlikSenseWebsocketTest.html file.
8. Copy the correct URL from the URL path
   
   
   
   
9. Open a web browser (from any machine from which you wish to test the WebSocket connection).
10. Paste the URL path and prefix the fully qualified domain name and https. 
    
    Example: https://qlikserver3.domain.local/content/WebSocketTester/QlikSenseWebsocketTest.html
    
    

What to do if any of them fail?

Verify that WebSocket is enabled in the network infrastructure, such as firewalls, browsers, reverse proxies, etc.

See the article below under Related Content for additional steps.

Related Content

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

When building a job using Jenkins,  it fails with the following error.

[ERROR] Failed to execute goal org.talend.ci:builder-maven-plugin:8.0.13:generateAllPoms (default-cli) on project standalone-pom: Transfer https://update.talend.com/Studio/8/updates/R2025-04/plugins/com.ibm.icu_67.1.0.v20200706-1749.jar failed -> [Help 1] 

Resolution

1. Check your configurations in Jenkins
   If there is a p2.base option, please remove it from TALEND_CI_RUN_CONFIG part and restart the build.
2. Host the update repository and add the missing dependency manually
   • Please host the update repository, by following the instructions here:
     Setting up an update repository by hosting it
   • Install the missing dependency like below.
     https://update.talend.com/Studio/8/base/plugins/com.ibm.icu_67.1.0.v20200706-1749.jar 
     In this example, it is the plugin "com.ibm.icu_67.1.0.v20200706-1749.jar" that is found in base.
   • Manually add the missing dependency to the Talend Studio update repository, under the following directory:
     <Talend Studio update repository>/studio/plugins/
   • Set the update repository that you have hosted as a Talend CommandLine parameter:
     For example:

     -Dtalend.studio.p2.update=D:/Talend/v80/StudioR202504 

Cause

From above error message, it indicates the com.ibm.icu_67.1.0.v20200706-1749.jar file is missing from the following URL which causes this issue.
https://update.talend.com/Studio/8/updates/R2025-04/plugins/com.ibm.icu_67.1.0.v20200706-1749.jar 

In Talend Studio R2024-04 or lower, the following CI Builder parameter was still supported:

-Dtalend.studio.p2.base   (Only supported for users with Talend Studio 8.0.1 R2024-04 or lower)

However, in Talend Studio R2024-05 or later,  the base option has been merged to the update repository.

Related Content 

For further details on configurations, please check here:
CI builder-related Maven parameters

Environment

• Talend Studio 
• Talend Data Integration 

Stitch's Facebook Ads integration supports only one account per integration. Multiple accounts are not supported.

Resolution

To use multiple accounts, create separate integrations for each account you wish to replicate data from.

Using multiple Facebook Ads integrations will only count as one source towards your plan's allotted sources.

Environment

• Stitch

This article aims to explain the use of the dev:dump-create command. The output of the command creates a compressed file containing the latest logs, bundle, and feature statuses, along with a heap dump file. This can be used to help troubleshoot an ESB Runtime container.

To run the command:

1. Open the Runtime console.
   • If the service is already running, in the Runtime container's "bin" folder, run the "client" script.
   • If the Runtime is not active, run the "trun" script.
2. Execute this command: 
   

   dev:dump-create

   
   
   
   The execution may take a few seconds.
   
   If you want to exclude the head dump file, leading to a smaller file and quicker execution, use this optional flag:
   

   --no-heap-dump

   
   
   
   
3. A dump zip will be located in the main folder of the Runtime container:
   
   

The dump file includes:

• Latest logs: audit.log, em.log, tesb.log
• bundles.txt
• environment.txt
• features.txt
• heapdump.hprof (VisualVM can be used to view this file)
• memory.txt
• threads.txt

Related Content

• Dev Scope | Talend ESB Container Administration Guide 
• Github README for Karaf container

Environment

• Qlik Talend ESB

Q: When does the Qlik Talend Administration Console license information update?

A: Adding a license to the Qlik Talend Administration Console will update it immediately.

When using a High Availability (HA) setup, the license cache remains for 60 minutes, and it takes 60 minutes for the recheck of the license from the database (licenses table) to take place. In a scenario where the first license was only just applied to the primary Talend Administration Console, the second Talend Administration Console will check the database after 60 minutes.

If a license check should be forced, restart the Talend Administration Console service(s) that need their license updated, or manually add the license in the server, which will write over the license in the database.

Environment

• Qlik Talend Administration Console (TAC)

By default, the built-in Map chart always uses maps on https://maps.qlikcloud.com. 

Some customers set up a local GeoAnalytics map server and would like to change the map URL to the local map server

From Qlik Sense April 2018, the built-in Map chart can be used with GeoAnalytics Server in an on-premise solution. For this GeoAnalytics Data Package 18.04 or newer is needed. First, install the data package according to the guide including the optional step named "Enable support for Qlik Sense Map" or similar. Then go to your Qlik Sense installation and point the Sense map to the server by editing the file mapconf.json in C:\Program Files\Qlik\Sense\Client\assets (or similar) and set the URL to the server in the serverUrl property and the key you have chosen during data package installation for Sense map users in serverKey.

Example:

{ "serverUrl":"https://mysite.com ", "serverKey":"abcdefg" }

Note that every time Qlik Sense is upgraded this file will be overwritten, so it will need to be edited again. Changing default configuration is not support by Qlik Support. Always make a backup prior to making any changes. 

Refer to Using GeoAnalytics with Qlik Sense map for more information. 

In certain scenarios, you may need to restart a Qlik Replicate task from a previously saved stream position, specifically a known LSN or SCN, rather than reload the entire task. This guide provides step-by-step instructions on how to resume a Microsoft SQL Server (MS-CDC) task from a stored stream position.

Steps to Start a Task from a Stored Stream Position

1. Locate the Previous Stored Stream Position
   
   Open the task log file and search for the final saved stream position. You should see an entry like the following:
   
   [SORTER          ]I: Final saved task state. Stream position 000000D8000062D00003:0:2147483647, Source id 12, next Target id 37, confirmed Target id 33, last source timestamp 1748932926987000  (sorter.c:777)
   
   In this example, the relevant stream position is: 000000D8000062D00003
   
   
   
   
2. Start the Task from This Position
   
   
   1. In the Qlik Replicate Console, open the relevant task
   2. Navigate to Task Settings --> Advanced Run Options
   3. Choose Tables are already loaded. Start processing changes from
   4. Choose Source change position (e.g. SCN or LSN) and enter the previously located Stream Position (000000D8000062D00003)
      
      
      
      
3. Validate in the Task Log
   
   

   After starting the task, check the log file to confirm that the task is starting from the specified stream position:

   [TASK_MANAGER    ]I: Task 'SQL-to-SQL__MS-CDC' running CDC only in fresh start mode, starting from log position: 'position:000000D8000062D00003'.  (replicationtask.c:1847)
   
   This confirms that Qlik Replicate is correctly picking up from the desired point in the transaction log.

   
   
   

Notes

• This method applies specifically to tasks using Microsoft SQL Server (MS-CDC) as the source.
• It is useful in scenarios such as resuming a failed task, reprocessing a limited set of changes, or disaster recovery testing.
• Always validate the stream position against the source database's current log retention to ensure the LSN is still available.

Environment

• Qlik Replicate, all versions
• SQL Server, all supported versions

When Qlik Replicate runs on a newly provisioned Linux server, the system memory usage is abnormally high and reaches critical thresholds.

Resolution

To resolve the issue, reduce or disable huge page allocation by updating the kernel parameter:
vm.nr_hugepages = 0

To make it persistent across reboots, update /etc/sysctl.conf. Then apply the change by "sudo sysctl -p"

Cause

The issue is related to the Linux kernel parameter vm.nr_hugepages, which defines the number of huge pages (typically 2 MB each) that are pre-allocated in memory.

In this case, the system was configured with:

vm.nr_hugepages = 24629

This reserves approximately 48 GB of memory (2M * 24629) for huge pages, significantly reducing the amount of available memory for other processes. If too many huge pages are reserved, the system may run low on regular memory pages, leading to performance degradation or instability.

Internal Investigation ID(s)

00352619

Environment

• Qlik Replicate, all versions
• Linux Server, all supported versions

The following error is found when executing a task that was built as a Docker image and accessing the directory using System.getProperty("user.dir").

Caused by: java.io.FileNotFoundException: /file/directory (Permission denied)

The error was not found in Talend 7.3, but after migrating to Talend 8.0, the issue exists.
Regarding building a job as a Docker image, further details can be found here: Building a Job as a Docker image.

Resolution

Use a directory that has public permission, such as: System.getProperty("java.io.tmpdir") 

Cause

Directory permission changes between Talend 7.3 and Talend 8.0 for the maven directory.

Environment

• Qlik Talend Studio

Exporting a task from Qlik Enterprise Manager fails with:

SYS-E-DESERIALERR, Failed to deserialize JSON to type ReplicationDefinitionExport: SYS-E-GT, LoadTimeout cannot be greater than 86400.

The task can be successfully exported from Qlik Replicate. 

Resolution

To resolve this issue, follow these steps to remove the invalid loadTimeout parameter and re-import the task:

1. Export the Task from Qlik Replicate
   
   
   1. Open Qlik Replicate
   2. Locate the failing task
   3. Export the task to a JSON file using the UI
      
      
2. Edit the Exported JSON File
   
   
   1. Open the exported .json file in a text editor (such as Notepad++, VS Code)
   2. Locate the following line under the target endpoint section:
      
      "loadTimeout": 144000,
      
      
   3. Delete the entire loadTimeout line
      
      
3. Delete the original task from the Qlik Replicate UI to prevent conflicts
   
   
4. Import the modified task
   
   
   1. Import the task to Qlik Replicate using the Import Task functionality (see Importing Tasks for more information)
   2. Select the modified JSON file
   3. Confirm that the task imports successfully without errors

Cause

The error is caused by an internal parameter, loadTimeout, which is set on the task’s target endpoint. This value exceeds the maximum allowed limit of 86400 seconds (24 hours).

This parameter is not set in the Qlik Replicate UI, but is added by manually editing the task’s JSON file.

Environment

• Qlik Enterprise Manager

This article explains how to change the log level for the QvWebStorageProviderConnector in Qlik Sense Enterprise on Windows.

Always back up .config files before making changes.

To change the log level of your QvWebStorageProviderConnectorPackage to debug mode:

1. Browse to %Program Files%Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage
2. Locate deploy.config
3. Open deploy.config file in a text editor with elevated permissions (Administrator)
4. Locate the <LoggingLevel> section:
   

   <!-- Valid values: Off, Error, Warn, Info, Trace - We would recommend you have at least Error set.
   --> 
   <LoggingLevel>Info</LoggingLevel>

5. Change the field Info to Trace
   
   Example:

   <LoggingLevel>Trace</LoggingLevel>

6. Save the file
7. Restart all Qlik Sense services

Environment

• Qlik Sense Enterprise on Windows