What is the recommended  setting for virtual memory in Qlik Sense and QlikView?

Environment:

QlikView 
Qlik Sense Enterprise on Windows 

Qlik Sense and QlikView require physical RAM to be operational. Using virtual memory will result in performance degradation. However, a too small pagefile will result in the Windows system misbehaving.
We recommend letting Windows manage the size of the file.

See also: Qlik Engine Memory Management

Prerequisites:

• 64-bit Java JRE 1.7 or higher
• GeoAnalytics connector (extension), at least version 1.3.0. To verify this open the connector in Qlik Sense or Qlik View.
  • Installing Qlik GeoAnalytics for QlikView Server
  • Installing Qlik GeoAnalytics Extensions for Qlik Sense Enterprise

Checking GeoAnalytics extension versions:

Qlik Sense:

Under Data load editor > Create new connection > Qlik GeoAnalytics Connector
The version should be visible in the top right of the connect dialog

QlikView:

Under Edit script > IdevioGeoAnalyticsConnector.exe > Connect...
The version should be visible in the top right of the connect dialogue

In order to update your GeoAnalytics connector install the appropriate version of Qlik GeoAnalytics extensions.

 Please ensure that the Server URL is changed to http://ga.qlikcloud.com if an old Idevio server address is observed.

 GeoAnalytics Plus must be installed on same machine where GeoAnalytics Connector (Extension) is running

 

Installing

Reference: Installing Qlik GeoAnalytics Plus

• Run GeoAnalyticsPlus64bitSetup-x.x.x.exe.
• If not running a local GeoAnalytics server, leave the default server URLs and press Next >

  Settings can later be changed in the IdevioGeoAnalyticsConnector.exe.config file found in C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector\

• Press Next>
• Accept the License Agreement and press Next> 
• Press Install and then Finish to complete the installation
  • If "Runtime Error (at 18:2562)" error dialog shows up, that indicates there is no GeoAnalytics Extensions installed prior to this installation. Install GeoAnalytics Extensions first. Refer to GeoAnalytics Plus: "Runtime Error (at 18:2562)" during installation

Reactivating license 

You need to reactivate the license for GeoAnalytics Connector after installing Qlik GeoAnalytics Plus, using the License Activation tool:

• In Windows Explorer go to C:\Program Files (x86)\QlikView\GeoAnalyticsLicenseTool
• Launch GeoAnalyticsLicenseTool.exe
• Enter your Serial number and Control number
• For other details when using the licensing tool see Installing Qlik GeoAnalytics Extensions for Qlik Sense Enterprise

 License details for GeoAnalytics Connector will by default be written into IdevioGeoAnalyticsConnector.exe.config during activation, which can be found in C:\Program Files\Common Files\QlikTech\Custom Data\QvIdevioConnector\

• Press Activate/Refresh license to activate the license

 Internet access is required for both activation and operation.

Verify installation

QlikView

• Create a new app in QlikView and go to Edit script
• Select IdevioGeoAnalyticsConnector.exe and press Connect...
• In the drop-down list verify GeoAnalytics Plus is available

Qlik Sense

• Create a new app in Qlik Sense and go to Data load editor
• Select Create new connection and select Qlik GeoAnalytics Connector
• In the drop-down list verify GeoAnalytics Plus is available

Common paths

Installation: C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector\lib

Settings: 

• QlikView  C:\Program Files\Common Files\QlikTech\Custom Data\QvIdevioConnector\IdevioGeoAnalyticsConnector.exe.config

 Although settings are stored in the above location, install files for GeoAnalytics Plus are still found in C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector\lib

• Qlik Sense C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector\IdevioGeoAnalyticsConnector.exe.config
  • • Installation path
    • Listening port
    • Location server URL
    • Route server URL
    • Geocoding server URL
    • Timeout
    • System proxy
    • Memory setting

Logs:

• C:\ProgramData\QlikTech\Custom Data\IdevioGeoAnalyticsConnector\Log
• C:\Users\<user>\AppData\Roaming\GeoAnalyticsPlus\logs

 When installed on Qlik Sense Enterprise logs will be stored in the <user> profile for the service account running Qlik Sense services

