Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
You can open and build an app on Qlik Cloud using a direct link.
To obtain the link:
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.
Qlik offers a range of opportunities to assist you in troubleshooting, answering frequently asked questions, and contacting our experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions).
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Contact Support on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
How to create a case using chat
Log in to manage and track your active cases in Manage Cases. (click)
Your advantages:
If you require a support case escalation, you have two options:
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
Qlik Cloud is a modern analytics and data platform built on the same software engine as QlikView and Qlik Sense Client-Managed and adds significant value to empower everyone in an organization to make better decisions daily. Qlik Cloud allows you to use one common platform for all users – executives, decision-makers, and analysts.
Migrating to Qlik Cloud can help your organization:
This site provides you the tools to monitor, manage, and execute a migration from Client-Managed Qlik Sense to Qlik Cloud.
No two client-managed Qlik Sense Enterprise deployments are the same. And no two migrations will be the same. The processes, procedures, and instructions in this section shouldn’t be considered a cookbook. Rather, they’re meant to guide you.
The Qlik Cloud Migration Center provides a general approach to migration along with sequencing, strategy, and best practice recommendations. It also includes tools such as a Qlik Sense app, scripts, and worksheets to aid in planning elements of the migration.
If your organization has a complex deployment with custom tooling, or sophisticated or complicated data integration pipelines, consider contacting your Qlik Customer Support representative.
This site provides comparisons of QlikView and Qlik Cloud, as well as best practices on how to move content, including information about migration assessments and QlikView document conversions.
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.
Upgrade to Replicate 2022.11 PR2 (2022.11.0.394, released already) or higher, or Replicate 2022.5 PR5 (coming soon)
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) .
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
support case #00066196
support case #00063985 (#00049357)
Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product. This article aims to provide information on where to find information about them or where to download them.
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.
How can I track the usage of my Tenant over time? How are my entitled users using the Tenant?
How can I better understand the usage of Analyzer Capacity vs. Analyzer & Professional Entitlements?
These are a couple of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Entitlement Analyzer for Qlik Sense Enterprise SaaS!
For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Sense Enterprise SaaS customers is available NOW!
These are a couple of the questions that you can answer with the App Analyzer.
For more information and to download the app and usage instructions, see The App Analyzer for Qlik SaaS customers is available NOW!
“How can I monitor reloads across the tenant?”
“How can I see what data connections and files are being used?”
“How can I view reload concurrency and peak reload RAM over time?”
These are a few of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Reload Analyzer for Qlik SaaS!
For more information and to download the app and usage instructions, see The Reload Analyzer for Qlik SaaS customers is available NOW!
“What users and groups have access to space <X>?”
“What users and groups have access to app <X>?”
“How does a user have access to app <X>; via direct assignment, group, or app share?”
“Are there redundancies in policies? E.g., does a user have the same access to a space via a direct assignment as well as a group?”
“Who has what roles across the tenant?”
These are a few of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Access Evaluator for Qlik SaaS!
For more information and to download the app and usage instructions, see New Monitoring App for Qlik Cloud: Access Evaluator
The OEM Dashboard is an application for Qlik Cloud designed for OEM partners to centrally monitor data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas—which would otherwise be a tedious process. This application includes data from the App Analyzer, Entitlement Analyzer, and the Reload Analyzer, all of which are other monitoring applications for Qlik Cloud that provide deep levels of detail on their respective areas. Together, a complete picture can be formed which is crucial to the successful management of an OEM environment.
For more information and to download the app and usage instructions, see OEM Dashboard - Qlik Cloud Application.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
System Performance Analyzer
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
A user is getting the error:
QVX_SYNTAX_ERROR:........Size of dataset is higher than maximum size allowed by license. Please contact your Qlik sales representative for upgrade options.
when using QGA Base there are limits route calculations and location lookups per call. The max route calculations is 400 per call and 50000 location lookups per call. Check out the license metrics for QGA for more info> https://www.qlik.com/us/legal/license-terms
It's good practice to split up large tables when making the connector calls, here's a guide: Splitting up GeoAnalytics connector operations.
The Qlik sense engine Service stops but engine.exe still running.
Qlik Sense Enterprise on Windows
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.
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.
Windows successfully diagnosed a low virtual memory condition
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.
This video demonstrates the basics on how to switch from Client Access Licenses (CALs) to the new Professional and Analyzer Access licensing.
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.
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.
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
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
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:
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.
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.
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
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,
Create the Relaying Party Trust for the "adfsapache" Virtual Proxy in ADFS
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
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
In our example, we configure the files to be deleted immediately after download.
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.
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".
You can open and build an app on Qlik Cloud using a direct link.
To obtain the link:
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.
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:
Qlik Sense Enterprise on Windows installations other than in C:\Program Files\Qlik\Sense are currently not supported.
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
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:
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.
Download the installer here.
Qlik PostgreSQL installer version 1.2.1 Release Notes
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.
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.
If you want to instead fully migrate an app to Qlik Cloud and make them available for modifications, then the app needs to be manually uploaded to the hub. Alternatively, we offer an automated option using the Qlik-cli (see the app import command).
Example Multi-Cloud App distribution setup in Qlik Sense
How To Publish Qlik Sense App to Qlik Cloud and Edit a Published 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
QlikView 12.50 and above
We can further configure the timeout using a setting for the QVManagementService.exe.config.
<appSettings>
<!-- ****** General ****** -->
</appSettings>
<!-- Setting in seconds which the QMS will wait for the QDS to deliver the list -->
<add key="GetSourceDocumentTimeoutSeconds" value="120" />
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.
The default timeout is 30 seconds.
The max concurrent reloads can be configured in the Qlik Sense Management Console.
<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
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:
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:
*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:
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.
When the account is blocked, you need to reset the password. Please follow the steps below.
If you are unable to access your account still, please contact Qlik Support.
Note: Suggest clearing space from all other Windows temp and other storage folders from the NPrinting Server or Engine computer(s) c:\drive.
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:
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:
Qlik NPrinting , all versions
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 )