Users who have been assigned Analyzer Licenses in Qlik SaaS (Qlik Sense Business or Qlik Sense Enterprise SaaS) cannot publish bookmarks.

See Assigning user allocations 

• Analyzer access: intended for users who only consume sheets and apps created by others. A user with analyzer access cannot create, edit, or publish sheets or apps, but can create stories, bookmarks and snapshots based on data in apps that are shared with them. The user can also generate on-demand apps, print objects, stories, and sheets, and export data from an object to Microsoft Excel.

• Analyzer access (minutes): intended for providing time-based analyzer access.

Environment

• Qlik Sense Business 
• Qlik Cloud 

The Qlik sense engine Service stops but engine.exe still running.

Environment:

Qlik Sense Enterprise on Windows 

Cause:

This is usually due to a high memory consumption, so when you stop the Qlik Sense Engine Service, the engine.exe will keep running it has released the memory. This can take a long time. 


Possible error message in Windows events log:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Engine.exe (77404) consumed 66804117504 bytes, dotnet.exe (29264) consumed 581591040 bytes, and dotnet.exe (49860) consumed 523714560 bytes.

Resolution:

To resolve this you can kill the engine.exe task but this will restart the service (as the services recovery properties are by default set to restart when the task fails), so you will have to stop the service again. 

Related Content:

Windows successfully diagnosed a low virtual memory condition  

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.

Prerequisites:

• Valid 3rd Party SSL certificates will be trusted by the Apache Web Server/Qlik Sense Server/ADFS server and are configured 
  • Note: Tested with all the certificates being created by the same Certificate Authority (CA - Tinycert.org) accompanied by the same Trusted Root across all servers.
  • Note 2: Tested Qlik Sense with a valid SSL certificate bound to the Proxy Service - How to: Change the certificate used by the Qlik Sense Proxy to a custom third party certificate / Editing proxies
  • Note 3: Tested using SHA256 certificates for SAML and verify that all certificates are configured correctly with the proper Cryptographic Providers - Error 500 - Internal server error in the Hub/QMC when connecting through SAML authentication
  • Note 4: For HTTPS/SSL for Apache needs the certificate to be split into two files (.crt and .key) - Same process is used for NPrinting and is described in the article: How to convert a certificate for NPrinting to the .key and .crt files for HTTPS/SSL in the Web Console and/or the NewsStand
• Access to Sense installed on a server that is configured to use SAML ADFS - Configuration of ADFS can be found in the article: Quick Guide to installing ADFS for testing SAML
• Access to a server to install and configure Apache Web Server

Example Environment:

• Qlik Sense: QlikServer1.domain.local - IP: 172.16.16.100
• Apache Web Server: QlikServer3.domain.local  - IP: 172.16.16.102
  • Other Active Servers:AD FS: DC1.domain.local
• Qlik Sense February 2018 GA
• Windows 2016
• ADFS 4.0 
• Apache 2.4 (httpd-2.4.33-o110h-x64-vc14-r2)
• HTTPS / SSL - SHA256 with "Microsoft Enhanced RSA and AES Cryptographic Provider" added Enabled / Active on Sense, ADFS and Apache. 

Note: This documentation is only to used to validate and test ADFS SAML while using Apache as a Reverse Web Server and HTTPS/SSL is enabled. This example is under the assumption there's an understanding of the environment and having the proper permissions to perform the actions shown. Accounts used are all Local Administrators and the servers are open, with nothing blocked and no other programs installed on them.​Read the entire documentation to verify access and understanding of all actions stated within prior to starting the install and configuration. Any other versions or configurations of any software may need other steps/options/settings/etc ... that are not documented here. ​Use this at your own discretion as Qlik does NOT support Apache/OpenSSL/ADFS in their installation/configuration or use.

Setup

Step 1:

