After deploying and subsequently undeploying a route, even when the route is undeployed, it causes issues for the deployment of subsequent routes. Attempts to deploy a different route are met with errors stating that unable to find the path of the existing undeployed route.

Resolution

The undeployed route left traces, ideally requiring the individual uninstallation of the KAR file(s).

1. Stop Talend Runtime. 
2. Stop Remote Engine.
3. Start Talend Runtime and allow it approximately five minutes to ensure it is fully prepared to receive JMX requests from Remote Engine.
4. In Talend Runtime, perform a 'kar:list' command and verify that no entries are displayed. For each specified output, you must execute the 'kar:uninstall' command.
5. Start Remote Engine.

Environment

• Talend Cloud 8.0.1

For general installation instructions and backwards compatibility information, see SAP Connector installation.

Qlik SAP Connector versions 8.0.1 or earlier include the SAP libraries.

Qlik SAP Connector versions 8.0.2 and later do not include the SAP libraries. You can download the SAP libraries from the SAP support download portal in accordance with SAP regulations after the upgrade of the Connector was performed. The Connector can be upgraded without issues first.

Index:

• Qlik SAP Extractor Connector
• Not using Qlik SAP Extractor Connector:
• Downloading and installing the SAP Libraries for connector 8.0.2 or later:

Qlik SAP Extractor Connector

Step 1:

For the SAP Extractor connector, follow the below steps before upgrading:

1. Open Services.MSC, find Qlik SAP Network Service, and then click "Stop."
2. Open cmd as an administrator and change the directory to C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector 
3. Run the SrvService Console.bat file.
4. Choose the option to uninstall the Qlik SAP Network Service. 

Step 2:

Once the service has been uninstalled, please proceed as follows:

1. Uninstall the SAP connector.
2. Install the new version SAP connector.

Step 3:

After installing the updated version of the Sap connector, follow the steps below to install the Qlik SAP extractor connector service "Qlik SAP Network Service."

1. Open cmd as an administrator and change the directory to C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector 
2. Run the SrvService_Console.bat file.
3. Choose option 2 to install the Qlik SAP Network Service. 
4. Open Services.MSC, find Qlik SAP Network Service, and then click "Start."

Note: Restart all the Qlik Sense Services if the installation is on a Qlik Sense system. The SAP Connector is not available in Qlik Sense until all the services are restarted.

Not using Qlik SAP Extractor Connector:

Examples: SQL, Bex, Info provider, Report, BW etc.

Once the service has been uninstalled, please proceed as follows:

1. Uninstall the SAP connector.
2. Install the new version SAP connector.

Downloading and installing the SAP Libraries for connector 8.0.2 or later:

The "SAP Connector for Microsoft.NET" and "SAP NW RFC SDK" versions will change for each connector upgrade based on SAP security patch releases, refer to the help page for additional information. Installing the connectors - Windows

1. Log into the SAP Support Portal with an S-user ID.
   
   
2. Go to SAP Connector for Microsoft .NET and search for: SAP Connector for Microsoft .NET, 64-bit, version 3.1 or later. This library is used by the Connectors with file extension .exe and contains sapnco.dll and sapnco_utils.dll.

3. Download these library files. Double-click the SapNCox64Setup.exe file. The installation wizard starts, and the files are installed in Global Assembly Cache (GAC).

4. Go back to the SAP Support Portal and search for: SAP NW RFC SDK, 64-bit, version 7.50 or later. This library is used by the legacy connectors with file extension .dll.

5. Download and unzip the library. The library contains all required files.
   • icudt50.dll
   • icuin50.dll
   • icuuc50.dll
   • libsapucum.dll
   • sapnwrfc.dll
     
     
6. Place the files in this folder: C:\Program Files\Common Files\QlikTech\externals

Microsoft ended support for Microsoft XML Parser and Microsoft XML Core Services (MSXML) 4.0 on April 12, 2014 and provides no further support.

Does uninstalling or disabling XML or MSXML cause any risks to QlikView, Qlik Sense, or Qlik NPrinting? 

No risk is posed to QlikView, Qlik Sense, or Qlik NPrinting if  Microsoft XML Parser and Microsoft XML Core Services are disabled.

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.

Environment

Qlik Sense Enterprise on Windows 
QlikView 
Qlik NPrinting 

