Advanced options is not visible when editing a sheet. This can happen on a specific app even if the option was present before.

Resolution

You can activate the "Show Sheet Header" option in the app settings to make the "Advanced option" button visible again.

1. Open the App settings.
   
2. Activate "Show Sheet Header".
   

Cause 

For some reasons, the "Show Sheet Header" could be deactivated in an app. "Advanced Options" is invisible when this happens, because it is located in the sheet header that is removed. The app looks like this in editing mode:

Environment

• Qlik Cloud

There may be several different symptoms associated with a need to regenerate and redistribute certificates;

• After installing, renewing, or changing a third-party certificate for use with Qlik Sense the Qlik Management Console (QMC) and Hub may become inaccessible leading to Page Cannot Be Displayed error.
  
  

  This article does not cover the use of a 3rd party certificate for end user Hub access, but the certificates used for communication between the Sense services. For recommendation on how to use a 3rd party certificate for end user access, see How to: Change the certificate used by the Qlik Sense Proxy to a custom third party certificate

• In the Qlik Sense Proxy trace logs, the last line may be indicating waiting for certificates to be installed or similar. In addition, even though Proxy service remains running, port 443 (by default) will fail to bind and start listening for requests.
  
  
• Qlik Sense may sometimes fail to create the correct certificates during installation if there are old/unused certificates left from a previous installation.  Also, certs can become corrupted, or newly installed certificates configured to be used may not be compatible. See Qlik Sense: Compatibility information for third-party SSL certificates and Requirements for configuring Qlik Sense with SSL.

Do not perform the below steps in a production environment, without first doing a backup of the existing certificates. Certificates are being used to encrypt information in the QRS database, such as connection strings. By recreating certificates, you may lose information in your current setup.
By removing the old/bad certificates, and restarting the Qlik Sense Repository Service (QRS), the correct certificates can be recreated by the service. If trying to remove certs, only the removal steps need to be followed.

The instructions are to be carried out on the Qlik Sense Central Node. In the case of a multi-node deployment, verify which node is the central node before continuing.

1. Open Qlik Sense Management Console (QMC)
2. Navigate to Nodes section
3. Add the column Central Node column through Column selector

If the current central node role is held by the failover, you need to fail the role back to the original central node by shutting down all the nodes (this implies downtime). Then start the original central node, reissue the certificates on it with this article, and when the central node is working apply the article Rim node not communicating with central node - certificates not installed correctly on each Rim node.

Step by Step instructions:

Test all data connections after the certificates are regenerated.  It is likely that data connections with passwords will fail.  This is because passwords are saved in the repository database with encryption.  That encryption is based on a hash from the certificates.  When the Qlik Sense signed certificates are regenerated, this hash is no longer valid, and the saved data connection passwords can not be decrypted.  The customer must re-enter the passwords in each data connection and save.  See article: Repository System Log Shows Error "Not possible to decrypt encrypted string in database"

1. Log on to the Central node using the Qlik Service Account and navigate to the 'Services' and to the Qlik Services.
   
   
2. Stop the QRS (this will also stop the other services; however, make sure the postgresql-64-12 or Qlik Sense Repository Database is still running).
   
   
    
3. Open Microsoft Management Console (MMC). 
   
   Important: Execute the MMC as the account configured to run the services (using Run as a different user [Ctrl-Shift & Right click on the exe to see option]... )
   
   
4. Add the following snap-ins for Certificates:
   
   
   • My user account
   • Local Computer account
     
     
5. In Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates, delete the Self-Signed certificates created by Qlik Sense, issued by HOSTNAME.domain-CA*
   
   *Where HOSTNAME is the machine name of the server in question and domain is the domain of the server.
   So for example, QlikServer1 is the computer hostname and the domain is domain.local, the certificate will be issued by QlikServer1.domain.local-CA
    
6. In Certificates (Local Computer) > Personal > Certificates, delete the Self-Signed certificate issued by HOSTNAME.domain-CA
   
   
7. In Certificates > Current User > Personal > Certificates, delete the Self-Signed certificate named QlikClient
    
8. Go to the folder C:\ProgramData\Qlik\Sense\Repository, delete the folder 'Exported Certificates'
   
   
9. Run this command from an elevated (admin) command prompt to create new certificates:
   
   "C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname 
   
   Note: If the script doesn't get to "Bootstrap mode has terminated. Press ENTER to exit.." and gets stuck at "[INFO] Entering main startup phase.." start the "Qlik Sense dispatcher service" and it will get to the end)
   
   
10. Verify the new certificates have been created by REFRESHING the screen for each certificate location, and then start the rest of the Qlik Sense services. In addition, verify that duplicate or multiple certificates were not created (rarely occurs). If so, the article will need to be followed again by starting with the deletion of the certificates.
    

There is no need to perform a full reinstall to propagate new certificates. Certificates are created by the QRS automatically if not found during the service startup process.

For Qlik Sense multi-cloud deployment (September 2020 or later):

The steps in this section must be performed after recreating certificates as described above.

1. Start Qlik Sense Repository Database service on CENTRAL NODE, or PostgreSQL Server service if running a dedicated instance of PostgreSQL database server.
   
   
2. Using pgAdmin tool or any other database client, connect to SenseServices database. (IMPORTANT: the below query needs to be executed on the SenseServices DB)
   
   

3. Execute following query against SenseServices database:

   DROP TABLE IF EXISTS hybrid_deployment_service.mt_doc_asymmetrickeysencrypt CASCADE;

    

4. Navigate to Deployments page of Multi-cloud Setup Console (MSC).

5. Delete and re-add any existing deployments by following the steps mentioned in Distributing apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS  and Distributing apps to Qlik Sense Enterprise on Kubernetes.

Node.js certificates

After the certificates have been recreated and then redistributed to all of the rim nodes, the node.js certificates stored locally on the central and all rim nodes also need to be recreated. Follow the below steps to perform this action:

1. Stop all Qlik Sense services
   
   
2. In Windows File Explorer, navigate to %ProgramData%\Qlik\Sense\Repository\Exported_certificates
   
   
3. Back up the Local certificates directory and then delete it
   
   
4. Restart the Qlik Sense services

Test all data connections after the certificates are rebuilt.  It is likely that data connections with passwords will fail.  This is because passwords are saved in the repository database with encryption.  That encryption is based on a hash from the certs.  When the Qlik Sense self-signed cert is rebuilt, this hash is no longer valid, and so the saved data connection passwords will fail.  The customer must re-enter the passwords in each data connection and save.  See article: Repository System Log Shows Error "Not possible to decrypt encrypted string in database"

Self Signed Certificates:

Notice if using an official Signed Server Certificate from a trusted Certificate Authority

The certificate information will also be in the QMC, under Proxies, with the Certificate thumbprint listed. If trying to merely remove all aspects of certs, this will need to be removed as well.

