End of Support for Qlik products follows Release Management Policy, as documented in the Product Terms found on the Qlik Site: On-Premise Products Release Management Policy

For detailed information on end of life and release dates, see:

 Qlik GeoAnalytics Product Lifecycle.

A Data Connection to SharePoint list in QlikView/Qlik Sense fails. When trying to connect, the user receives an error:

Access is denied: the authentication has failed or has not been provided

Resolution:

The authentication error when connecting to SharePoint is caused by the service account ID not being passed to the zone. We will need to modify settings to allow for UserID and Password to be passed.

In order for QlikView/Qlik Sense to be able to connect to a SharePoint list using a URL, a local policy setting must be used. To add this local policy, perform the following steps on the QV publisher server(s) / QS Central Node (&Proxy RIMSs).

1. From run enter gpedit.msc and press <enter>
2. Under Computer Configuration expand administrative templates
3. Expand Windows Components
4. Expand Internet Explorer
5. Expand Internet Control Panel
6. Highlight Security Page
7. Under Security Page you will see Site To Zone Assignment List
8. In the window on the right hand in the upper left corner you will see Edit policy setting. Click on what looks like a link. That will open up a window for the policy setting.
9. Make sure the Enable radio button is selected.
10. Click on the show button.
11. This will open up a show contents window
12. In the value name box key in domain you want to allow (SharePointsite).
13. In the value box key in a “1”. This will set the domain to local Intranet. This will allow any account on the server to connect to the domain via a URL.
14. Click Ok, then Click Ok again.
15. Close the Local Policy Editor

Related content:

How to load an Excel file from sharePoint to Qlik Using Qlik Web Connectors
Fetching data from files on SharePoint with Qlik Sense

This issue can affect multiple products (QlikView, Qlik Sense, NPrinting, etc..)

One more more services are not starting in the Windows Services Console. The message below is displayed:
...
Error 1069: The service did not start due to logon failure
...

The Engine logs may register from when the services were still running:
...
Command=Open app;Result=1003;ResultText=Error: App not found
... 

• Qlik Sense Enterprise on Windows , all versions
• QlikView Server, all versions
• Qlik NPrinting , all versions

Cause:

This may indicate that the service account, or service account password, currently used by the Qlik Services is incorrect. To resolve the issue, update the credentials in the Windows Services Console. Other reasons for this issue include:
     -  If this does not work it may be because the account is locked. Contact the server or domain administrator to unlock the account.
     -  Or the password has expired
     - Service account no longer has local administrator rights
     - Service account no longer has Logon As a Service rights

Resolution:

Note: Please note that for Qlik Sense the Repository Database Service has to be executed by Local System at all times.
1. Right click the Service > Properties > Log On > Change the account credentials/password to be correct.
 

2. Under Windows Local Security Policies > Security Settings > Local Policies > User Rights Assignment > Log on as a service, make sure the service account is added.
3. Make sure service account is a local administrator. Under Local Users and Groups > Groups > Administrators, add the service account.

Related Content:

Qlik NPrinting Engine service - Error 1069, 1067, 1053 

Oracle OLEDB data connection can not be set up through the Qlik Sense connection wizard. The wizard dialogue gets stuck in an endless progress spinner.

ODBC connection to the same database server works from Qlik Sense. 

Environment:

• Qlik Sense Enterprise on Windows 

Name resolution to the Oracle DB System is not working.

Resolution:

Edit Windows hosts file (C:\Windows\System32\drivers\etc\hosts) and add IP and hostname pointing to the Oracle database server. 

This article supplements documentation that requires changes to the Qlik Sense Engine Settings.ini. No settings are provided in this article. 

Steps:

1. Stop the Qlik Sense Engine and Qlik Sense Service Dispatcher services on all nodes with engines.
2. For each of the nodes: open Notepad as Administrator
3. Open the Settings.ini file. Default location: C:\ProgramData\Qlik\Sense\Engine\Settings.ini
4. Modify the file to fit this schema:
   

   [Settings 7]
   Key=Value
   

   
   Note the blank line at the end of the file.
   
   The file will look like this:
   
   
   
   
5. The key and value will be provided by other knowledge articles or by a Qlik Support technical resource
6. Save the file
7. After these changes have been made on all nodes, start the Qlik Sense Engine and Qlik Sense Service Dispatcher services on each node.

