Cause

Due to security considerations, the proxy setting has not yet been adapted to the CICD server.

Resolution

To resolve this issue, two options can be adopted: adding proxy settings at the Operating System or Maven level, as follows.

Operating System level:

vi /etc/profile

export http_proxy=http://USERNAME:PASSOWRD@proxy-server.mycorp.com:3128/
export https_proxy=http://USERNAME:PASSOWRD@proxy-server.mycorp.com:3128/
export no_proxy=localhost,127.0.0.1,*.xxx.com

Maven level:
vi  maven-setting.xml

<settings>
....


	<proxies>
		<proxy>
			<id>example-proxy</id>
			<active>true</active>
			<protocol>http</protocol>
			<host>proxy.example.com</host>
			<port>8080</port>
			<username>proxyuser</username>
			<password>somepassword</password>
			<nonProxyHosts>localhost|127.0.01|*.example.com</nonProxyHosts>
		</proxy>
	</proxies>

....


</settings>

Related Content

Qlik Talend CICD build fails with an error: Could not resolve dependencies for project

Environment

• Talend Data Integration 

A Talend ESB Data Service job with tSalesforceConnection component fails with following error in Runtime server while it works in Studio

java.lang.RuntimeException:java.lang.NoClassDefFoundError: org/apache/avro/AvroTypeException

Resolution

Please upgrade Talend Runtime to R2025-02 or manually install avro dependency by Karaf console as a workaround

karaf@trun()>bundle:install -s mvn:org.apache.avro/avro/1.11.4

Cause

The avro will not be contained in the built jar file hence it should be enabled on Talend Runtime Server side (it is not automatically enabled).

Environment

Talend ESB 

When trying to use Qlik Data Transfer for the first time after a correct installation, you might have the below white screen:

Having a white screen basically means one of the Qlik DataTransfer micro service is not started and/or not working. This can be checked in the Windows Event Application (Source: Qlik Sense Service Dispatcher) or in the Qlik DataTransfer logs (C:\ProgramData\Qlik\DataTransfer\Log).

In the \DataUploadService logs you will see this error message:

localhost 6.0.0 Global INFO Responding certificates after reading it from defined location.
localhost 6.0.0 Global ERROR Unable to unlock the ReloadService, cannot continue.
localhost 6.0.0 Global ERROR Exception: Error: Unable to unlock the reload service.

Resolution

This error message is happening directly after the step of reading certificate:

INFO Responding certificates after reading it from defined location.

Verify the certificate:

Verify what certificates you have listed in the MMC console.

1. Are no certificates listed?
   
   
   
   

2. A group policy or other system security settings may have prevented certificates from being installed. Follow the Reset certificates steps found in the second half of the article after lifting potential restrictions on the account or machine which previously prevented the certificates from being installed. 

3. If you see some Qlik DataTransfer duplicate certificates (fig 1), duplicates must be deleted.
   
   fig 1
   
   