1. Go to Proxies 
   
   
2. Select your Proxy and click Edit
   
   
3. In the right pane, select Security
   
   
4. Scroll down and locate "SSL browser certificate thumbprint" in the Security section to locate the thumprint info.

If the Central Node repository service hanging in the logs:

1. Open C:\ProgramData\Qlik\Sense\Log\Repository\Trace
   
   
2. Look for this Example "API service initialized with 1501 available methods".  This is Central Node. 
   
   
3. If you see this Example "API service initialized with 2 available methods". This is a Rim node. 
   
   
4. For Central Node you should see as an example ""API service initialized with 1501 available methods". 
   
   
5. Running this command "C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname will resolved this issue.
   
   

If the above does not work, see Qlik Sense Enterprise Hub and Qlik Management Console (QMC) down - bootstrap fails with "Newly created client certificate not valid; root certificate can't sign new certificates"

When migrating Camel 3 projects that use the camel-rabbitmq library to interact with RabbitMQ, several important changes in components, dependencies structure and connection configuration must be considered. The primary change involves shifting from the native camel-rabbitmq component to the spring-rabbitmq component, as well as updating the connection configuration approach.

This article outlines all the necessary steps to successfully migrate projects that use the cMessagingEndpoint component with RabbitMQ.

Changes in Talend Studio that were made

• A new component, cRabbitMQ, has been added. This component must now be used in all Talend Studio routes to produce or consume messages from RabbitMQ.
• Additionally, a new type of configuration has been introduced in the cMQConnectionFactory component: MQ Server = RabbitMQ. This configuration is used to set up connections to RabbitMQ for any cRabbitMQ component.
• In Camel 4, the camel-rabbitmq dependency has been removed and replaced by the dependency for the new spring-rabbitmq component. This dependency is automatically added when the new component is used.

How to Migrate from cMessagingEndpoint with camel-rabbitmq to the New cRabbitMQ Component

1. The first step in the migration process is to replace the cMessagingEndpoint component (Fig. 1) with the new cRabbitMQ component (Fig. 2) in your project.
   The cRabbitMQ component has two base parameters: Exchange Name and Connection Factory.
2. The URI is now constructed based on Connection Factory properties and the values provided in the Advanced Settings of cRabbitMQ. Any additional needed options you can add in  Advanced Settings. 
   
   Now generated URI for the cRabbitMQ component will start from “spring-rabbitmq:” instead of “rabbitmq:” that it was in cMessagingEndpoint.
   
   Figure 1 - Old approach that used cMessagingEndpoint
   
   Figure 2 - New approach that uses cRabbitMQ and cMQConnectionFactory components
   
   
3. Since cRabbitMQ uses the cMQConnectionFactory component for connection setup, you will also need to add this component. In its settings, specify the MQ Server type as RabbitMQ, and provide your connection parameters: Host name, Port, Virtual host, as well as authentication parameters or SSL settings if necessary.
   
   Figure 3 - Example of cMQConnectionFactory settings
   
   
4. With the transition to the spring-rabbitmq component in Camel 4, there may be some changes in the format and support for certain parameters. For up-to-date information on the parameters supported in Camel 4, it is recommended to refer to the official Spring RabbitMQ component documentation: https://camel.apache.org/components/4.8.x/spring-rabbitmq-component.html

Related Content

• The upgrade to Java 17 and Apache Camel 4
• Qlik Talend and your Move to Camel 4: What you need to know

The QlikView Services can be set up to either use the local QlikView Administrators Group, or Digital Certificates. The Service Account has specific requirements. 

The two options during installation are Use digital certificates and Use QlikView Administrators Group.

Use digital certificates: 

Authenticate communication between QlikView servers using digital certificates and SSL. This alternative is recommended in environments where not all servers have access to a common Windows Active Directory or when the security provided by certificate authentication is required. Note that digital certificates are only supported by Windows Server 2008 R2 and later.

Use QlikView Administrators Group: 

Authenticate communication between QlikView services based on membership in the local Windows group QlikViewAdministrators. This alternative can be used in environments where all servers that are part of the QlikView installation can authenticate using a common Windows Active Directory.

Regardless of the option chosen, the service account used to run the services has to be:

• A local administrator on the host operating system
• Be able to run as a network service
• Have access to all the QlikView related folder structure, such as ProgramData, Program Files, and configured application data (.qvw storage, .qvd storage, log files) locations. 

Note:  GMSA (Standalone Managed Service Accounts) are not supported for Qlik products

Environment: 

Related Content:

• How to Change QlikView Service Account
• Is GMSA supported for use with Qlik Products 
   

The Qlik Sense Desktop or Server installation fails with:

INSTALLATION FAILED
AN ERROR HAS OCCURRED
For detailed information see the log file.
 

The installation logs (How to read the installation logs for Qlik products) will read:

Error 0x80070643: Failed to install MSI package.
Error 0x80070643: Failed to configure per-user MSI package.
Detected failing msi: DemoApps

Error 0x80070643: Failed to install MSI package.
Error 0x80070643: Failed to configure per-user MSI package.
Detected failing msi: SenseDesktop
Applied execute package: SenseDesktop, result: 0x80070643, restart: None
Error 0x80070643: Failed to execute MSI package.
ProgressTypeInstallation
Starting rollback execution of SenseDesktop

CAQuietExec:  Entering CAQuietExec in C:\WINDOWS\Installer\MSIE865.tmp, version 3.10.2103.0
CAQuietExec:  "powershell" -NoLogo -NonInteractive -InputFormat None 
CAQuietExec:  Error 0x80070002: Command failed to execute.
CAQuietExec:  Error 0x80070002: QuietExec Failed
CAQuietExec:  Error 0x80070002: Failed in ExecCommon method
CustomAction CA_ConvertToUTF8 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (74:54) [10:44:37:941]: Note: 1: 2265 2:  3: -2147287035 
MSI (s) (74:54) [10:44:37:942]: User policy value 'DisableRollback' is 0
MSI (s) (74:54) [10:44:37:942]: Machine policy value 'DisableRollback' is 0
Action ended 10:44:37: InstallFinalize. Return value 3.

The Failed to Install MSI Package can have a number of different root causes.

Install C++ redistributable

Dependencies may be missing. Install the latest C++ redistributable. 

.NET Framework update installation error: "0x80070643" or "0x643".

This issue may occur if the MSI software update registration has become corrupted, or if the .NET Framework installation on the computer has become corrupted (source: Microsoft, KB976982). 

Repair or reinstall .NET framework. 

PowerShell path not set as a system variable

How to troubleshoot:

Option 1

1. Start "Advanced System Settings" ->  "Advanced" tab -> "Environment Variables"
2. Select "Path" from "System variables" and Click Edit
3. Check if the PowerShell path is listed
4. If it is missing, add "%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\" and save the change
   
   Please make sure powershell.exe can be evoked successfully from %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ before adding the path.
   
   

