Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.
The behaviour began after an upgrade of Qlik Sense Enterprise on Windows.
This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.
Enable QmcTaskTableCacheDisabled.
To do so:
Upgrade to the latest Service Release and disable the caching functionality:
To do so:
NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.
Should the issue persist after applying the workaround/fix, contact Qlik Support.
Upgrading Qlik Sense Enterprise on Windows does not automatically upgrade the bundled PostgreSQL version. New versions of PostgreSQL are only deployed during a new install. This means upgrading to, for example, Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.
For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:
Content:
The information in this article is provided as-is and to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.
It is highly recommended to test this process in a test environment to get familiar with it.
The first step is to upgrade your environment to Qlik Sense Enterprise on Windows. This article was originally written for May 2021, but can be applied to any version. Follow the required steps and recommendations for an upgrade for your version. Example: August 2023.
Once the upgrade is done make sure your Qlik Sense site is completely operational.
At this point, you have an operational Qlik Sense site running on your new version of Qlik Sense Enterprise on Windows. However, the bundled PostgreSQL is still on version 9.6 or 12.5, depending on the originally installed version.
The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.
You will now need to uninstall Qlik Sense from the central node following these instructions.
During the uninstall:
Now that Qlik Sense Enterprise on Windows is uninstalled on the central node, you will reinstall it as a result will deploy either a bundled PostgreSQL 14.8 (August 2023 and later) or a bundled PostgreSQL 12.5 (May 2021 to May 2023). Instructions available here (choose your version).
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.
You now have a clean Qlik Sense Enterprise on Windows deployed on your central node with PostgreSQL 14.8 or 12.5. You now need to restore your environment to retrieve all your configurations and apps.
Please follow the Restoring a Qlik Sense site (including the certificates).
Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;
pg_restore: warning: errors ignored on restore: 1
Once the environment is restored, you should be able to start your central node and rim nodes successfully.
Qlik Sense Enterprise on Windows May 2021 and later
The Qlikview server has been set up with Kerberos authentication. When navigating to the QlikView Management Console the following errors are printed:
Login Failed
This web page cannot be displayed
Environments:
Kerberos authentication is not supported in the QlikView Management Console.
For information regarding the AccessPoint, see Kerberos support using QlikView Webserver
Upgrading the Qlik Sense Enterprise on Windows PostgreSQL instance using QPI (Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer) fails.
The following is logged in the installation log file:
[ERR] Error! Exception when trying to stop Service: QlikSenseRepositoryDatabase in: 60 s: Cannot open 'QlikSenseRepositoryDatabase' service on computer '.'.. Please make sure you are running the application as an administrator.
[INF] QlikSenseRepositoryDatabase was stopped
[WRN] The service: QlikSenseRepositoryDatabase could not be stopped, tryin to kill process...
[INF] Trying to kill process: 7440
[INF] Found process, checking status
[INF] Could not kill process for some reason: Access denied
[ERR] Error! Failure while: QlikSenseRepositoryDatabase
For information on how to locate the Qlik Sense Installation logs, see How To Collect Qlik Sense Installation Log File.
Ensure the setup file is "Unblocked" and accessible for installation.
The account that is running the setup does not have access permissions.
Qlik PostgreSQL Installer (QPI)
What is the default user session timeout for Qlik Sense Business and Qlik Sense Enterprise SaaS? Can the session timeout for Qlik Cloud be changed?
The default (fixed) value is set to 30 minutes. This is controlled by SESSION_TTL.
It is not currently possible to adjust the session timeouts in the Qlik Cloud.
Qlik Sense Enterprise on Windows was installed and the installation successful, but neither the Qlik Management Console (QMC) or the hub will open.
Qlik Management Console displays error:
Not Found HTTP Error 404. The requested resource is not found.
Note that for the above, Qlik Sense Proxy service was not reached.
For instances where the Proxy service is reached but returns a 404 with a Qlik Sense log displayed on the returned page as the example below....
... please see How to approach Qlik Sense Error 404 Not Found The following URL is unknown for Hub and QMC
It is caused by port conflicts. Proxy Service cannot listen to port 443 or 80 because the two ports are occupied by something else.
Proxy logs may read the following if there are other port conflicts in the environment besides for the apparent conflict on port 443.
https://127.0.0.1:4242 is not reachable.
Here is a detailed explanation:
URL https://<hostname>/qmc or https://<hostname>/hub includes following information:
In a normal environment, port 80 and 443 should be listened by Proxy Service of Qlik Sense, which knows what /qmc and /hub stand for.
It is possible that some other services occupied port 80 and 443 before Proxy Service could do so. Those services, which are not provided by Qlik Sense, do not know what /qmc and /hub stand for. Hence 404 error is returned.
Note: finding out what service is currently occupying port 80 or 443 is not always straightforward and needs to be handled by user's system admin instead of Qlik Support.
Typically, the following command can show which process is using port 443 or 80:
netstat -a -n -o | findstr ":443 :80"
Verify if port 443 and/or 4242 are already bound in the system by 3rd party software by opening a Windows Command line (cmd) and running:
netsh http show urlacl
Search for port 443 and port 4242 and if necessary delete those entries with the following commands:
netsh http delete urlacl url=https://+:443/ netsh http delete urlacl url=https://+:4242/
After deleting the port bindings, restart the Sense services. Now the services can have different ports bound, or the other software be uninstalled/reconfigured. More detailed solutions below.
Please install Qlik Sense Enterprise to a dedicated Windows server. Please uninstall other application that uses Port 443.
Suppose, SQL Server is using port 443. Stop SQL Server services. That would free up port 443.
The Qlik Sense Engine allows for a hard max limit to be set on memory consumption, which, if enabled on the Operating System level as well, will make a best effort to remain below the set limit.
The setting is located in the Qlik Sense Management Console > Engine > Advanced and can be configured as an option in the setting Memory usage mode.
See Editing an engine - Qlik Sense for administrators for details on Engine settings.
This setting requires that the Operating System is configured to support this, as described in the SetProcessWorkingSetSizeEx documentation (QUOTA_LIMITS_HARDWS_MAX_ENABLE parameter).
Even with the hard limit set, it may still be possible for the host operating system to report memory spikes above the Max memory usage (%).
The reason for that is because the Qlik Sense Engine memory limit will be defined based on the total memory available.
Example:
The memory working setting limit is not a hard limit to set on the engine. This is a setting that set how much we allocate and how far we are allowed to go before we start alarming on the working set beyond parameters.
QLIK-96872
While uninstalling the Qlik Sense patch, the setup will fail with the below error,
The older patch could not be uninstalled! Please uninstall the patch manually. This installation will exit.
The installation log file will read the below,
Error! Validation of: D:\Program Files\Qlik\Sense\\Client\1366.f02a********.css failed: Could not find file 'D:\Program Files\Qlik\Sense\Client\1366.f02a********.css'.
Checking if file D:\Program Files\Qlik\Sense\\Client\1366.f02a********.css is locked...
Qlik Sense Installation logs can be found here, (How To Collect Qlik Sense Installation Log File).
In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).
For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.
Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.
Index
Video Walkthrough
Video chapters:
The following versions have been tested and verified to work with QPI (1.4.0):
Qlik Sense February 2022 to Qlik Sense November 2023.
If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.
The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.
Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Download the installer here.
Qlik PostgreSQL installer Release Notes
The following versions have been tested and verified to work with QPI (1.4.0):
February 2022 to November 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a 9.6 update is blocked.
Uninstall the old Qlik Sense Repository Database service.
This step is required. Failing to remove the old service will lead the upgrade or patching issues.
Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts.If you do not immediately upgrade:
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.
Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.
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.3.0 Release Notes
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades
This article provides the steps needed to successfully upgrade Qlik Replicate installed on a Windows Cluster.
repctl -d "YOUR_DATA_DIRECTORY_PATH" exportrepositoryExample: ~Program Files\Attunity\Replicate\bin> repctl -d "S:\Programs\Qlik\Replicate\data" exportrepository
This article provides the steps needed to successfully upgrade Qlik Replicate installed on a Windows Cluster.
repctl -d "YOUR_DATA_DIRECTORY_PATH" exportrepositoryExample: ~Program Files\Attunity\Replicate\bin> repctl -d "S:\Programs\Qlik\Replicate\data" exportrepository
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 configured 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. This is not recommended.
The work flow looks as follows:
The improvement to track the Max concurrent reloads can, if desired, be disabled. This reverts Sense to an older load balancing method that relies only on CPU usage.
To disable the setting:
In our example, we allow one concurrent reload, but we assume that two reloads are executed at the same time.
! Note: Do NOT modify the NPrinting Database for any reason using PG Admin postres query or any other execution tools as this will damage your NPrinting Deployment and prevent successful NPrinting Database backup and restore operations.
! Note: Do NOT restore an older version of an NPrinting Database to a New NPrinting server or restore a newer version of the NPrinting database to an older version of NPrinting Server.
Examples:
These rules apply to general releases and service releases: The point version of the NPrinting Database being restored must match the point version of NPrinting Server being restored to (see Backup and restore Qlik NPrinting).
! Note: From NPrinting February 2020 and later versions, it is NOT necessary to enter a superuser database password
! Note: If you are making a backup for the Qlik Support team, please add the following NPrinting user information so that we can log onto the NPrinting Web Console following the local restore of the database (also ensure that NPrinting Authentication is enabled. Go to Admin > Settings > Authentication
This procedure is meant to backup and restore (partial backup and restore of these individual items is not possible*):
NP Web Console Items:
NP Backup zip File Contents (do NOT open and modify the contents of this file):
NOTE:
c:\nprintingbackups
Before Proceeding: Please log on as the NPrinting service account used to run the NPrinting Web Engine and Scheduler services before proceeding
Open the Windows Service Manager (services.msc), and stop the following services (by right-clicking them, and then clicking Stop). This will ensure any manual or scheduled NPrinting Publish Tasks are not executed during the backup or restore process:
C:\NPrintingBackups
Do NOT modify any syntax or add any additional unnecessary spaces
Open the command prompt making sure to run cmd.exe as Administrator and change directory as follows:
cd C:\Program Files\NPrintingServer\Tools\Manager
Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere
or with Current Supported versions of NPrinting (no password required)
Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"
Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere
Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"
File C:\Users\domainuser\AppData\Local\Temp\2\nprintingrestore_20201203082300\files\xxxxxxxxxxxxxxxxxxxxxxxxxxxx does not exist in the source backup package.
! Note: If re-installing on existing or restoring to a different NPrinting server environment, ensure that the destination NPrinting server license is enabled/activated before restoring the NP database.
NPrinting Engine:
NP Connections:
Qlik Sense Certificates (if using NPrinting Qlik Sense connections)
C:\Program Files\NPrintingServer\Settings\SenseCertificates
Other helpful information about the NP Backup and Restore tool and process:
C:\ProgramData\NPrinting
Note:The pre and post upgrade backup files are appended with the NP version number and backup dateC:\ProgramData\nprinting\logs\nprinting_manager.log
*NOTE:
This article contains steps on how to do backup and restore the Qlik Sense Enterprise on Windows (QSEoW) site.
For full instructions on how to backup and restore a Qlik Sense site, see the online help under Backup and restore Qlik Sense Enterprise on Windows.
For sole database backup information article can be found here: How to backup PostgreSQL database in Qlik Sense
Backup and Restore Targets:
These steps are provided as-is based on latest version available of Qlik Sense product at the time of writing and/or last update to the article. Please make sure to cross-reference these steps with the official documentation for your product version under Backup and restore Qlik Sense Enterprise on Windows.
Downtime is required
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\backup\QSR_backup.tar" QSR
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\dropdb.exe -h localhost -p 4432 -U postgres QSR
.\createdb.exe -h localhost -p 4432 -U postgres -T template0 QSR
.\pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\backup\QSR_backup.tar"
For further reference, consult the Qlik Sense Help Site for your respective version.
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\dropdb.exe -h localhost -p 4432 -U postgres QSR
.\createdb.exe -h localhost -p 4432 -U postgres -T template0 QSR
.\pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\Backup\QSR_backup.tar"
cd "C:\Program Files\Qlik\Sense\Repository"
.\repository.exe -standalone -restorehostname
Please refer to the Backing up Certificates Help site documentation for details and verify that the information matches your current version.
Please refer to the Restoring certificates Help site documentation for details and verify that the information matches your current version.
Normally, It is similar to the section for apps, the path where these files live is in the StaticContent folder on the Share path.
Restoring a Qlik Sense site to a machine with a different hostname
Advanced options is not visible when editing a sheet. This can happen on a specific app even if the option was present before.
You can activate the "Show Sheet Header" option in the app settings to make the "Advanced option" button visible again.
For some reasons, the "Show Sheet Header" could be deactivated in an app. "Advanced Options" is invisible when this happens, because it is located in the sheet header that is removed. The app looks like this in editing mode:
This Techspert Talks session covers:
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
Click here to see video transcript
You have been running Qlik Sense normally for quite some time. Over time you have accumulated an abundance of reload tasks configured in your Qlik Sense QMC.
Recently however, you have noticed that Qlik Sense QMC reload tasks are in the following state:
To resolve the issue, it is recommended to add an additional scheduler node (or nodes) in order to manage the ever increasing number of reload tasks in the affected Qlik Sense environment.
As time goes on, add additional scheduler nodes in proportion to the increasing number of reload tasks added/deployed in your environment.
The existing Qlik Sense scheduler nodes simply cannot manage the additional burden placed upon it by ever increasing reload tasks.
Concurrent Reload Settings in Qlik Sense Enterprise
QB-20013
Upgrading Qlik Sense Enterprise on Windows with a standalone PostgreSQL database to August 2023 or later fails. The installer does not return an error on-screen.
A Qlik Sense Enterprise on Windows environment can have a bundled PostgreSQL database or a standalone database.
If your Qlik Sense environment has relied on a standalone PostgreSQL database since its initial setup, and still has its PostgreSQL 9.6 database and binaries, additional steps are required to prepare for an upgrade to any versions beyond Sense August 2023.
These binaries will be in the following folder:
C:\Program Files\Qlik\Sense\Repository\PostgreSQL\version number
Where version number is 9.3 or 9.6.
The old binaries need to be uninstalled and new binaries installed (on all nodes).
Qlik Sense August 2023 and higher as the target version
Qlik Sense May 2023 and lower as the source version
Before proceeding with an upgrade:
The msi will be revealed.
The msi will be revealed.
The upgrade will be blocked when a 9.6 or 9.3 database binary folder is found. These folders can be in either:
C:\Programdata\Qlik\Sense\Repository\PostgresSQL\version number
C:\Program Files\Qlik\Sense\Repository\PostgresSQL\version number
The failure (400) of Nexus API service causes task execution failed and generates intermittent occurrences of "Unexpected Error" issues with low frequency from plan/task execution.
Nexus Log
10.80.3.171 - admin [01/Apr/2024:05:03:31 +0800] "GET /service/rest/v1/search/assets/download?repository=releases&maven.groupId=xxx&xx&version=2.0.0&maven.extension=zip.md5&maven.classifier= HTTP/1.1" 400 - 184 6 "Apache-HttpClient/4.5.10 (Java/1.8.0_292-ea)" [qtp661824503-136003]
TAC Log
2024-04-01 05:06:48 ERROR ExecutionTaskHandler - org.talend.exception.BusinessException: There is no artifact for task 'job_xxx_ingestion_v2' in NEXUS 3 Repository.
2024-04-01 05:06:48 ERROR ExecutionTaskHandler - java.util.zip.ZipException: error in opening zip file
2024-04-01 05:06:48 ERROR ExecutionTaskHandler - org.talend.json.JSONException: JSONObject["filePath"] not found.
These above logs from both TAC and Nexus reveal that the Nexus server's REST API failed to provide a correct status code (200), which is essential for the successful completion of the TAC zip downloading process. The Nexus API service response resulted in a 400 error and this failure (400) causes the execution of plans/tasks to fail.
The root cause of this failure (400) of Nexus API service issue could be attributed to
Boost the Nexus with longer session time by modifying the following UI settings
Session Timeout
Standard Request Timeout
Extended Request Timeout
Enhance Monitoring