If you are looking to modify the Qlik Sense Desktop client settings.ini:

• The file is found in:  C:\Users\<username>\Documents\Qlik\Sense\Settings.ini 
  Where <username> will be the user who installed Qlik Sense Desktop.
• The steps remain the same, although no services need to be restarted.

The Qlik Sense Management Console (QMC) lists specific nodes as offline.

The Repository Trace System logs (default C:\Programdata\Qlik\Sense\Log\Repository\Trace\) the following error is registered:

Failed to retrieve service status from 'http://ServerName:4444/status/' (Unable to connect to the remote server)

Resolution:

Possible points of failure to correct:

• The Rim node is not listening on the port 4444. The command netstat -bano | findstr 4444on the Rim server to determine if listening. Otherwise, restarting the services on the Rim node might help. Follow the order documented under Manual Start and Stop order of Qlik Sense services
• The communication between the Central node and the Rim node via port 4444is blocked. You can use this article to determine that How To Check Open Ports Using PowerShell 

Cause:

To get the service status from the Rim node, the Central node needs to make request to the Rim node which is supposed to be listening on port 4444.

Environment: 

Qlik Sense Enterprise, all versions

Qlik Sense Hub requires Web Sockets connectivity. You can check if your browser works with Web Sockets.

You can verify if your system is WebSocket ready by using this 3rd party website: http://websocketstest.com/

An example (positive) result should look like this: 

For more in-depth investigation, see Qlik Sense Websocket Connectivity Tester.

When customers are using AD or Windows for QlikSense authentication, sometimes they may experience the issue to automatically login to Qlik products with the wrong accounts and do not have the chance to re-enter the correct login as it is using SSO. 

Environment:

Qlik Sense Enterprise on Windows 

Resolution:

Here are a few configuration options to correct this issue:

Option 1: Set up Forms authentication

See Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub 

Option 2: Configure the local client to prompt for login

The instructions provided here apply to Internet Explorer. Consult other browser vendors for details on their software. 

1. Start Internet Explorer
2. Open Internet Option
3. Go to Security
4. Select the Zone which the Qlik Sense Hub falls under (Intranet, Internet, etc...)
5. Select Security Settings
6. Locate and configure Prompt for user name and password
   
   

HTTP Response Header exposes Microsoft-HTTPAPI/2.0 as the server source. An attacker could use this information to expose known vulnerabilities for the server source.

Resolution

This header is included in the HTTP header by .NET framework, which means it can not be directly controlled by Qlik software. 

Environment

Qlik Sense Enterprise on Windows, all version
QlikView, all versions
Qlik NPrinting, all versions

Internal Investigation IDs:

• QLIK-90522

Data Connections are created either inside a Qlik Sense App or on the hub in the Data Manager. 

To create a Data Connection on a Qlik Analytics Platform (which disables the ability to directly create and manage apps on the hub) do the following: 

1. Create an app in Qlik Sense Desktop
2. Create data connections in Data load editor
3. Import *.qvf file to Qlik Analytics Platform
4. The data connection will also be imported to Qlik Analytics Platform

If you develop apps in Qlik Sense Enterprise, you can use the same technique.
Just to create an empty app in Qlik Sense Desktop with data connections. Then import.

The Qlik Sense hub is by default available on:

https://hostname/hub or https://hostname.fqdn.com/hub.

By creating a DNS alias and correctly configuring the connected network infrastructure, this can be changed. 

If you are looking for information on how to change the host name of the server, see Qlik Sense: Change hostname (and certificates) after an installation.

Resolution:

1. Create an Alias(CNAME) in the DNS for the Hostname (Server). 
   
    
2. Add the IP address and the newly created CNAME in the Host Allowlist. 
   See How to configure the WebSocket origin white list and best practices for details.
   
   
3. Ensure all the Qlik relevant ports are opened for the client network.
   See Required Ports for Qlik Sense Enterprise for details. 
   
   
4. Restart all Qlik Sense services. 
   
   
   
   

Related Content

Qlik Sense: Change hostname (and certificates) after an installation
Required Ports for Qlik Sense Enterprise 
How to configure the WebSocket origin white list and best practices 
Unable to access Qlik Sense Hub and QMC using DNS alias: The target name used is not valid 