1. Run the batch file in the article Windows Commands To Retrieve Environment Information v2.14
2. Open the result file and find the "Environment Variables" part
   

   ********************************************        
   *********  Environment Variables  **********        
   ********************************************    
   .......
   
   Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\administrator\AppData\Local\Microsoft\WindowsApps;C:\WINDOWS\system32\inetsrv\​

3. If the path of PowerShell is missing, refer to option 1 to add into the system variables. 

Web Platform Installer Extensions required

Install the Web Platform Installer Extension that includes the latest components of the Microsoft Web Platform, including Internet Information Services (IIS), SQL Server Express, .NET Framework and Visual Studio.

More information about the tool on the Microsoft page. 

Windows Updates are pending

Verify if there are pending Windows updates. Complete them and try again.

The Installer is not hosted on a local drive

The installation may fail if the installer is being executed from a network drive. Copy the installer to your local drive.

Environment:

Qlik Sense Desktop 

This article aims to demonstrate how to connect AD users to a Qlik Replicate instance installed on Linux.

Prerequisites

• The Linux Qlik Replicate server IP (obtained through, for example, ifconfig)
• The server password of the Linux box
• Qlik Replicate installed as per: How to install Qlik Replicate on Linux and set up browser access 

Preparation Steps:

1. Install Qlik Replicate on a Microsoft Windows machine.
2. When prompted to Select the Replicate Server that the Qlik Replicate Console will work with select 
   Connect to a remote Linux Replicate Server
   
   
   
   
3. Add the Linux machine IP and change the port if not using the default one
   
   
   
   
4. Review the data:
   
   
   
   
5. Finish the installation process.
6. Once completed, open the Windows Services app
7. Verify that the installation only installed Qlik Replicate Ui server
   
   
   
   
8. Open a command prompt (CMD) as administrator and run:
   
   cd C:\Program Files\Attunity\Replicate\bin
   
9. In this directory, run:
   
   repctl SETSERVERPASSWORD <same Linux server password>
   
   
10. Restart the Qlik Replicate UI server
11. Open the Qlik Replicate console
12. License the product
13. Log in with your windows credentials. You are now connected to the Linux Qlik replicate server as a local admin
    
    
    
    

Adding AD users

We suggest handling user roles in Activity Directory on the security group level rather than individual roles. This allows for better governance and is generally considered a good practice. 

For instance, you can add four groups:

• Admins
• Operators
• Viewers
• Designers

And then add your desired users to these specific groups. 

1. In the Qlik Replicate Console, switch to the Server view and open the User permission tab
   
   
   
   
2. Click + Add
   
   
   
   
3. You can either add a domain user or a domain group (Domain\user or Domain\group) 
4. Click OK
5. The new user/group will be added to the User/Group list.
   
   
   
   
6. To test, open an incognito browser and log in with the required authorized AD user.
   
   
   
   
7. You are connected to the Linux box with AD user.
   
   

Environment:

Qlik Replicate 

A DI task, which includes a tSystem component responsible for executing a PGP encryption command, was deployed to run on a remote Jobserver and encountered an error:

"1001 could not open keyrings, file not found."

Cause

"1001 could not open keyrings, file not found" - this appears to be an error message related to keyring or credential access on a system. This specific error typically occurs in Linux systems when there's an issue with the keyring service. The "1001" likely refers to a user ID, and the system is unable to find or access the keyring file that stores passwords and credentials.

After conducting a thorough examination, it was determined that in comparison to the working environment, the Jobserver utilizes a specific user session to run as a service. However, on the new/updated environment, the Jobserver service was not configured with the appropriate user/logged-on session.

Resolution

Ensure that the appropriate user session is used for the Jobserver service registry in Linux/Windows.

Environment

• Talend Data Integration 8.0.1

If your Qlik Sense Enterprise on Windows version is not compatible with the QSR database. 

This may occur if:

• You have upgraded Qlik Sense (for example: from May 2023 to November 2023) and have started the services. This will have migrated your QSR database from the May 2023 schema to the November 2023 schema.
  
  You have then decided to roll back to May 2023 and are attempting to restore the November 2023 QSR. They are not compatible and the migration will fail.
  
  the DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.
  
  
• If an incorrect version was installed during an upgrade of a Qlik Sense Enterprise on Windows multi node environment, such as installing different versions on RIM nodes, the Qlik Sense Repository service will not start on any node (including the central node). 
  

An incorrect version of Qlik Sense Enterprise on Windows in a multi node environment will trigger a database migration to this version. The result is that the Qlik Sense Repository service fails to start with the error: 

Fatal exception during startup Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.↵↓An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext

Resolution

As database migration started which had caused database corruption, you need to revert back to the old database backup to resolve this issue or contact Qlik Support for assistance.

Internal Investigation ID(s)

QB-8813

Environment

Qlik Sense Enterprise on Windows all versions

The upgrade to Java 17 and Apache Camel 4 marks a significant milestone for Qlik Talend users, ensuring alignment with modern technological standards while maintaining security and performance. This article provides technical details on why the move is important, as well as the move's key benefits and impacts. 

Content

• Context
• Why move to Camel 4?
• What has been the main challenge to provide Camel 4 support?
• What's the exact Camel 4 version used in 8.0.1-R2025-02?
• Benefits & impacts
• From Javax to Jakarta
• What are the new components brought by Camel 4?
• What are the components removed from Camel 4?
• What are the main API changes in Camel 4?
• Support for ActiveMQ 6.x in Route components
• Route/Job components update
• Jetty 12 /Spring 6/CXF 4.1 based Microservice
• Reference Links

Context

Why move to Camel 4?

• Camel 3 reached end of life by the end of 2024
• Full Java 17/21 support
• Jakarta EE 10 (Spring 6 / Jetty 12 / CXF 4.1 supported)
• New Camel components available (including AI components)
• ActiveMQ 6 support
• Up-to-date 3rd parties libraires
• Performance optimization

What has been the main challenge to provide Camel 4 support?

