Show Less

The Qlik Replicate server service in Windows used to be named Attunity Replicate Server. 

This name has changed to Qlik Replicate Server. The change was introduced in the 2022.11 release.

If you are running a Windows Cluster and are monitoring Qlik Replicate through it, or if you have deployed third-party applications monitoring the service uptime, these applications must be modified to look for the correct service name. 

 

Environment

2021.11 and later

 

 

Show Less

All on-premise Qlik Products can be downloaded from Qlik's Product Download Site.

To access the Download Site, you need an active QlikID. You will be able to see all products your account is eligible for.

If you encounter issues with the download site, start a chat with us and we will be able to help you right away.

 

You can access the Download Page directly here, or navigate to it from the Community Home page:

1. Open the Qlik Community
2. Click on Support
3. Under  Product News
4. Select  Product Downloads 
   
   If you do not see Product Downloads, please log in to the community.
   
   
   

                                        

This shows the download page with the Latest release and patch preselected.

1. Choose a different filter in Release Assets if you are looking for older product versions. By default, only the Latest release and patch will be displayed. 
   
   
   
   
2. From here:
   
   
   1. choose your Category (Qlik Data Analytics, Qlik Data Integration, Search All),
   2. your Product,
   3. your Release,
   4. and Release Number.
   5. Then click the Download Link
      
      
      
      
      

Alternatively, instead of selecting your product directly, you can also search all available columns:

1. Click the Magnifying Glass
2. Begin typing your search
3. Select the result
4. Confirm the result
   
   

 

Click here for video transcript

 

Show Less

Show Less

Core-based and capacity-based licensing is a change from traditional licensing. Rather than limiting the number of users who can access the Qlik Sense site by a limit on tokens, core-based licensing restricts user access by limiting the number of CPU cores which can be used by the Engine to deliver end-user content.

With a core-based license, there is no functional reason to use the License Monitor app since the users will not use tokens. Instead, consumption of apps can be gauged by reviewing the Session Overview and Session Details sheets on the Operations Monitor.

Environments:

• Qlik Sense Enterprise on Windows with Core-based license

 

Show Less

Show Less

Show Less

In this article, we address best practices through a questionnaire for Qlik Replicate administrators and architects before an environment goes live in production.  Having answers to these questions is helpful for a successful deployment and sustainable implementation. 

Content:

• Pre-deployment
• Qlik Professional Services
• Source
• Source Sizing
• Sizing
• Testing
• Additional Administration
• Table and data level
• Go live
• Support
• Security
• Related Content

 

Pre-deployment 

1. Is is possible to perform a POC? If a POC already occurred, what would you like to repeat or avoid?
2. Are the source and target endpoint versions in compliance with Replicate Support Matrix?
3. Which role is in charge of installing correct drivers and pre-requisites? DBAs, Replicate administrators, systems engineers, etc.
4. What type of replication will you be requiring (Store changes, Apply changes, both, bi-directional, full load only etc.)?
5. Although driven by your Replicate license, it is helpful to define the following:

1. Number and types of sources
2. Number and types of targets

 

 

Qlik Professional Services

1. Is there a process or budget to engage  Qlik Professional services for the following?
   1. Implementing new endpoints
   2. Performance tuning task settings

 

Source 

1. Is there a source DBA available to help configure source connection? Are they available for troubleshooting?
2. What are the source log retention limitations?
3. Does  Qlik Replicate have proper permissions configured to source DB?
4. Test opportunity: Work with Source DBA to confirm security policy and test permissions access to tables
5. If three or more tasks connecting to a source database, have you considered implementing Log Stream?

 

Source Sizing

1. Please work with Qlik Replication project owners and administrators to define values for the following: 
   1. Rate of source changes
   2. Number of source schemas
   3. Number of source tables
   4. Size of all tables (rows, data)
2. Do tables have LOB columns? If so, how many tables and what size?

 

Sizing 

1. Define the location of Servers (source, targets, Qlik Replicate) type (on premise, cloud, on premise virtual machine)
2. Is there hardware already procured to work with or can Qlik help size the hardware (Professional Services)?
3. What is the network bandwidth available between endpoints and Qlik Replicate?
4. Qlik Replicate disk storage size (disk requirements if changes are written to disk)
5. Is your \data folder location in a separate location from the Qlik Replicate install folder? 
6. If using log stream, is your storage path on a separate drive from your /data directory?  This can help with disk contention by having separate drives. 
7. What is your acceptable latency requirement (time from source commit to target commit)?

 