4. Delete the two duplicates (which have no Friendly Name listed. 
5. Restart the Qlik DataTransfer service.

Are other Qlik Products installed on the same server?

Installing Qlik Sense Enterprise on Windows (Desktop or otherwise) will also lead to compatibility issues, including certificate mismatches.

1. If the other product was previously uninstalled, the certificate may still be present.
2. Verify in the MMC console and navigate to Certificates (Local Computer) --> Personal -- Certificates to see if another QlikClient certificate is installed.
3. Remove it.
4. Then follow the Reset Certificates steps found below.

Are you using a Proxy?

A proxy system variable may be set in Windows. Example: https_proxy=http://PROXY:80 

Qlik Data Transfer does not support the use of a proxy. Delete the Windows variable.

Reset Certificates 

If only Qlik DataTransfer is installed on the machine, do the following:

1. In Windows Services, stop the Qlik DataTransfer service.

2. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and delete the certificates there.
   
   

3. Navigate to C:\Program Files\Qlik\DataTransfer\DataUploadService\install-utils.

4. Run Remove-Certificate.ps1 in PowerShell.

5. Delete the following folder: C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate
   

6. Start the Qlik DataTransfer service.

7. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:

   • client.pfx

   • server.pfx

If Qlik DataTransfer and Qlik Sense Enterprise on Windows are installed on the machine, do the following:

1. In Windows, Services, stop the Qlik DataTransfer service.

2. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and delete the certificates in the folder.
   
   

3. In the Windows Certificate Store, delete the following certificates:

   • Local Computer > Personal > QdtClient

   • Local Computer > Trusted Root Certification Authority > <hostname.domain> or <hostname>

   • Current user > Personal > QdtClient

   Alternatively, you can run Remove-Certificate.ps1 in PowerShell as the administrator.
   
   

4. Run Configure-Service.ps1 in PowerShell as the Qlik Sense services user.

   1. For the first input dataTransferCertificatePath, enter C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate.

   2. For the second input qsefwPresent, enter Yes.

5. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:

   • root.pfx

   • client.pfx

   • server.pfx

6. Restart the Qlik DataTransfer service.

Related Content 

Installing and Using Qlik DataTransfer  
Troubleshooting Qlik DataTransfer 

Environment

Qlik Data Transfer any release

After upgrading the Remote Engine from version 2.12.0 to 2.12.14 and restarting it, some jobs cannot be deployed, resulting in the error "java.io.IOException: Failed to deploy job xxxx".

Detailed error messages can be found in the log:

the 8.0.1.20221125_1614_patch | | java.net.SocketException: Broken pipe (Write failed)
org.talend.remote.commons.exception.ClientServerException: java.net.SocketException: Broken pipe (Write failed)
at org.talend.remote.jobserver.client.FileSenderClient.sendData(FileSenderClient.java:307) ~[bundleFile:?]
2025-01-13T02:31:49,390 | ERROR | MultiSocketServer_FileServer_ConnectionPool_pool-37-thread-3 | MultiSocketServer | 307 - org.talend.remote.server - 8.0.1.20221125_1614_patch | | org.talend.remote.jobserver.commons.utils.io.JobLimitException: Current upload of job archive will exceed the allowed size of archive directory of: '107374182400' (configured in org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ARCHIVES_DIR_SIZE)
org.talend.remote.commons.exception.ClientServerException: org.talend.remote.jobserver.commons.utils.io.JobLimitException: Current upload of job archive will exceed the allowed size of archive directory of: '107374182400' (configured in org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAX_ARCHIVES_DIR_SIZE)

Cause

Based on the detailed log checking, the failed broken pipe exception is due to the limitation of org.talend.remote.jobserver.commons.config.JobServerConfiguration.MAXARCHIVESDIR_SIZE being reached. This issue can be resolved by increasing the default size from 100G. 

Additionally, from a management perspective, you can uncomment the following settings in <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.deployment.agent.cfg file to reduce the overall size of the artifacts in the <RemoteEngineInstallationDirectory>/data/m2/ folder.

# karaf maven data cleaner configurations, use 0 days interval to disable cleaner
local.maven.clean.interval.days=2
local.maven.clean.max.gb.size=8
local.maven.clean.older.than.days=7

Resolution

1. Increase the value of the parameter org.talend.remote. job server.commons.config.JobServerConfiguration.MAX_ARCHIVES_DIR_SIZE.
2. Enable <RemoteEngineInstallationDirectory>/data/m2/ folder cleaning work to reduce storage burden, for more details, please refer to Automating artifact cleanup for better performance of your Remote Engine.

Environment

• Talend Studio R2023-02
• Remote Engine 2.12.x
• Java 11

Qlik Sense URL(s) tested on SSLlabs (ssllabs.com) return the following weak Cipher suites:

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 1024 bits FS WEAK
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK

The steps documented in this article are an example of how cipher suites can be disabled. All steps are to be performed by a Windows Administrator on Windows level and cannot be supported by Qlik Support. 

We recommend to consulting with your security or Windows administrator before proceeding as they may have automated practices in place. 

The security in Qlik Sense does not depend only on the Qlik Sense software. It also relies on the security of the environment that Qlik Sense operates in. This means that the security of, for example, the operating system and the cryptographic protocols (such as TLS/SSL) has to be set up and configured to provide the security needed for Qlik Sense. See Protecting the platform.

Configuring TLS Cipher Suite Order

You can review and configure the cipher suites order using a Group Policy. See Manage Transport Layer Security (TLS) | Microsoft Learn.

Please refer to fig 1:

Fig 1

This policy determines the cipher suites used by the Secure Socket Layer (SSL). If you enable the policy setting, SSL cipher suites are prioritized in the order specified.

If you disable or do not configure this policy setting, the factory default cipher suite order is used.

SSL2, SSL3, TLS 1.0 and TLS 1.1 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHA TLS_RSA_WITH_NULL_MD5

TLS 1.2 SHA256 and SHA384 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_NULL_SHA256 TLS 1.2 ECC GCM cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521

How to modify this setting:

1. Open a blank notepad document.
2. Copy and paste the list of available suites into it.
3. Arrange the suites in the correct order; remove any suites you don't want to use.
4. Place a comma at the end of every suite name except the last. Make sure there are NO embedded spaces.
5. Remove all the line breaks so that the cipher suite names are on a single, long line.
6. Copy the cipher-suite line to the clipboard, then paste it into the edit box. The maximum length is 1023 characters.

Related Content:

Configuring preferred cipher suites for Qlik License Service in Qlik Sense Enterprise on Windows

Environment:

Qlik Sense Enterprise on Windows any version

As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).