• Timeline
• Standard run vs third-party run
• Standard runs
• Third-party runs
• Possible third-party runs
• Transition of existing entitlements
• Starting Jan 30th (introduction of third-party runs, current packaging still applies)
• Starting April 2nd (switch to new packaging)
• Packaging details
• FAQ

 

Timeline

The below timeline illustrates how the various stages of this packaging update will happen. In-between each stage should be sufficient time to analyze your usage and prepare for the enforcement.

• January 30th – Introduction of third-party runs
• April 2nd – New third-party packaging is available for purchase 
• May 1st – Enforcement
  • Third-party limits for seat-based licenses
  • Third-party overages for capacity licenses

Standard run vs third-party run

Standard runs

An automation run is considered a standard run if it only executes blocks from the following categories:

• All Qlik connectors (Qlik Cloud Services, Qlik Reporting, Qlik AutoML, Qlik …)
• Base blocks (excluding Call URL & Cloud Storage)
• Mail & Microsoft Outlook

Example:

 

Third-party runs

An automation run is considered a third-party run if it executes any blocks that are not in the standard connector categories.

As a rule of thumb, a standard run will execute one or more blocks from third-party connectors. Among others, third-party connectors are connectors like Slack, Amazon S3, Microsoft Excel, Call URL. A full overview of all automation connectors if available here.

Example:

Every run of this automation will execute the Send Message (Slack) block.
This will make every run a third-party run as the Slack connector is a third-party connector.
The “Contains third-party blocks” label indicates that the automation contains an active third-party block.

Possible third-party runs

For a run to be considered a third-party run, we only evaluate executed blocks. If the third-party blocks in the automation were not executed, the run will not count as a third-party run. A block not being executed could be caused by many factors like Condition blocks, Filter List blocks, deactivated third-party blocks, ...

This illustrates that an automation with a “Contains third-party blocks” label will not necessarily generate third-party runs on every run.

Example:

This automation will only execute the Send Message (Slack) block if the reload fails (from the Do Reload block). This means it will only generate third-party runs depending on the state of the Condition block.

Transition of existing entitlements

Starting Jan 30th (introduction of third-party runs, current packaging still applies)

1. Customers who are entitled to included runs will get these as third-party runs
2. Purchased runs will be converted to third-party runs
3. Renewals before the end of March will maintain the same included third-party runs until next renewal.

Starting April 2nd (switch to new packaging)

1. Every new purchase will be using the new packaging
2. Renewals will revert third-party runs to the edition included quantity of the new packaging + any purchase of third-party runs using the new packaging

Packaging details 

The below table provides an overview of the new packaging for automations that will come in effect on April 2, 2025. Please reach out to your account manager for quotes and pricing related questions. 

 

FAQ

1. Will max concurrency be shared across run types?
Yes, both run types will count towards the same max concurrency.

2. Will usage of Qlik APIs through the Call URL block or other generic connectors count towards third-party runs?
Yes, when these blocks and connectors are used to make API requests to Qlik APIs, they will still count towards third-party runs. If you are missing blocks or functionality in a Qlik connector, please create an improvement request on our Ideation portal or support an existing request.

3. Will the new packaging have an included amount of third-party runs?
Yes, the new packaging will continue to provide some third-party runs for most editions of Qlik Cloud. Details are available in the above section "Packaging details".

4. Why are some automations with third-party blocks missing the label "Contains third-party blocks"?
An automation will only receive the label when someone performs a manual run or saves it in the editor. We are planning a new update that will apply this label to all automations with active third-party blocks regardless of someone saving them or not.
Please note that regardless of this label being on an automation or not, automation runs will still be evaluated and receive a correct billable yes/no label.

With a filter and a data quality cleansing rule defined on the same column, the data warehouse task fails with the following error:

[ERROR ] [] sqlstate '42000', errorcode '1003', message 'SQL compilation error:

syntax error line 404 at position 24 unexpected 'WHEN'.' java.sql.SQLException: sqlstate '42000', errorcode '1003', message 'SQL compilation error:

syntax error line 404 at position 24 unexpected 'WHEN'.'

Resolution

This issue was caused by defect RECOB-6917. 

Fix Version: 

• Qlik Compose 2023.11 SP10 and later releases

Contact Support to obtain the relevant fixes.

Cause

