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
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical 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 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)
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)
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.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
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 Chat Now 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:
Log in to manage and track your active cases in Manage Cases. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
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.
Navigation:
Migrating to Qlik Cloud can help your organization:
Q&A with Qlik: Qlik Sense Migration to Qlik Cloud
Articles relevant to migration and new Qlik Cloud users
This site provides you the tools to monitor, manage, and execute a migration from Client-Managed Qlik Sense to Qlik Cloud.
Index and home
Planning your migration
Setting up the Qlik Cloud migration tools
Create and configure a cloud tenant
This site provides you the tools to begin your journey to move from QlikView to Qlik Sense and Qlik Cloud.
Some script logs are not transferred to Archive log Folder.
Storage Locations:
Qlik Sense log folder:
C:\ProgramData\Qlik\Sense\Log\Script
Log names consist out of the AppID and a year, date, and timestamp.
Archived log Folder:
\\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script
Log names consist out of the AppID and a year, date, and timestamp.
By design, not all script logs are transferred to the Archived logs folder. Reloads executed from the hub are not transferred.
1. When reloading data in app via hub, Script log will be left in Script log folder C:\ProgramData\Qlik\Sense\Log\Script
2. When reloading data via QMC/task, Script log will be transferred to Archived logs folder \\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script
Security Rules can be configured to allow end-users to reload tasks directly from the Qlik Sense Hub. This way the users who don't have access to Qlik Sense Management Console can run the tasks that are created for the app directly from the hub.
Security Rule examples are provided as-is. Further customization cannot be supplied by Qlik Support and we recommend engaging with our active community in the Qlik Sense Management forums for further assistance.
Note: Too many tasks run in parallel by users can cause a performance impact.
The specified users can now right-click on the hub to access the Management Reload Task (rule a) or/and Reload option (rule b). See Fig 1.
Fig 1
Clicking Reload to initiate the reload and open the App in a new tab.
Clicking Manage reload tasks to access all available reload tasks for this App. Tasks can then be started (Fig 2) or stopped (Fig 3)from this menu.
Fig 2
Fig 3
The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."
Please, reach out to your account manager to have that fixed.
When trying to use Qlik Data Transfer for the first time after a correct installation, you might have the below white screen:
Having a white screen basically means one of the Qlik DataTransfer micro service is not started and/or not working. This can be checked in the Windows Event Application (Source: Qlik Sense Service Dispatcher) or in the Qlik DataTransfer logs (C:\ProgramData\Qlik\DataTransfer\Log).
In the \DataUploadService logs you will see this error message:
23 20211115T131155.794+0100 localhost 6.0.0 Global INFO Responding certificates after reading it from defined location.
24 20211115T131155.844+0100 localhost 6.0.0 Global ERROR Unable to unlock the ReloadService, cannot continue.
25 20211115T131155.845+0100 localhost 6.0.0 Global ERROR Exception: Error: Unable to unlock the reload service.
This error message is happening directly after the step of reading certificate:
INFO Responding certificates after reading it from defined location.
It will be needed to delete the 2 duplicates (where there is no Friendly Name), and then restart the Qlik DataTransfer service.
In that situation it would be needed to install the certificate and/or check why your system prohibit the certificates installation.
It could be a group policy preventing the installation of the needed SSL certificates. Or some missing rights for the Windows account.
Proposed action
If only Qlik DataTransfer is installed on the machine, do the following:
In Windows Services, stop the Qlik DataTransfer service.
Navigate to C:\Program Files\Qlik\DataTransfer\DataUploadService\install-utils.
Run Remove-Certificate.ps1 in PowerShell.
Start the Qlik DataTransfer service.
Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:
client.pfx
server.pfx
If Qlik DataTransfer and Qlik Sense Enterprise on Windows are installed on the machine, do the following:
In Windows, Services, stop the Qlik DataTransfer service.
In the Windows Certificate Store, delete the following certificates:
Local Computer > Personal > QdtClient
Local Computer > Trusted Root Certification Authority > <hostname.domain> or <hostname>
Current user > Personal > QdtClient
Alternatively, you can run Remove-Certificate.ps1 in PowerShell as the administrator.
Run Configure-Service.ps1 in PowerShell as the Qlik Sense services user.
For the first input dataTransferCertificatePath, enter C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate.
For the second input qsefwPresent, enter Yes.
Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:
root.pfx
client.pfx
server.pfx
Restart the Qlik DataTransfer service.
Installing and Using Qlik DataTransfer
Troubleshooting Qlik DataTransfer
With Qlik Application Automation, you can get data out of Qlik Cloud and distributing it to different users in formatted Excel. The workflow can be automated by leveraging the connectors for Office 365, specifically Microsoft SharePoint and Microsoft Excel.
Here I share two example Qlik Application Automation workspaces that you can use and modify to suit your requirements.
Content:
Video:
Note - These instructions assume you have already created connections as required in Example 1.
This On-Demand Report Automation can be used across multiple apps and tables. Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance.
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.
This article is meant to get users starting on the Oauth connector in Qlik Application Automation.
This connector is meant for advanced users to platforms where we did not (yet) build a dedicated connector for.
The connector makes use of the authorization code flow of Oauth2. The authorization code flow is well explained on the following link: https://oauth.net/2/grant-types/authorization-code/
First start by looking for the connector "OAuth2". When you click on connect it requests the following input parameters:
When all of this is provided and you click the Save button, it will open a popup taking you to the login screen where you will be prompted to provide consent. Your connection is now ready to be used.
When selecting the connector in an automation you will notice Raw API Request block. This block has the following input variables:
Apart from the above input variables, RAW API LIST blocks have the following input variables
Input variables | raw API list request - page number based paging | raw API list request - offset based paging | raw API list request - cursor token based paging | raw API list request - cursor URL based paging |
Page Size Field Name | Yes | Yes | Yes | Yes |
Page Size | Yes | Yes | Yes | Yes |
Offset Field Name | Yes | |||
Page Start | Yes | Yes | ||
Json Path For Output Records | Yes | Yes | Yes | Yes |
Json Path For Cursor | Yes | |||
Output Name For Cursor Token | Yes | |||
Page Number Field Name | Yes | |||
Json Path For Cursor Url |
Yes |
The following example will obtain tasks from the Microsoft Todo application. We do not yet have a connector to do this and Oauth is used to obtain the value for the Authorization header.
We first start by obtaining the Authorize URL, Access Ttoken URL and Refresh Token URL. From the Microsoft documentation we can find these at https://docs.microsoft.com/en-us/graph/auth-v2-user. We use the following values:
The documentation of the Microsoft Graph API can be found at https://docs.microsoft.com/en-us/graph/use-the-api?context=graph%2Fapi%2F1.0&view=graph-rest-1.0.
We obtain the Base URL: https://graph.microsoft.com/v1.0.
We will have to obtain a client ID and client secret. We can do the registration for an app at https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade. We register a new application, give it the name "Todo App" and set it to only allow accounts from this organizational directory only. For the redirect url the following value needs to be provided: https://connector.qlikcloud.com/callback. Set the platform to Web.
On the next screen you can obtain your Client ID. Copy this value. Click on Add a certificate or Secret and it will take you to a page where you can create a new client secret.
Create one and copy the value that is now visible.
In the left sidebar click on the button API Permissions. Click on Add a Permission and provide the scope Tasks.ReadWrite.
Back to your connector configuration - Provide the client ID and client secret that were obtained and for the scopes provide the following: User.Read Tasks.ReadWrite offline_access openid
Now click on Save and you should be presented with a screen to login.
1) Raw API Request block:
Create a new automation and drag the Raw API Request block on to the canvas. Set the path to /me and the method to GET. When you now execute it, you should receive a JSON result containing the keys response, headers and status. Most relevant information should be part of the response.
Next let's obtain a list of tasks. Drag another Raw API request block and put it below the earlier one. Set the path to /users/{$.rawApiRequest.response.id}/todo/lists and method should remain at GET. Now when you execute this, it will return you the lists you keep in Todo.
2) List Blocks: Depending on the type of pagination, we have 4 different List blocks. Therefore, depending on the type of pagination in API, any one of the List blocks should be used for a certain API.
We tested the blocks using four distinct APIs, each with a different pagination implementation.
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.
Beginning with QlikView May 2021, the QlikView Publisher no longer installs PDF-XChange and will default to Microsoft Print To PDF.
How to generate PDF reports on a Windows 2012 server, since Print To PDF is not installed there?
Have the PDF X-Change 3.0 installed with a previous version of QlikView. If you begin with 12.60, follow this article.
After PDF X-Change 3.0 has been installed, follow these steps:
Additional third party printers have not been tested. In case of performance or stability issues, install one of the two supported printers (PDF X-Change or Microsoft Print to PDF).
QlikView May 2021 (12.60) on a Windows 2012 server
Currently, in Qlik Application Automation it is not possible to export more than 100,000 cells using the Get Straight Table Data block.
Content:
To overcome this limit, the workaround is to export records in batches from the Qlik Sense straight table to the cloud storage platform of your choice. The prerequisite is to have a unique numerical field in your dataset. If you don't have the unique field in your dataset, you can add it using RowNo() function in the load script as shown below. This counts the rows in the dataset.
In this example, we will export data from the Qlik Sense straight table to Dropbox as a CSV file.
You can also find an exported version of this automation and application attached to this article. More information on importing automation can be found here.
Automation Part 1
Automation Part 2
Automation Part 3
Before reading this, please refer to the official QlikView Authentication - Qlik Online Help and your specific version for details.
QlikView allows for a number of 3rd party, custom authentication methods to be implemented, which may leverage an Identity Provider (IdP) of choice. However, many aspects of this integration is limited to best-effort support from Qlik Technical Support. See How and When to Contact the Consulting Team?
By default. QlikView only interacts with Windows using the appropriate APIs in the background, allowing Windows to carry out any authentication attempts and passing that information to the QlikView system. Custom Users in the Directory Service connector are a second option, which allows QlikView itself to do authentication.
Any other user repository will require external, 3rd party implementations.
! 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 document includes some possible examples in a QlikView 11 implementation of WebTickets and Header authentication, with examples from .NET, PHP, and LDAP integrations. The examples are provided as is.
! The document references http://localhost:4730/qtds.asmx, which was a valid URL used in QlikView 10 (no longer supported).
This function has been removed in QlikView 11.
! The document references a WebTicket implementation limitation:
A current limitation is that the QVWS or IIS used in steps 2 and 3 (i.e. the server you collect the ticker from and the server you redirect the user to) must be the same machine.
This limitation no longer applies in the current QlikView 12 and 11.20 versions.
SQL server table partitions will be excluded from CDC if the partitions are not found to be uniform. Partitions will not be uniform if only some of the partitions are compressed/uncompressed.
In some occurrences, you may also find that partitions can become non-uniform even when all partitions are uncompressed or compressed. The offset position values of the partitions no longer match with each other which will lead Qlik Replicate to log the following warning message.
Table 'schema.table' is not uniformly mapped across partitions. Therefore - it is excluded from CDC
The indexes of the partitions will need to be completely rebuilt if the offset position values have changed and the warnings are received. This fix is only intended for scenarios where all partitions are either uncompressed or compressed.
Limitation:
CDC is not supported from tables which have both compressed and uncompressed partitions.
If only some of the partitions are compressed, the following message will be shown: Table 'xxx' is not uniformly mapped across partitions. Therefore it is excluded from CDC.
For instances where all partitions are either compressed or uncompressed, the same warning message will be displayed if partitions are still found to be non-uniform.
The following query can be used to check the offset position values of the partitions. The values are expected to be the same for all partitions for them to be considered uniform. Partition id and schema will need to be changed to reflect your own values.
select
c.colid as col_id,
c.length as col_len,
pc.leaf_offset as xoffset,
pc.leaf_bit_position as bitpos,
pc.leaf_null_bit as null_bit_pos
from syscolumns c ,sysobjects o, sys.system_internals_partition_columns pc
where
(c.colid = pc.partition_column_id) and
(c.id=o.id and o.uid = schema_id(N'dbo')) and
o.name = N'dm_pa' and
o.xtype = N'U' and
pc.partition_id = 72057596702621696 and
pc.is_uniqueifier = 0 and
pc.is_dropped = 0 and
c.iscomputed = 0
order by c.colid;
RECOB-6727
Qlik Replicate
SQL Server source endpoint
Datetime2 datatypes should be used in place of the datetime datatype. Qlik Replicate tasks will default to datetime2 datatypes although the datetime datatype can still be used. The datetime datatype can have a loss of precision for milliseconds when in use through the ODBC layer for update operations. This may cause updates to not apply as the loss of precision for the timestamp will cause a mismatch with the original record. The Replicate task will proceed to move the update to the apply_exceptions_table and treat the updates as '0 rows affected'.
This scenario will affect tables that do not have Primary Keys or Unique indexes and MS-CDC is used for replication. In the event that MS-CDC is used, the before images of the datetime columns are also used to check for changes. The before image will not be found due to mismatches from loss of precision.
In the table settings of the table, change datetime datatypes to datetime2 datatypes. The tables will need to be reloaded.
The design of the datatime datatype goes through some calculations that lead to inaccurate millisecond values for updates when ODBC is involved. Millisecond values are only accurate if they end with 0,3,7 values. Other values are off and will cause a mismatch between the original record and the new copy of the before image.
Datetime2 is the redesigned datatype of datetime and does not exhibit the same behavior with the use of ODBC.
RECOB-7133
Qlik Replicate
Microsoft Azure SQL Database target endpoint
You can access Qlik Sense demo apps from https://demos.qlik.com/.
If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.
If you are looking to download demo apps:
This article provides a step-by-step guide on building a write back solution with only native Qlik components and automations.
Content:
Disclaimer for reporting use cases: this solution could produce inconsistent results in reports produced with automations; when using the button to pass through selections, the intended report composition and associated data reduction for the report may not be achieved. This is due to the fact that the session state of Qlik Application Automation cannot be transferred to the report composition definition that is passed to the Qlik Reporting Service.
When analyzing results in a Qlik Sense app, it could happen you spot a mistake in your data or something that seems odd. To address this, you may want someone from your team to investigate this or you may want to update data in your source systems directly without leaving Qlik. Or maybe your data is just fine but you want to add a new record from within Qlik without having to open your business application. These scenarios fit in the following use cases:
This is the least intrusive form of writing back that delegates the change to someone in your data team. The idea is that you create a ticket in a task management system like Jira or ServiceNow. Someone from your team will then pick up the ticket, investigate your comment, and review the data. The difference with sending an alert or email is that the ticketing system guarantees that the request is tracked.
Another option to communicate changes is to write a comment or a tag for one or more records directly to the source system. This could be a comment on a deal record in your CRM or it could be stored in a separate database table if you're loading data from a database.
The final use case allows for updating records directly from within the sheet. Make sure you know who has access to the button before setting this up since this will allow users to change records directly.
All the above use cases can be realized in the same way: by configuring a native Qlik Sense button in your sheet to run an automation. Before you start this tutorial, make sure you already have an app and a new, empty automation. The tutorial has 2 parts:
To configure the app, we'll use the following native Qlik Sense components:
Steps:
Enable the "Show notifications" toggle, this will send a toast notification back to the user in the sheet after the automation completes. Feel free to increase the duration.
Tip: using a Container component will allow your variable inputs & button to scale better for smaller screens.
Upon automation run, this will resolve to the first text value selected for the field hs_object_id (which corresponds to the deal ID from HubSpot). To update this to a comma-separated list of IDs, the mapping must first be changed to output a list of all values for hs_object_id. To do this, toggle the formula parsing:
Bonus: add a link to the toast notification
Instead of showing a plain message in the toast notification, it's also possible to include a link to point the user to a certain resource. This can be done by configuring the Update Run Title block with the following snippet:
{"message":"Ticket created", "url": "https://<link to jira ticket>"}
Depending on the button's configuration and the automation run mode, use either the Update Run Title block or the Output block to show the toast notification.
See the below table for each option:
Run mode configuration in the automation | Run mode in the button | Block for toast notification | Who can see the notification |
Triggered async | Triggered | Update Run Title | Automation owner only |
Triggered sync | Triggered | Output | Everyone |
Triggered sync | Not triggered | Update Run Title | Automation owner only |
The run mode in the button can be configured by toggling the 'Include Selections' option in the button's settings:
The run mode in the automation can be configured here in the Start block:
After writing back to your source systems, you'll want to do a reload to see your changes reflected in the app. Be mindful of the impact of doing these reloads. If multiple people are using this button at the same time, you don't want to do a reload for each update.
Problems:
Improvements:
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.
Most Qlik Web Storage Provider Connectors require an encryption key. If no key exists, the following error will be displayed when authenticating:
Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.
General information, as well as a list of which connectors require an encryption key, can be found in Setting an encryption key | Qlik Connectors Help.
The actual generation of a key depends on your organization's best practices, but we can provide you with an example on how to go about it with OpenSSL:
The below example is not supported by Qlik Support. Review it with your local security office to see what method your organization follows.
Follow the instructions on how to set the encryption key in Qlik Sense Enterprise on Windows and/or Qlik Sense Desktop:
Setting an encryption key on Qlik Sense Enterprise on Windows
Setting an encryption key on Qlik Sense Desktop
Setting an encryption key | Qlik Connectors Help
Setting an encryption key on Qlik Sense Enterprise on Windows
Setting an encryption key on Qlik Sense Desktop
Qlik Web Connectors allows loading Excel files (xls, xlsx) hosted in online file storage services such as Box, Dropbox, Google Drive and OneDrive directly into QlikView and Qlik Sense without having to save the file to disk first.
Different methods need to be applied to fetch files depending on what edition of Qlik Sense is used.
Note that the in-built Web Connectors are available are:
Unavailable at the moment are:
To connect to, for example an excel file, stored on Google Drive:
More information: Managing data sources in spaces.
You can add data files and data connections directly in shared and personal spaces. This enables data sources to be added outside of apps for use by other space members.
We use the query GetRawFileAsBinary of the appropriate connector in Qlik Web Connectors.
Once the binary content is sucessfully loaded in Qlik Web Connectors web console, you can create a webfile connection in QlikView or Qlik Sense to load data from Qlik Web Connectors.
In QlikView:
SaaS Topics:
Managing data sources in spaces.
Built-in Qlik Web Connectors
STT - Reloading Your Data in Qlik Sense Business
WebConnectors (not SaaS):
Data sources included in Qlik Web Connectors
Google Drive and Spreadsheets
OneDrive
Dropbox
Qlik Web Connectors authentication fails with error "Could not establish trust relationship for the SSL/TLS secure channel"
Starting at Qlik Sense Enterprise on Windows May 2021, the bundled PostgreSQL has been upgraded to version 12.5.
However, PostgreSQL 12.5 will only be deployed during a fresh installation of Qlik Sense Enterprise on Windows May 2021. This means that, if you are upgrading to 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 May 2021 following the steps and recommendations provided on this link.
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 Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.
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 May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5. Instructions available here.
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 May 2021 deployed on your central node with PostgreSQL 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