Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
Adjust the MaxHttpHeaderSize as documented in Qlik Sense Client Managed: Adjust the MaxHttpHeaderSize for the Micro Services run by the ServiceDispatcher.
The console error 431 means Request Header Fields Too Large in HTTP.
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.
To fix the affected Qlik Reporting template, change the body font currently used in the Excel template to a supported font family:
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.
An unsupported font is used in the current Qlik Reporting template.
SUPPORT-3842, QCB-32146
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:
This behavior was changed between 12.70 and 12.80. To reenable the previous default:
If the steps did not succeed:
QCB-32143
The central proxy virtual proxy cannot be deleted and virtual proxy prefix are unique per proxy.
In order to change to remove the prefix for a different virtual proxy to use another authentication method by default:
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.
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.
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.
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
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
Expand cloud storage for MySQL or perform a data cleanup to free up the space required.
Cloud MySQL has reached the cloud storage quota during data writes.
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
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.
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.
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.
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.
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.
Qlik Sense Enterprise on Windows
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.
<add key="WebSocketCSWSHCheckEnabled" value="true"/>
<add key="WebSocketCSWSHCheckEnabled" value="false"/>
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.
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]
-Dtalend.studio.p2.update=D:/Talend/v80/StudioR202504
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.
For further details on configurations, please check here:
CI builder-related Maven parameters
Stitch's Facebook Ads integration supports only one account per integration. Multiple accounts are not supported.
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.
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:
dev:dump-create
--no-heap-dump
The dump file includes:
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.
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.
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.
When Qlik Replicate runs on a newly provisioned Linux server, the system memory usage is abnormally high and reaches critical thresholds.
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"
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.
00352619
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.
Use a directory that has public permission, such as: System.getProperty("java.io.tmpdir")
Directory permission changes between Talend 7.3 and Talend 8.0 for the maven directory.
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.
To resolve this issue, follow these steps to remove the invalid loadTimeout parameter and re-import the task:
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.
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:
<!-- Valid values: Off, Error, Warn, Info, Trace - We would recommend you have at least Error set.
-->
<LoggingLevel>Info</LoggingLevel>
<LoggingLevel>Trace</LoggingLevel>