Testing

1. Define number of environments DEV, QA/TEST, PROD
2. Do you have at least 1 non-production environment that mirrors production for data volume, data types, and processes?
3. Define a testing plan, scripts, queries for:
   
   1. Validating row counts between source and target
   2. Validating any filters or transformations
   3. Validating failover if a HA/failover environment
   4. Validating query times on source and target. If needed, reduce the batch size or increase timeout parameters.
   5. Validating row size limits 
   6. Practicing a Advanced Run Options -> Restart from time or SCN/LSN (and when to use these options)
   7. Adding or removing a table from a task
   8. Apply Conflicts settings such as UPSERT mode 
4. How do we handle maintenance or upgrades on Source DB and target DB? How often do we expect these to occur?

 

Additional Administration 

1. How many users will be engaging with Qlik Replicate at one time? Who is responsible for managing adding, removing or configuring users?
2. Are notifications configured on server or task errors? For Disk/CPU limits? What emails are included to receive notifications?
3. Is there a naming convention established for sources, targets, and tasks?
4. Is there a change control strategy in place? Qlik Enterprise Manager has audit trail capabilities if also installed with Qlik Replicate environment. 

 

Table and data level

1. Do tables have PKs? Are PKs changing on any tables? Tables with a PK which is not changing will have the best performance with bulk apply mode. 
2. For change data capture: are you using Transactional apply vs Bulk apply?

 

Go live

1. Do we bring all task online at once or can they be started sequentially or in batches?

 

Support

1. How long will it take to perform a full reload on each task?
2. Are there any task/tables where a Full load is not an acceptable option?
3. Do you know how to increase Task and Server logging and/or download diagnostic package?
4. Do we have a team who can manage 24 hour Severity 1 Support?
5. What is process for applying Qlik Replicate service packs with fixes? (i.e Dev then prod, or direct on Prod, how quickly can these fixes be applied?)
6. Are you familiar with decrypting log files?
7. Does your team have access to the Case Portal? 

 

Security

1. Have you tested access to the system with set password? 
2. Has openSSL been set up and configured for Qlik Replicate UI Console and Server?

 

Related Content

How To Get Started with Qlik Replicate

 

Environment

Qlik Replicate 

 

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.

 

 

 

Show Less

This Techspert Talks session addresses:

• Monitoring multi-node activity
• Centralized metrics collection
• Demo of available tools

 

 

• 00:00 – Intro
• 01:19 - Overview of multi-node architecture
• 02:04 - Butler SOS architecture
• 03:24 - Grafana Loki architecture
• 05:20 - Butler SOS demo
• 11:32 - Loki with Grafana demo
• 16:30 - Selenium IDS tool
• 17:53 - New Relic Demo
• 19:49 - Q&A: What about data model and app optimization?
• 20:16 - Q&A: What security issues are there?
• 23:04 - Q&A: What metrics should we be monitoring?
• 24:06 - Q&A: Can this be done with the Operations Monitor app?
• 25:03 - Q&A: How to set this up?
• 25:51 - Q&A: Are these tools free and publicly available?
• 26:26 - Q&A: Will these tool work with QlikView?
• 26:50 - Q&A: Can you measure App response times?

 

 

Resources:

Optimizing Performance for Qlik Sense Enterprise

Qlik Sense Enterprise deployment examples

Butler SOS

Setting up Butler SOS

Grafana Loki | Grafana Loki documentation

Docker + Compose

Portainer for Docker management

Selenium IDE for user session replay

Webmin for server admin

 

Click here to see video transcript

 

 

 

Show Less

March 14th 2023: You may have upgraded Qlik Sense and located a warning banner in your Management Console stating that this version of PostgreSQL is not supported. If you are running a standalone PostgreSQL database later than 9.6, this message can be disregarded. We are working on resolving the underlying cause. 

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.

 

Index

• Supported Scenarios
• Considerations
• Installing anew Qlik Sense Repository Database using PostgreSQL 12.5
• Qlik PostgreSQL Installer - Download Link
• Upgrading anexisting QRD to PostgreSQL 12.5
• The Upgrade:
• Finalizing the Upgrade/Uninstalling the old Database Service:
• Compatibility with PostgreSQL installers
• Troubleshooting
• Related Content

 

