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 

The index becomes unusable when an index rebuild fails due to ORA-1652 during a full load operation.

Despite the error, the Qlik Replicate task log does not display any errors, making it difficult to detect the unusable index.

Resolution

Uncheck Use Direct Path Full Load in the Oracle target endpoint settings.

This will allow Qlik Replicate to detect the issue and suspend the table accordingly.

Cause

When using direct load, some integrity constraints appear to be automatically disabled, allowing all data to be loaded but causing the index to become unusable.

Since the OCI functions return successfully, no errors are indicated. This is a product limitation when using Oracle as the target.

Environment

• Qlik Replicate all versions

When using Amazon Kinesis as a target endpoint in a Qlik Replicate task, there is a prerequisite to create a stream named attrep_apply_exceptions. This stream allows the Apply Exceptions control table to be written to the target.

Creating a Kinesis stream named attrep_status doesn't mean the attrep_status table is added to the newly created stream. Instead, it is added into the main data stream. 

Is there a way in which the attrep_status table can be put into its own stream?  

Resolution

In the Amazon Kinesis Data Streams target endpoint settings, there are two options for publishing data:

• Specific stream: All data, including user data messages and Qlik Replicate internal control messages (e.g., the attrep_status message), is published to a single stream.
  
  Example: All messages are delivered to the stream APACKinesis
  
  
  
  

• Separate stream for each table: Each table's data is published to a stream with the same name as the table by default. This behavior can be customized using $stream.

   

  The task’s status messages are always published to the attrep_status stream.

Check that Separate stream for each table is set. This is the correct option to route the  attrep_apply_exceptions and attrep_status related messages to dedicated streams.  

Cause

The incorrect use of Specific stream causes the attrep_apply_exceptions and attrep_status routing messages to be added to the same target stream.

Environment

• Qlik Replicate

The following error is logged if the transaction log was encrypted during backup and the Microsoft SQL Server endpoint is set to:

• Backup Logs Only (a)
• Replicate has file-level access to the backup log files toggled on (b)
• Encrypt only the transaction log backup file (.trn) (TDE not enabled)

Resolution

If you want to encrypt transaction logs, enable Transparent Data Encryption (TDE).

Transparent Data Encryption (TDE) is only supported when accessing backup transaction logs through SQL Server’s native functionality.

It is not supported when using the endpoint's file-level access option.

When enabling TDE, do not select the option Replicate has file-level access to the backup log files.

Cause

Encrypted backups are not supported when accessing backup transaction logs, which is a limitation when using the Microsoft SQL Server as a source. See Limitations and considerations for details.

Environment

• Qlik Replicate

There is a difference of the display in the UI after upgrading from Talend Data Catalog version 8.0 to 8.1.

In Talend Data Catalog 8.0, if you add “Defines“ relationship with term and model, and then add it to your custom presentation, the display name is Model Name.

TalendDataCatalog8.0

After upgrading from Talend Data Catalog version 8.0 to 8.1, "Defines" in Talend Data Catalogn 8.1 shows Host Name (hostname:port) instead of Model Name while defining a model.

 TalendDataCatalog8.1

Resolution

This issue is fixed by 20241217 release and please upgrade to it.

Cause

This issue is from the name of objects at the end of relationships in manage repository UI and a related MITI jira issue has been raised.

Internal Investigation ID(s)

Here is a JIRA ticket for MITI: TALMM-5871

Environment

• #Talend Data Catalog v 8.1
• Talend Studio 

The Qlik Sense log files can be easily collected using the Log Collector. 

The Log Collector is embedded in the Qlik Sense Management Console. It is the last item listed in the Configure Systems section.

For instructions on how to use the Log Collector, see Log collector (help.qlik.com).

Content

• Requirements
• Using the Log Collector
• What does the Qlik Sense Log Collector access?
• Manually collecting log files
• Older Qlik Sense Versions (3.1 and earlier)

Requirements

The user must be a root admin and have administrative permissions.

Using the Log Collector

The best way to gather these logs is to use the Qlik Sense Log Collector. If the tool is not included in your install, it can be downloaded from this article. 

1. Login to Windows Server on Qlik Sense node
2. Open Windows File Explorer
3. Navigate to Log Collector folder at C:\Program Files\Qlik\Sense\Tools\QlikSenseLogCollector
4. Press Shift key and right click on QlikSenseLogCollector.exe 
5. Select Run as different user
6. Enter Qlik Sense service account credentials.
7. Configure log collection
   • Date range to collect logs from (minimum of 5 days if possible)
   • Support case number to include in ZIP file name
   • Select options 
   • Include Archive logs