A Qlik Sense upgrade fails with:

Superuser password validation error

This means the step of validating the superuser password has failed.

See Fig 1 and Fig 2:

Fig 1

Fig 2

This can happen regardless of the correct password being provided.

Environment

• Qlik Sense Enterprise on Windows all versions

Resolution

Workaround 1:

Upgrade using the silent installer.

This will work up to version April 2020.

Example command-line string:

Qlik_Sense_setup.exe -s -log "C:\_logs\logs.txt" accepteula=1 userpassword="Qlik123" dbpassword="abc"

Workaround 2:

Remap the alternative port e.g. 5432 to 4432

1. From the command line run:
   

   netsh interface portproxy add v4tov4 listenaddress=localhost listenport=4432 connectaddress=localhost connectport=5432​

2. Start the installer, provide service user and database superuser credentials and just before starting the upgrade.
3. Revert step 1 by running:
   

   netsh interface portproxy delete v4tov4 listenport=4432 listenaddr=localhost​

4. Start the upgrade.

Workaround 3:

Reinstall Qlik Sense

1. Uninstall the current version of Qlik Sense BUT keep the database and certificates.
2. Install the new version of Qlik Sense on top of the existing database.

Cause

If the internal Qlik Sense Repository database is not running on the default port 4432. It does not happen with a standalone database which is running on a different port than 4432.

In the  Does QlikView Support NAS Storage?  Knowledge Base article, it is mentioned that "QlikView Server currently only conforms with Windows File Share or a Windows-based NAS."

Does that mean that Windows clusters are supported as file servers?

Environment

• QlikView server, any

Resolution

QlikView supports clustered Windows File Servers, as long as they are of the Active-Passive type.

Scale-out File Servers, being of the Active-Active type, are not supported.

Qlik Sense Enterprise on Windows was upgraded from a version prior to February 2020 or from other versions previously patched to address a node.js issue as documented in Node.js Vulnerability - FAQ. 

After reimporting the certificates from Qlik Sense into NPrinting, tasks may no longer publish correctly to the hub.

The following warning is displayed: 

Cannot publish to Sense Hub. ERROR: The remote server returned an error: (403) Forbidden

Environment

• Qlik NPrinting  all versions after an upgrade from Qlik Sense Enterprise on Windows February 2020

Resolution

1. Log in the NPrinting server with the account that is used to run NPrinting services
2. Delete the certificate called QlikClient in certificates - Current user -> Personal -> Certificates
   1. Launch Microsoft Management Console (mmc.exe) on the NPrinting server
   2. In the MMC, go to File > Add / Remove Snap-in...
   3. Select Certificates and click Add
   4. Select Computer account, click Next, select Local computer and click Finish
   5. In the MMC, go to Certificates (Local Computer)/Personal
   6. Locate the QlikClient certificate and delete it
3. Reimport the certificates from Qlik Sense as documented in: Connecting Qlik NPrinting with Qlik Sense 

Despite having a device that apparently matches the requirements, Qlik Sense Mobile for Android is not listed on the Google Play Store. Using a direct link to the app page will result in the message “Your device isn't compatible with this version.”

Environment

• Qlik Sense Mobile  for Android, any

Resolution

You will need to use a device that runs on a 64-bit instruction set (arm64-v8a)

Cause

Sometimes, even if the chipset in the phone is capable of 64-bit, it still runs in 32 bit mode. 
This happens when device uses a 32-bit CPU instruction set (armeabi-v7a).

More details can be found at these external links:

• What is the difference between armeabi-v7a, arm64-v8a, x86?
• How to Check Android Phone’s Processor (ARM, ARM64, or x86)

What is CheckSum?

An MD5 checksum is a mathematical algorithm is usually a set of 32-character hexadecimal letters and numbers that are computed on a file with a tool. These numbers are generated using special tools that employ “cryptographic hash function producing a 128-bit (16-byte) hash value”. It is used not only to encrypt a ZIP archive or an EXE installer but all kinds of files. You can assign an MD5 sum even to a text or document file. The perfect match of MD5 checksum value ensures that the digital integrity and security of a file has not been broken by someone else and also that it is the accurate copy of the original file.