Supported Scenarios

• Upgrades: Before using the Qlik PostgreSQL Installer, upgrade to a supported version of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.
  
  We tested and validated Qlik Sense Enterprise on Windows from February 2022 to February 2023. Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Sense upgrade.
  
  
• New installs: The Qlik PostgreSQL Installer supports installing a new Qlik Sense Repository Database cluster on a new server, setting up a new environment or migrating an existing Database to a separate host.

 

Considerations

• This installer will not detect a standalone PostgreSQL database installed by any other means, other than through an official Qlik installer package, installed on the standard folders in the C drive. 
• The installer itself does not provide a rollback feature. This is described below. 
• The user who runs the installer has sufficient permissions to execute it and install services 
• The user who runs the installer has sufficient permissions to create folders and files in the backup destination 
• The backup destination has sufficient free disk space to dump the existing database  
• The backup destination is not a network path or virtual storage folder. It is recommended the backup is stored on the main drive 
• There will be downtime during this operation, please plan accordingly 

 

Installing a new Qlik Sense Repository Database using PostgreSQL 12.5

1. Run the Qlik PostgreSQL Installer as an administrator 
   
   
2. Click on Install 
   
   
3. Accept the Qlik Customer Agreement 
   
   
4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 
   
   
5. Set your Database superuser password and click Next
   
   
6. Set the database installation folder, standard: C:\Program Files\PostgreSQL\12
   
   
7. Set the database data folder, standard: C:\Program Files\PostgreSQL\12\data
   
   
8. Review your settings and click Install, then click Finish
   
   
9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.
   
   The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.
   
   
10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  
    
    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 
    

 

Qlik PostgreSQL Installer - Download Link

Download the installer here.

Qlik PostgreSQL installer version 1.2.1 Release Notes

 

Upgrading an existing QRD to PostgreSQL 12.5

Before using the Qlik PostgreSQL Installer, upgrade to a supported version of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.

We tested and validated Qlik Sense Enterprise on Windows from February 2022 to February 2023. Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Sense upgrade.

Qlik Sense Enterprise on Windows installations other than in C:\Program Files\Qlik\Sense are currently not supported. 

 

The Upgrade:

1. Stop all services on rim nodes 
   
   
2. On your Central Node, stop all services except the Qlik Sense Repository Database 
   
   
   
   
3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 
   
   
   
   
4. Highlight the database and click Upgrade 
   
5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (b) Next.
   
   
   
   
6. Provide your existing Database superuser password and click Next.
   
   
7. Define your Database backup path and click Next.
   
   
   
   
8. Define your Install Location (default is prefilled) and click Next.
   
   
   
   
9. Define your database data path (default is prefilled) and click Next.
   
   
    
10. Review all properties and click Upgrade.
    
    
    
    
11. The upgrade is completed. Click Close.
    
    
     
12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.
    
    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 
    
    
    
    You will also find a new postgresql-x64-12 service. Do not rename this service. 
    
    
    
    
13. Start all services except the Qlik Sense Repository Database service. 
    
    
14. Start all services on your rim nodes.
    
    
15. Validate that all services and nodes are operating as expected.

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

1.  

Finalizing the Upgrade/Uninstalling the old Database Service:

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:

1. Open a command prompt and run the command:
   cd "C:\ProgramData\Package Cache"
2. From there, run:
   c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
3. The folder containing PostgreSQL.msi will be revealed.
4. Right-click on the PostgreSQL.msi file and select uninstall from the menu.

 

Compatibility with PostgreSQL installers

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.

 

Troubleshooting

1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:
   
   C:\Users\Username\AppData\Local\Temp\2
   
   A backup of the original database contents is available in your chosen location, or by default in:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\9.6
   
   The original database data folder has been renamed to:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\9.6_deprecated
   
   
2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:
   
   This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.
   
   See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.
   
   To resolve this, start the postgresql-x64-12 service.

 

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.

 

Related Content

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

Show Less

Getting data out of Qlik Sense Enterprise SaaS, and distributing it to different users in formatted Excel, has been a manual task until now.

Thanks to the release of Qlik Application Automation, it is now possible to automate this workflow 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. 

 

Video:

 

Considerations