8. Click Collect
9. If Qlik Sense is not automatically accessible on the node, further options are presented.  
   • Qlik Sense is running and on this host
     this option to get more options on automatic log collection
   • Qlik Sense is not running or accessible
     this option allows to define the path to local Qlik Sense log folder
   • Qlik Sense is located elsewhere
     this option allows to enter FQDN of remote Qlik Sense server
10. Wait until collection is finished
11. Click Close
12. Open generated ZIP file in C:\Program Files\Qlik\Sense\Tools\QlikSenseLogCollector
    Note, no need to unzip the file, simple double click on the ZIP file to browse its content
    • Confirm it contains JSON and TXT files, if system info options were enabled in Step 6
    • Confirm there is one folder per node in the deployment, named in same way as the node
    • Confirm there is a Log folder representing Archived Logs from persistent storage
13. If ZIP content is incomplete, repeat steps above or contact support for further guidance
14. If ZIP content is accurate, attach ZIP file to support case for further analysis by Qlik

What does the Qlik Sense Log Collector access?

This list provides an overview of what system information the Qlik Sense Log collector accesses and collects.

• WhoAmI (information)

  C:\Windows\System32\whoami.exe

• Port status (information)

  C:\Windows\System32\netstat.exe -anob

• Process Info (information)

  C:\Windows\System32\tasklist.exe /v

• Firewall Info (information)

  C:\Windows\System32\netsh.exe advfirewall show allprofiles

• Network Info (information)

   C:\Windows\System32\ipconfig.exe /all

• IIS Status (iisreset /STATUS Display the status of all Internet services.)

   C:\Windows\System32\iisreset.exe /status