User is implementing example code as per help: IQMS2.GetCALConfiguration Method

Timestamps returned for Last Used are not reflecting what was reported in QlikView Management Console, despite considering UTC format. 

Only accessing the QlikView Management Console before issuing the GetCALConfiguration is presenting the expected value.  

Environment:

QlikView 

The GetCALConfiguration is retrieving its values from the QlikView Server cache.

Before calling the API GetCALConfiguration clear the QVS Cache from the current CAL Configuration using ClearQVSCache  and as parameter QVCacheObjects.CALConfiguration . 


 
 

Qlik Sense Enterprise on Windows allows for the counting of active sessions using its backend APIs.

This can be achieved using Qlik-Cli.

Environment:

Qlik Sense Enterprise on Windows 

Resolution:

1. Have Qlik-Cli installed and configured (see Installing Qlik-Cli for more insight on how to install and configure Qlik-Cli)
2. Connect to the Sense site. Example command here(bolded text is configurable): Connect-Qlik -computername QlikSenseServer.company.com -username DOMAIN\UserName
3. Run Invoke-QlikGet command to the API path. Sample command: Invoke-QlikGet -path https://QlikSenseServer.company.com:4747/engine/healthcheck
4. Inspect the session JSON response for the number of active sessions:
   
   

The QlikView Server environment using certificate trust for communication stops working without any system changes other than Windows Updates being applied. 

QlikView Services have the status 'disconnected' in the QlikView Managment Console although they are definitely up and running. You see the following error in the respective QlikView service log:

SSL: Main loop error: -1
SSL: Decrypt Message Error: -2146893008

Environment: 

Microsoft has delivered patches that change how TLS communication is handled in Windows. It affects any application that relies on the .NET framework.

As QlikView 11.20 (up to SR15) relies on an older version of the framework, it cannot communicate using TLS 1.2 so allowing the QlikView binaries is the only workaround for the time being.

Resolution:

The issue can be resolved by uninstalling the following Windows Updates depending on the Server OS version:
 
Windows Server 2012 R2 with .Net Framework 4.6/4.6.1

KB3135998: https://support.microsoft.com/en-us/kb/3135998

KB3142036: https://support.microsoft.com/en-us/kb/3142036

KB3205402: https://support.microsoft.com/en-us/kb/3205402

Windows Server 2008 R2 with .Net Framework 4.5.2

KB3142033: https://support.microsoft.com/en-us/kb/3142033

If uninstalling the updates is not an option, the following workarounds are available currently:

For QlikView 11.20 up to SR15
 
Upgrade to the latest version of QlikView. 
 
For recent QlikView versions
 
TLS 1.2 will need to be enabled by running the PowerShell script attached. 

Allow all QlikView (and IIS service if being used) binaries by running the Version 12 specific .reg file attached to this article. It should be run on every server that runs a QlikView (and IIS) service. If the customer has installed QlikView in a custom folder, you need to edit the reg-file accordingly. I.e. Correct the file paths.  In order to run the file, rename the downloaded file by adding the .reg extension, then right-click the file and choose the Merge option, this will launch the Registry Editor and apply the changes.  Server reboots are required as well for the changes to fully take effect.

Please ensure that you have a system backup available in case of unforeseen issues. Should you have any questions regarding the workaround please contact Support. 

The Qlik Indexing (QIX) Engine allocates and utilizes memory during data reloads and calculation of visualizations. The QIX engine and memory allocation works the same way in Qlik Sense Enterprise, Qlik Analytics Platform, QlikView Server and QlikView Publisher. 

Index:

• Memory Utilization During Data Reload
• Memory Utilization During User Activity
• Memory Allocation On Hardware
• Linear Scaling Of Resources

For system requirements, see: System requirements for Qlik Sense Enterprise | System Requirements for QlikView Server 

Note that system requirements for basic installation do not equate to performance. Each Qlik system will have a different memory, CPU, and disk requirement depending on data, apps, and user behaviour. 

If you are looking for information on how to scale your environment, proceed with this article. For direct assistance, engage with our Professional Services, who can provide you with guidance based on your requirements.

Memory Utilization During Data Reload