RECOB-6917

Environment

• Qlik Compose

Connecting to data using a web file connection may fail with the following error if the connection is routed to an internet proxy.

Environment

• Qlik Sense Enterprise, any version

Resolution

The additional configuration will be required in the Settings.ini file.

1. Stop the Qlik Sense Engine and Dispatcher Services.
2. Add the following key values under [Settings 7]. Refer to How to modify Qlik Sense Engine's Settings.ini  
3. Sart the Qlik Sense Engine and Dispatcher Services.

[Settings 7]
UseProxyServerForWebFileConnectors=1
WebFileConnectorProxyServer=xxxx.xxxx.com (Replace this with your actual proxy URL)
WebFileConnectorProxyPort=8080(Replace with your proxy's port number)

Related Content 

Can not connect to web file using Web file Connector if the Qlik Sense Enterprise uses Proxy to connect to internet  

The video above demonstrates how to convert Qlik Sense Enterprise servers with Tokens to the Professional and Analyzer capacity licensing model.

The conversion breaks down like this:

• User Access Passes -> Professional
• Everyone else into Analyzer Capacity

Steps

1. Copy and Save existing User Access rules, storing for future reference.
2. Do the same for Login Access rules
3. Paste the Signed License Key (SLK) in the signed license box, and hit Apply
4. Recreate the Professional Access rules from scratch or copy and paste from the User Access Rule.
5. Validate the rule and click Apply
6. Recreate the Analyzer Capacity access rule from scratch or copy the Login Access rule
7. Validate the rule and click Apply

Environment

• Qlik Sense Enterpise

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.

Related Content 

Please refer to the Qlik Sense® License Conversion Policy dated March 2021 for details.

Transcript

Hello and welcome to this short video guide on upgrading a Qlik Sense token server to a Qlik Sense Professional and Analyzer subscription license.

Our starting point for this upgrade guide is a very simple Qlik Sense Enterprise server, which is using the token style license. That means users gain access using either a User Access or a Login Access pass. Token style Qlik Sense uses the legacy LEF license with a serial and control number activation. This will be replaced in the Professional and Analyzer model license with a Signed License Key (SLK).

Make sure that you copy or save the existing user access rules storing the rules for future reference. We will do the same for the login access rules. Copy and save the rule conditions for future reference.

When you're issued with your new Qlik Sense Enterprise Professional and Analyzer subscription license, you will be issued a new license key or a new tenant. You may continue to use the old Qlik Sense Enterprise token license for up to four months. This will allow you to stand up a new Qlik Sense Enterprise site with Professional Analyzer users in parallel, and transition over time; or do it in one big go.

In this example, we are going to upgrade an existing Qlik Sense token server using the Signed License Key to move it to the Professional and Analyzer user model. Paste the Signed License Key in the signed license box and hit apply. When the license is successfully applied, you will see the license number as well as a license summary on the summary page. In this example, we have 4 Professional Users, as well as 8,000 minutes of Analyzer Capacity per month. There are no user allocations carried over from the old token model.

We need to recreate the Professional access rules. You can create rules from scratch or copy and paste the old token rules to a new Professional allocation rule, like so. Make sure you validate the rule and then hit apply.

We will do the same thing for the Analyze Capacity access rule. Copy the old token access rule for login access and paste it in the analyze capacity access rule. Validate the rule and hit apply. A quick test will validate that the Professional user access rules are functioning correctly. And here we can see that a Professional user was successfully allocated according to the rule we've set up.

Now we will check that the Analyzer capacity allocation rule is also working as expected. Click on the license usage summary tab; and here you can see that 6 minutes of analyzing capacity have been consumed. Everything is working as expected.

Thank you for watching. We hope you found this video useful.

If you would like more information, take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in the Qlik product forums on Qlik community; or check out the support program space. Here you can search for answers in the support knowledge base, learn directly from Qlik experts via support webinar like Techspert Thursdays, and don't forget to subscribe to the support update blog. Thanks for watching.

You may experience intermittent issues when accessing the Talend Administration Center (TAC), along with the following warning message if you are using MySQL as the database

Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

And this issue is random and sometimes can be temporarily resolved by refreshing the Talend Administration Center page.

(ConnectionImpl.java:456) at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:246) at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:199) at java.sql.DriverManager.getConnection(DriverManager.java:664) at java.sql.DriverManager.getConnection(DriverManager.java:247)