• This example is built on distributing a SharePoint link. It is also possible to use attachments with the Mail block (see Reporting).
• Qlik Application Automation has a limit of 100,000 rows when getting data out of a Qlik Sense straight table object.
• The On-Demand example uses an extension in QSE SaaS to send data to the Automation. An update to the Qlik Sense Button object is expected soon, which will provide a native way to pass selections to an Automation.

 

Example 1: Scheduled Reports

1. Download the 'Scheduled Report.json' file attached to this document.
2. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right clicking in the editor canvas, and selecting 'Upload workspace'.
3. Select the 'Create Binary File (Personal One Drive)' block, select 'Connection' in the block configurator to the right, and then create your connection to Microsoft SharePoint.
4. Select the 'Get Straight Table Data' block. Under 'Inputs' in the block configurator, lookup your the App Id, Sheet Id, and Object Id for the relevant QSE SaaS table you wish to output.
5. Select the 'Create Excel Table With Headers' block, select 'Connection' in the block configurator, and then create your connection to Microsoft Excel.
6. Select the 'Send Mail' block. Under 'Inputs' in the block configurator update the 'To' to reflect the addresses you wish to deliver to.
7. With the 'Send Mail' block still selected, select 'Connection' in the block configurator and add your Sender details.
8. To test, Save and then Run the Automation
9. If you receive any warnings or errors, navigate to the relevant blocks and ensure your Connection is selected in the block configurator. 
10. Select the 'Start' block. Under 'Inputs' in the block configurator, change Run Mode to Scheduled and define your required schedule. 

 

Example 2: On-Demand Reports

Note - These instructions assume you have already created connections as required in Example 1.

1. Download the 'On-Demand Report v3.json' file attached to this document.
2. Download and install the 'qlik-blends' extension. See: 
   https://github.com/rileymd88/qlik-blends/files/6378232/qlik-blends.zip
3. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right-clicking in the editor canvas, and selecting 'Upload workspace'.
4. Ensure your Connections are selected in the block configurator for each of the following blocks, 'Create Binary File (Personal One Drive)', 'Create Excel Table With Headers', 'Add Rows To Excel Worksheet Table (Batch)', 'Create Sharing Link', and 'Send Mail'.  Save the Automation.
5. Select the 'Start' block and ensure Run Mode is set to Triggered. Make note of the of URL and Execution Token shown in the POST example. 
6. Open your chosen QSE SaaS application, and Edit the Sheet where you wish to add a Button to trigger an On-Demand report. 
7. Under 'Custom Objects' look for 'qlik-blends' from the Extensions menu and drag this into your Sheet.
8. Under the 'Blend' properties to the right, add-in your POST webhook URL and Token as noted in Step 5.
9. We will now add three measures to the 'qlik-blends' object. It is important you add them in the order described.  Add the first measure, using the following function in the expression editor: GetCurrentSelections()
10. Add the second measure, using the following function DocumentName()
11. The final measure will be the Object ID of the table you wish to use. To find the Object ID, select 'Done Editing'.  Then right click on the table, select 'Share', select 'Embed', then look for the Object ID under the preview. Copy this value, go back into Editing mode and paste this as your third measure value. 
12. With the 'qlik-blends' object selected, under Form select 'Add items'. For 'Item type' select Text. Under default value you can choose to add a default email address. For 'Label' and 'Reference'  type 'Email'. It is critical that Reference is updated to 'Email'.  Turn 'Required input' on. 
13. You can change the Appearance properties to suit your preferences, such as updating the Button label and message, enabling Dialog, and changing the Color under Theme.
14. Back in the Automation, under the Start Block. Set  'Run asynchronously' = yes to allow multiple requests to run at the same time (This will also increase the max run time from 1min to 60min)
15. Once happy, test the On-Demand report by entering an email and clicking the button.

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. 

 

Environment

• Qlik Application Automation 
• Qlik Cloud 
• Microsoft Office 365

 

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.

 

Show Less

When using Qlik Cloud with a custom IdP and a user is removed from the IdP, will that change be propagated into Qlik Cloud? 

 

Resolution

The answer to the question depends on the IdP used and the if the provisioning has been enabled or not.

If the current IdP used does not support SCIM then the changes done on your IdP side will not be propagated into Qlik Cloud. So, the user will not be flagged as inactive or removed on your tenant.

If you are using Azure AD* and the provisioning has been enabled, then the changes will be propagated as explained in Provisioning users and groups using SCIM | Qlik Cloud Help.