Camel 4 removed OSGi support, this increased the required efforts to build a Talend Runtime container “Camel 4 compliant”. It has been resolved by the camel-karaf project (https://github.com/apache/camel-karaf).

What's the exact Camel 4 version used in 8.0.1-R2025-02?

Camel 4.8.1 LTS (Long Term Support version) in both Studio and Runtime.

Benefits & impacts

From Javax to Jakarta

API libraries updates

Studio code-gen updates

• javax.activation => jakarta.activation
• javax.annotation.Priority => jakarta.annotation.Priority
• javax.ws.rs.Path => jakarta.ws.rs.Path
• javax.ws.rs.Consumes => jakarta.ws.rs.Consumes
• javax.ws.rs.Produces => jakarta.ws.rs.Produces
• javax.ws.rs.PathParam => jakarta.ws.rs.PathParam
• javax.ws.rs.MatrixParam => jakarta.ws.rs.MatrixParam
• javax.ws.rs.QueryParam => jakarta.ws.rs.QueryParam
• javax.ws.rs.HeaderParam => jakarta.ws.rs.HeaderParam
• javax.ws.rs.DefaultValue => jakarta.ws.rs.DefaultValue
• javax.ws.rs.ext.MessageBodyWriter => jakarta.ws.rs.ext.MessageBodyWriter
• javax.ws.rs.core.MediaType => jakarta.ws.rs.core.MediaType
• javax.ws.rs.core.StreamingOutput => jakarta.ws.rs.core.StreamingOutput
• javax.ws.rs.core.Response => jakarta.ws.rs.core.Response
• javax.ws.rs.core.UriInfo => jakarta.ws.rs.core.UriInfo
• javax.ws.rs.core.MultivaluedMap => jakarta.ws.rs.core.MultivaluedMap
• javax.ws.rs.WebApplicationException => jakarta.ws.rs.WebApplicationException
• javax.ws.rs.InternalServerErrorException => jakarta.ws.rs.InternalServerErrorException
• javax.jms.ConnectionFactory => jakarta.jms.ConnectionFactory

For the custom bean classes, javax package names above will be migrated to jakarta package names automatically. 

Example:

import javax.annotation.Generated; => import jakarta.annotation.Generated;

What are the new components brought by Camel 4?

What are the components removed from Camel 4?

What are the main version upgrades of 3rd-party libraries in Camel 4?

What are the main API changes in Camel 4?

You can get access to the advanced APIs in CamelContext known as ExtendedCamelContext via context.getCamelContextExtension().

For example, the Studio code-gen is changed from:

((org.apache.camel.impl.DefaultCamelContext) camelContext).setRegistry(realRegistry);

to:

((org.apache.camel.impl.DefaultCamelContext) camelContext).getCamelContextExtension().setRegistry(realRegistry);

More changes can be found here: Apache Camel 3.x to 4.0 Migration Guide (Apache.org).

Support for ActiveMQ 6.x in Route components

From Camel 4.7.0, there is a newly available camel-activemq6 component which support connecting with AMQ Server 6.x and is jakarta compatible.

• Apache camel 4.7.0 Release (Apache.org)
• camel-activemq - Upgrade to ActiveMQ classic 6.x or create camel-activemq6 (Apache.org)

In Studio, switch to camel-activemq6 in the cMQConnectionFactory component is done, and cJMS component is updated with “jakarta.jms” support.

Now, the cMQConnectionFactory is able to connect to AMQ Server 5.x and AMQ Server 6.x.

For a matrix table, see Summary Table of ActiveMQ Series Status (Apache.org).

Route/Job components update

cAWSSQS

• Added commons-io-2.15.1.jar as dependency
• Check AWS Simple Queue Service (SQS) for more option/parameter changes
• camel-aws-sqs: support for polling more than 10 messages from AWS SQS

cExchangePattern

Kept INONLY/INOUT pattern, others are removed

cREST

• jakarta.xml.ws-api-2.3.3.jar => jakarta.xml.ws-api-4.0.2.jar
• jakarta.xml.bind-api-2.3.3.jar => jakarta.xml.bind-api-4.0.2.jar
• Added jakarta.servlet-api-6.1.0.jar as dependency
• "javax.ws.rs.core.Response.class" => "jakarta.ws.rs.core.Response.class"

cSOAP

• jakarta.xml.ws-api-2.3.3.jar => jakarta.xml.ws-api-4.0.2.jar
• jakarta.xml.bind-api-2.3.3.jar => jakarta.xml.bind-api-4.0.2.jar
• Added jakarta.servlet-api-6.1.0.jar as dependency
• Added saaj-impl-3.0.4.jar as dependency

cXmlParser/cXmlWriter

• Removed XStream support

cMail

• Added jakarta.mail-api-2.1.3.jar as dependency
• Added angus-mail-2.0.3.jar as dependency

cKafka

• Added zstd-jni-1.5.6-3.jar as dependency

cHttp

• Jetty 12 based when it acts as Server

tRESTRequest

• jakarta.xml.bind-api-2.3.3.jar => jakarta.xml.bind-api-4.0.2.jar
• Added jakarta.xml.ws-api-4.0.2.jar as dependency
• Added jakarta.servlet-api-6.1.0.jar as dependency

tRESTClient (deprecation planned, prefer tHTTPClient)

• Added jakarta.xml.ws-api-4.0.2.jar as dependency

tESBConsumer

• jakarta.xml.ws-api-2.3.3.jar => jakarta.xml.ws-api-4.0.2.jar
• jakarta.annotation-api-1.3.5.jar => jakarta.annotation-api-2.1.1.jar
• jakarta.activation-api-1.2.2.jar => jakarta.activation-api-2.1.3.jar
• Added saaj-impl-3.0.4.jar as dependency

Jetty 12 /Spring 6/CXF 4.1 based Microservice

• Upgraded the microservice-utils to 1.0.81
• Added new BasicHttpAuthFilter

Reference Links

• https://camel.apache.org/manual/camel-4-migration-guide.html
• https://camel.apache.org/manual/camel-4x-upgrade-guide-4_1.html
• https://camel.apache.org/manual/camel-4x-upgrade-guide-4_8.html
• https://camel.apache.org/releases/release-4.0.0/
• https://camel.apache.org/releases/release-4.8.1/
• https://camel.apache.org/components/4.8.x/index.html
• https://cxf.apache.org/cxf-410-release-notes.html
• https://cxf.apache.org/docs/41-migration-guide.html
• https://issues.apache.org/jira/browse/CXF-8643 Remove Atom/Abdera from CXF
• https://issues.apache.org/jira/browse/CXF-8671 Support Jakarta EE 10

Environment

• Qlik Talend Studio

The task scheduling is stuck in the Sending/Requesting run loop, resulting in the following error messages appearing in the technical.log file.

The error java.lang.NoClassDefFoundError: Could not initialize class com.android.apksig.internal.apk.v1.V1SchemeSigner is caused by a java.lang.IllegalAccessError, which indicates that a class is attempting to access a restricted class (sun.security.x509.AlgorithmId) that is not exported by the java.base module in the newer Java versions.

Cause

Incompatible Java Version: this issue frequently arises when running an application on Java 17+ version, as access to internal APIs like sun.security.x509.AlgorithmId is restricted.

Resolution

Downgrade the JAVA version of TAC from Java 17 to Java 11 (or 8), as the TAC patch you are currently using, such as V8_R2024-01, is still base on JDK 8 and 11.

Environment

• Talend Administration Center 

Manually restart Qlik Sense services in right order is important because the Qlik Sense Repository Service is dependent on the Qlik Sense Repository Database (QRD) and the rest of the services are dependent on the Qlik Sense Repository Service.

Please review the Qlik Sense Online help for the relevant Sense version to find the Service Dependencies for your specific version. 

In a Multi-node environment, start the central node first and stop the rim nodes first.

Content:

• Correct Start Order:
• Central node
• Rim node
• Correct Stop Order:
• Central node
• Rim node
• Sample PS Script below for stopping and starting the Qlik Sense services:
• Optional monitoring of start process:

Correct Start Order:

Central node

1. Qlik Sense Repository Database

   If PostgreSQL has been unbundled, look for postgresql-x64-X

2. Qlik Sense Service Dispatcher
3. Qlik Sense Repository Service

   Delay for up to five seconds before starting the Qlik Sense Repository Service to allow the Dispatcher time to start its microservices.

4. Qlik Sense Proxy Service, Qlik Sense Engine Service, Qlik Sense Scheduler Service, Qlik Sense Printing Service

Rim node

We are unable to provide a comprehensive start or stop order as rim nodes can have a number of different combinations of services installed. Please skip any services you do not have installed.

1. Qlik Sense Service Dispatcher
2. Qlik Sense Repository Service

   Delay for up to five seconds before starting the Qlik Sense Repository Service to allow the Dispatcher time to start its microservices.

3. Qlik Sense Proxy Service, Qlik Sense Engine Service, Qlik Sense Scheduler Service, Qlik Sense Printing Service

Correct Stop Order:

Central node

1. Qlik Sense Repository Database (QRD)

   If PostgreSQL has been unbundled, look for postgresql-x64-X

   This is expected to terminate all services with a dependency on the Repository Database (see Service dependencies) if PostgreSQL is still bundled.
   
   
2. If not stopped by step one: Qlik Sense Repository Service 
3. If not stopped by step one: Qlik Sense Proxy Service (QPS), Qlik Sense Engine Service (QES), Qlik Sense Scheduler Service (QSS), and Qlik Sense Printing Service (QPR) in no specific order
   
   
4. Qlik Sense Service Dispatcher (QSD)

Rim node

We are unable to provide a comprehensive start or stop order as rim nodes can have a number of different combinations of services installed. Please skip any services you do not have installed.

1. Qlik Sense Proxy Service, Qlik Sense Engine Service, Qlik Sense Scheduler Service, Qlik Sense Printing Service
2. Qlik Sense Repository Service
3. Qlik Sense Service Dispatcher (QSD)

Sample PS Script below for stopping and starting the Qlik Sense services:

Get-Service "Qlik*" | Where-Object {($_.Name -like "QlikSense*" -and $_.Name -notlike "QlikSenseRepositoryDatabase") -or ($_.Name -eq "QlikLoggingService")} | Stop-Service -Force 
Start-Service -Name "Qlik Sense Service Dispatcher" 
Start-Service -Name "QlikSenseServiceDispatcher" 
Start-Service "Qlik*"

Optional monitoring of start process:

Open the following location: C:\ProgramData\Qlik\Sense\Log\Repository\Trace
Monitor the folder after starting the Qlik Sense Repository Service (QRS). Files with appended time/date will disappear.
 

This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.

If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.

Content

• Requirements:
• Preparation
• Upgrading to a later service release
• Upgrading to a new major PostgreSQL release

Requirements:

• Only upgrade to a supported version of PostgreSQL. See the Qlik Sense Enterprise on Windows System Requirements for details. 
• This guide covers deployments where PostgreSQL has been installed separately or previously unbundled using the Qlik PostgreSQL installer. 

This document covers the following scenario:

• Windows Server OS. The use of Linux, in managed cloud deployments or on-prem, is not covered. 
• Generic PostgreSQL deployment. Stream replication, SSL, or any other advanced configuration are not covered.

Preparation

Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.

• Qlik Sense Repository Database (from PostgreSQL database server)
• Qlik Sense share folder
• Qlik Sense CA-signed certificates

Upgrading to a later service release

These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8). 