This allows for analyzer capacity to be shared across all systems using the same license.

Environment:

QlikView 
Qlik Sense Enterprise on Windows 
With a Signed License Key (SLK) applied as a unified license across multiple environments 

Here is an example;

A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.) 

This can be accessed through: System > Licenses > Professional and Analyzer access.

Fig 1

If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up to date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.

This can be accessed in the Qlik Sense Management Console > License Management > License usage summary

Fig 2

The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.

Fig 3

For local consumption data, each server will store its own consumption and user information.   

For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.

For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:

RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe

It is recommended to enable HTTPS for Qlik GeoAnalytics Server. This can be done either during the installation or by editing the config.ini after the installation.  

The deployed SSL certificate may need to be updated regularly, which requires a repeat of the initial installation steps. 

Environment: 

Resolution:

Before you begin

• Make sure you have a certificate in PKCS12 (.pfx, p12) format, including the private key! This can be exported out from Windows Certificate Manager, Qlik Sense Management Console (if using self-signed certificates generated by Qlik Sense) or acquired by your certificate authority
• Make sure the certificate matches the hostname where Qlik GeoAnalytics Server is installed, (example: myserver.domain.local ) 
• Place the certificate where it can be accessed by Qlik GeoAnalytics Server

Set / Change certificate during install

The recommended way to enable HTTPS is to run the installation package and set/change the certificate during install. Setting the certificate during install will automatically obfuscate the password stored in config.ini.

1. Launch the Installer
2. On the second step of Server Settings (Basic) enable HTTPS and browse to the desired certificate. See fig 1.
   
   Fig 1
   
   
3. Proceed with the installation. 

Alternative way to enable HTTPS on an already installed Qlik GeoAnalytics Server

1. Edit config.ini found in %ProgramData%\Qlik GeoAnalytics Server and add the following to the [SSL] section, replacing details to match your environment:
   

   [SSL]
   sslEnabled=true
   sslPort=443
   sslKeystore=c:\\path_to_certificate\\certificate_filename.pfx
   sslPassword=certificate_password​

2. While encryption of passwords is required in later versions, it should still be possible to use clear text password in the ini. However, it's recommended to re-run the installation program to set the parameters and then the password will be obfuscated like enc:0B0115327474.
   
   All obfuscated passwords should start with enc:
   
   
3. Open Qlik GeoAnalytics Configure Service console and restart the service
4. Verify HTTPS working properly.
5. Any errors/warnings about the certificate not being valid, such as missing Subject Alternative Name, issues with the certificate chain etc may result in errors when using the server and needs to be investigated and fixed.