SCIM provides a standardized way for IT systems to communicate and exchange user identity data. With SCIM, you can:

• Create a new user in one system and automatically provision the same user in another system.

• Update user information in one system and reflect that change in all other systems.

• Delete a user in one system and automatically deprovision the user in all other systems.

By standardizing the user management process, SCIM makes managing users across different IT systems easier and reduces the likelihood of errors or discrepancies in user information.

Related Content 

Provisioning users and groups using SCIM - Qlik | Help
SCIM: System for Cross-domain Identity Management (simplecloud.info)
SCIM synchronization with Azure Active Directory - Microsoft Entra | Microsoft Learn

 

*SCIM connectors that work with Qlik Cloud (as of the date of creation of this article - 15th March 2023) :

1. Qlik Cloud supports Microsoft Azure Active Directory (Azure AD).

 

Environment

Qlik Cloud 

Show Less

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:

• Move Qlik Sense database to standalone PostgresSQL database in which case you will have control of which PostgreSQL version is deployed as long as it is supported by the system requirements
• Continue to use the bundled PostgreSQL with version 12.5 (see the process below)

Content:

• Step 1: Upgrading your Qlik Sense site
• Step 2: Backing up your Qlik Sense site
• Step 3: Uninstall Qlik Sense on the central node
• Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node
• Step 5: Restoring your Qlik Sense site

 

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.

 

Step 1: Upgrading your Qlik Sense site

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.

 

Step 2: Backing up your Qlik Sense site

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.

 

Step 3: Uninstall Qlik Sense on the central node

You will now need to uninstall Qlik Sense from the central node following these instructions.

During the uninstall:

• Have all rim nodes stopped.
• Don't check the box Remove Qlik Sense demo apps, certificates, and data folders.
• After uninstall and before reinstall rename C:\programdata\qlik to C:\programdata\qlik.old and rename C:\program files\qlik to C:\program files\qlik.old (if you changed it on another drive adjust accordingly)

 

Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node

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.

• select the same host name and database settings as before
• The file share can point at a temporary one since you will take the original one again after restoring the QSR database in step 5.

Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.

 

Step 5: Restoring your Qlik Sense site

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.

 

Environment

Qlik Sense Enterprise on Windows May 2021 and later

 

Show Less

A newly designed Replication task (with default settings) reported errors in the first run:

2023-03-15T21:02:28 [STREAM_COMPONEN ]E: Replication task cannot support lobs, since log stream staging task does not [1020480] (ar_cdc_channel.c:261)
2023-03-15T21:02:28 [METADATA_MANAGE ]E: Allocating utility stream component failed [1020480] (metadatamanager.c:837)
2023-03-15T21:02:28 [METADATA_MANAGE ]E: Cannot create the source utility component [1020480] (metadatamanager.c:753)
2023-03-15T21:02:28 [TASK_MANAGER ]E: Creating Metadata Manager's utility components failed [1020480] (replicationtask.c:3893)

In general this error comes with "Replicate LOB columns" is deselected in Log Stream Staging task :

 

 

Workaround:

1. Enable "Replicate LOB columns" in Log Stream Staging task if LOB columns are needed, or see (2), (3) below.
2. If no need to replicate LOB columns, or there are no LOB columns in the table(s) selected, then Edit Replication task and SAVE (any change is good enough, eg change Task setting --> Logging --> PERFORMANCE from INFO to Trace, SAVE, and change it back to INFO again). This operation will add the missing components implicitly.
   
   
   