1. Download the PostgreSQL installer from them PostgreSQL site
2. Stop the Qlik Sense Enterprise on Windows services. Leave your standalone PostgreSQL database running.
3. Run the PostgreSQL installer and follow the instructions.
4. Start the Qlik Sense Enterprise on Windows services.

No further steps are required.

Upgrading to a new major PostgreSQL release

If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14. 

1. Download the PostgreSQL installer from them PostgreSQL site
   
   
2. Run the installer
   
   During install:
   
   
   • Install the database on the standard 5432 port. 
     
     This allows us to have 12 running on the Qlik Sense default 4432 port and the 14 instance on 5432.
     
     
   • Set the same password as the one currently in use with the version 12 PostgreSQL instance. 
     
     
3. Open a Windows File explorer and create a backup folder, such as C:\backup 
   
   
4. Backup your version 12 database 
   
   This step is crucial. You may have already backed up your site, but in this step we will create the specific backup we will use to migrate your database, using a modified command.
   
   To do so:
   
   
   1. Stop all Qlik Sense Enterprise on Windows services on all nodes. Leave postgresql-x64-12 service (your current repository) running
      
      
   2. Stop postgresql-x64-14 (your newly installed PostgreSQL instance)
      
      
   3. Open a Windows Command Line (CMD) as administrator
      
      
   4. Run:
      SET PGPASSWORD=postgrespassword (replace this with the actual password)
      
      
   5. Run:
      cd “C:\Program Files\PostgreSQL\12\bin”
      
      
   6. Run
      pg_dumpall.exe -h localhost -U postgres -p 4432 -f c:\backup\backup_db.sql
      
      
   7. Follow the onscreen instructions and wait until the backup is finished
      
      Note: If you are prompted to input the password (even if it was previously entered correctly), you will need to modify pg_hba.conf. 
      
      Location: C:\Program Files\PostgreSQL\12\data\pg_hba.conf
      
      Change md5 to trust and restart the postgresql-x64-12 service. See Changing the Database Superuser Password without Qlik Sense Installed for details.
      
      Once the backup has completed, revert back to md5.
      
      
5. Migrate from 12 to 14
   
   We are now moving our Qlik Sense repository from the earlier release of PostgreSQL into the new one.
   
   
   1. Start the postgresql-x64-14 service
      
      
   2. Stop postgresql-x64-12
      
      
   3. Open a Windows Command Line (CMD) as administrator
      
      
   4. Run:
      cd “C:\Program Files\PostgreSQL\14\bin”
      
      
   5. Run
      psql -h localhost -U postgres -p 5432 -f c:\backup\backup_db.sql
      
      
   6. Follow the onscreen instructions.
      
      Note: If you receive the error password authentication failed for user "postgres", (even if it is correct), you will need to modify pg_hba.conf. 
      
      Location: C:\Program Files\PostgreSQL\14\data\pg_hba.conf
      
      Change scram-sha-256 to md5 and restart the postgresql-x64-14 service  and redo step e). See Changing the Database Superuser Password without Qlik Sense Installed for details.
      
      