• Proxy Activated (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyEnable"

• Proxy Server (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "proxyserver" 

• Proxy AutoConfig (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "AutoConfigURL" 

• Proxy Override (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyOverride" 

• Internet Connection (information)

   C:\Windows\System32\ping.exe google.com

• Drive Mappings (information)

   C:\Windows\System32\net.exe use

• Drive Info (information)

   C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT logicaldisk get size

• Localgroup Administrators (information)

   C:\Windows\System32\net.exe localgroup "Administrators"

• Localgroup Sense Service Users (information)

   C:\Windows\System32\net.exe localgroup "Qlik Sense Service Users"

• Localgroup Performance Monitor Users (information)

   C:\Windows\System32\net.exe localgroup "Performance Monitor users"

• Localgroup Qv Administrators (information)

   C:\Windows\System32\net.exe localgroup "QlikView Administrators"

• Localgroup Qv Api (information)

   C:\Windows\System32\net.exe localgroup "QlikView Management API"

• System Information (information)

   C:\Windows\System32\systeminfo.exe

• Program List (information)

   C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT product get name

• Service List (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "gwmi win32_service | select Started

• Group Policy (information)

  C:\Windows\System32\gpresult.exe /z

• Local Policies - User Rights Assignment (information)

   C:\Windows\System32\secedit.exe /export /areas USER_RIGHTS /cfg

• Local Policies - Security Options (information)

   C:\Windows\System32\secedit.exe /export /areas

• Certificate - Current User(Personal) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\my | Format-list"

• Certificate - Current User(Trusted Root) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\Root | Format-list"

• Certificate - Local Computer(Personal) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\my | Format-list"

• Certificate - Local Computer(Trusted Root) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\Root | Format-list"

• HotFixes (information)

  $FormatEnumerationLimit=-1;$Session = New-Object -ComObject Microsoft.Update.Session;$Searcher = $Session.CreateUpdateSearcher();$historyCount = $Searcher.GetTotalHistoryCount();$Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date, @{name="Operation"; expression={switch($_.operation){1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}}}} | out-string -Width 1024

• UrlAclList (information)

   C:\Windows\System32\netsh.exe http show urlacl

• PortCertList (information)

   C:\Windows\System32\netsh.exe http show sslcert

Manually collecting log files

Any versions of Qlik Sense Enterprise on Windows prior to May 2021, do not include the Log Collector.

If the Qlik Sense Log collector does not work then you can manually gather the logs.

• Default storage (before archiving): C:\ProgramData\Qlik\Sense\Log
• Default archive storage: C:\ProgramData\Qlik\Sense\Repository\Archived Logs
• Manual retrieval of Reload logs: How to find the Script (Reload) logs in Qlik Sense Enterprise

For information on when logs are archived, see How logging works in Qlik Sense Enterprise on Windows.

Older Qlik Sense Versions (3.1 and earlier)

Persistence Mechanism Current Logs(Active Logs) Archived Logs

Note: Depending on how long the system has been running, this folder can be very large so you will want to include only logs from the time frame relevant to your particular issue; preferably a day before the issue began occurring.

Related Content

How logging works in Qlik Sense Enterprise on Windows 

The Sense System Performance Analyzer app has been deprecated.

The Sense System Performance Analyzer (Sense System Performance Analyzer) does not show data. The reload of the app has finished successfully.

Environment

• Qlik Sense Enterprise on Windows May 2021 and later

This is expected. The app pulls platform and process performance data as well as Windows event data from the logging database. However, since the May 21 release centralized logging has been deprecated.  See Deprecation of Centralized Logging in Qlik Sense Enterprise on Windows.

Internal Investigation ID(s) 

HLP-10692 

In order to access your microservice Job remotely, this article briefly introduces How to set up the Microservice Job Deployment for Remote Access.

Please follow the steps below:

1. Open the Project Settings dialog box from File > Edit Project Properties.
2. Open the Default Configuration Setting from Build > Microservices. MicrosoftServicesConfiguration
3. In #server section, please specify server.host as 0.0.0.0. Also, notice that the server.servlet.context-path parameter is set as "/services". This will be included in the path to connect to the server.

   server.host = 0.0.0.0

4. Deploy the Microservice job.
5. Connect to the Microservice job via using the following URL:
   http://<IP address of the engine server you deployed the microservice on>:<port><server.servlet.context-path parameter>/<endpoint specified for the microservice job>
   For example: http://IP.Address.Of.Server:8065/services/test

Related Content

For further information regarding Microservices, please check: Building a Data Service Job as a Microservice.

Environment

Talend Studio 

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

This article documents how to delete the data from your Qlik Alerting database. The attached script is set to retain data history for up to a hundred (100) scans. You can modify the script to keep more. We do not recommend reducing the number to below a hundred as that would negatively impact alert conditions and history.

Always backup your Qlik Alerting database before running the script. See How to take Backup and Restore Qlik Alerting MongoDB Database for details.

To configure and execute the script:

1. Verify that NodeJS is installed on your machine
   
   
2. Save the attached scriptRunner.js script in an easily accessible location, then open it
   
   
3. Change the configuration of the script to include your dbURI and dbName:
   

   'recordsToKeep':100, //enter values to keep in the datahistory table this values indicates number of the alert scan values 
   dbURI: 'mongodb://127.0.0.1:27017', //enter the database URL of qlik alerting database 
   dbName:'qlikalerting' // Update the database name if you have changed the default databse name for Qlik Alerting  
   } 

   
   
   
4. Open a Windows Command prompt with elevated (administrator) permissions
   
   
5. Switch to the location of your scriptRunner.js file and run it using the command:

   node scriptRunner.js

   The command creates a folder named alerting-databse-cleaner, creates app.js, installs the required dependencies (mongodb NodeJS drivers), and then runs the app.js file.
   
   
6. The result should be:
   
   
   
   The first message logs the creation of the directory. We then log the installation of the npm package and list the number of records we want to keep in the database. This is followed by the MongoDB connection message and, lastly, shows if there is data that matches the previously set condition.
   
   If there are fewer records than the recordsToKeep, nothing will be deleted, and the message No data available for deleting with given values is shown.

Not keeping the minimum of a hundred (100) scans for an alert will impact the Previous Scanned Conditions set during Alert Creation. (Fig 3)

Fig 3

Alert History Example

Environment

• Qlik Alerting

If the H2 database has been selected as the database to use for Talend Administration Center, you can change the password from web console by following the steps below:

1. Login to Talend Administration Center Portal
2. Select "Configuration" from the panel on the left side
3. Choose "Database" TACConfiguration
4. Click on the URL of the Web Console to access the H2 Database
5. After providing DB Connection Login and Password by default tisadmin and tisadmin, click on "Connect" and access the H2 Database
6. Write in the following SQL statement to change your password in DB
   

   ALTER USER <Name of User> SET PASSWORD '<Password of your choice>';

   For example:

   ALTER USER tisadmin SET PASSWORD 'password';

7. Go to db config page (default protected page password is admin ) for filling in the New Password in db config page after changing it from H2 web Console.

Embedded for development, test, and demo purposes only. H2 is not supported if you migrate from previous versions. To migrate from a previous version, you need to migrate from H2 to MySQL or other supported databases first in the source version, and then trigger the upgrade of Talend Administration Center to the target version.

Related Content

For more information, please check here:

• H2 Database Administration and Maintenance
• compatible-databases

Environment

Talend Administration Center 

Talend Management Console Task cannot run and is blocked on AWS S3 Transferring Artifact step. It is caused by Expiration of Certification 

java.io.IOException: Error resolving artifact actions.Project_xxx.xxx:AZURE_SYNAPSE_CONNECTION_CHECK:zip:0.1.1.20252702044904: [Could not transfer artifact actions.Project_xx.xx:AZURE_SYNAPSE_CONNECTION_CHECK:zip:0.1.1.20252702044904 from/to xx-7914-4a8e-9000-xxx.release (s3://eu-production-minio-artifacts/repositories/xx-7914-4a8e-xxx-xx/): Unable to execute HTTP request: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]

Resolution

1. Download certificate chains from targeting
   for eu based s3 storage as an example
   

   echo "" | 
      openssl s_client -showcerts -connect s3-eu-west-1.amazonaws.com:443 |
      awk '/BEGIN/ { i++; } /BEGIN/, /END/ { print > "aws-crt-" i ".crt"  }'
   #above command will download several certificates 

2. Import all certificates to JVM used by Remote Engine and Runtime servers
   

   keytool -import -trustcacerts -alias xxxcert-1 -file /tmp/aws-crt-1.cer -keystore  jvm/lib/security/cacerts -storepass changeit
   keytool -import -trustcacerts -alias xxxcert-1 -file /tmp/aws-crt-2cer -keystore  jvm/lib/security/cacerts -storepass changeit
   keytool -import -trustcacerts -alias xxxcert-1 -file /tmp/aws-crt-3.cer -keystore  jvm/lib/security/cacerts -storepass changeit

3. Restart Remote Engine Server to reload s3 certificates 

Cause

Talend Management Console relies on AWS S3 for centralized storage of compiled job designs. To maintain robust cloud security, AWS S3 periodically updates its server certificates. This requires the Java Virtual Machine (JVM) on the Remote Engine side, where Talend Management Console Tasks are executed, to be configured to recognize and adapt to these certificate changes, as expired certificates will cause connection issues.
 

Environment

Talend Cloud 

The Qlik Replicate UI fails to connect to Snowflake. The following error is shown:

SYS-E-HTTPFAIL, Cannot connect to Cloud server.
SYS,GENERAL_EXCEPTION,Cannot connect to Cloud server,RetCode: SQL_ERROR SqlState: HY000 NativeError: 4 Message: [Snowflake][Snowflake] (4) REST request for URL https://usable-abi.privatelink.snowflakecomputing.com:443/session/v1/login-request?requestId=1fdc7df9-5a92-4155-b71e-03e71bfec971&request_guid=40f8178d-0e61-4a36-a027-77034998b1b9&databaseName=DEV_RAW_CORE_DB failed: CURLerror (curl_easy_perform() failed) - code=56 msg='Failure when receiving data from the peer'.

Using the Qlik Replicate server curl command is successful:

curl -v https://usable-abi.privatelink.snowflakecomputing.com:443
* Rebuilt URL to: https://usable-abi.privatelink.snowflakecomputing.com:443/
* Trying 10.200.2.4...
* TCP_NODELAY set
* Connected to usable-abi.privatelink.snowflakecomputing.com (10.200.2.4) port 443 (#0)

Connecting with iSQL command from the Qlik Replicate server is also successful (How to create Snowflake ODBC DSN On Linux CentOS ? and Installing and Configuring the ODBC Driver for Linux) while using the root account. Connecting using a service account, the same error is observed. 

Resolution

Run command source ./arep_login.sh from the Qlik Replicate bin directory and issue was resolved.

Environment

Qlik Replicate 

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor and License Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

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 SQL Server endpoint is not retrieving databases on Qlik Enterprise Manager. The Browse option on the endpoint opens with the message:

No Databases were retrieved

Resolution

Reset the connection between Qlik Replicate and Qlik Enterprise Manager.

1. In the Qlik Enterprise Manager, click Stop Monitoring for your Qlik Replicate server.
   
   
   
   
2. Resume monitoring by clicking Start Monitoring. 
   
   
   
   

Cause

The Qlik Enterprise Manager API calls to the Qlik Replicate server did not properly retrieve endpoint information. The connection between Qlik Enterprise Manager and Qlik Replicate needs to be reset.

Environment

• Qlik Enterprise Manager
• Qlik Replicate

In transactional data marts, it is possible to use inner joins for dimensions instead of subqueries, improving query efficiency and performance.

Environment

• Qlik Compose 2023.11 SP04 or higher 

To enable inner joins for dimensions, two Windows environment variables must be set to true:

1. Open the Windows Control Panel, System and Security, and System
2. Switch to the Advanced tab
3. Open Environment Veriables...
4. Change the following variables to true:
   
   • qlk_PersistDenormForFctT
   • qlk_PersistPreselForFctT
5. Confirm the changes
   
   
   
   
6. Restart the Qlik Compose services. Changes will not take effect until the services have been restarted.

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

Content

• Rationale
• Understanding interactive IdPs in Qlik Cloud
• Why Qlik Cloud only supports one interactive IdP
• Why Federate Identity In-House?
• Solution: Federate IdPs with an enterprise-grade IdP
• How to Implement a Federated IdP
• Conclusion

Qlik Cloud is designed to support a single interactive Identity Provider (IdP) per tenant.

This approach enhances security, governance, and operational control while simplifying authentication management. Organizations that require multiple identity sources can achieve this by using a federated IdP (such as Azure Entra, Auth0, Keycloak, or Okta) to consolidate authentication and seamlessly connect it to Qlik Cloud

Rationale

Understanding interactive IdPs in Qlik Cloud

Qlik Cloud allows organizations to configure an interactive IdP to manage user authentication. Options include:

• Qlik Account (default for new, non-government tenants).
• A standards-compliant OIDC or SAML provider, such as Azure Entra, Okta, Auth0, or Keycloak.

Any unauthenticated user attempting to access the tenant is redirected to the configured interactive IdP for authentication, ensuring a streamlined and secure login experience.

Why Qlik Cloud only supports one interactive IdP

Using a single interactive IdP is a best practice for identity management and ensures consistency, security, and simplified administration.

Key reasons include:

• User Identity Consistency: Qlik Cloud relies on a user's subject and email as unique identifiers. Managing a single interactive IdP helps prevent duplicate identities and ensures seamless user access, reducing risk of users gaining unauthorized access to sensitive data or permissions.

• Streamlined Identity & Access Management: Since Qlik Cloud does not transform incoming claims beyond remapping keys, keeping authentication centralized prevents unintended variances in usernames, email formats, or group names. This improves security and reduces maintenance of licenses and entitlements.

• Optimized Group Management: A single interactive IdP provides a consistent structure for groups, ensuring they align with an organization’s access policies. By managing group filtering in one place, organizations can maintain clear and structured permissions. Managing groups across multiple IdPs can quickly become unmanageable, leading to inconsistencies in user access.

• Simplified Access Control: Groups in Qlik Cloud are referenced by name, making it more efficient to manage access through a single federated IdP rather than multiple sources.

• Efficient Token Management: A unified IdP helps maintain consistency in authentication tokens, reducing administrative overhead and ensuring a smooth user experience.

• Enhanced Security & Auditability: By centralizing authentication through a single IdP, organizations can apply security controls, enforce device policies, and monitor user access through audit logs.

A federated IdP ensures that organizations retain full control over authentication policies, while providing a seamless experience for users accessing Qlik Cloud.

Why Federate Identity In-House?

Many organizations choose to use a federated identity provider to streamline identity management, enhance security, and improve user experience across multiple applications. Benefits include:

• Centralized User Lifecycle Management: Users from different sources can be managed in a single system, reducing duplication and inconsistencies.

• Improved Security Policies: Organizations can enforce multi-factor authentication (MFA), conditional access policies, and device trust settings at the IdP level.

• Single Sign-On (SSO) Across Applications: Users authenticate once and gain seamless access to multiple platforms, including Qlik Cloud.

• Comprehensive Logging & Compliance: A federated IdP provides consolidated audit trails and governance controls for user authentication.

By implementing a federated identity provider, organizations can maintain flexibility in their authentication strategy while ensuring compatibility with Qlik Cloud.

Solution: Federate IdPs with an enterprise-grade IdP

The recommended approach for organizations that need to authenticate users across multiple identity sources is to configure a federated IdP that consolidates authentication. Solutions like Azure Entra ID or Okta can be used to unify identity management and connect to Qlik Cloud via OIDC or SAML.

How to Implement a Federated IdP

1. Set Up a Federated IdP (Azure Entra ID, Okta, or another identity management solution).

2. Sync Identity Sources within the federated IdP to ensure unique identities across different user groups.

3. Configure OIDC/SAML Authentication in Qlik Cloud with the federated IdP.

This approach ensures a secure, efficient, and scalable authentication strategy that aligns with best practices for enterprise identity management.

Conclusion

Qlik Cloud is designed to integrate seamlessly with a single interactive IdP, providing a robust and secure authentication framework. Organizations that need to consolidate multiple identity sources can achieve this through a federated IdP, ensuring centralized management, improved security, and a streamlined user experience. By leveraging enterprise-grade IdPs like Azure Entra ID or Okta, organizations can enhance their identity management strategy while maintaining full control over authentication policies and governance.

Environment

• Qlik Cloud