3. Or export/import the  Replication task by adding the missing property explicitly:
   
   "common_settings": {
   "support_lobs": false,
   "change_table_settings": {
   
   

Internal Investigation ID(s):

RECOB-6036, #00075812, #00054094

 

Environment:

Replicate 2022.5   (eg PR02, PR03, PR04)
Replicate 2022.11 (eg PR03)

 

Show Less

Error 429 (Too many requests) is returned in September 2020 and later when uploading a big number of files.

Environments:

• Qlik Sense Enterprise on Windows September 2020 and later releases

 

 

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.

 

Resolution

 

This is due to the new DoS (Denial of Service) protection in those versions. Error 429 will happen more than 60 upload requests are sent in a 30 seconds time frame.

This protection can be disabled. Qlik does not recommend disabling DoS attack protection. 

In C:\Program  Files\Qlik\Sense\Repository\Repository.exe.config file, set the following option to false to disable it.

<add key="UseDosProtector" value="false"/>

Qlik cannot be held responsible for any damage caused by a DoS attack if the above option has been disabled.

Show Less

When an end-user connects to the Qlik Sense Hub, Qlik Sense verifies first if they have a valid license to interact with the product. This could be a professional or analyzer user license, an analyzer capacity license, or a user or login access pass. If the user cannot be verified to have any license assigned, an error will be shown.
 

 
The message may be shown despite of the user having been allocated a license.

In Qlik Sense June 2019 and later, an additional version of the error message was introduced, indicating when a user has reached their maximum allowed concurrent sessions:
 

* See You cannot access Qlik Sense because you have no access pass - intermittent problem.

Environment:

Qlik Sense Enterprise on Windows 

 

Resolution:

 

Does the user have a license?

Verify if the user has a license assigned. 

For Signed License Keys this could be a:

• Professional License (Managing professional access)
• Analyzer License (Managing analyzer access )
• Capacity License (Analyzer capacity license and comparison with other license allocations and how to check usage)
  Verify if there are still Capacity minutes remaining. 

For licenses still using Tokens, this could be a:

• User Access Token (Allocating user access)
• Login Access Pass (Creating login access rules)
  Verify if there are still Login Access Passes available. 

 

Solution:

Assign a License or ensure you have sufficient Capacity minutes 

 

If the user has just been assigned a license prior to logging in the first time:

This often occurs when a user is being assigned a license or token based on an active directory group, and has not yet been synchronized. The license check for user-based licenses (professional and analyzer) and tokens occurs when you access the hub.

If you access the hub without a license and subsequently are assigned a token or professional or analyzer access, the license check has already occurred, and you will get a "no access pass" error, stopping you from interacting with apps. Log out and log in again for the license to be recognized.
 
Solution:

1. Logout with the user from both the hub and Qlik Sense Management Console (if applicable).
2. Log back in.

 

If the Qlik Sense server is licensed with a signed license and the licensing server has not been reachable for too long:

If a signed license key cannot be verified with the license backend for 5 days, licenses will be disabled. 

The below log entities can be found from Licenses Log
{"caller":"handler.go:61","level":"info","message":"invalid license error, license verification error: lic is stale","res.errorType":"licenses.InvalidLicenseError","res.statusCode":403,"timestamp":xxxxxx"}

Or:

{"caller":"sync.go:290","corrId":"26ab589a897f6e56:26ab589a897f6e56:0:1","level":"info","licenseNumber":"XXXXXXXX","message":"re-syncing assignments with the backend","timestamp":"2020-01-20T08:13:32.7038396Z"}
{"caller":"handler.go:44","corrId":"35b5cbb055734329:35b5cbb055734329:0:1","errorMessage":"Too much time has passed since the last license update","errorType":"LICENSES-OutdatedLicense","level":"info","statusCode":403,"timestamp":"2020-01-20T08:13:32.7438444Z"}


Verify that the Qlik Sense server has an active internet connection and that connectivity to license.qlikcloud.com on port 443 is possible from the server running the Qlik Sense licensing service. 

See Using a Qlik signed license in an offline environment for details. 

Solution:

• Reconnect the Qlik Sense server to the internet and allow for the licensing service to check in with license.qlikcloud.com.
• Restart Dispatcher service 
• In some rare cases, the Management-Server only has temporary access to the Internet, so sometimes it is able to connect to https://license.qlikcloud.com and sometimes not. It needs to have permanent access to the licence-URL, to be able to correctly work.
• If you are in the above rare cases or if the sync doesn't seems to be performed, there is a way to force the sync: go to the QMC site license (qmc/sitelicense), remove one character and click to "apply".

  The license will be refused as it's an incorrect one. This action will force the license synchronization.

 

A license conversion was planned and the date has passed

During the conversion, the client has to prepare and switch the users from tokens to professional/analyzer licenses. 

After this conversion date, a periodic cleanup of tokens in the backend license server will occur. If this clean up happens and an admin has not finished the conversion, all tokens will be removed from the users. The result will be the 'no access pass' message.

Solution:

Allocate new professional analyzer licenses according to the conversion plan. 

 

For additional troubleshooting steps, see:

• Qlik Sense April 2018 and later- Service account getting "You cannot access Qlik Sense because you have no access pass"
• You cannot access Qlik Sense because you have no access pass - intermittent problem
• Unable to open Qlik Sense app after changing Internet Proxy or Firewall settings  

Show Less

Start from Step 2 if you are using Qlik Sense Enterprise SaaS. 

1.  Use this link to register for Qlik Sense Business and fill out the prompted form and "Submit". If you already have a Qlik account, please log in and continue to Step 2.
   
   An e-mail will be sent to the e-mail address specified in this step.
   
   This e-mail is required for the next step. 

IMPORTANT One Email, One Tenant. You cannot create a second tenant using the same email address.

2. After completing the signup, go to your email inbox used in the form. Open the email "Qlik Sense on Cloud Services Setup" and select  "Lets Get Started"
   
   

    

3. If you do not have a Qlik Account, proceed as instructed in this step. If you do have a Qlik Account, skip to step 5.
   
   Verify your email address, create a password and confirm that you agree to the terms and conditions. Click "Next". 
   
   

    

4. Choose your region by clicking on the map. Click "Get started" 
   
   
   
   
5. Log in with your email address and password 
   
   
   
   
6.  Read and confirm the terms and conditions. Click "Get Started"
   
   
   
   
7. Your tenant is now created. You can now access your tenant with your Tenant URL or go to My Qlik:  www.qlikcloud.com 
   
   
   
   To access the Tenant from My Qlik, click your Avatar after logging in. Click Qlik Cloud.
   
   

 

 

Related Content:

Aliasing the Qlik Sense SaaS Tenant Name 

 

Show Less

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:

• Support and Professional Services; who to contact when.
• Qlik Support: How to access the support you need
• 1. Qlik Community, Forums & Knowledge Base
• The Knowledge Base
• Blogs
• Our Support programs:
• The Qlik Forums
• Ideation
• How to create a Qlik ID
• 2. Chat
• To create a case using chat:
• 3. Qlik Support Case Portal
• Escalate a Support Case
• Resources

 

 

 

Support and Professional Services; who to contact when.

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.
Error messages ​ Task crashes​ Latency issues (due to errors or 1-1 mode) Performance degradation without config changes​ Specific questions​ Licensing requests​ Bug Report / Hotfixes ​ Not functioning as designed or documented​ Software regression		Deployment Implementation​ Setting up new endpoints​ Performance Tuning​ Architecture design or optimization​ Automation​ Customization​ Environment Migration​ Health Check​ New functionality walkthrough​ Realtime upgrade assistance

(*) reach out to your Account Manager or Customer Success Manager

 

 

 

Qlik Support: How to access the support you need

 

 

1. Qlik Community, Forums & Knowledge Base

Your first line of support: https://community.qlik.com/

​Looking for content? Type your question into our global search bar:

 

The Knowledge Base

Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!

1. Go to the Official Support Articles Knowledge base
2. Type your question into our Search Engine
   
   
   
   
3. Need more filters?
   1. Filter by Product
   2. Or switch tabs to browse content in the global community, on our Help Site, or even on our Youtube channel
      
      

 

Blogs

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)

 

Our Support programs:

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.

 

The Qlik Forums

• Quick, convenient, 24/7 availability
• Monitored by Qlik Experts
• New releases publicly announced within Qlik Community forums (click)
• Local language groups available (click)

 

Ideation

Suggest an idea, and influence the next generation of Qlik features!

Search & Submit Ideas
Ideation Guidelines

 

How to create a Qlik ID

Get the full value of the community.

Register a Qlik ID:

1. Go to: qlikid.qlik.com/register
2. You must enter your company name exactly as it appears on your license or there will be significant delays in getting access.
3. You will receive a system-generated email with an activation link for your new account. NOTE, this link will expire after 24 hours.
   
   If you need additional details, see: Additional guidance on registering for a Qlik account
   If you encounter problems with your Qlik ID, contact us through Live Chat!

 

2. Chat

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:

• Answer common questions instantly through our chatbot
• Have a live agent troubleshoot in real time
• With items that will take further investigating, we will create a case on your behalf with step-by-step intake questions

 

To create a case using chat:

1. Log in to the community with your business account prior to requesting a case to be logged
2. Open chat
3. Type Create a case 
4. When prompted, choose A Support Issue or Question 
5. Choose how you would classify your question:
   • Account, Access, or License related
   • Data Analytics product related
   • Data Integration product related
   • or Qlik Cloud product related
6. Choose if you would prefer to speak to a Live Agent or Create a Case
7. Enter your business email associated with your Qlik Support Portal
8. Choose the Qlik Product your query is about
9. Follow any additional prompts
10. Choose your Severity (General Inquiry/Assistance or Major functionality issue)
11. Summarize and describe the issue in as much detail as possible.
12. The case will be created and you will receive an email confirming the case number. You can immediately review and modify the case in our Case Management Portal.

 

How to create a case using chat

 

3. Qlik Support Case Portal

Log in to manage and track your active cases in Manage Cases. (click)

​Your advantages:​

• ​Self-service access to all incidents so that you can track progress​
• Option to upload documentation and troubleshooting files
• Option to include additional stakeholders and watchers to view active cases​
• Follow-up conversations ​​

 

Escalate a Support Case

If you require a support case escalation, you have two options:

1. Request to escalate within the case, mentioning the business reasons.
   
   To escalate a support incident successfully, mention your intention to escalate in the open support case. This will begin the escalation process.
   
   
2. Contact your Regional Support Manager
   
   If more attention is required, contact your regional support manager. You can find a full list of regional support managers in the How to escalate a support case article.

 

Resources

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.

Show Less

This article explains what is supported and what is not when using Azure Active Directory.

 

Environments:

• Qlik Sense Enterprise on Windows 
• Qlik Cloud 

 

Authentication with Azure AD as an Idp for Qlik Cloud

How to: Configure Qlik Sense Enterprise SaaS to use Azure AD as an IdP

 

Authentication with Azure

In any Qlik Sense Enterprise for Windows version 2.0 and higher, Azure Active Directory is tested and confirmed as supported as a SAML Identity Provider with Qlik Sense.

Regarding the implementation of SAML Authentication with Azure, please see instructions at the following link:
https://docs.microsoft.com/en-us/azure/active-directory/active-directory-saas-qliksense-enterprise-tutorial 
 

User Directory Connector with Azure AD

Unlike a regular Active Directory, Azure AD does not support the LDAP protocol and therefore cannot be used in Qlik Sense at the moment.

A User Directory Connector is solely used to synchronise groups and user attributes from the directory so that you can build your security rules based on those and do not impact authentication.

For groups, as a workaround, you can use group attributes sent in the SAML request by Azure and build your security rules based on those.

You just need to be aware that those attributes will not show up in the user information in the QMC as they are session-based.

The group attribute received from a SAML provider is stored in the user.environment.group variable instead of the user.group variable.

If you are uncertain of what group attributes were received, you can enable Debug log on the Qlik Proxy service to check those. See instructions in:
How to see SAML attributes received by Qlik Sense (user.environment)
 

User Directory Connector with Azure AD DS

Azure AD DS and Azure AD are 2 different offers and have different features. Please see the below link about the differences:

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-compare-with-azure-ad-join

As said above, Azure AD does not support LDAP, but Azure AD DS does.

Below are a few helpful links when setting up Azure AD DS in Qlik Sense:

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-admin-guide-configure-secure-ldap
Qlik Sense: Does User Directory Connector supports LDAPS?

Once the User Directory Connector is setup correctly in Qlik Sense, use the user.group variable in your security rules to assign the access rights.

Show Less

If a Qlik Sense Server or Desktop installation is cancelled or if it did not complete successfully, detailed information can be found in the installation log file within the temp folder.

Environment:

• Qlik Sense Enterprise, all versions
• Qlik Sense Desktop, all versions

 

Resolution:

In order to access the Qlik Sense installation log file:

1. Right click on the Windows button 
2. Click on Run
3. Paste %temp%
4. For Qlik Sense Desktop: This should open a File Explorer window and the Installation log file should be named, for example, Qlik_Sense_Desktop_version.log, where "version" is the numerical version of the product being installed.
5. For Qlik Sense Enterprise server: That should open File Explorer under the ...\temp\2 folder. If so, review the recent files and also move up one level (e.g. \temp\) which is usually where the Qlik Sense server installation logs are found.

The primary log file will be joined by multiple log files for each sub component. 

The installation files use the following name formats:

PRODUCT_VERSION_DATETIMESTAMP.log
PRODUCT_VERSION_DATETIMESTAMP_NUMBER_SUBCOMPONENT.log

More information on how to troubleshoot can be found in How to read the installation logs for Qlik products and within the Troubleshooting section of our Help site.

Show Less