Download (​Recommended to verify the zip file is not Blocked: Right click on the zip file -> Properties -> General -> Click Unblock -> Apply), Extract the Zip file and Read the "readme_first.html" then use the instructions to Install Apache Web Server as Service on a separate machine from Sense and ADFS - https://httpd.apache.org/docs/2.4/platform/windows.html. Verify Apache is running under HTTP/HTTPS.
Location Installed: C:\Apache24\

Note: Tested with http://www.apachehaus.com version Apache 2.4.33 x64 Distribution File: httpd-2.4.33-o110h-x64-vc14-r2.zip

Step 2:

Place a valid certificates .crt and .key files on the Apache Web Server.
Location used: C:\Apache24\conf\ssl

Note: Process used: How to convert a certificate for NPrinting to the .key and .crt files for HTTPS/SSL in the Web Console and/or the NewsStand

Step 3:

Navigate to the location and Edit the "httpd.conf" file (Location used: C:\Apache24\conf\). Then uncomment certain modules used in this example and save the file.

Search for and then uncomment the following modules:

• LoadModule proxy_module modules/mod_proxy.so
• LoadModule proxy_http_module modules/mod_proxy_http.so
• LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
• LoadModule rewrite_module modules/mod_rewrite.so
• LoadModule vhost_alias_module modules/mod_vhost_alias.so

Find and uncomment the following line so that the reverse proxy will use the configuration that will be written later:

Include conf/extra/httpd-vhosts.conf