Resolution

1. Please download the latest MySQL driver Connector/J from this official page: https://dev.mysql.com/downloads/connector/j/
2. Load the latest MySQL driver to the Talend Administration Center lib folder
   <TomcatPath>/webapps/org.talend.administrator/WEB-INF/lib 
3. Restart Talend Administraion Center application after adding the driver 

MySQL JDBC drivers are backward compatible.

Cause

As per MySQL documentation, the driver class name has been updated from com.mysql.jdbc.Driver (deprecated) to com.mysql.cj.jdbc.Driver and using the deprecated driver may cause compatibility or communication issues.

For more information, please refer to MySql official document:

https://dev.mysql.com/doc/connector-j/en/connector-j-api-changes.html

Related Content 

installing-external-modules-manually-for-tac

Environment

Talend Administration Center 

The following error is thrown when running an ETL task on a specific table in Qlik Compose:

ETL task aborted - Unexpected Primary Key violations detected in 'Table Name'.

Resolution

Enable Handle Duplicates on the problematic table.

Cause

Troubleshooting steps taken:

1. We identified that PK violation errors occurred on the staging table (TSTG). Compose checks for duplicate records in the staging table and raise this error when duplicates are found.
2. In the DWH ETL process, Qlik Compose loads data from landing tables (both full load and CDC) into staging tables before transferring it to DWH tables. As part of this process, Qlik Compose also checks for duplicates in the staging table.
3. After reviewing the table mappings, we observed that lookups are defined for certain columns in the problematic table. Additionally, based on the task statements, the staging table population logic includes a join between the landing table and lookup tables to retrieve data for the lookup columns.

If the lookup tables contain duplicate records, the query will insert those duplicates into the staging table, leading to the PK violation errors.

Environment

• Qlik Compose

When opening the Table Selection option in the Designer tab or clicking the Test Connection button for an endpoint, the following error may appear:

Error: SYS-E-HTTPFAIL, SYS-E-UNRECREQPARM, Unrecognized request parameter 'action'.. SYS,GENERAL_EXCEPTION,SYS-E-UNRECREQPARM, Unrecognized request parameter 'action'.,SYS,UNRECOGNIZED_REQUEST_PARAMETER,action

Resolution

Restart the Qlik Enterprise Manager service.

Cause

Qlik Enterprise Manager API calls are not processing parameters correctly.

Environment

• Qlik Replicate

When the Use direct path full load option is in use for an Oracle as a target endpoint, some integrity constraints are automatically disabled and will be recreated after the Full Load, such as Indexes.

Failure to create the Indexes will result in the following error message in your task log once CDC replication starts and the task attempts to use the index:

[TARGET_APPLY    ]E:  ORA-01502: index 'Schema.Table' or partition of such index is in unusable state  [1020436]  (oracle_endpoint_bulk.c:893)

Resolution

Identify the root cause of the Index creation failure with your Oracle DBA. This particular scenario failed to create the Index as the Oracle DB did not have enough temp table space to create the Index on the large tables.

The issue was resolved by increasing the temp table space used for the Index creation to unlimited.

Cause

The Oracle target Database did not have enough temp table space to complete the Index creation for the table.

Internal Investigation ID(s)

SUPPORT-693

Environment

• Qlik Replicate

• header_change_oper is a Qlik header from Qlik change tables to log the operation of the CDC event. (Delete, Update, Insert)
• Operation_indicator function is a transformation that can be applied as a new column to act as a soft delete function. Soft deletes will prevent a delete operation from deleting the record. Instead of deleting the record, the record is updated with the desired value of your choosing in the new column added.
• operation_indicator (value_on_delete, value_on_update, value_on_insert)
  When the operation_indicator function is in use, deletes will no longer apply, meaning the header_change_oper values will also reflect the change. All Delete operations will be reflected as an Update operation. This behavior is by design.

Resolution

To achieve the default behavior where a delete gets a 'D' value for header_change_operation,  remove the Operation_indicator function from your transformation.

See the headers and functions documentation for details:

• Qlik Headers Documentation 
• Qlik Functions Documentation 

Environment

• Qlik Replicate