A talend Job is failing with the following error when you publish it to Cloud

java.io.FileNotFoundException: <File Path Here> (Access is denied) 

Resolution

1. Please check that you have enough permissions to the file and folder path, and for the remote engine as well. This is an example of when using the remote engine as a Windows service  Jobs fail due to a "java.io.FileNotFoundException: \\fileshare\filename (Access is denied)" error
2. Please check for possibilities of the folder or file being accessed from a different process or a different job, which may cause conflict.
3. Please double check your job design, and make sure that the file is created and exists in the directory. A component that you can use for this situation is tFileExist. For guidance on how to use the component, please refer to this documentation Checking for the presence of a file and creating it if it does not exist.

Cause 

1. The user does not have enough permissions to the file or folder path, or for the remote engine.
2. The folder may be accessed from a different process or a different job, which may cause conflict.
3. The folder or file may be missing from the directory at that particular time.
4. If you are using absolute Path to the source file, please ensure there are no spaces or Special characters, escape sequence issues in the file path string.

Environment

Talend Cloud 

The process of migrating a Qlik Sense Enterprise for Windows environment after unbundling PostgreSQL is similar to Migrating any other Qlik Sense environment to a different host.

1. Begin with the Verification of all requirements, the Preparation Reading, and Backup as documented in Migrating Qlik Sense Enterprise to a different host 
   
   
2. Then install a supported version of PostgreSQL and prepare databases as documented in Installing and configuring PostgreSQL.

   Select your corresponding Qlik Sense Enterprise for Windows version from the dropdown select box

3. Install the Central Node using the new PostgreSQL instance prepared in step 2.
    
4. Restore the site. For this, we will use Restoring a Qlik Sense site to a machine with a different hostname, as a general guide, but we will follow a set of modified steps: 
   
   
   1. Stop all Qlik Sense Services you have just installed
   2. Drop the following databases:
      
      This step is only necessary if you already have data in the databases. Otherwise, skip this step and move to step d.
      
      
      • QSR
      • SenseServices
      • QSMQ
      • Licenses
        
        Use the command dropdb -h localhost -p 4432 -U postgres <Database>
        
        
   3. Create the same databases you have just dropped:
      
      
      • QSR
      • SenseServices
      • QSMQ
      • Licenses
        
        Use the command createdb -h localhost -p 4432 -U postgres -T template0 <Database> -O qliksenserepository
        
        
   4. Restore the newly created databases:
      
      
      • QSR
      • SenseServices
      • QSMQ
      • Licenses
        
        Use the command pg_restore -h localhost -p 4432 as documented in Restore the repository database 4.c in Restoring a Qlik Sense site to a machine with a different hostname.
        
        
5. Before proceeding with Restoring a Qlik Sense site to a machine with a different hostname steps 5 to 7:
   
   
   1. Evaluate and prepare your file share. If the share needs to be changed, follow the instructions in How to change the share path in Qlik Sense (Service Cluster)
   2. If you have a multi node with rim or worker nodes which will change names (FQDN), follow the instructions in What about my rim nodes? 
      Note that the LocalConfigs table is removed in the most recent Qlik Sense versions. Do not be alarmed if it is missing.
   3. If your Active Directory Domain changes, proceed with Qlik Sense Entrprise moved to a new domain from point 3 onwards, replacing the old domain name with the new domain, especially for RootAdmin users and new Service User Accounts. 
      
      
6. Continue with Restoring a Qlik Sense Site steps 5 to 7.
   
   
7. At this point, the Central node will be up and running and report its worker or rim nodes as down or not contacted. Continue with the Worker Nodes:
   
   
   1. If the Worker nodes are new, simply install Qlik Sense and add them to the central node
   2. If the Worker nodes have already existed, it may be necessary to regenerate and redistribute new certificates: 
      
      
      1. Open the MMC as the Service user account on the Worker Node and add the Certificate for the Local Server and Current User
      2. Back up the current SelfSigned Qlik Sense Certificate issued by the Old Central Node, then delete it.
      3. Back up and then remove files.pem in “C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates”
      4. Verify connection strings to the new database of the new Central node using the QlikSenseUtil and the scripts described in QlikSenseUtil and the ConfigureScript.ps1 for Qlik Sense Dispatcher subservices
      5. Start the services and after a short delay verify in the QMC if you need to repeat the Redistribution of Certificates.
         
         
   3. Repeat accordingly for remaining Worker Nodes      

