This is a companion article to the Upgrade advisory for Qlik Replicate and SAP HANA DB 2.0 SPS7 and SPS8 blog post.

Multiple log-based replication issues may affect Qlik Replicate customers using SAP HANA DB 2.0 who are upgrading to the SAP HANA service packs SPS7 and SPS8.

What problems have been identified?

SAP HANA DB 2.0 SPS7 (Service Pack 7):

• RECOB-9379: SAP Hana Log-Based SPS7 (73 and 76) version date and timestamp columns replicating as NULL
• RECOB-9427: SAP HANA log-based task erroring when the log position was at the end of the transaction log

RECOB-9379 and RECOB-9427 have been addressed by Qlik. An early build (Qlik Replicate 2024.11, SP03 Early Build) is available.

Download the early build from: https://files.qlik.com/url/wucx4x2nbyytwseu (password: pk2pfzup)

No other issues in Service Pack 7 are known.

SAP HANA DB 2.0 SPS8 (Service Pack 8):

• RECOB-9652: There is still ongoing work in R&D related to DML operations failing to get data values in Hana Log Based SP08 (80 & 81).

What action can be taken?

Customers planning to upgrade to SPS7 or SPS8 should be aware of the risk, particularly with the changes to Hana logs affecting the Hana log parsing with respective to Qlik Replicate. We strongly advise postponing any upgrades to these versions until Qlik R&D has reviewed and certified these service packs.

What about trigger-based replication?

Qlik has not received any reports of customers using trigger-based replication experiencing the same issues. However, if an upgrade is planned, we recommend thoroughly testing in lower environments before scheduling any production upgrades.

Environment

• Qlik Replicate
• SAP HANA DB 2.0 SPS7 and SPS8

A Binary Load on a Qlik Sense App located in the Qlik Sense App share fails. 

The following error is logged in the Script Log: 

Environment:

Qlik Sense Enterprise on Windows 
QlikView 

There are four main requirements for a successful binary load:

1. Binary load must be the first statement in the load script
2. Only one binary load statement per script
3. The source QVW or QVF file must be available during the entire binary load*
4. The reloading user must have access to read the source QVW or QVF file*

*Binary Loads from live Qlik Sense Apps are not supported in Qlik Sense Enterprise on Windows.

Example: BINARY [SenseAppID];  (for example BINARY 2d405d18-ddd3-5353-5128-adce12e482bd;)

QVF files in the Server Apps folder are read/written by Engine service when:

1. When users are doing modifications on those apps, so a file lock will be always possible to happen on those files at any moment.
2. In a multi-node environment, apps are constantly being synchronized(called 'binary sync) onto all nodes, which means any changes on such app from any node will have the possibility to lock the app.
3. And some 'binary sync does not happen instantly. The sync actions will be delayed for several hours when the system load is high. So the file lock is very unpredictable.

During these operations, those files may be locked and causing reload task failure.

Resolution

For Qlik Sense:

Do binary load on static QVF/QVW files if necessary, or load QVD files generated by other QVD generators.

What to generally consider:

• Binary load is not the first command line in the script
  It is a requirement that binary load is the first executable command in the load script. See below online help references:
  Qlik Sense: Binary Load
  QlikView: Binary Load 
   
• The source application is Section Access protected
  The reloading user must be allowed to access and open the file being targeted in the binary load. This means that the QlikView or Qlik Sense service user must be included in the Section Access table. 
   
• Source QVW is updated by another task during binary load
  No other task can update the source QlikView (QVW) or Qlik Sense (QVF) application file during the binary load. 
   
• Source QVW is locked by 3rd party process, like anti-virus or backup
  No other software can lock the source QlikView (QVW) or Qlik Sense (QVF) application file during the binary load. 
   
• Source QVW is located on a file share, and file share access is interrupted by network problem
  Any file share hosting the source QlikView (QVW) or Qlik Sense (QVF) application file must be available during the binary load.

Using a Salesforce source endpoint, especially while using the Incremental Load source endpoint, all UPDATE operations are treated as INSERT operations for the table "UserRole". This leads to duplicate IDs found from the target table in the CDC processing stage.

Environment

• Qlik Replicate, all versions
• Salesforce source, all versions

Resolution

Set the task to UPSERT mode with Apply Conflicts set to Update the existing target record and Insert the missing target record. For more information see Apply Conflicts.

Note: this WA applied to Apply Change Mode, if the 'store changes' are enabled, duplicate ID is presented in __ct table still.

Cause

71 objects are missing the "CreatedDate" system field (including tables "AccountShare", "UserLogin", "UserRole", and similar). This is why Qlik Replicate can't identify if the change is inserted or updated, leading to both INSERT and UPDATE being converted to INSERT operation for these tables.

Internal Investigation ID(s)

00294581

Purpose

The purpose of this post is to help you install the database drivers necessary to allow your Qlik Data Gateway to communicate with your company's servers once you have completed the Qlik Data Gateway installation itself. 

Background

If you are anything like me, perhaps you panicked a bit at the thought of installing the Qlik Data Gateway in a Linux environment. I have a lot of experience with .EXE installations in Windows environments. You know "Next – Next – Next – Finish." But an .RPM file?  I had never even see that extension type before. If you were a Linux connoisseur beforehand, you probably guessed that my image for this post is an homage to the Fedora flavor of Linux. Otherwise you just thought it was an advertisement for the new "Raiders of the Lost Data" movie.

In any event, by now you have created your first Data Gateway, applied the registration key, completed the setup instructions and thankfully the command to check your Data Gateway service shows that it is running.

When you go back to the Data Gateway section of the Management Console and do a refresh your eyes fill you with happiness because your brand spanking new Data Movement Gateway shows "Connected.”

 A lesser person would go celebrate right now. But you've decided to try and connect to a source before doing your happy dance. So, you create a new Data Integration project to the destination of your choice. While you will ultimately have many different data sources, let's imagine that you decide to start with a "SQL Server (Log Based)" connection, as your first source test.

You input the server connection details, but your SQL Server doesn't use a standard port for security. Finally, you find information online that you should input your server IP followed by a "comma and the port #". As an example, if your servers IP is 39.30.3.1 and your security port is 12345 you would input "39.30.3.1,12345'. Next you input the user and password credentials. Your last step is to choose the database. Easy peezy, lemon squeezey. Right?

You press the "Load databases" button but suddenly a dialog comes up telling you that the Data Gateway can't connect because it can't find a SQL Server driver.

Driver Installation

Your heart starts beating quickly but naturally as a pro, you remain calm on the outside. Eventually you realize that whether on Windows or Linux, applications have always required drivers to communicate with servers. This is nothing new, we just got excited when we saw that connected message and thought we were done. Upon going back to the setup guide

[https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-setting-up.htm]

you realize that there is in fact a link labeled "Setting up Data Gateway – Data Movement source connections."

So, you go ahead and click the link and it takes you to:

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Landing/connecting-data-2.htm 

Wow, so many sources, and so many additional links to click to ensure the required drivers are in place for the sources your company will need. All the documentation is there, but I know firsthand that it can get a bit overwhelming, especially if Linux isn't your native language, which is the reason for this post.

Obviously every one of you reading this works in an environment that may require different data source connections than the others. Thus, there is no way for me to predict and help with your exact configuration. However, odds are strong that most of you likely require at least: SQL Server, Databricks, Snowflake, Postgres or MySQL, various combinations of them, or perhaps all of them.

As tedious, or imposing as it may be, I highly recommend you walk through the documentation for each data source you will need. But thanks to my buddy John Neal, I have attached a Linux shell script that can be executed to configure all 5 of those data sources for you. Given the many flairs and versions and configurations of Linux I can't ensure that it will work for everyone, but at least it is a start for those that may want to press an easy button, and those that like me may be somewhat or brand new to Linux.

If you choose to take advantage of it, understand that it is only being offered a shelp, and is not meant to replace the documentation. To utilize it you will need to do the following (Please note in my examples I have changed to the root user. If you are logged in as a normal user account, you may need to use SUDO "super user do"):

1. Copy the attached "repldrivers-el7.sh.txt" file your Linux home directory where you placed the gateway .RPM file.
2. Change the file name to simply be "repldrivers-el7.sh" so that it's clear that it is a shell script in case you or others see it in the future.
3. Issue the following command from your prompt: "chmod 775 repldrivers-el7.sh" so that the file has the appropriate security allowing it to be executed.
4. Issue the following command from your prompt: "./ repldrivers-el7.sh"  
5. Issue the following command from your prompt: "cd /etc"
6. Issue the following command from your prompt: "cat odbsinst.ini"    

If all went well with the installation your output should look like similar to the following image that was part of my file:

It's almost time to do our happy dance, but let's hold off until we test. In my starting example I asked you to assume we wanted to test against a "SQL Server (Log Based) connection." When we left off it was because we got an error message we had no driver while trying to load the list of databases. I will try that again.

 Oh no, the heart rate is going up again. 

We have successfully installed the Qlik Data Gateway. We have successfully installed the required drivers. Yet, we are getting this new error message. Let's focus on our breathing and try and digest the situation. What could cause our attempt to connect to our data source to timeout? I got it.

It's likely network security. We know what we want to talk to. We know the location. We know the credentials. But our networks aren't always wide open to do the talking. Resolving your connectivity/firewall issues may or not be with your abilities and if you are like me, you may need to seek the help of your IT/Networking team.

When I reached out to my friendly IT guru, here within Qlik, he was able to help me get everything in place so that my Linux server could speak with my database servers, including all of the needed ports.

Once they were completed I was able to test and sure enough my data connection succeeded.

Whether or not you do a happy dance, as I did, I hope that this post has helped you get to that sweet smell of success. After all, someone has to be known as the amazing person who got your Qlik Data Gateway going so that others in the Data Engineering team could create all of those lights out Qlik Cloud Data Integration projects that would be feeding data in near real time to all of those wonderul analytics use cases. Hopefully with the help of the documentation and this post, that person is you my friends. 

Challenge 

One of the things I've long admired about the Qlik Community is their willingness to help each other through this Community site. If you are a Linux guru and are so inclined I would love to see you share other versions of the shell script that I have started. Maybe your organization is using another flair/version of Linux and you needed to make a few tweaks to my file. Maybe your organization needed Oracle added and you can tweak my file. Whatever the reason, I sure hope you will give back to the community by sharing all of those tweaks here. Who knows, your help might help them be able to do their happy dance. And we all know the world is a better place when more people do their happy dance. 

Related Content 

Qlik Data Gateway - Data Movement prerequisites and Limitations - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-prerequisites.htm

Setting up the Data Movement gateway - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-setting-up.htm

PS - I created both of the images here using a generative AI solution called MidJourney. I hope they've added to the fun of this post. 

By default, Qlik Replicate creates target table columns with the same size as the source, especially when the source and target databases are homogeneous and share the same character set. However, in certain scenarios, you may need to automatically create target columns with double the size of their corresponding source columns.

This can be achieved using a Global Transformation rule:

Convert data type
	for %.% with column % and data type STRING
	to data type STRING, Length: [$AR_M_SOURCE_DATATYPE_LENGTH * 2] and sub type Regular

With this configuration, all STRING data type columns in the target database will have twice the length of their corresponding source columns.

To achieve this:

1. Go to Global Rules
2. Click New Rule and Transformation... 
3. Set Transformation Type to Convert data type
4. Click Next
5. Set the Transformation Scope
   In our example, we will increase all STRING columns to double. This means we set Data Type: to STRING
   
   
   
   
6. Click Next
7. In the Transformation Action window, press the fx button
   
   
   
   
8. Drag the column "$AR_M_SOURCE_DATATYPE_LENGTH" from the left menu into the Build Expression field. Complete the expression as:
   

   $AR_M_SOURCE_DATATYPE_LENGTH * 2

   
   
   
9. Click OK
10. Name your new transformation rule (example: Double-STRING-column-size)
11. Click Finish
12. Reload or re-run the task

Environment

• Qlik Replicate

This article explains how to set up a job that allows you to stop all currently running tasks with only one click.

1. Open the Qlik Replicate Console and navigate to the SERVER page
2. Go to Scheduler → Scheduler Jobs, then click + New Scheduler Job
3. Configure the job with the following settings:
   
   Name: Stop All Tasks
   Type: Stop Task
   Schedule Time: Local time or UTC
   Schedule: Once
   At: Jan 1, 2035, 00:00
   
   We set the schedule to a future date to prevent accidental execution.
   
   Apply to Tasks: All tasks (or specific tasks you want to stop)
   
   
   
   

You can now stop all tasks by simply adjusting the Schedule Time we previously set to a future date to one or a few minutes ahead. Once the schedule executes, all tasks will be stopped.

This method provides an efficient way to stop tasks without manual intervention each time.

Environment

• Qlik Replicate

A connection issue has occurred between Talend Cloud and Talend Remote Engine showing the following error:

Server unreachable 127.0.0.1:8003, message: Connection refused: connect

Cause

1. Network problems are occurring at the time. Please check with your network team.
2. The Remote Engine version that you are using is outdated. (For example: Talend Remote Engine 2.12).

Resolution

1. Try the following settings to see if it helps mitigate the problem.
   Open the file: <Remote Engine installation folder>/etc/org.talend.ipaas.rt.deployment.agent.cfg 
   
   The default value of the following parameters will be 300. Please adjust it to 600.
   

   wait.for.connection.parameters.timeout = 600
   flow.deployment.timeout = 600 ​

   
   If the issue still occurs, please adjust the timeout settings to see if it helps.
2. Upgrade to Talend Remote Engine 2.13, since Talend Remote Engine 2.12 has been retired, and ongoing improvements are being made to resolve connection issues between TMC and Talend Remote Engine.

Environment

• Talend Cloud 

This article provides an overview of the available blocks in the Apache Kafka connector in Qlik Application Automation.

Apache Kafka is an open-source distributed event streaming platform used by thousands of companies for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications.

Authentication

Authentication to Apache Kafka happens through Basic Authentication. To use this connector, you need to provide the username and password to your Rest Proxy Server. When you connect to Apache Kafka in Qlik Application Automation you will be presented with the following screen:

Available blocks

The blocks that are available in the Apache Kafka connector focus on Producing events to topics in the Apache Kafka cluster.

• Get Broker
• List Brokers
• Delete Broker
• Get Cluster
• List Clusters
• Create Topic
• Get Topic
• List Topics
• Delete Topic
• Produce Event

Working with the Apache Kafka blocks

Apache Kafka blocks make use of the Confluent Rest Proxy APIs to produce and consume messages from an Apache Kafka cluster.

1. Follow this step-by-step guide to set up your Confluent Rest Proxy API. Make sure you have an active cluster before proceeding.
2. Use the Get Cluster and List Cluster blocks to get basic information about your cluster.
3. Create a topic in your cluster using the Create Topic block from which you will produce and consume the messages.
4. You can make use of the Produce Event block to produce messages/data to the Topic.

Apache Kafka Use Case: Enabling Users To Perform Reverse ETL

Some companies may already use Apache Kafka for application integration challenges. Applications push and pull data from specific topics to communicate with one another. This solves the issues where each application has to talk to every other application. It is identical to what a service bus would do.

• We can publish messages to a Kafka topic that can be picked up by a customer's operational systems.
• It can be multiple systems at once, for example, their CRMs and ERP applications.
• It can be a single application (might be an on-premises system and we might not have a connector).
• Operational systems would be consumers on topics we publish to.
  
  

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

"RestConnectorMasterTable" General Script Error in statement handling

RestConnectorMasterTable:
20200826T102106.344+0000 0088 SQL SELECT
20200826T102106.344+0000 0089 "name",
20200826T102106.344+0000 0090 "value"
20200826T102106.344+0000 0091 FROM JSON (wrap off) "contactCustomData"
20200826T102106.344+0000 0092 WITH CONNECTION (
20200826T102106.344+0000 0093 URL "      ",
20200826T102106.344+0000 0094 HTTPHEADER "Authorization" "**Token removed for security purpose**"
20200826T102106.344+0000 0095 )
20200826T102106.967+0000 General Script Error in statement handling
20200826T102106.982+0000 Execution Failed
20200826T102106.986+0000 Execution finished.

Environment

Qlik Sense Enterprise on Windows 

Resolution

To be able to catch the exact error and mitigate the issue they need to apply our recommended best practices for error handling in Qlik scripting using the Error variables
Error variables 
Script control statements 

Set to ErrorMode=0 it will ignore any errors and continue with the script. You can use the IF statement to retry the connection or move to another connection for a few attempts and then it will change it to ErrorMode=1 and fail or just disconnect on its own.

A sample script is located here, but further options can be added from the Help links already provided.
Qlik-Sense-fail-and-retry-connection-sample-script 

Note: QlikView scripting is the same in these functions for Qlik Sense unless otherwise stated, but there are some very helpful items in the links.
Best-Practice-Error-Handling-in-Script 

Cause 

Error with the fetch of the token with the rest call. If the number of rows in a table doesn't match or is less than expected, trigger the script to throw an error and have it try to load the table again for more records, or if the count is off, do a Loop until returns the correct number.

Internal Investigation ID(s) 

QB-3164

Data warehouses are optimized to store historical data for complex analytics and reporting. Historical data can include transactional history (e.g. store all transactions for seven years), or slowly changing dimensions attribute history (e.g. manage changes to specific attributes like name or address, over time). Consequently, we rarely purge data from the data warehouse.

However, operational systems that feed the data warehouse, frequently delete records. Some systems allow for complete record removal, while others impose restrictions. As a result, the data warehouse can experience side effects of record deletion form the source systems.

In short, managing record deletion in a data warehouse is complicated, and this paper describes the best practices for handling various data deletion scenarios with Qlik Data Integration.

<<UPDATED 3/5/2021 with additional comments on how to handle data marts>>

Storing a table containing NULL value to a txt or qvd file fails with error General Script Error in statement handling

For example, the following piece of the script fails with the above error when executed:

DataTable: 
LOAD * INLINE [ 
NP 
1 
]; 

LEFT JOIN
LOAD  * INLINE [ 
NP, AD 
2, test 
]; 

STORE AD FROM DataTable INTO [lib://Temp/test.csv] (txt); 

Environment:

• Qlik Sense Enterprise on Windows , November 2018 IR to Patch 4 versions

Resolution:

• Verify if there are extra and unintended characters in any of the column names (blank spaces, extra letters). Remove them and run the script again. In addition, see IsNull - script and chart function which may help with troubleshooting.
• Verify that sufficient disk space is available. 
• This issue was reproduced in lab only in the November 2018 releases and not on newer builds. There was no fix officially produced for the problem found on November 2018. Note that November 2018 is no longer a supported version, so upgrading to a newer release to check if issue is resolved would be required. See Qlik Sense, QlikView, NPrinting, Qlik Insight Bot End of Support Date 

If you experience the issue in an up to date Sense environment, connect with our active Qlik Community for creative application development assistance and ideas.

When uploading multiple data files (such as QVDs) to Qlik Cloud, only a fraction of the files is successfully uploaded.

No error message is displayed. The upload completes with the “Succesfully Uploaded Files” message and reports a lower number of files than the ones selected for upload. 

Attempting to close or move away from the window will prompt a pop-up stating, “Are you sure you want to cancel the upload?”

Resolution

This is caused by browser cache issues.

Either:

• Clear the browser's cache
• Switch to a different browser or use incognito mode

Environment

• Qlik Cloud Analytics

Talend Remote Engine Heart Beat is failing hourly with 'GOAWAY received' error and the karaf.log shows below:

2024-08-01T10:16:58,638 | ERROR | pool-28-thread-1 | JAXRSUtils | 469 - org.apache.cxf.cxf-rt-frontend-jaxrs - 3.6.2 | | Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
2024-08-01T10:16:58,638 | WARN | pool-28-thread-1 | PhaseInterceptorChain | 467 - org.apache.cxf.cxf-core - 3.6.2 | | Interceptor for {http://pairing.rt.ipaas.talend.org/}PairingService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
Caused by: java.io.IOException: /<IP>:<port>: GOAWAY received

This could also be a possible solution when the following error is also showing in the log:

Caused by: java.io.IOException: HTTP/1.1 header parser received no bytes

Resolution

1. Stop Remote Engine.
2. Edit the <RemoteEngineInstallation>/etc/org.talend.ipaas.rt.pairing.agent.cfg file and replace the line 

   heartbeat.interval=60 (by default) 

   with 

   heartbeat.interval=65

3. In the file <RemoteEngineInstallation>/etc/system.properties, remove or comment out the line below (if it exists):
   

   org.apache.cxf.transport.http.forceVersion=1.1​

4. Restart Remote Engine.

Do not set heart interval to more than 180 seconds(3 mins). If Talend Cloud does not receive a heartbeat from the Remote Engine for more than 3 mins, it will show the Remote Engine's status as unavailable.

Cause

The connection to the server pair.xx.cloud.talend.com is kept during 60 seconds and Heartbeat.interval > 60 seconds allows to close this connection and prevent "GOAWAY received" error message.

Related Content

For more information about heartbeat concept and heartbeat interval, please refer to documentation:

Monitoring-remote-engine-health

Internal Investigation ID(s)

 Internal Jira Case ID: TMC-4122

Environment

Talend Cloud 

A folder with a name consisting of non-alphabetical characters (such as in Japanese) has been correctly added to the configuration-file-connector.properties file stored in C:\ProgramData\Qlik\Gateway\, but the folder is not listed in the File (via Direct Access gateway) Connector.

For more information about the connector, see File (via Direct Access gateway).

Resolution

Verify configuration-file-connector.properties is set to UTF-8:

1. Open configuration-file-connector.properties in an editor such as Notepad++
2. Verify the character code
   
   
   

Cause

The character code of configuration-file-connector.properties is not set to UTF-8. This prevents the File Connector from recognizing the name.

Environment

• Qlik Cloud Analytics

This article provides information on how to set up Multi-Factor Authentication (MFA) for your Qlik Talend Cloud login when using Qlik Account to log in.

How can I set up Multi-Factor Authentication for my Qlik Talend Cloud Account for Qlik ID login?

Qlik Talend Cloud has been migrated to a unified Qlik Account login. Since then, multi-factor authentication can be enabled as described in How to Setup Multi-Factor Authentication (MFA) for Qlik Sense Business. 

These steps are specific for Qlik Account only. If you already have an SSO provider set up (not Qlik Account), Multi-Factor authentication must be configured on the third party provider (see Configuring single sign-on (SSO) for Talend Cloud).

1. Install a Multi-Factor Authentication (MFA) app on your phone, such as Google Authenticator, LastPassAuthenticator, Microsoft Authenticator, or similar.

   Using only a QR reader will not work. An MFA Authenitcator app is required.

2. Go to your Qlik ID portal and log in with your Qlik ID
3. Navigate to the Password & Security settings (link)
4. Follow the instructions for setting up MFA as documented in How to Setup Multi-Factor Authentication (MFA) for Qlik Sense Business.
   1. In Password & Security, scroll to Multi-Factor Authentication and click Setup
   2. Scan the QR code with your Authenticator app
   3. Follow the onscreen instructions in your Authenticator app to complete the setup
   4. Save the provided Recovery Code.

      This code is mandatory in case you need to recover your account. A new one will be generated after use; always save the most recent one.

   5. Multi-Factor Authentication is now enabled.

Environment

• Qlik Talend Cloud

Upgrading Qlik Sense Enterprise on Windows fails with a generic error message:

An error has occurred
For detailed information see the log file

The Qlik Sense Repository Database service is no longer installed after the failed installation.

This means that the database password validation did not complete and a partial rollback has occurred. This has removed the database software, but it has not removed the database itself.

The database password is normally password is checked before the upgrade process begins, but under some circumstances, such as the database service being stopped, this check does not occur. Once the new version of the database software is installed it will attempt to open the database as part of the install verification process and will fail. This then prompts a rollback of the database software and removing the new version.

Resolution:

Reinstall Qlik Sense. (Uninstall, Reinstall)

During the uninstall process, do not remove the certificates or database. 

Once Qlik Sense is uninstalled, you can proceed to install the desired upgraded version of Qlik Sense, the installer will detect the existing database and request the password, if it is from an earlier version the installer will make the necessary changes as part of the installation process.

Environment:

Qlik Sense Enterprise on Windows 

This is a companion article to Qlik Sense Enterprise for Windows - New Security Patches Available Now  and only applies to the patches affected by QB-30633.

If you have experienced issues with visualizations and extensions not loading after upgrading to the security patches released on the 4th of December 2024, upgrade to the new patches which address QB-30633:

• May 2024 Patch 11
• February 2024 Patch 15
• November 2023 Patch 17
• August 2023 Patch 17
• May 2023 Patch 19
• February 2023 Patch 16

If visualizations and extensions do not behave as expected after the upgrade, follow the outlined steps below:

• If the extensions are not available in the Qlik Sense Management Console, on the file share, as well as in the assets panel
  
  Solution:
  
  Restart the Qlik Sense Services services, then verify again
  
  
• If the extensions are available in the Qlik Sense Management Console, on the file share, as well as in the assets panel, but not visible in any of your Qlik Sense apps
  
  Solution:
  
  Clear the browser cache
  
  
• If sheets are not rendering and the error 'an error occured' is thrown
  
  Solution:
  
  Clear the browser cache
  
  
• If extensions continue to not import or load, regardless of the above two steps taken.
  
  Solution:
  
  
  1. Stop the Qlik Sense Repository service
  2. Open the file C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
  3. Go to the section <appSettings>
  4. Add the key VisualizationExtensionsExtractFilter as the last key in the <appSettings> section:
     
     <add key="VisualizationExtensionsExtractFilter" value="md|css|js|json|pdf|png|qext|txt|html|htm|gif|jpg|jpeg|wbl|otf|ttf|woff|woff2|eot|svg|bmp|mp3|jp2"/>
     
     
  5. Save the file
  6. Restart the Qlik Sense Services

If issues continue regardless, contact support so that we can assist you effectively.

Environment

• Qlik Sense Enterprise on Windows May 2024 Patch 11
• Qlik Sense Enterprise on Windows February 2024 Patch 15
• Qlik Sense Enterprise on Windows November 2023 Patch 17
• Qlik Sense Enterprise on Windows August 2023 Patch 17
• Qlik Sense Enterprise on Windows May 2023 Patch 19
• Qlik Sense Enterprise on Windows February 2023 Patch 16

QlikView QVD files contain lineage information of the stored data. 

Environment:

QlikView any version

The lineage information can be found in the QVD file XML header and might look like below, with connection details and the SQL statements used during reload. 

Resolution:

1. Open Qlikview Desktop client 
2. Go to Help > About Qlikview...
3. Right click the QlikView logo in the bottom right corner
4. Highlight the AllowDataLineage value
5. Set the value to -1 to disable the Lineage information
6. Click Set to store the value change
7. Close the settings and about dialog boxes
8. Reload the QVD generator application
   
   

1. Open the QlikView Server’s batch settings.ini file in a text editor. Default file path; C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch\Settings.ini
2. Add AllowDataLineage=-1 in the [Settings 7] section of the settings file. 
3. Save the settings file and close text editor
4. Restart QlikView Server, to trigger loading of the altered settings 
5. Reload the QVW file from QlikView management console to see that the setting has been changed
6. To enable the lineage information follow the steps above, but set the Value to 0 instead of -1 in step 5.

TAC task failed to start randomly, with the following error displayed as follows:

Job start failed because of parallel clean jobId = 20250318 155947 gfsl3or deplovment.comons.exception.clientserverException: org.talend.remote.commons,exception,clientserverException: job start failed because of paralrq.talend.remotecleanupdeployment jobId = 20250318 155947

Cause

The value assigned to the 'org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAXOLDEXECUTIONS_LOGS' parameter in the TalendJobServer.properties file was set too low, specifically at 30.

Resolution

Adjust the value of 'org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAXOLDEXECUTIONS_LOGS' parameter to a default setting of 1000 or a higher number in the TalendJobServer.properties file. For example:

org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAXOLDEXECUTIONS_LOGS=1000

Environment

• Talend Administration Center 8.0.1

Creating a new SAP Extractor endpoing in Qlik Talend Cloud fails with the following error:

[INFO ] Sending services health status: {"type":"poll_replicate_async_request","payload":{"request_type":"services_status_change_report","jobId":"Uxg6kx6963IMPloynt-1hCD_sQa-DktO","requestedContext":{"servicesStatus":[{"Name":"local_repsrv","State":"CONNECTED","Message":null},{"Name":"qdi-db-commands","State":"CONNECTED","Message":null},{"Name":"external-data-provider","State":"CONNECTED","Message":null}]}}}
13 2025-03-26 10:46:34 [Service ] [ERROR] Failed analyzing request, traceId: 7e8a49232266af1bb1dee5dae84edcf7
Attunity.Infrastructure.Globals.AttInfrastructureException: SYS-E-HTTPFAIL, Failed to load dynamic endpoint properties.
at Attunity.Infrastructure.Globals.AtRestApiClientUtils.DoWebRequestIntern(String address, String method, String[] headers, Object body, Stream outStream, String contentType, Boolean isReconnect)
at Attunity.Infrastructure.Globals.AtRestApiClientUtils.DoWebRequest(String address, String method, String[] headers, Object body, Stream outStream, String contentType)
at Attunity.Aem.Globals.DirectRequest.ReplicateDoWebRequest(ReqData reqData, Stream requestStream)
at Attunity.Infrastructure.HostManager.RestHandler.Dispatch(ReqData reqData, Stream requestStream, DispatchResponseFormat responseFormat)
at Attunity.Infrastructure.HostManager.RestHandler.Dispatch(ISession session, String requestUrl, RestHttpMethod httpMethod, Stream requestStream)
at QCSConnectionBroker.QcsConnectionBroker.OnMessage(String jsonMessage)

Resolution

Correct the password or create a password that avoids special characters. 

Cause

The error is caused by an invalid password or the password being used has special characters, such as !@#$%^&*()_+.

Internal Investigation ID(s)

QCDI-1424

Environment

• Qlik Talend Cloud