Replicating data from Oracle, where the data type is `RAW` (such as  C6B578B216B05B2555541FBD6BF1B216B046B00B25), casting the `RAW` data to a `STRING` results in the value being stored with a `0x` prefix (such as: 0xC6B578B216B05B2555541FBD6BF1B216B046B00B25).

Transformations to remove the `0x` prefix specifically will not work. The Hex function should be applied to the column to remove the `0x` prefix.

Resolution

The '0x' prefix is added by the AWS S3 reader. To resolve this, modify the transformation process in Qlik Replicate by applying the hex function when converting to a string. On the column's expression builder, add hex($Column_Name) where Column_Name is the name of your Raw datatype column.

Cause

AWS S3 reader converts the Raw datatypes with additional prefixes due to how the Binary data is processed.

Internal Investigation ID(s)

RECOB-9409

Environment

• Qlik Replicate

In Qlik Sense, bookmarks can be created with the "Include Layout State" option to capture both current selections and the layout of visual objects, such as the expanded or collapsed state of pivot tables. However, users may notice that after reloading the document and reapplying the bookmark, the pivot table does not return to the expected expanded/collapsed layout.

Resolution

To ensure that the pivot table layout is retained when using bookmarks:

• Avoid changing the structure of the pivot table after creating the bookmark.
• Ensure that dimension value order remains consistent in the data source to prevent layout mismatch.
• If changes to dimension order or pivot structure are necessary, consider creating new bookmarks to reflect the updated layout.

Cause

This behavior is due to how Qlik Sense manages the expand/collapse structure in pivot tables. Specifically:

• Qlik Sense relies on the data load order of dimension values to track and restore the expand/collapse state.
• If the order of values in a dimension changes in the source data, the original layout state stored in the bookmark becomes invalid.
• When the pivot table structure changes (e.g., dimensions are reordered, added, or removed), Qlik Sense considers it a new layout, and the previously saved layout state can no longer be applied.

Impact of Changing Dimensions in a Pivot Table

If you change the pivot table structure after creating a bookmark (such as removing or reordering dimensions):

• Qlik Sense treats this as a different visual object layout.
• The bookmark will still apply filter selections but not the layout state.
• The expand/collapse configuration of the pivot will not be restored.

Environment

• Qlik Sense Enterprise on Windows all versions
• Qlik Cloud Analytics

You may encounter error that pax web server could not started from talend runtime side with the following error in log

2025-04-10T16:32:33,598 | ERROR | paxweb-config-1-thread-1 (change controller) | x.web.service.internal.Activator 623 | 227 - org.ops4j.pax.web.pax-web-runtime - 9.99.0 | Unable to start Pax Web server: Cannot recover key java.security.UnrecoverableKeyException: Cannot recover key at sun.security.provider.KeyProtector.recover(KeyProtector.java:304) ~[?:?]

Resolution

Please adapt the following variables (password) to  runtime/etc/custom.properties accordingly

TESB_TLS_KEYSTORE_PASSWORD=password
TESB_TLS_KEY_PASSWORD=password

Cause

Based on

keytool -v -list -keystore xxx

checking, the TESB_TLS_KEYSTORE_PASSWORD and TESB_TLS_KEY_PASSWORD are not setting correctly in  custom.properties file which caused the issue : java.security.UnrecoverableKeyException: Cannot recover key

org.ops4j.pax.web.cfg
org.ops4j.pax.web.ssl.password=${env:TESB_TLS_KEYSTORE_PASSWORD:-${TESB_TLS_KEYSTORE_PASSWORD}}
org.ops4j.pax.web.ssl.keypassword=${env:TESB_TLS_KEY_PASSWORD:-${TESB_TLS_KEY_PASSWORD}}

Related Content 

If you are looking for how you can configure your Talend ESB Container to be able to encrypt and decrypt your security properties, please refer to beblow documentation from Help site

enabling-password-encryption

Environment

Talend ESB 

When publishing a DI Job to TMC, if the artifact has been migrated and was previously an OSGI bundle, TMC may display the artifact in question as a "Data Service". However, when viewing the Job in question, there may be no “Job Type” selection in the “Job/Deployment” tab; and all commands were left in DI mode, if using CICD.