6. With the import finished, copy the following two files from your old 12 data folder into your new 14 data folder:
   
   
   • pg_hba.conf 
   • postgresql.conf 
     
     
7. Open postgresql.conf and verify that the port is set to 4432 (the standard Qlik Sense port)
   
   
8. (If not done already) stop the postgres-x64-12 service
   
   
9. Restart the postgres-x64-14 service
   
   
10. Start all Qlik Sense services
    
    
11. Once you have confirmed all functionality and tested, uninstall PostgreSQL 12. This can be done directly from the Windows Control Panel and Programs and Features

Related Content:

Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer 
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version 
Changing the Database Superuser Password without Qlik Sense Installed 

Talend CIDI Pipeline is showing that the project is duplicated in the reactor when running generateAllPoms command from Maven like below:

mvn org.talend.ci:builder-maven-plugin:8.0.X:generateAllPoms

ERROR] [ERROR] Project 'org.example.odin_migration.job:ClaimMigrationControl:0.1.0' is duplicated in the reactor @
[ERROR] Project 'org.example.odin_migration.job:ClaimMigrationControl:0.1.0' is duplicated in the reactor -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

Resolution

Using the latest version (version=lastVersion) to avoid version confusion issue:

mvn org.talend.ci:builder-maven-plugin:8.0.X:generateAllPoms  | clean deploy
-DitemFilter=(type=process)and(version=lastVersion)
(windows : --define “itemFilter=(type=process)and(version=lastVersion)” )

Cause

It seems to be a Version Confusion Issue and there are job versioning and maven versioning, which are not compatible with together.

For example

It happens often because of this, as you can easily have 

job version 0.1 => maven version 0.1.0
job version 0.2 => maven version 0.1.0 (same)

It would be better to set it for example in the filter of Build>Maven:version=latest then re-generate the poms, it will keep only the latest version of jobs.
If  you still need to use all the versions, it is not possible to use only the latest version of jobs.

Please try to do a generateAllPoms from maven with some filters (based on your use case) + build the jobs as you need.

Environment

Talend Studio 

This article documents how to configure a Qlik tenant to send emails using MS365.

Prerequisite

An account with an active Office365 license is required for this setup.

MS365 Setup

First, we configure the MS365 tenant to support the configuration.

Once you have an account set up on the MS365 side, let's go to the Microsoft Tenant settings:

1. Open the Microsoft Entra admin center (Home - Microsoft Entra admin center)
   1. Go to Overview
   2. In the overview screen, you will see your Tenant ID. Copy this value, you will need it to configure your Qlik Cloud Tenant.
   3. Click Application to register an application
   4. Click + New registration
      
      
      
      
   5. Name your application
   6. Select the Supported account type that matches your needs
   7. Click Register to register your application
2. Create a Client Credential 
1. Click Certificates & Secrets
2. Click + New client secret
3. Describe (name) the client secret and select its expiration value
4. Click Add to finish this step
   
   
   
   
5. After creating your client secret, the following is displayed:
   
   
   
   
6. Copy the value and save it in a safe place. You will need it to complete your Qlik Cloud Tenant setup.
   
   
3. Enabling the right APIs:
   1. Go to API Permissions
   2. Click + Add Permission
   3. Select Microsoft Graph
   4. Select Application permissions
   5. In the Select permissions field look for Mail.Send
   6. Select the Mail.Send permission

      Setting Application permissions to Mail.Send grants the application to use any email address from your organization.

   7. Click Add permission
   8. Click Grant admin consent for <MS Tenant Name> to finish this step
      
      
      
      
4. Select an Owner for the application
   1. Click + Add Owner
   2. Type the name of the User who will be the Owner
   3. Mark the user and click Select 

Qlik Cloud Tenant Setup

1. Open your Administration activity center (see Accessing the Administration activity center)
2. Go to the Email Provider section
3. Select Microsoft 365
   
   
   
   
4. Insert all previously set information:
   1. Sender email address: Insert an email registered on Microsoft. This can be your email address or another dedicated account created specifically for this purpose. 
   2. Tenant ID: Obtained from the Microsoft Entra Overview section.
   3. Client ID: The Application (client) ID you previously created.
   4. Client secret: The Client secret value which you saved in the previous setup steps.
      
      
      
      
5. Save the changes
6. Send a test email

Environment

• Qlik Cloud Analytics
• Microsoft Office 365

The information in this article is provided as-is and will be used at your 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.

In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).

For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.

Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.

Index

• Supported Scenarios
• Upgrades
• New installs
• Requirements
• Known limitations
• Installing anew Qlik Sense Repository Database using PostgreSQL
• Qlik PostgreSQL Installer - Download Link
• Upgrading an existing Qlik Sense Repository Database
• The Upgrade
• Next Steps and Compatibility with PostgreSQL installers
• How do I upgrade PostgreSQL from here on?
• Troubleshooting and FAQ
• Related Content

Video Walkthrough

Video chapters:

• 01:02 - Intro to PostgreSQL Repository
• 02:51 – Prerequisites
• 03:24 - What is the QPI tool?
• 05:09 - Using the QPI tool
• 09:27 - Removing the old Database Service
• 11:27 - Upgrading a stand-alone to the latest release
• 13:39 - How to roll-back to the previous version
• 14:46 - Troubleshooting upgrading a patched version
• 18:25 - Troubleshooting upgrade security error
• 21:15 - Additional config file settings

Supported Scenarios

Upgrades

The following versions have been tested and verified to work with QPI (1.4.0): 

Qlik Sense February 2022 to Qlik Sense November 2023.

If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.

New installs

The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.

Requirements

• Review the QPI Release Notes before you continue

• Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:

  • Uninstall all patches before using QPI (see Installing and Uninstalling Qlik Sense Patches) or
  • Upgrade to an IR release of Qlik Sense which supports QPI

• The PostgreSQL Installer can only upgrade bundled PostgreSQL database listening on the default port 4432.
• The user who runs the installer must be an administrator.
• The backup destination must have sufficient free disk space to dump the existing database  
• The backup destination must not be a network path or virtual storage folder. It is recommended the backup is stored on the main drive. 
• There will be downtime during this operation, please plan accordingly
• If upgrading to PostgreSQL 14 and later, the Windows OS must be at least Server 2016

Known limitations

• Cannot migrate a 14.8 embedded database to a standalone
• Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• The installer itself does not provide an automatic rollback feature.

Installing a new Qlik Sense Repository Database using PostgreSQL