Thus, there are the two main reasons if the MD5 hash value of a file you downloaded does not match against the original sum:

The file might be modified by someone else in an unauthorized way.
The file was not downloaded properly and some of its elements might have been corrupted.

How does CheckSum work?

A file is pushed through an algorithm, which outputs a unique alphanumeric string called a checksum, also known as a "hash". Different files, even those with minute differences, produce different checksum values.
There are multiple algorithms that can be used to produce a checksum value. The algorithm can be MD5, SHA-1, SHA-256, and SHA-512, etc.

How to calculate the CheckSum of a file (Windows)

Option1:

1. Open Windows Powershell from the Windows menu.
2. Get-FileHash <filepath> -Algorithm MD5. Example can be:

            Get-FileHash "C:\Users\bww\Downloads\Qlik Alerting Installer (2).exe" -Algorithm MD5

       3. Press Enter

Option2:

1. Download the latest version of WinMD5Free.
2. Extract the downloaded zip and launch the WinMD5.exe file.
3. Click on the Browse button, navigate to the file that you want to check and select it.
4. Just as you select the file, the tool will show you its MD5 checksum.
5. Copy and paste the original MD5 value provided by the developer or the download page.
6. Click on Verify button.

The Windows event logs are filled up with the entry and restarting the Qlik Sense services stops this problem for a short time.

ERROR: null value in column "payload" violates not-null constraint
DETAIL: Failing row contains (255769031, 2020-12-09 11:27:18.845765-06, DEBUG, 76, QlikSensePrintingWebSocketProxy, servername, printing, 10696, null).
CONTEXT: COPY log_entries, line 8

STATEMENT: COPY public.log_entries (entry_timestamp, entry_level, thread, logger, process_host, process_name, process_id, payload) FROM STDIN WITH BINARY

Environment

• Qlik Sense Enterprise on Windows  November 2020
• Qlik Sense Enterprise on Windows  February 2020

Resolution

R&D identified a 3rd party library (SuperSocket) which by default uses log4net as its logger, being the same Qlik default logger this is used and a null value is written. R&D is working on a fix. 

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support at support.qlik.com with the ID QB- 3361 for reference.

Workaround:

A possible workaround is to change the table log_entries in the QLogs database to accept NULL values. 

cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"

• psql.exe -h localhost -U postgres -d QLogs -p 4432 -c "ALTER TABLE log_entries ALTER COLUMN payload DROP NOT NULL;"

Fix Version:

Qlik Sense Enterprise on Windows April 2021

Cause

Product Defect ID: QB-3361

A Qlik Sense Enterprise for Windows server is used by different customers.

Qlik Alerting will be used with it, but the Qlik Alerting environments must be separate, so that users from a customer cannot see the users from the other one when setting up alerts.

Is it allowed to run different instances of Alerting connecting to the same Qlik Sense server? Will the license allow this?

Environment

• Qlik Alerting, any

Resolution

This is technically possible, and the license won't prevent multiple Qlik Alerting servers from connecting to the same Qlik Sense Enterprise for Windows environment 

When trying to connect from Qlik Alerting to Qlik Sense during the first setup, the error "HTTP-400","title":"Invalid request.","detail":"Bad Request" is displayed.

The HAR file provides some more details:

{"error":[{"code":"HTTP-400","title":"Invalid request.","detail":"Bad Request"}],"errors":[{"code":"HTTP-409","title":"Conflict.","detail":"The request could not be completed due to a conflict with the current state of the target resource."}]}

Environment

• Qlik Alerting, November 2020

Resolutions

• The issue might be due to Qlik Alerting being installed on a Domain Controller. If so, please, install Qlik Alerting on a standard server.
• Make sure to have a license assigned to the user used by Qlik Alerting
• Upgrade to November 2020 SR1 or higher, since that includes improvements in the connection between Qlik Alerting and Qlik Sense