Environment

• Qlik Sense Enterprise on Windows

The following error is showing for tasks that were hanging in queue:

No engines were available to process this task. You can try to run the task manually now. Run this task during a time when your processors are available.

Resolution

If you are running too many tasks in parallel, experiencing time out and tasks failed, please consider the following.

1. Set max.deployed.flows to a higher value.
   This value should be considered upon how much memory you can use for task executions.
   This is the amount of executed tasks you have in parallel.
   For more information on how to set this value, please check here: Running tasks in parallel on Remote Engine.
   
   
2. If the time does not matter on how long it takes for all tasks to complete,
   then consider having few job executions in parallel.
   For example: If you have 80 plans running at the same time, consider creating 3 plans
   running at the same time with all the jobs included.
   
   
3. Consider using remote engines in a cluster, so you have more 
   remote engines that can be used to execute the tasks.
   For more information on clusters, please check here: Creating Remote Engine clusters.
   
   
4. Increase the amount of memory you have in the environment where the remote engine is placed,
   so you can allocate more memory to the remote engine.
   
   
5. Adjust the time when tasks execute, so timeout does not occur.
   This may be the only solution if you have very limited amount of memory to be used.

Cause

Too many tasks are running at the same time, and since the tasks that were in queue timed out, it failed to execute.

Related Content

On a different note, please also review the steps to clean up the task logs on the Remote Engine

automatic-task-log-cleanup

Environment

Talend Cloud 

Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.

The behaviour began after an upgrade of Qlik Sense Enterprise on Windows. 

Fix version:

This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.

Solution for August 2023 and above:

Enable QmcTaskTableCacheDisabled.

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify or add the QmcTaskTableCacheDisabled flag for these values to true
   
   {"contentHash":"CONTENTHASHHERE","originalClassName":"FeatureToggle","flag":"QmcTaskTableCacheDisabled","enabled":true}
   
   Where CONTENTHASHHERE matches the number in all other features listed in the capabilities.json.
   
   Example:
   
   
   
   This will disable the caching on the tasks table only, leaving the overall QMC Cache intact to gain performance. If you had previously set QmcCacheEnabled, QmcDirtyChecking, QmcExtendedCaching to false, please set it to true again.
   
   
4. Restart the Qlik Sense services

Workaround for earlier versions:

Upgrade to the latest Service Release and disable the caching functionality: 

To do so:

1. Navigate to C:\Program Files\Qlik\Sense\CapabilityService\
2. Locate and open the capabilities.json
3. Modify the flag for these values to false
   • QmcCacheEnabled
   • QmcDirtyChecking
   • QmcExtendedCaching
4. Restart the Qlik Sense services
   
   

NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.

Should the issue persist after applying the workaround/fix, contact Qlik Support.

Internal Investigation ID(s): 

QB-2096
QB-5168
QB-7655
QB-17238

Environment

Qlik Sense Enterprise on Windows 

After following the Qlik article Configure Qlik Sense to use a dedicated PostgreSQL server and update the connection string to point to the new host, Qlik Sense appears to work fine at first. However, access by the Qlik Sense Service account to the old host is registered or errors are found in the logs similar to what is found in the example below:

In the AppDistributionService trace logs:

307308 20210104T170444.859+01:00 INFO QLIKSERVER 70 DOMAIN\serviceaccountname Retry attempt: 10/10. Previous result: "No such host is known". 304796
307309 20210104T170451.812+01:00 ERROR QLIKSERVER 70 DOMAIN\serviceaccountname Error processing message queue notifications. System.Net.Sockets.SocketException (11001): No such host is known
at System.Net.Dns.HostResolutionEndHelper(IAsyncResult asyncResult)