1. Run the Qlik PostgreSQL Installer as an administrator 
   
   
2. Click on Install 
   
   
3. Accept the Qlik Customer Agreement 
   
   
4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 
   
   
5. Set your Database superuser password and click Next
   
   
6. Set the database installation folder, default: C:\Program Files\PostgreSQL\14

   Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

7. Set the database data folder, default: C:\Program Files\PostgreSQL\14\data

   Do not  use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.

8. Review your settings and click Install, then click Finish
   
   
9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.
   
   The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.
   
   
10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  
    
    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 
    

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer Release Notes

Upgrading an existing Qlik Sense Repository Database

The following versions have been tested and verified to work with QPI (1.4.0): 

February 2022 to November 2023.

If you are on any version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade.  From Qlik Sense August 2023 a 9.6 update is blocked.

The Upgrade

1. Stop all services on rim nodes 
   
   
2. On your Central Node, stop all services except the Qlik Sense Repository Database 
   
   
   
   
3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 
   
   
   
   
4. Highlight the database and click Upgrade 
   
5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (b) Next.
   
   
   
   
6. Provide your existing Database superuser password and click Next.
   
   
7. Define your Database backup path and click Next.
   
   
   
   
8. Define your Install Location (default is prefilled) and click Next.
   
   
   
   
9. Define your database data path (default is prefilled) and click Next.
   
   
    
10. Review all properties and click Upgrade.
    
    The review screen lists the settings which will be migrated. No manual changes are required post-upgrade.
    
    
    
    
11. The upgrade is completed. Click Close.
     
12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.
    
    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 
    
    
    
    You will also find a new postgresql-x64-14 service. Do not rename this service. 
    
    
    

     

13. Start all services except the Qlik Sense Repository Database service. 
    
    
14. Start all services on your rim nodes.
    
    
15. Validate that all services and nodes are operating as expected. The original database folder in C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
    

     

16. Uninstall the old Qlik Sense Repository Database service.

    This step is required. Failing to remove the old service will lead the upgrade or patching issues.

    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the appropriate msi file.
       
       
       
       If you were running 9.6 before the upgrade, search PostgreSQL.msi
       If you were running 12.5 before the upgrade, search PostgreSQL125.msi
       
       
    3. The msi will be revealed.
       
       
    4. Right-click the msi file and select uninstall from the menu.
       
       
       
       
    
    
17. Re-install the PostgreSQL binaries. This step is optional if Qlik Sense is immediately upgraded following the use of QPI. The Sense upgrade will install the correct binaries automatically. 
    

    Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts. 

    If you do not immediately upgrade:
    
    
    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
       
       
    2. From there, search for the .msi file appropriate for your currently installed Qlik Sense version
       
       
       
       For Qlik Sense August 2023 and later: PostgreSQL14.msi
       Qlik Sense February 2022 to May 2023: PostgreSQL125.msi
       
       
    3. Right-click the file
    4. Click Open file location
       
       
       
       
    5. Highlight the file path, right-click on the path, and click Copy
       
       
       
       
    6. Open a Windows Command prompt as administrator
       
       
    7. Navigate to the location of the folder you copied
       
       Example command line: 
       
       cd C:\ProgramData\Package Cache\{GUID}
       
       Where GUID is the value of the folder name.
       
       
    8. Run the following command depending on the version you have installed: 
       
       Qlik Sense August 2023 and later
       
       msiexec.exe /qb /i "PostgreSQL14.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       Qlik Sense February 2022 to May 2023
       
       msiexec.exe /qb /i "PostgreSQL125.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
       
       This will re-install the binaries without installing a database. If you installed with a custom directory adjust the INSTALLDIR parameter accordingly. E.g. you installed in D:\Qlik\Sense then the parameter would be INSTALLDIR="D:\Qlik\Sense".
       
       
18. Finalize the process by updating the references to the PostgreSQL binaries paths in the SetupDatabase.ps1 and Configure-Service.ps1 files. For detailed steps, see Cannot change the qliksenserepository password for microservices of the service dispatcher: The system cannot find the file specified.

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

Next Steps and Compatibility with PostgreSQL installers

Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.

Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads. 

How do I upgrade PostgreSQL from here on?

See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.

Troubleshooting and FAQ

1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:
   
   C:\Users\Username\AppData\Local\Temp\2
   
   A backup of the original database contents is available in your chosen location, or by default in:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\X.X
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated
   
   
2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:
   
   This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.
   
   See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.
   
   To resolve this, start the postgresql-x64-XX service.

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 video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

Related Content

Qlik PostgreSQL installer version 1.3.0 Release Notes  
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades 

Qlik Sense patches can be downloaded from the Qlik Download page. Patches are cumulative, and only one patch can be installed at a time.

Example: Patch 4 for Qlik Sense February 2019 will include all fixes from 3, 2, and 1.

Before applying a patch:

• Read the Release Notes to locate any dependencies of new features or changes to features which can affect your environment
• Verify and record all customisations (manual changes to setting files or configuration files not otherwise represented in the GUI). While patches generally do not change settings or revert configuration files to default, a drastically changed feature (see release notes) can impact customisations.
• Previously installed patches on the same release track do not need to be uninstalled

To install:

1. Download the required patch 
2. Schedule a brief downtime as the server will need to be restarted
3. Execute the patch installation package and follow the on-screen instructions
4. Restart the Windows server host

To uninstall:

Executing a patch installation package will automatically uninstall the previous patch and install the new one. If you need to uninstall a patch manually:

1. Open the Windows Add and Remove Programs menu
2. Click View installed updates from the left panel
3. Locate the Patch
4. Uninstall the Patch
5. Restart the Windows Server host

If uninstall through Control Panel is not possible:

1. Locate the Qlik_Sense_update.exe installer package in C:\ProgramData\Package Cache\[guid]\.
   
   If the package required for the uninstall has been removed or renamed, a possible workaround is to obtain an exact copy (same version, release) of the Qlik_Sense_update.exe from a different environment and manually replacing it.
   
   
2. Right click the Qlik_Sense_update.exe and click Uninstall

Related Content:

Custom configuration file changes not kept after Qlik Sense upgrade 

AWS KMS-Managed Keys (SSE-KMS) should be disabled when "Server-Side Encryption" is disabled in component tS3Put, however, after comparing the generated code lines, KMS is still Enable.

As a result, the job will get an error. Even there is a workaround by explicitly disabling KMS in component setting, though it is hard to find what the job error is as the parameter is hidden.

Steps to reproduce

1. Drag tS3Put component from Palette into Designer and then generate the code to compare later in studio
2. Enable "Server-Side Encryption" and "Use KMS" by ticking checkbox and Save the current job
   KMSEnabled

    

   
   KMSEnabledCode

   