Memory is allocated during reload to hold loaded data records and cache results of data value processing. The amount of memory required for the loaded data depends on the nature of the data, in terms of number or rows and symbols required to represent the data. See How Is Data Stored In Qlik Sense And QlikView? for more details on how data is stored in memory. If the loaded data is manipulated during load, this will lead to additional memory allocation to hold cached results of the aggregation or manipulation. After finished reload the cached values related to the reload are purged from memory.

In server side reload the reloaded data model is stored from memory to file, followed by the data in memory being purged. After this there is no remaining memory allocation related to the reload. The application will be loaded into memory again once opened by the server or reloaded again. 
In desktop client the reloaded data model remains in memory as long as the application remains open in the client. If the data model size increased during reload, the memory allocation can appear larger after reload compared to before reload. 

Any manipulation or processing of data values require memory in order to store and handle the associated calculation. As a consequence a reload can consume more memory than the actual loaded data size, if the loaded data is manipulated during load. After finished reload the cached values related to the reload are purged from memory.

The best way to evaluate and estimate the memory required for reload, is to simple reload an app and observe the memory allocation. There can be room for optimisation of reload structure, if memory utilisation is considered too large. It is important to consider data growth over time, when estimating memory need.

Memory Utilization During User Activity

Memory allocation during user activity and interaction consists of three parts;

The parts above lead to a memory usage history as described in Technical Brief: QlikView Server Memory Management And CPU Utilization and exemplified in below images where one or multiple open and accessed apps. 

Estimate the required memory to open a specific app by opening it on a blank sheet. There are no calculations without visualizations, so this will indicate the minimum required memory to open the app. By opening all apps that are expected to be accessed at the same time, it is possible to estimate the total minimum required memory for opening all the relevant apps. 

By opening the apps with a user, the above estimation of memory for opening an app includes one user session. Accessing the apps with for example 10 users enable estimating the memory required for the sessions per user. Multiplying the estimated user session size with the number of anticipated simultaneous users gives an estimation of required memory for expected concurrent user sessions. 

The above estimations added on top of an estimation of how much memory is required for the OS and other processes, will tell how much memory is left for the Qlik server cache. A larger cache enables more reuse of previous calculations, and enables better performance and user experience. Note, reload of the app can lead to cache being purged as previous results can not longer be assumed as valid. 

The memory consumption in QIX engine is considered linear, so scaling needs can be quite easy to evaluate once a base line of expectation has been estimated. 

Memory Allocation On Hardware

Higher amounts of RAM will allow for more cached result sets and typically better performance. Supported memory configurations for best performance should be confirmed with the main board manufacturer. The manufacturer should have guidelines for which configurations of RAM can be deployed whilst keeping the bus speed as high as possible. The QIX engine allocates memory uniformly over all available RAM, meaning that it is important to always have the amount of memory per CPU socket evenly distributed

Linear Scaling Of Resources

Qlik Scalability Center has tested and evaluated how memory scales over different sizes of apps and user loads. These test results show that by adding up the resource usage of individual Qlik apps, it is possible to get a close approximation from a resources perspective of what resources are needed when the apps run in parallel. 

Related Content:

Technical Brief: QlikView Server Memory Management And CPU Utilization
List of Favorable Server Hardware from Qlik Scalability Center

The Qlik Sense installation fails with:

Installation failed
An error has occurred
For detailed information see the log file

The very first step to take when troubleshooting an installation problem is to look at the error message provided by the installer. If it does not contain a useful warning or instructions the next step is to look at the Qlik Sense installation logs.

The installation and upgrade logs are stored in the same place which is the user temporary folder running the Qlik Sense installer. (By default: C:\Users\<Username>\AppData\Local\Temp).

For detailed troubleshooting steps see: Troubleshooting your Qlik Sense Installation or Upgrade 
For general information on how to read installation logs, see: How to read the installation logs for Qlik products

A QlikView Publisher overwrites any manually set file permissions on .qvw files distributed by the Publisher to the User Documents folder. 

Environment:

QlikView 

This is working as designed.

In a Publisher enabled environment, authorisation to QlikView documents is governed by the Publisher distribution task, whether DMS mode or NTFS mode is being used. For more details on how to set up these different methods, please see Authorization on the Qlik Help site.

Example

A QlikView distribution task is set up to distribute documents or all users:

The permissions currently set on the document manually will be overwritten:

The below steps explain how to check a valid certificate in Windows Server. It would need to check it after deploying a new certificate.

This can also be used to verify when a third party certificate (see How to change the certificate used by the Qlik Sense Proxy to a custom third party certificate) expires and needs to be updated. 

Environment:

QlikView 
Qlik GeoAnalytics 
Qlik NPrinting 
Qlik Sense Enterprise on Windows 

Open the Microsoft Management Console and add the Certificates Snap-in.

1. To launch the MMC, open the start menu and in the Run command line type mmc.   
   
   

1. In the MMC navigate to File > Add/Remove Snap-ins...
   
   
   
2. Choose Certificates and click Add. 
3. In the follow up dialogue, choose Local Computer 
4. Click Next and return to the overview menu to click OK. 
    

Locate and open the installed certificate.

1. In the MMC, navigate to Certificates (Local Computer) 
2. Expand Personal 
3. Expand Certificates
4. Open the certificate with a double click or right click. 

Review the certificate.

If it is a valid certificate, the certificate must fulfill the requirement below

• Issued to: Verify server name must match FQDN or domain of the local machine 
• Issued by: Verify Certificate Authority is the expected one
• Valid from: Valid dates between past and future 
• Message: Verify the message's status "You have a private key that corresponds to this certificate"

    

How to check the Product Support/Maintenance Contract end date for a specific Qlik Product License key?

Environment:

LEF license
Qlik Sense Enterprise on Windows 
Qlik NPrinting 
QlikView 
Qlik Web Connectors 

The Product Support Contract End date can be seen under LEF PRODUCTLEVEL attribute (See img 1).

Fig 1

1. The license cannot be applied to a version of the product which was released after the expiration date was reached.
2. The licensee is not entitled to updates
3. The licensee is not entitled to support
4. The license can still be used in the currently licensed system 

• How to view Active and Expired Licenses in Support Portal
• How to request a control number and LEF
• Unable to Apply Evaluation License Due to Expired Time Limit

The Repository service does not start after patch removal or repair installation.

The Windows Application Event logs record the following:

Log Name: Application
Source: PostgreSQL
EventID:0
Level: Error:
User: N/A
General:
...
FATAL: password authentication failed for the user "postgres"
DETAIL: Password does not match for user "postgres".
           Connection matched pg_hba.conf line 80: "host  all       all      127.0.0.1/32        md5"

The Repository > Trace > System Repository logs the following:

Fatal exception password authentication failed for user "postgres"??The provider did not return a ProviderManifestToken string.??An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file

or

ERROR SERVERNAME System.Repository.Repository.Repository.QRSMain 6 <ID> domain\user Fatal exception during startup  Waiting for database timed out after 0 seconds

Resolution

The repository configuration file (C:\Program Files\Qlik\Sense\Repository\Repository.exe.config) has been modified and is no longer passing the correct credentials.

1. Stop all services
2. Backup the Repository.exe.config file (default: C:\Program Files\Qlik\Sense\Repository\Repository.exe.config but is where ever they install Qlik Sense)
3. Open the "Connection String Editor" in QlikSenseUtil.exe
4. If not already, direct it to the Repository.exe.config file (default: C:\Program Files\Qlik\Sense\Repository\Repository.exe.config but is where ever they install Qlik Sense)
5. Use the "Connection String Editor" in QlikSenseUtil.exe to decrypt the Connection String (Click on "Read")
6. Check and see that the password and user ID is correct. If not correct to look as the following:
   

   <connectionStrings>
       <add name="QSR" connectionString="User ID=postgres;Host=localhost;Port=4432;Database=QSR;Pooling=true;Min Pool Size=0;Max Pool Size=90;Connection Lifetime=3600;Unicode=true;Password='ENTERYOURSUPERUSERPASSWORDHERE';" providerName="Devart.Data.PostgreSql" />
   </connectionStrings>​

7. Make the same correction to other strings if present (newer versions), except for the one connecting to the database called "postgres"
8. It is possible that steps in The QSR, SenseServices, QSMQ, and Licenses login role need to be revisited if the password does not match.
9. Save the file
10. Restart all services

Environment:

Qlik Sense Enterprise on Windows