Every time you upgrade Qlik Sense you get a warning about your certificates and are forced to recreate the root like you were impacted by the Node.js vulnerability issue fixed in early 2020

Unfortunately the check on the certificate is run on against a localised string, meaning that the check always fails in versions of windows running in a language other than English.

Being forced to recreate the certificate means you also have to redistribute the certificate to rim nodes and can disrupt links to cloud deployments.

Environment

• Qlik Sense Enterprise on Windows  February 2020 or later
• Account is running in a language other than English

Resolution

This is expected to be fixed in the Qlik Sense February 2021 installer.

Workaround:

Change the OS language to English before installing

Cause

Product Defect ID: QB-3243

Issue:

The Qlikview Distribution Services (QDS) is not running any tasks. In the Windows event logs you get the error:

*The description for Event ID ( 0 ) in Source ( QlikView Distribution Service v12.50.20200 ) could not be found.

Either the component that raises this event is not installed on the computer or the installation is corrupted.You can install or repair the component or try to change Description Server.

Failed to create QlikView Engine.. Exception=System.Runtime.InteropServices.COMException (0x80004005: Error HRESULT E_FAIL has been returned from a call to a COM component. ||    at QlikView.Global.DoLogProcessSummary() ||    at QVBWrapper.Document.CreateQVBProcess(ILogBucket logBucket, Boolean createEmptyDoc)

and/or

The Open Procedure for service ".NETFramework" in DLL "C:\windows\system32\mscoree.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

The COM+ Event System failed to create an instance of the subscriber {128EC798-ADC6-4F75-9569-3E81D6092559}.  StandardCreateInstance returned HRESULT 8000401a.

Environment

• QlikView November 2018 (12.30)
• QlikView April 2019 (12.40)
• QlikView April 2020 (12.50)

Resolution

Repair  the installation of .Net 4.7.2 or higher on the server. Then reboot one more time.

Cause

Broken .Net installation

Related Content

You can find the .Net Repair tool here:

https://support.microsoft.com/en-gb/help/2698555/microsoft-net-framework-repair-tool-is-available

Environment

• NPrinting All Supported Versions

Symptoms:

• NPrinting Web Console may appear 'stuck' and does not response after logging in
• NPrinting Scheduler and Engine services may fail to start.
• When logging into the web console, you may see an error as follows: "Error trying to open the page"
• Can no longer access any pages such as connections, apps, reports etc. after logging into the web console
• Accessing links in the Web Console is very slow
• The License Page is repeatedly presented to you

Solution:

• Follow the link in the Related Content section of this article to resolve the issue

Related Content 

• Identify wrong NPrinting database version restored to NPrinting Server

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.

Qlik Sense Enterprise on Windows comes with a set of databases:

• Qlik Sense repository database (QSR)
• Qlik Sense services database (SenseServices)
• Qlik Sense message queue database (QSMQ)
• Qlik Sense logging database (QLogs)
• Licenses service database (Licenses)

For an up to date list of databases, check the Qlik Online Help for your respective Qlik Sense Enterprise on Windows version. 

Resolution:

The names of these databases cannot be changed.

When trying to connect to Qlik Alerting over https, the Qlik Sense Extension displays a "Could not retrieve user info" error.

Environment

• Qlik Alerting, any
• Qlik Sense Enterprise for Windows, any

Resolution

In order to connect to Qlik Alerting over https, you'll need to use:

• a fully qualified domain name for the Qlik Alerting server
• an SSL certificate that goes with the fully qualified domain name

Please, refer to the help site for details.

Until you get a certificate you will need to use http for both Qlik Sense and Qlik Alerting, since browsers won't allow mixed content.

Simplifying a single or multi node installation. This technical paper aims to break down the QlikView installation procedure into a simple step-by-step guide.

What you will find:

• Instructions for a simple Single Node setup
• A Multi Node scenario built on Certificate Trust
• Links to relevant and related content Tips and Tricks as collected by Qlik Support to help tackle challenges