3. Disable "Server-Side Encryption" from component basic settings, save the current job and then compare the new generated code with the code in the step1. You can see KMS is still enabled in code.
   Server-sideEncryptionDisabledKMSDisabledCode
    

Resolution

Fix version of related bug was updated to: 8.0.1-R2025-03 

Cause 

It was a known bug and raised in an internal Issue: QTDI-1133

Related Content

For more information about tS3Put component setting, please see tS3put

For more information about the server-side encryption information, see Protecting Data Using Server-Side Encryption.

Internal Investigation ID(s)

Internal Investigation IDs : QTDI-1133

Environment

• Talend Studio 
• Talend Data Integration 

Connecting to a local GeoAnalytics servers fails with Error: Invalid Key , Error Message Either your key is invalid or it has expired

The message Invalid Key can also be displayed on the map objects when using the GeoAnalytic extensions:

Environment:

Qlik GeoAnalytics 

Resolution

Using internal GeoAnalytics server:

The licenses for GeoAnalytics connector and map extensions must match the license applied to the GeoAnalytics server. If not, please re-license the connector or the server as instructed in the following articles: 

Installing Qlik GeoAnalytics server
Installing Qlik GeoAnalytics for Qlik Sense

However, in some circumstances, the license key may not take effect due to no connection to the Internet. Then, manual change needs to be done in the configuration files for GeoAnalytics connector, extensions, or server:

QlikSense server
GeoAnalytics connector:    C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector\IdevioGeoAnalyticsConnector.exe.config

Example:

<add key="licenseKey" value="0000000011111111:1654281610406"/>

GeoAnalytics extensions:   \\<file shared server>\QlikShare\StaticContent\Extensions\ideviomap\License.js

1. edit License file

Example

define([], function () {return "00000001111111"});

QlikView server
GeoAnalytics connector:    C:C:\Program Files\Common Files\QlikTech\Custom Data\QvIdevioConnector\IdevioGeoAnalyticsConnector.exe.config

Example:

<add key="licenseKey" value="0000000011111111:1654281610406"/>

QlikView GeoAnalytics extensions: 

C:\ProgramData\QlikTech\QlikViewServer\Extensions\Objects

or

C:\Users\YourAdminName\AppData\Local\QlikTech\QlikView\Extensions\Objects

or

Open the QV QMC  - Sytem - QlikView Servers -  Folders

Check the System Folder for "Alternate Extensions Path"

1. edit License file

Example

define([], function () {return '00000001111111';});

GeoAnalytics server
 C:\ProgramData\Qlik GeoAnalytics Server\server3\config\IdevioLicenses.lef

Please make sure all license information in the above files match. If not, please manually change it accordingly. 

Using Qlik GeoAnalytics Server:

Verify the license has been applied to the correct installation path. The extensions are stored in the StaticContent folder within the shared directory. To verify the path of the StaticContent folder, go to QMC > Service Cluster.

Run the license tool (C:\Program Files (x86)\QlikView\GeoAnalyticsLicenseTool) using Custom Installation with the path listed for Static Content root folder with '\extensions\' appended. 

Example: \\servername\Share\StaticContent\Extensions

After the license is applied successfully, go back to the app, refresh the page, and verify the map appears as expected.

While updating the qliksenserepository user with any of the Configure-Service.ps1 scripts, you may encounter the following error: 

Invoke-Query : Exception calling "Start" with "0" argument(s): "The system cannot find the file specified"
At C:\Program Fi 1es\Qlik\Sense\Mobi1i tyRegistrarService\install\instal1-uti1s\Postgres.psl:56 char :10
+ $ret = Invoke-Query $command
+ Categorylnfo : NotSpecified: (:) [Invoke-Query], MethodlnvocationException
+ FullyQualifiedErrorld : Win32Exception,Invoke-Query

Cause

Some Power-shell scripts have not been updated for the new default value of the Database home.

Different versions of Qlik Sense Enterprise for Windows come with their own bundled PostgreSQL version.

Examples: Qlik Sense Enterprise for Windows from May 2021 to May 2023 will install PostgreSQL 12.5, while previous releases used PostgreSQL 9.6 as a default during a new install. Similarly, from Qlik Sense Enterprise on Windows August 2023 onwards, Qlik pre-installs PostgreSQL 14.8 as the default database. For more details on the default, see the System Requirements for your respective version.

When you upgrade from an earlier release you will keep 9.6 or 12.5 and you should not have the issue.

This leads to issues with the following line:

Variation One:

[string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\9.6",

Variation Two:

[string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",

Environment

• Qlik Sense Enterprise on Windows

Resolution

Apply the actions in this solution on all nodes.

Depending on your version of Qlik Sense Enterprise on Windows different corrections will be needed.

1. Search for all *.ps1 scripts in C:\Program Files\Qlik\Sense
   
   For example, you can use Notepad++, utilizing its Search > Find in Files option: 
   
   
   
   Your directory may vary if you have used an alternative folder.
   
   
2. Find out what version of PostgreSQL binaries you have installed with Qlik Sense Enterprise on Windows:
   
   
   1. Open a Windows File Explorer and browse to C:\Program Files\Qlik\Sense\Repository\PostgreSQL
      
      
   2. You will find the PostgreSQL binaries folder
      
      
      
      
3. After identifying your PostgreSQL binaries version, replace the old path reference in the Configure-Service.ps1 files with the new version.
   
   Examples:
   
   replace 
   
   $senseInstallPath\Repository\PostgreSQL\9.6
   
   with 
   
   $senseInstallPath\Repository\PostgreSQL\12.5
   
   or
   
   replace 
   
   $senseInstallPath\Repository\PostgreSQL\12.5
   
   with 
   
   $senseInstallPath\Repository\PostgreSQL\14
   
   
4. Repeat this action on the path C:\Programdata\Qlik and update C:\Programdata\Qlik\Sense\QSMQ\scripts\SetupDatabase.ps1 
   
   

This is an example list of .ps1 files needing to be edited in the Qlik Sense Enterprise for Windows August 2023 version:

• C:\Programdata\Qlik\Sense\QSMQ\scripts\SetupDatabase.ps1 
  
  Line 12: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\AppDistributionService\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\DataPrepService\install\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\HybridDeploymentService\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\Licenses\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\MobilityRegistrarService\install\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\NLAppSearch\install\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\NLBroker\install\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\NotifierService\install\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",
  
  
• C:\Program Files\Qlik\Sense\PrecedentsService\install\Configure-Service.ps1
  
  Line 13: [string]$postgresHome = "$senseInstallPath\Repository\PostgreSQL\12.5",

Resolution

After deleting the Dynamic Engine, it is important to also delete the Dynamic Engine environment. Simply deleting the Dynamic Engine will not halt token usage. To fully free up the tokens, both the Dynamic Engine and its environment must be removed.

Environment

• Talend Cloud