[INFO] RelativePath: process
[INFO] StartingDir: /var/lib/jenkins/workspace/<Repo Name>/<project name>/process
[INFO] DefaultContext: QA
[INFO] JobType: data_service
[INFO] Git author: , Id: , Date: null, Project: BBW_OSGI, Branch: null
[INFO] Artifact id: <artifact name>
[INFO] Artifact groupId:
[INFO] The latest published version is: null
[INFO] Publish version: 0.1.0
[INFO] Environment: rpooyadev-env1; workspace: testing-tasks; owner: rpooya
[INFO] Publishing process: /var/lib/jenkins/workspace/<Repo Name>/<project name>/poms/jobs/process/<iten name>/target/<artifact name>.zip
[INFO] UpdateFlow: false

Cause

This has been confirmed to be due to a change that automatically detects the "Build Type" (when an ESB component, such as RESTClient, is present) rather than requiring it to be selected for a DI Standalone Job.

Regarding the items in question, they may have been saved or exported during a time when an ESB component was included, which would explain the presence of the line "<additionalProperties xmi:id="_AVcasO-mEe-T64JJ_U4MkQ" key="BUILD_TYPE" value="OSGI"/>" in the ".properties" file.

Resolution

Internal Investigation ID(s)

Support-2172

Environment

• Talend Data Integration 8.0.1

When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

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 default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:

1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)

   [globals]
   LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
   (...)
   MaxHttpHeaderSize=16384

2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.

Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows 

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 

Document thumbnails on the QlikView AccessPoint are either missing/blank or showing No Preview Available.

The thumbnails on the QlikView AccessPoint are not refreshing after being updated. 

Environment:

• QlikView Server, all versions

This issue can have multiple root causes. 

Saved in WebView mode

The QlikView document may have been saved in WebView mode. In this case, the .qvw will not display a thumbnail on the AccessPoint and always show No Preview Available. 

To solve: Ensure "Web View" is not active in the document and resave it. 

To turn off WebView go to View in the toolbar and toggle Turn on/off WebView

The wrong sheet is selected for thumbnail creation

Verify that the correct sheet is used for creating the thumbnail.

To solve: Open the document and verify the setting.

To do so, go to:

• Settings
• Document Properties
• Opening tab
• Ensure Document Thumbnail is set to "Opening Sheet"

QlikView Server cached the wrong data

QlikView may have the wrong data for the thumbnail cached. 

To solve: Restart the QlikView Server service. This will clear the cached data or configure how frequently the thumbnail cache is being updated. 

PLEASE NOTE: The refresh interval only applies to a situation where the Thumbnail should be updated following a reload in the desktop client in graphical mode. Reloads done via the QlikView Distribution Service or via batch will not update the thumbnail. This is a known limitation.

To change the setting:

1. Stop the QlikView Server Service
2. Edit the settin.ini file located in “C:\ProgramData\QlikTech\QlikViewServer” 
3. Add “QvThumbnailCacheUpdateInterval=X” inside the [Settings 7] section of the file, where X equals the custom number in minutes

Example:

[Settings 7]
   QvThumbnailCacheUpdateInterval=2

   NOTE: The setting.ini must have an empty line at the end, in order for settings to apply.

4. Save the file and start the QlikView Server Service
5. Restart the QlikView WebServer service, or if using IIS, perform an IISRESET from a CMD prompt

Manually force a refresh of the Thumbnail

If the above fail, try toggling the setting under QlikView Desktop > Settings > Document Properties > Opening > Document Thumbnail, to "None". Then reload the app, and change the setting back to "Opening sheet", and reload the app. 

Cause:

This situation may occur if there were changes to the thumbnail configuration in specific documents prior to being published. Configuration is under QlikView Desktop > Settings > Document Properties > Opening > Document Thumbnail.
QlikView Server may still be in the process of caching some thumbnails information or has not yet reached the thumbnails caching system routine which may have been interrupted by external factors.

You may encounter the following issue while trying to push code to the Bitbucket repositories from Talend Studio Application

Error: Command org.eclipse.jgit.api.PushCommand was called in the wrong state

Caused by: org.eclipse.jgit.errors.TransportException: ********.git: push not permitted
 

Resolution

As Write access is required to push code to the repository, please kindly check with the Bitbucket admin to obtain write access for the repository/project and attempt to push again.

Cause

This error typically occurs when there is no proper write access for the repository/project. For example, you may have read-only access to the repository on Bitbucket.

Environment

Talend Studio