Resolution

There are a few new services starting on the September 2019 release of Qlik Sense which did not exist in June 2018. Some of them were also removed/replaced on the new release.

Option 1 (recommended): Updating the files using PowerShell:

1. Stop all the Qlik Sense services
2. Open a PowerShell command prompt in administrator mode and then, either run the following:
   
   

   # Set the Installation Directory for Qlik Sense
   $installDir = 'C:\Program Files\Qlik\Sense\'
   #change that to the new database server
   $newdatabasehostname='new database server'
   # Specify the new password for the qliksenserepository account
   $password = 'MyNewPassword'
   # Find all Configure-Service.ps1 scripts in the installation directory and execute them
   $files = Get-ChildItem -Path $installDir -Include Configure-Service.ps1 -Recurse
   foreach ($file in $files) {
       $ScriptToRun=$($file.FullName)
       &$ScriptToRun $newdatabasehostname 4432 qliksenserepository $password -postgresHome 'D:\Qlik\Sense\Repository\PostgreSQL\12.5'
   }​

   
   In case of having a custom path Qlik Sense installation, change the last line to:

&$ScriptToRun $newdatabasehostname 4432 qliksenserepository $password -postgresHome 'D:\Qlik\Sense\Repository\PostgreSQL\12.5'
}

Where "D:\Qlik\Sense" is Qlik Sense installed folder and where "12.5" is the Postgres version installed.

Option 2: Manually update each file

Change to the following directories with the commands below before running the Configure-Service.ps1 command listed further below.

Repeat the step for every subfolder mentioned below.

Note: If you previously upgraded you may find folders in your system which are not listed here. Ignore them. No steps need to be taken.

Qlik Sense February 2021 and later.

Locate Configure-Service.ps1 in C:\program files\Qlik\Sense\.

It lists all services that need to be changed.

Qlik Sense June 2018:

Qlik Sense September 2019:

Example:

For AppDistributionService...

PS C:\> cd 'C:\Program Files\Qlik\Sense\AppDistributionService'
PS C:\Program Files\Qlik\Sense\AppDistributionService> .\Configure-Service.ps1 DatabaseHost Databaseport DatabaseUser DatabasePassword

e.g. .\Configure-Service.ps1 newdatabasehostname 4432 qliksenserepository Password123!

The answer will look similar to this:

AppDistributionService configuration started.
WARNING: Skiping the database initialization. No superuser or password specified.
Reading the settings file.
Saving the modified settings.
Exporting the copy of the invocation parameters.
AppDistributionService configuration successful.

Related Content:

• Configure Qlik Sense to use a dedicated PostgreSQL server

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 

What is the default user session timeout for Qlik Sense Business and Qlik Sense Enterprise SaaS? Can the session timeout for Qlik Cloud be changed?

The default (fixed) value is set to 30 minutes. This is controlled by SESSION_TTL.

It is not currently possible to adjust the session timeouts in the Qlik Cloud.

Environment:

Qlik Cloud 

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",

The Qlik Sense Engine allows for a Hard Max Limit to be set on memory consumption. 

To be able to enforce "Hard max limit" the engine requires access to a specific endpoint in the Windows operating system API.

If the operating system blocks calls to this endpoint, then an attempt to use the configuration "Hard max limit" will fail, and the engine will instead operate according to the "Soft max limit" configuration.

Refer to the documentation provided by Microsoft fur forther information: "SetProcessWorkingSetSizeEx"

How to review your memory settings in Qlik Sense or configure the Hard Max Limit:

1. Open the Qlik Sense Management Console in a supported browser
2. Navigate to Engines in the Management Console and select your engine
   
   
   
   
3. Expand the Advanced settings from the menu to the right
   
   
   
   
4. Review your memory settings and verify that Max Max Limit is selected
   
   

See Editing an engine - Qlik Sense for administrators for details.

To note:

Even with the hard limit set, it may still be possible for the host operating system to report memory spikes above the Max memory usage (%).