Note: To uncomment the option/module remove the pound ( # ) symbol in front of the line and save the file.

Step 4:

Navigate to and Edit the file "httpd-vhosts.conf" under the directory (Location used: C:\Apache24\conf\extra) to add the virtual host that will used for Qlik Sense and save the file. 

Example "httpd-vhosts.conf":

# Virtual Hosts
#
# Required modules: mod_log_config
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:http://httpd.apache.org/docs/2.4/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.
#
# Qlik Sense configuration needed:
#
# - Create a new virtual proxy with SAML called adfsapache
# - Add reverse proxy name and IP address to whitelist of virtual proxy
#Put IP address of reverse proxy as LOCAL_ADDR
#Put IP address of Qlik Sense server as REMOTE_ADDR
#Put your virtual proxy prefix as VIRTUAL_PROXY

Define LOCAL_ADDR 172.16.16.102
Define REMOTE_ADDR 172.16.16.100
Define VIRTUAL_PROXY adfsapache
 
<VirtualHost *:443>
    ServerAdmin name@qlik.com
    DocumentRoot "${SRVROOT}/htdocs"
    ServerName ${LOCAL_ADDR}:443
    ServerAlias qlikserver3.domain.local
    
    SSLProxyEngine on
    SSLEngine on
    SSLProxyCheckPeerCN off
    SSLProxyCheckPeerName off
    
   #Location of the SSL certificate used for this virtual host in their .crt and .key file format
    SSLCertificateFile  "${SRVROOT}/conf/ssl/QlikServer3Certificate.crt"
    SSLCertificateKeyFile   "${SRVROOT}/conf/ssl/QlikServer3Certificate.key"
 
    ProxyRequests Off
    ProxyPreserveHost On
    KeepAlive On

    RewriteEngine On

    # If it is a websocket request forward as websocket traffic
    RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
    RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
    RewriteRule ^/(.*) wss://${REMOTE_ADDR}%{REQUEST_URI} [P]
    <Proxy *>
         Require all granted
    </Proxy>
    <Location /${VIRTUAL_PROXY}>
        ProxyPass https://${REMOTE_ADDR}/${VIRTUAL_PROXY} connectiontimeout=5 timeout=300
        ProxyPassReverse https://${REMOTE_ADDR}/${VIRTUAL_PROXY}
    </Location>
</Virtualhost>

Note: Some parameters/options may need to be turned off or on depending on your certificates and other configuration items.

Step 5 & 6:

For Steps 5 & 6, refer to Article Quick Guide to installing ADFS for testing SAML starting from Step 5 until Step 11  and apply where needed

Step 7:

Configure a Virtual Proxy in Qlik Sense called "adfsapache"

Note: Verify the Host allow list has the correct IPs/DNS (FQDN/Servername/Alias) added to it,

Step 8:

Create the Relaying Party Trust for the "adfsapache" Virtual Proxy in ADFS

Step 9:

Restart the Apache Web Server service and attempt to log into a URL from a machine that's NOT the Apache Server. Example URL: https://qlikserver3.domain.local/adfsapache 

Note: Reason for attempting it outside the Apache Web Server is that certain OS level settings may not allow access to the FQDN/Servername locally to the machine. Review this article if you're able to connect to it locally with IP/Localhost: Authentication failed repeatedly when using external DNS alias locally on the server

Environment:

Qlik Sense Enterprise on Windows 

When requesting an export to Excel or Print using the QlikView Ajax client, QlikView Server creates a temporary Excel file on the server. The file will be removed after one hour (3600s).

The time until deletion can be customized. 

By default, QlikView Server scans through the temp folder once an hour and removes all the files that are at least one hour old. This means that a file is stored somewhere between 1 and 2 hours, depending on when the file was created in relation to when the latest scanning occurred.

The value you can change is ServerTempSecTimeout (default 3600) which changes both time values.
E.g. if the setting is changed to 1800 (30 minutes), QlikView Server will scan the temp folder every 30 minutes. Any file that is at least 30 minutes old will be removed.

The temporary folder can be found in \QlikTech\QlikViewServer\Temp Folder

Resolution

In our example, we configure the files to be deleted immediately after download.

1. Stop the QlikView Server service
2. In a Windows File browser, browse to: C:\ProgramData\QlikTech\QlikViewServer\
3. Open the settings.ini (if necessary, with administrative permissions)
4. Add the following entry in the [Settings 7] section:
   
   [Settings 7]
   RemoveExcelAfterDownload=1
   
   Note: The setting references excel, but the setting also impacts HTML/PDF files.

Environment:

QlikView 

This article explains how the Reporting connector in Qlik Application Automation can be used to generate simple multi-page PowerPoint reports. It also explains how to store the generated report on a cloud storage tool, like Microsoft SharePoint.

Environment

• Qlik Sense Enterprise SaaS
• Qlik Application Automation

Full Automation

Step-by-step description

The following steps describe how to build the demo automation. You will find a version of this automation attached to this article: "Store-a-simple-multi-page-PowerPoint-report-to-Microsoft-SharePoint.json".

1. Search for the 'Create Report' block in the Reporting connector, drag it to the automation editor, and attach it to the Start block. Configure it by specifying a name for the report and selecting Sheets mode = All option
2. Add the 'Generate Report' block to the automation and configure it to use the report we are building. Select PowerPoint as the format mode to generate a PowerPoint report.
   
   
   
   
3. Find the Cloud Storage connector in the Block Library and add the 'Copy File' block to the automation. Configure it to use the output from the 'Generate Report' block as the Source File and set the Destination connector to Microsoft SharePoint (or another destination of your choice). Include the Path from the output of the Generate Report block in the Destination Path parameter to use the generated filename. Use the 'do lookup' functionality to find a Drive Id or a Site Id,  but do not specify both.
   
   
   

Related Content

• Qlik Reporting Connector

You can open and build an app on Qlik Cloud using a direct link.

To obtain the link:

1. Log in to Qlik Cloud
   
   
2. After a successful login, type the following URL in your browser's address bar: 
   
                 https://<TenantURL/api/v1/apps>
   
   Example: https://cloudtenant.eu.qlikcloud.com/api/v1/apps
   
   The output will look as follows:
   
   
   
   
3. Locate the app you wish to open directly. 
   
   For example, if we need an app named "Demo App": {"attributes":{"id":"2ec35684-3d28-46e8-b744-d4194eab0aa5","name":"Demo App}
   
   
4. Copy the id. This is your App ID.
   
   
5. In your browser's address bar, type the link to the app, formatted as:
   
        https://<Your TenantURL>/sense/app/<App ID>/overview
   
   Example: https://cloudtenant.eu.qlikcloud.com/sense/app/2ec35684-3d28-46e8-b744-d4194eab0aa5/overview
   
   
6. You will now be redirected to the app's overview page. 

Environment

Qlik Cloud

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.

In this article, we walk you through the requirements and process of how to upgrade an existing Qlik Sense Repository Database from PostgreSQL 9.6 to PostgreSQL 12.5 (see supported scenarios) or install a brand new Repository based on PostgreSQL 12.5.

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 

PostgreSQL 9.6 has reached End of Life Reference: PostgreSQL Versioning Policy.

Index

• Supported Scenarios
• Considerations
• Installing anew Qlik Sense Repository Database using PostgreSQL 12.5
• Upgrading anexisting QRD to PostgreSQL 12.5
• The Upgrade:
• Finalizing the Upgrade/Uninstalling the old Database Service:
• Compatibility with PostgreSQL installers
• Qlik PostgreSQL Installer - Download Link
• Troubleshooting
• Related Content

Supported Scenarios

• Upgrades: Before using the Qlik PostgreSQL Installer, upgrade to one of the supported versions (see below) of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.
  
  Only the following Qlik Sense Enterprise on Windows releases are supported for the upgrade scenario:
  
  
  • February 2022
  • May 2022
  • August 2022  
  • November 2022 (does not support 9.6, but will allow an upgrade)
    
    
• New installs: The Qlik PostgreSQL Installer supports installing a new Qlik Sense Repository Database cluster on a new server, setting up a new environment or migrating an existing Database to a separate host.

Considerations

• This installer will not detect a standalone PostgreSQL database installed by any other means, other than through an official Qlik installer package, installed on the standard folders in the C drive. 
• The installer itself does not provide a rollback feature. This is described below. 
• The user who runs the installer has sufficient permissions to execute it and install services 
• The user who runs the installer has sufficient permissions to create folders and files in the backup destination 
• The backup destination has sufficient free disk space to dump the existing database  
• The backup destination is not 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 

Installing a new Qlik Sense Repository Database using PostgreSQL 12.5

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, standard: C:\Program Files\PostgreSQL\12
   
   
7. Set the database data folder, standard: C:\Program Files\PostgreSQL\12\data
   
   
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 
    

Upgrading an existing QRD to PostgreSQL 12.5

Before using the Qlik PostgreSQL Installer, upgrade to one of the supported versions (see below) of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.

Only the following Qlik Sense Enterprise on Windows releases are supported for the upgrade scenario:

• February 2022
• May 2022
• August 2022 
• November 2022 (does not support 9.6, but will allow an upgrade)

Qlik Sense Enterprise on Windows installations other than in C:\Program Files\Qlik\Sense are currently not supported. 

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.
    
    
    
    
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-12 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.

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

Finalizing the Upgrade/Uninstalling the old Database Service:

No further steps are needed unless you plan to upgrade Qlik Sense Enterprise on Windows to the next major release. If you plan to upgrade to, for example, November 2022, the old Qlik Sense Repository Database service must be removed from the server.

Perform the following steps to delete the Qlik Sense Repository Database Service:

1. Open a command prompt and run the command:
   c:\cd ProgramData\Package Cache
2. From there, run:
   c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
3. The folder containing PostgreSQL.msi will be revealed.
4. Right-click on the PostgreSQL.msi file and select uninstall from the menu.

Compatibility with PostgreSQL installers

This version of the upgrade tool is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.

If you need to upgrade to a higher release than Qlik provides, you can install the same minor PostgreSQL release 12.x.

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer version 1.2.1 Release Notes

Troubleshooting

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\9.6
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\9.6_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-12 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.2.1 Release Notes  
Techspert Talks - Upgrading Qlik Sense Repository Service
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

A multi-cloud deployment allows you to distribute Qlik Sense apps to the cloud for consumption. You can set up your deployment to connect Qlik Sense Enterprise on Windows to Qlik Cloud. For more information on multi-cloud deployments, see: Multi-cloud deployments to Qlik Cloud 

In these multi-cloud environments, Qlik Cloud can be considered an expansion of the Qlik Sense Enterprise on Windows platform, whereas all app development is carried out on the client-managed platform, and the apps can be made available for further consumption in Qlik Cloud.

Any additional editing (modifications of the Data Model) or duplication of the distributed apps is not possible directly on Qlik Cloud and needs to be carried out in Qlik Sense Enterprise on Windows.

Limited options are available on the Qlik Cloud hub for apps distributed from a client-managed platform:

In this article, we outline the ideal workflow used when distributing apps.

Reviewing the QlikView Source Documents list may show missing entries.  

The QlikView Management Console log shows the following entry: 

QDS did not respond to request.Last exception (for
http://qlikserver1:4720/QDS/Service The request channel
timed out while waiting for a reply after 00:00:30. Increase the timeout value
passed to the call to Request or increase the SendTimeout value on the Binding.
The time allotted to this operation may have been a portion of a longer timeout.

—> System.TimeoutException: The request channel timed out while waiting for a
reply after 00:00:30. Increase the timeout value passed to the call to Request
or increase the SendTimeout value on the Binding. The time allotted to this
operation may have been a portion of a longer timeout. —>
System.TimeoutException: The HTTP request to
'http://qlikserver1:4720/QDS/Service' has exceeded the
allotted timeout of 00:00:30. The time allotted to this operation may have been
a portion of a longer timeout. —> System.Net.WebException: The operation has
timed out 

Environment

QlikView 12.50 and above

Resolution

We can further configure the timeout using a setting for the QVManagementService.exe.config.

1. Stop the QlikView Management Console Service
2. In a Windows browser, navigate to:
          C:\Program Files\QlikView\Management Service\
3. Open QVManagementService.exe.config with an editor of your choice (may require administrative permissions)
4. Locate the <appSettings> section of the file:
   

   <appSettings>
   <!-- ****** General ****** -->
   
   </appSettings>

5. At any point between <appSettings> and </appSettings> add the following:
   

   <!-- Setting in seconds which the QMS will wait for the QDS to deliver the list -->
   <add key="GetSourceDocumentTimeoutSeconds" value="120" />

6. Save the file
7. Start the QlikView Management Console Service

The Management Console will now wait for two minutes to read all its files to build the list. Should you have a far larger amount of source documents, the timeout may need to be increased further. 

Cause

The default timeout is 30 seconds.

The max concurrent reloads can be configured in the Qlik Sense Management Console.

1. Open the Qlik Sense Management Console
2. Navigate to Schedulers 
3. Enable the Advanced section (if not already on by default)
4. Set the required max concurrent reloads
   
   
   

    

IMPORTANT TO REMEMBER

• A reload node could run NumberOfCores - 2
• If for example, the reload node has 8 CPU Cores then it could possibly run 6 concurrent reloads at its maximum.
• A reload task typically consumes at least one core, sometimes more
• With more concurrent tasks running than there are number of cores, the total time to complete a number of tasks that is larger than the number of cores does not improve with more parallel tasks running due to starvation of the server
• Each reload running is loaded into RAM. This means that the average RAM footprint grows with more parallel reloads
• With more parallel reloads than cores the probability for total starvation increases since the QIX engine is CPU hungry and other processes (for example, the operating system) might not get enough CPU cycles to perform their duties
• Use the guideline, NumberOfCPUCores - 2 in performing capacity planning on the possible amount of concurrent scheduled reloads.
• Scheduled reloads are queued, however, if not enough resources in the system
• To validate that environment needs proper capacity planning, go to C:\ProgramData\Qlik\Sense\Log\Scheduler\Trace\<Server>_System_Scheduler.txt, an example log shows below:
  
  

  <ServerName>_System_Scheduler.txt
  Domain\qvservice    Engine connection released. 5 of 4 used 
  Domain\qvservice    Engine connection 6 of 4 established 
  Domain\qvservice    Request for engine-connection dequeued. Total in queue: 25

Concurrent settings

Use the "Max concurrent reloads" to limit the maximal concurrent tasks can be run at same time on current node. By default, it's set to 4, which means only 4 tasks can be run at same time on this node.
When the 5th task comes in:

1. It will be queued by sequence. 
2. The queue has a time setting, which will eliminate (erase) a queued task if the timeout limit reaches. By default, it's set to 30 mins, in this case, if none of the first 4 tasks finishes in 30 minutes after the 5th task comes in, then the 5th task will be cancelled due to timeout. It has to be triggered again (manually or next scheduled time slot).
3. Once one of the 4 running tasks finishes, the 5th task will be executed on this node if it's not timed out.
4. If you set timeout to 0, this will make the queue never timeout.
5. It's suggested not to run more than 10 concurrent reloads at once, unless the schedular node has an extreme amount of resources dedicated to it.
6. If there is low memory or cores available on the node, then some tasks may kick off however take several hours to complete. Adding resources to the node running the reloads is suggested.

Multi-node deployment

On a multi-node deployment, tasks will be balanced from the manager node to any node(s) designated as workers.

It's highly advised to check if the central node in the QMC in the Schedulers section is set to Manager and Worker or "Manager". When set to "Manager", it will send all reload jobs to the reload/scheduler nodes, as it should. However if a central node is set to Manager and Worker, this means the Central node will also be involved in performing reloads, and is not suggested.

When there's a 3 nodes deployment (one manager and two workers) and each node is set to "Max concurrent reloads" = 4 and "Engine timeout" = 30:

1. Manager node receives a new task execution request.
2. Manager node checks the resource availability on each of the worker nodes. 
3. Manager node assigns this task to the node with the lowest number of running tasks per "Max concurrent reloads" setting, tracking this value on the scheduler master node at the moment of triggering*.

*Qlik Sense November 2019 introduced a new load balancing scheme. In previous versions of Qlik Sense, the algorithm always chose the load-balancing node with the lowest CPU load. The CPU load of all nodes was updated every 5 seconds, which might have resulted in consecutive reloads being distributed to the same node.

To improve the handling of frequent consecutive reloads, the algorithm has been changed to select the node with the lower number of running tasks per "Max concurrent reloads" setting, tracking this value on the scheduler master node.

This improvement is enabled by default. If you wish to disable it, do the following:

1. Open the Scheduler.exe.config, which by default is located in: C:\Program Files\Qlik\Sense\Scheduler\Scheduler.exe.config
2. Set DisableLegacyLoadBalancingBehavior setting to false
3. Restart Qlik Sense Scheduler Service
4. Repeat these actions on each node of the cluster running the Qlik Sense Scheduler Service

Dependent Tasks

For chained tasks, there is no load balancing that happens for tasks. All chained tasks are sent to the same Scheduler Node as the original task. This original assignment is based on overall availability based on metrics. This means having a large number of Chained Tasks is going to send all of those to the same node. This should be avoided with Chained Tasks being used for 'dependencies' for the current job. 

Your Qlik Account may be locked out after multiple consecutive (unsuccessful) login attempts.

The following message will be printed:

YOUR ACCOUNT HAS BEEN BLOCKED AFTER MULTIPLE CONSECUTIVE LOGIN ATTEMPTS.

Environment

• Qlik Sense Business 
• Qlik Cloud 

Resolution

When the account is blocked, you need to reset the password. Please follow the steps below. 

1. Click "I forgot my password"
2. Enter your registered email address and click "Send email" 
3. Click "Reset Password" in the email
4. Enter a new password and "Save" 

If you are unable to access your account still, please contact Qlik Support. 

Description

• NPrinting Publish Task, NP Connection, On-Demand executions have become stuck recently for no specific apparent reason
• NP Executions are stuck in a 'Running' status

Environment

• NPrinting Server
• NPrinting Engine(s)
• QlikView Desktop

Diagnosis

• NPrinting Executions are stuck in a 'Generating' status
• Log directly in to the NPrinting Server and each NPrinting Engine Computer
• Check c:drive hard drive space to determine if it is low on space
• If you find the c:drive to be low on space proceed to resolution section of this article

Resolution

1. Identify the QVW used in each NPrinting Connection
2. Do "File>Open" to access the QVW document properties
3. Go to 'Document Properties'
4. Deselect the 'Generate log file' property and save the QVW
5. 
6. Navigate to "C:\ProgramData\QlikTech\QlikView"
7. Delete all logs
8. Empty recycle bin
9. Restart all NPrinting Services

Note: Suggest clearing space from all other Windows temp and other storage folders from the NPrinting Server or Engine computer(s) c:\drive.

Cause 

• The windows operating system requires sufficient drive space to operate normally which by default includes an expanding local system page file and other logging functions which store information on the c:drive. The NPrinting will also deposit files on the c:\drive.
• Thus is it is important to use performance monitoring tools to monitor the c:\drive for low space warning
• If the c:\drive becomes low on space, this will affect operational performance of the Windows Server and thus the NPrinting server/Engine computer(s) where NPrinting is installed along with the QlikView Desktop.

Related Content

• System requirements for Qlik NPrinting Server
• System requirements for Qlik NPrinting Engine

Does Qlik have a defined security policy?

Qlik takes the security of our products seriously.  We have a dedicated team of security experts working on testing, hardening and securing our products.  We also work closely with external security companies, our customers and partners to ensure the security of our products is of the highest standard.  

Our Qlik Trust and Compliance Center provides details for compliance and security questions across all Qlik products. 

What do I do if I find a security vulnerability in a Qlik product?

Please report any security vulnerability concern to Qlik Support. For an accurate an detailed evaluation of a potential security vulnerability, it is important to clear describe the scenario in which a vulnerability has been exposed. This includes describing the steps for how security is compromised and what detail can be exposed by an attacker.

Notice, that generic test reports from 3rd auditing tools typically do not include detailed steps of vulnerability exposure in their security report. These reports commonly referring to potential risk based patterns, they do not actually expose a vulnerability as part of their system evaluation. Consequently this means that the default report details are not enough for Qlik to take any immediate action on based on the raised concern. Please consult 3rd party security auditor or local security expert for complete test case details before reporting support case with Qlik. 

To enable qualified and efficient investigation and action by Qlik, please report each vulnerability concern as an individual support case with Qlik Support. This means that each concern raised in a 3rd party test report must be reported as a separate support case.

For each case consider adding as much detail as possible, in line with below items:

• Qlik product name
• Qlik product version
• Test case subject/name (if based on test report)
• Complete penetration test report (attach full report for reference)
• Name of security tool used for testing
• Details of how to replicate the vulnerability
  • Step by step description on how to expose vulnerability
  • Recording of reproduction
  • Supporting material, e.g. logs, traffic traces or screenshots
• Vulnerability impact
  • Type of information exposed
  • Unauthorized access to content
• CVSS score if provided by security auditor

There could be certain situations when creating a connection with a QlikView application in NPrinting, the connection verification would fail the compatibility check.

The system will display a verification error message as below: "QlikView Server version is compatible with installed QlikView Desktop" as screenshot below:

Environment:

Qlik NPrinting , all versions

Resolution:

To resolve this do the following: 

Option 1:

Completely uninstall QV desktop on NP server then re-install  fresh version that exactly matches the QlikView server version, then fully restart the NP server

( Once you uninstall make sure that there are no installation folders left over and manually remove them before installing the correct version )

Create a new connection in NPrinting after the new installation

Option 2:

- Uninstall QlikView desktop client 

- Remove Qliktech folder registry; 

HKEY_CURRENT_USER > Software > QlikTech 

- Remove QlikTech folder from Application Data; 

Windows Server 2008 : C:\Users\ <user>\AppData\Roaming\QlikTech 

- Reboot machine 

- Install QlikView Desktop 

Option 3:

For the Cluster connection, under the cluster tab, make sure that the "Address" is entered as HTTP and not HTTPS in the address URL.
If there is no certificate setup, the address should be http and it could cause this same error ( know issue in the product )

Qlik Sense Enterprise on Windows (client-managed) caches user searches performed in an app in the Service Cluster location you have defined on setup. Example: \\server01\share\Apps\Search.

The same location will be used to store the Search Index created during an app reload, however, the most common way to create content there is to use the search functions in an app. This may cause the folder size to increase to the point of filling up the particular storage drive.

This path will change if you have chosen to store your Apps in a different location.

This folder can be cleaned periodically to remove old files. It is advisable to study the file creation pattern before deciding on a cleanup schedule so as not to disrupt the end-user experience.

In a multi node environment:

The default behaviour creates a search index during reload.

If you experience issues with reloads as documented in "Failed to create search index" script error during reload, we recommend changing the behaviour and setting nodes that perform reloads to not create search index during reload. See "Failed to create search index" script error during reload for configuration options. 

Environment

Qlik Sense Enterprise on Windows 

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 

Engine Settings: Create search index during reload

How To Grant Users The Access To Data Model Viewer.

With default security rules and settings, users can not see the data model for published apps. However, we can achieve this by creating/updating security rules through the Qlik Sense Management Console.

Resolution

Option 1: Create a new Security Rule

1. Go to the Qlik Sense Management Console
2. Open Security Rules
3. Click Create new 
4. Create the following rule:
   1. Name = DataModelViewers
   2. Description = A description of your choice.
   3. Resource filter = App_*
   4. Actions = "Read","Update"
   5. Conditions = Users of your choice or a previously defined role you will tag the users with.
   6. Context = Both in hub and QMC or Only in hub
      
5. Click Apply

Option 2: Tagging users as ContentAdmins

This requires a rework of the ContentAdmin rule and will provide far more permissions to users than Option 1. See ContentAdmin for details on what a ContentAdmin is allowed to do. 

1. Tag the users you want to be able to see data models with the ContentAdmin role. 
2. Go to the Security Rules 
3. Locate the default ContentAdmin rule and open it
4. Modify the rule by changing QMC only to Both in hub and QMC
5. Click Apply

Replicate reported errors during resume task if source MySQL running on Windows (while MySQL running on Linux then no problem)

[SOURCE_CAPTURE ]I: Stream positioning at context '$.000034:3506:-1:3506:0'
[SOURCE_CAPTURE ]T: Read next binary log event failed; mariadb_rpl_fetch error 1236 (Could not find first log file name in binary log index file)

Replicate reported errors at MySQL source endpoints sometimes (does not matter what's the MySQL source platforms):

[SOURCE_CAPTURE ]W: The given Source Change Position points inside a transaction. Replicate will ignore this transaction and will capture events from the next BEGIN or DDL events.

Environment:

• Replicate 2022.5   PR4 (2022.5.0.815)
• Replicate 2022.11 PR1 (2022.11.0.289)
• MySQL source database , any version

Fix Version & Resolution:

Upgrade to Replicate 2022.11 PR2 (2022.11.0.394, released already) or higher, or Replicate 2022.5 PR5 (coming soon)

Workaround:

If you are running 2022.5 PR3 (or lower), then keep run it, or upgrade to PR5 (or higher) .

No workaround for 2022.11 (GA, or PR01) .

Cause & Internal Investigation ID(s):

Jira: RECOB-6526 , Description: It would not be possible to resume a task if MySQL Server was on Windows

Jira: RECOB-6499 , Description: Resuming a task from a CTI event, would sometimes result in missing events or/and a redundant warning message

Related Content:

support case #00066196

support case #00063985 (#00049357)

Qlik Replicate