This is down to how the Qlik Sense Engine memory limit will be defined based on the total memory available.

Example:

• A server has 10 GB of memory in total, and the Max memory usage (%) is set to 90%.
• This will allow the process engine.exe to use 9 GB of memory. 
• Another application or process may at that point already be consuming 5 GB memory, and this will cause an overload of the system if the engine is set to use 9 GB. 
• The engine.exe will not be able to respect other services

The memory working setting limit is not a hard limit to set on the engine. This is a setting which determines how much we allocate and how far we are allowed to go before we start alarming on the working set beyond parameters. 

Internal Investigation IDs:

QLIK-96872, HLP-17517

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 (may also be called postgresql-x64-12)
2. (if installed) Qlik Sense Logging Service 
3. Qlik Sense Service Dispatcher
4. Qlik Sense Repository Service 
   Note: Delay for up to five seconds before starting the Qlik Sense Repository Service to allow the Dispatcher time to start its microservices. 
5. 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. (if installed) Qlik Sense Logging Service 
2. Qlik Sense Service Dispatcher
3. Qlik Sense Repository Service 
   Note: 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

Correct Stop Order:

Central node

1. Qlik Sense Repository Database (QRD)
   This will first terminate all services with a dependency to the QRD (see Service dependencies on the Qlik Sense Online Help)
2. (if installed and not stopped already by step 1.) Qlik Sense Logging Service (If feature was enabled during installation)
3. 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. (if installed) Qlik Sense Logging Service 
3. Qlik Sense Repository Service
4. 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.
 

There are environments where the cryptographic protocols available to the Windows Operating System need to be restricted for security or compliance reasons. This article will outline where various TLS versions are supported. This article will not have full coverage of the impact of TLS changes to other software installed on the Qlik Sense server. For examples of potential impacts:

• SQL connection not working with TLS 1.2
• OLEDB Connection not working with TLS 1.2

Resolution

• Full compatibility with TLS 1.2 in all current and supported versions of Qlik Sense Enterprise on Windows
• TLS 1.3 is not yet fully compatible [Internal Reference ID: SHEND-1269]

Implementation

To enable strong TLS implementation make sure to have all your servers updated to a version of both the operating system and the Qlik software, which explicitly details they support the required version of TLS.

If you have a clustered environment with multiple nodes spread across different machines, please make sure to enable the same subset of protocols on all Sense machines, otherwise the services will not be able to successfully communicate.

Using a third-party toolset

Third-party tools such as IIS Crypto can be used to enable and disable SSL or TLS. Consult your Windows administrator or network security team for what tools are usually used in your organization. 

Manual

The correct protocols and ciphers can then be applied using the PowerShell (PS) scripts and making changes to the Windows Registry. Consult Microsoft or your Windows administrator for details. 

Related Content

IIS Crypto is an example 3rd party tool that can be used to achieve this. IIS Crypto is not supported by Qlik, but by its respective vendor, NARTAC Software. To obtain IIS Crypto, visit https://www.nartac.com/Products/IISCrypto. 

After a Qlik Sense upgrade, the Qlik Sense Repository service fails to start. The following error is logged in the Windows Application Event log:

Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
System.IO.FileLoadException: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5'
at Repository.QRSService.Start(Action`1 terminate)
at

Resolution

The initial recommendation is to repair the installation. See How to repair an installation.

If the repair does not resolve the problem:

1. Copy the Qlik.Sense.Logging.dll from another environment of the identical Qlik Sense version, including patch version. The file can be located in: [Installation Qlik Sense folder]\Qlik\Sense\Repository\
2. Place the copied file in the same folder on the failing server
3. Restart the Qlik Sense Repository service.

Cause

The Qlik.Sense.Logging.dll present in [Installation Qlik Sense folder]\Repository\ was missing required inforamtion. 

Environment

Qlik Sense Enterprise on Windows 

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

An error has occurred
For detailed information see the log file

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

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

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

Resolution:

Reinstall Qlik Sense. (Uninstall, Reinstall)

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

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

Environment:

Qlik Sense Enterprise on Windows