This article explains how a reload task chain can be built that will run longer than the maximum automation run limit of 4 hours. 

This is an advanced article, if you’re new to automations or task chaining, I suggest you first read this basic article.

Content:

• General idea
• Preparation
• Automation 1: Task Chain Initiator
• Automation 2: Task Chain Manager
• Results
• Bonus: reducing total executions of automation

General idea

The maximum run time of an automation is 4 hours. This can be a problem when you want to build a task chain of multiple reloads of big apps that could take longer than that. To solve this, we'll build a system of two automations that run together:

Automation 1: Task Chain Initiator, this automation will run once and start the task chain. It will trigger the first app reloads.

Automation 2: Task Chain Manager, this automation will be scheduled to run every 5 minutes. It will verify if any reloads have finished, whether they were successful and if any new reloads should be triggered.

The Task Chain Manager automation will need to know which reloads were triggered by the Task Chain Initiator and will need a way to store which reloads it already processed in previous runs. In other words: these automations need some sort of state to track the progress of the reload task chain. We’ll use Google Sheets for this, but of course, feel free to use any other cloud storage tool.

Preparation

The state will be stored in one file and divided over 4 sheets. Go ahead and create a new file in Google Sheets.

Sheet 1: Apps for initial reload, this sheet contains the ids and names of the apps that should be reloaded in the first automation. They will be executed by the Reload Initializer automation and run in parallel. Add a new sheet to the file you created, give it the name “Apps for initial reload” and add each app's id and name as in the below example. The order of the apps in the sheet is ignored.

Sheet 2: Queued reloads, this sheet will keep track of which apps were already triggered for reloading.

Add the sheet to the file and name it “Queued reloads” but don’t fill in any fields, the content of the sheet is autogenerated by the automations.

Sheet 3: Finished reloads, this sheet keeps track of all reloads that have finished, it contains their id, name, the status of the reload, and the reload log. Add the sheet to the file and name it “Finished reloads” but don’t fill in any fields, the content of the sheet is autogenerated by the Task Chain Manager automation.

Sheet 4: Chained reloads, this sheet dictates which apps should be reloaded after certain apps finished reloading. Add a new sheet to the file and name it “Chained reloads” specify the order in which apps should be executed.

The order of the rows in the sheet is ignored, the sheet is processed as follows:

If a reload has finished for an app from column “First_id”, then trigger a new reload for the app that’s specified in the column “Next_id” on the same row.

Add this sheet to the file and specify the apps as in the example below:

Automation 1: Task Chain Initiator

This automation will only run once at the beginning of the full task chain process, it will execute the following steps:

1. First, it will clear the Queued reloads & Finished reloads sheets, this will remove all data from previous task chain executions.
2. Next, it will add headers to these sheets
   1. Examples of the generated headers in the Queued reloads sheet:
      
      
      
      
   2. Examples of the generated headers in the Finished reloads sheet:
      
      
      
      
   3. Your automation should now look like this:
      
      
      
      

       

3. After initializing these sheets, the automation will get all apps from the Apps for initial reloads sheet and trigger a reload for each of them in parallel (by setting the Run Mode in the Do Reload block to ‘Start reload and continue’).
   1. Each app’s id, name, and reload id are written to the Queued reloads sheet:
      
      

       

   2. This part of the automation looks like this:
      
      

Note: an export of this automation is attached to this article as a JSON file named "Task chain initiator.json".

Automation 2: Task Chain Manager

This automation will run on a schedule and will be the engine of our task chain process. Feel free to adjust the schedule according to your needs. On each run of the automation, the following steps will be executed:

1. Get all records from the Queued reloads sheet, the Finished reloads sheet and the Chained reloads sheet.
   
   
   
   
   1. Tip: we won't use the loops on these blocks, right-click these blocks and choose "hide loop" to make your automation smaller.
2. Compare queued & finished reload records to find all apps that are in the Queued reloads sheet but not in the Finished reloads sheet. This will return a list of all apps from the queue that haven’t yet finished. Make sure to configure the settings of the Compare Lists block as follows. (List 1 should contain that queued reloads and list 2 should contain the finished reloads)
   
   
   
   
   
3. For each record returned by the Compare Lists block (= unfinished reloads), execute a Get Reload Record block to get the reload status and use a Case block to verify if the reload has finished:
   
   
   
   
   1. The reload finished successfully (status == SUCCEEDED):
      1. Write the app & reload information to the Finished reloads sheet.
      2. Use a filter list block & filter the records from the Chained reloads sheet. Filter it to get all records where First_id == the id of the app of the reload that succeeded.
      3. For each record returned by the Filter List block, trigger a new reload with the Do Reload block and write the reload id to the Queued reloads sheet.
      4. This part of the automation should look like this:
         
         
         
         
   2. The reload failed (status == FAILED):
      1. Write the app & reload information to the Finished reloads sheet.
      2. Optionally, send an email or a Slack message with the reload log.
      3. Configure this part like this:
         
         
         
         

Note: an export of this automation is attached to this article as a JSON file named "Task chain manager.json".

Results

The reloads in the Finished reloads sheet will look like this:

Bonus: reducing total executions of automation

When scheduled every 5 minutes, the "Task Chain Manager" automation will generate 288 daily runs. This bonus paragraph explains how the number of total runs can be reduced. Instead of having an automation that has many executions that run short, we'll build an automation that has only a few executions that run for a longer time.

1. Take all blocks from the Task Chain Manager automation and place them inside a Loop block. Use the explode formula to create a loop in the Loop block's List input field. Specify a comma-separated list of 30 items. For example: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30.
   
   
   
   
2. Then add a Condition block at the end of the automation right after the blocks from the original Task Chain Manager automation. Configure the block to validate the number of items returned by the Compare Lists block (use the Count formula for this). If this equals 0, the Task Chain has finished. Add an Exit Loop block to stop the automation.
3. Now add a sleep block after the condition to sleep for 60 seconds.
   
   
   

    

4. Finally, change the automation's schedule to run every minute. This will reschedule the next run of the automation 1 minute after the previous automation has finished. The automation will now run for 30 minutes (30 loop executions x 1 minute from the sleep block) + the total execution time of the other blocks in the loop.
   
   

Notes

• You can easily modify this automation to send messages to Microsoft Teams or emails.
• If multiple apps should be reloaded after a certain app’s reload is finished, just add multiple rows to the Chained reloads sheet with each time a different Next_id
• In the Task Chain Manager automation, if the output of the Compare Lists block is empty, the task chain has finished. Feel free to add a condition block to the end of this automation to verify this and alert your team.

The information in this article is provided as-is and to be used at your 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.

Related Content

How to task chaining with Qlik Application Automation
How to import and export automations

Some customers might have Spaces associated with deactivated Forts. Since those Spaces contain apps, it's not possible to delete them.

Resolution

1. Install and configure the QlikCli
2. In a command prompt run (replacing SPACEID with the actual spaceId😞
   

   qlik item ls --spaceId SPACEID

3. For each of the apps (and other items) contained in the space you will get something that starts with:
   
   [
   {
   "actions": [
   "change_owner",
   "change_space",
   "create",
   "delete",
   "duplicate",
   "export",
   "export_reduced",
   "import",
   "read",
   "reload",
   "share",
   "source",
   "update"
   ],
   "collectionIds": [],
   "createdAt": "2022-10-12T09:02:32Z",
   "creatorId": "creator",
   "description": "",
   "fortressId": "63467e4b6ede1e21c1f4385b",
   "id": "634682a8cc899cfd5b95ac43",
   
   
4. Look at the "id" above and run:
   

   qlik item rm 634682a8cc899cfd5b95ac43 (REPLACE THE ID)​

5. The command above will delete the metadata concerning the app.
   
   The app itself, in theory, won't be deleted. But since it is on a Fort that is no longer available, that won't really matter.
   
   
6. Once the metadata for all apps and items contained in a space is removed, then you will be able to remove the space from the Management console (or using the command line: qlik space rm SPACEID)

Environment

Qlik Cloud 

Qlik Catalog Install Error:

PostgreSQL psql not found when launching Catalog

Resolution

1. Verify that the machine you are performing the install on has internet access and that you can download files using wget or curl.
2. Run the QDC Prereqs.sh script
3. Configure the QDCinstaller.properties file.
4. Run the QDCinstaller.sh script.

Cause 

The issue is typically caused by insufficient internet access. This leads to the automatic install failing as it is unable to download the required files. 

Environment

Qlik Catalog 

You are seeing a large number of tasks failing. 

When checking your QlikView Distribution Service logs you can see issues to open files.

Example: 

20220316T134429.704+0000 Error: Cannot open file: '\\qlikview.domain.local\Qlikview\QlikViewStorage\Reporting\QVD\2021\xyz.qvd' (System error: Failed to open file in write mode for file: \\qlikview.domain.local\Qlikview\QlikViewStorage\Reporting\QVD\2021\xyz.qvd)

When checking for the QVD on its network location you can observe a size at 0 KB

Environment

QlikView April 2020 SR3 (12.50)

Resolution

To troubleshoot this issue please follow these steps: 

1. Make sure you do not have any security software scanning the QlikView folders or processes 
   
   See QlikView Folder And Files To Exclude From Anti-Virus Scanning
   
   To be sure no other software is locking the QlikView files you can also monitor the file access following the steps from this article:  File Access and Process Monitoring - How to find locked files and the processes locking them
   
   If you find any other 3rd party tool locking QlikView files, please contact your Internal IT team in charge of fixing this. 
   
   
2. Check your file server Disk performance
   
   To save a data collection of  your storage performance you could use Performance Monitor for this: How to log CPU, Disk, and memory usage with Microsoft Performance Monitor on a windows 2012 Server (PerfMon)
   
   You can also review the actual performance live in the Resource Monitor:
   
   
   
   A good indicator to check is the Disk Queue Length. A good-performing disk should show a value as close to 0 as possible.
   
   In this example here we can see a very high Queue Length, demonstrating a general bad performance of the disk, which ended up preventing Qlikview to open files in a timely manner.
   
   See QlikView and its backend File Share System.
   
   If you are facing this problem, please contact your Internal IT team in charge of Storage performance.
   
   Also, make sure you are following best practices documented in Scaling QlikView Publisher 

Cause 

• 3rd party tool locking QlikView files
• Degraded disk performance

Related Content

Scaling QlikView Publisher

If Qlik Catalog is running on a virtual machine, the easiest way to create a reliable backup is to pause the VM and take a snapshot.  

If Qlik Catalog is not run on a virtual machine, or snapshots do not meet your requirements, then the following three resources need to be manually backed up (and consequently restored):

• Database: podium_md (as user podium_md)
• Database: podium_dist (as user podium_dist)
• Directory: /usr/local/qdc/data

Backup steps:

1. To back up the directory, copy the files to a separate backup location.
2. To back up the PostgreSQL databases, run pg_dump and save the resulting file.
   
   Example PostgreSQL pg_dump commands: 
   
   pg_dump -U postgres --format=c --file= podium_md
   pg_dump -U postgres --format=c --file= podium_dist

Restore steps:

1. Restore the /usr/local/qdc/data directory.
2. Restore the PostgreSQL database backups generated using pg_dump using the pg_restore command, entering the PostgreSQL user password when prompted.
   
   The pg_restore command will restore the database schema and data from the backup file into the target database.
   
   Note that the target database must be empty before you run pg_restore or else it may result in errors or data corruption.
   
   Example pg_restore command:
   
   pg_restore -U <username> -d <database_name> <backup_file>
   
   Replace <username> with the username of the PostgreSQL user who has permissions to access the target database. Replace <database_name> with the name of the target database.
   
   Replace <backup_file> with the name of the backup file to be restored. If the backup file was compressed, you can use the -F option to specify the format of the backup file.
   
   For example, if the backup file was compressed with gzip, you can use: pg_restore -U <username> -d <database_name> -F t <backup_file>
   
   
   

Environment

Qlik Catalog 

The Qlik Sense installer fails with an error describing to call Qlik Support or to instead perform a silent installation. 

The Qlik Sense Installation logs show:

Unexpected error during configuration: System.AggregateException: One or more errors occurred. ---> System.Management.ManagementException: Invalid class

Environment

Qlik Sense Enterprise on Windows 
Microsoft Windows 2012 to 2016

Resolution

The note to contact Qlik Support is misleading. The issue is caused by a corrupt repository for the WMI (Windows Management Instrumentation).

For information on how to resolve this issue, see winmgmt - Win32 apps | Microsoft Learn

You can verify the integrity of your Windows OS files by running sfc /scannow in a command prompt. This may lead to further information about any required repairs. 

Cause 

A corrupt repository for the WMI (Windows Management Instrumentation). There are several way to confirm if this is in fact the problem:

1. Check directly the WMI properties:
   1. Go to Computer management
   2. Open Services and Applications
   3. Right-click on WMI Control
   4. Click properties:
      
      It should describe that "Successfully Connected to : <local computer>
      
      And include information for:
      
      Proccessor
      Operating System
      Service Pack
      WMI Version
      WMI Location
      
      
   5. If an error or "invalid class" is displayed, then the repository is corrupted. 
      
      
2. Using the command prompt:
   
   1. Run the command line as admin
   2. Run the following: winmgmt /verifyrepository
   3. If it returns: Repository is inconsistent then the repository is consider corrupted. 

If the above steps didn't solve your problem there is an alternative solution by creating the batch file below. This one will reset your current WMI configuration, and generate a new one after a system reboot. This also worked in cases where the above check under point 2b sends the response Repository is consistent but Qlik Sense would still not install.

 on 
cd /d c:\temp 
if not exist %windir%\system32\wbem goto TryInstall 
cd /d %windir%\system32\wbem 
net stop winmgmt 
winmgmt /kill 
if exist Rep_bak rd Rep_bak /s /q 
rename Repository Rep_bak 
for %%i in (*.dll) do RegSvr32 -s %%i 
for %%i in (*.exe) do call :FixSrv %%i 
for %%i in (*.mof,*.mfl) do Mofcomp %%i 
net start winmgmt 
goto End :FixSrv 
if /I (%1) == (wbemcntl.exe) goto SkipSrv 
if /I (%1) == (wbemtest.exe) goto SkipSrv 
if /I (%1) == (mofcomp.exe) goto SkipSrv 
%1 /Regserver 
:SkipSrv 
goto End 
:TryInstall 
if not exist wmicore.exe goto End 
wmicore /s 
net start winmgmt 
:End

To start it save the block above as cleanwmi.bat in e.g. C:\temp\ and run the script as an administrative user. If its finished please reboot the machine.

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.

(*) 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.

A Qlik Replicate DB2 z/OS task may stop/fail with the following message:

[SOURCE_CAPTURE ]W: R4DB2: ALL CB ENTRIES ARE IN USE 

This means that a task is trying to start, but the maximum number of R4Z Control Blocks (in the  R4Z CDC service environment on the mainframe) is in use. The task will not be able to start unless the MAXSESSIONS setting is increased to allow more than 32 R4Z sessions to start. One temporary solution is to stop some other tasks that are unnecessary to have running at the moment.  Another possible long-term solution is to implement  LOGSTREAM tasks to reduce the number of sessions being created on the mainframe.  Below are the steps to resolve this issue by increasing the total number of sessions. 

Environment

All versions of Qlik Replicate using R4Z
UDTF:     'XXX.your_R4Z_UDTF__CDC1'    <<<   Your  UDTF's CDC server environemnt CDC1, CDC2, DB2T, DB2P as examples.
APPLENV:     'XXX.your_R4Z_APPLENVF__CDC1'    <<<   Your  APPLENV 's CDC server environment CDC1, CDC2, DB2T, DB2P as examples.

Resolution

1. Stop ALL GUI Qlik Replicate DB2 z/OS  ONLY tasks
   
   
2. Wait for the tasks to finish Stopping.
   
3. Run/Submit the XMDUMP Job from the  .INSTALL library. This is a simple reporting job that shows how many sessions are in use and how many are available.
   
   Don't forget to edit the CDCSERV parm = CDC1 or DB2P or whatever your 4 characters are for the CDC service.
   
4. /V WLM,applenv=xxxxxx,Quiesce
   
   This quiesces the application environment associated with the corresponding UDTF and CDC Service, for example, R4Z_MYAPPLENV__CDC1 or R4Z_MYAPPLENV__DB2P)
   
   
5. Run the XMTERMIN Job from the .INSTALL library and expect a return Code: RC=0 The job terminates the CDC service environment ( for example CDC1 or DB2P for Prod) and releases the ECSA memory allocation.
   
   Don't forget to edit the CDCSERV parm = CDC1 or DB2P or whatever your 4 characters are for the CDC service.
   
   
6. Run the XMDUMP Job again, from the .INSTALL library and  expect a return Code: RC=1 = NON-EXISTENT
   
   This verifies that the CDC service environment is truly gone and memory is freed up.
   
7. Edit the .CONFIG file members:
   
   Change all members that contain the MAXSESSIONS setting and increase it by 5 or 10, for example. 
   
   
8. Save the .CONFIG file members
   
   
9.  /V WLM,applenv=xxxx,RESUME
   
   This resumes the application environment associated with the corresponding UDTF and CDC Service, for example, R4Z_MYAPPLENV__CDC1 or R4Z_MYAPPLENV__DB2P.
   
   
10. Resume the Qlik Replicate DB2 z/OS tasks from the Qlik Replicate console.

Related Content 

Controlling the CDC process | Qlik Help

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.  

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

Environment

• Qlik Sense Enterprise SaaS
• Qlik Application Automation

This article shows how to generate a report from a Qlik Sense app, upload the report to any cloud storage platform, create a sharing link, and send out an email with the link in the body. 

We can send the report as an attachment using the Send Mail block in the Mail connector, but this block only supports attachments of size 40MB. An alternative solution is to store reports in any of the cloud storage platforms that support the creation of sharing links and send emails with the links.

I will go through a few examples to show how this can be achieved using the following cloud storage connectors:

1. Dropbox
2. Microsoft OneDrive
3. Microsoft SharePoint
4. Amazon S3

I will not go through the steps on how to generate the report using Qlik Reporting blocks as it's already explained in this article.

The four automation files used in the examples are attached to this article. More information on importing automations can be found here.

Dropbox

The following steps explain how to create a public URL using the Dropbox connector.

1. Store the generated report on Dropbox using the "Copy File on Dropbox" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Dropbox. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename.
   
   
   
   
2. Add the "Create Sharing Link" block from the Dropbox connector to the automation and configure it to use the path of the file from the output of the "Copy File on Dropbox" block in the Path parameter.
   
   
   
   
3. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Microsoft OneDrive

The following steps explain how to create a public URL using the Microsoft OneDrive connector.

1. Store the generated report on Microsoft OneDrive using the "Copy File on Microsoft OneDrive" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Microsoft OneDrive. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename.
   
   
   
   
2. Add the "Get Item By Path" block from the Microsoft OneDrive connector to the automation. Configure it to use the file path from the output of the "Generate Report" block in the File Path parameter to use the generated filename.
   
   
   
   
3. Add the "Create Sharing Link" block from the Microsoft OneDrive connector to the automation. Configure it to use the ID of the file from the output of the "Get Item By Path" block in the Item Id parameter.
   
   
   
   
4. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Microsoft SharePoint

The following steps explain how to create a public URL using the Microsoft SharePoint connector.

1. Store the generated report on Microsoft SharePoint using the "Copy File on Microsoft SharePoint" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Microsoft SharePoint. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename. Use the do lookup functionality to find a Drive Id or a Site Id,  but do not specify both.
   
   
   
   
2. Add the "List Items On Drive By Site" or "List Items On Drive" block from the Microsoft SharePoint connector to the automation to get all the items on a drive/site. Use the do lookup functionality to find a Drive Id or a Site Id.
   
   
   
   
3. Add a "Filter List" block to retrieve the generated report stored in SharePoint based on the report name. Note that the report name is equivalent to the Path obtained from the output of the "Generate Report" block. Set the condition as shown in the screenshot below.
   
   
   
   
4. Add the "Create Sharing Link" block from the Microsoft SharePoint connector to the automation. Configure it to use Drive Id and Id from the output of the "Filter List" block in the Drive Id and Item Id parameter. Set the Scope parameter value to anonymous to provide access to the sharing link to anyone (including individuals outside your organization) without needing to sign in. Keep in mind that this won't work if the anonymous support is disabled by the SharePoint admin. More info about enabling the external sharing option can be found here. Also, configure the Expiration Date Time Parameter which indicates the expiration time of permission.
   
   
   
   
5. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Amazon S3

The following steps explain how to create a public URL using the Amazon S3 connector.

1. Store the generated report on Amazon S3 using the "Copy File on Amazon S3" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Amazon S3. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename. Also, configure Region and Bucket parameters.
   
   
   
   
2. Add the "Create Presigned Object URL" block from the Amazon S3 connector to the automation and configure it to use the path of the file from the output of the "Copy File on Amazon S3" block in the Key parameter. Also, configure Region, Bucket, and Expiration parameters.
   
   
   
   
3. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Related Content

• Qlik Reporting
• Multi app reports
• Microsoft Outlook 365 Connector

Qlik AutoML is a tool within Qlik Cloud where you can quickly train and deploy models, and the make predictions against said models. In this article, we address best practices for preparing training datasets for ML experiments and/or apply datasets for generating predictions.

Guidelines

1. For column names, use camelCase or column names without spaces or punctuation.
2. No special characters in column names.
3. When working with Excel data, remove all formatting such as bold/italics, borders, currency, or color formats.
4. Make sure data types are consistent between training and prediction datasets. It may be worth checking in Qlik Catalog to see if datasets are profiling the data type you are expecting.
5. Qlik AutoML only works with structured, tabular data. Any flat file which can be uploaded and profiled in Qlik Cloud can be used by AutoML. Based on experience, we have best results with CSV, QVD, XLSX formats.
6. AutoML does not support sentiment analysis. This would require a third-party service (such as Amazon Comprehend) to generate structured data points for AutoML to use.  You can use Comprehend in Qlik Sense directly using our connector and then use that output as a feature in AutoML.
7. For multi-table files such as Excel, only the first sheet will be used for a table.
8. Date columns are currently treated as categorical feature type. Feature engineering of date columns to numeric type should be done prior to using the dataset in an ML experiment.
9. Be aware of dataset size limits based on your tenant type.
10. For null data, if a column contains more than 50% null values it will be dropped.
    
    If greater than 50%:
    For numeric type: it uses the mean.
    For categorical type: uses value 'other'

We will continue to update this list as we encounter other issues related to data used in Qlik AutoML.

Environment

Qlik AutoML 

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.

Related Content

How To Get Started with Qlik AutoML

If you require further details on an error code or if you encounter error codes we do not have listed, please contact support. We will investigate further.

Related Content

Authentication and Authorization

Authentication and authorization with the Microsoft Excel Connector in Qlik Application Automation works through oAuth2. When a user attempts to connect a Microsoft Excel datasource, the user will be redirected to the Microsoft login page where a user is prompted to give permission for Qlik Application Automation to access their Office 365 tenant.

The following scopes are being requested by Qlik Application Automation:

• Offline_access
• User.Read
• Files.ReadWrite.All

Working with excel worksheets

The Microsoft Excel connector has blocks available to perform actions on worksheets, data inside worksheets and tables inside worksheets. When working with data, we always recommend to work with tables rather than data on the worksheet due to ease of use.

Listing rows from Excel File

This block obtains values from an excel file worksheet from a specified range. The following input parameters are used:

• Drive ID: This is a lookup that will query a user's drive.
•  Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet name: Can be selected using lookup or alternatively the worksheet name or ID can be manually provided.
• Start Cell: The upper left bound cell of the range to return.
• End Cell: The lower right bound cell of the range to return.

The block returns a double nested array. The first level contains a row, the second level contains the value of a column in that row.

The same block also exists for working with tables. Here the start cell and end cell are replaced by a Table ID.

Create a new worksheet

With the block Add Worksheet to Excel File a user can add a new worksheet to an Excel document. It takes the following input parameters:

• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Name: Name for the new worksheet name.

Updating Rows in a Worksheet

Using the block Update Rows in Excel Sheet you can specify a range in which you want to overwrite existing data. The following input parameters are required:

• Drive ID: This is a lookup that will query a user's drive. A sharepoint drive ID can also be provided.
• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet name: Can be selected using lookup or alternatively the worksheet name or ID can be manually provided.
• Start Cell: The upper left bound cell of the range to return.
• End Cell: The lower right bound cell of the range to return.
• Values: A double nested array containing data for each cell in the specified range. This has to match the range specified by the Start Cell and End Cell inputs. It is strongly recommended to work with variables and construct a listOfRows variable. This variable should be a list and it should be filled with multiple lists. An example could look like the following:

Create a new table

Using the block Create Excel Table With Headers a user can create a table in Excel. Using the block Add Table to Excel File Worksheet a user can also create a table without headers. The following input parameters are being requested:

• Drive ID: This is a lookup that will query a user's drive.  A sharepoint drive ID can also be provided.
• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet: When item is selected, a lookup can be used to search for the different sheets in which the table has to be placed. You can also provide the name or ID of the worksheet.
• Start Row: The row where the headers will be placed. Indexes in Excel start from 1.
• Start Column: Use alphabetic letter.
• End column: Use alphabetic letter.
• Headers: Array of strings to use as header values. Keep in mind that the number of columns selected using the start column and end column have to match with the headers array. E.g. C-E as column start/end for an array of 3 headers.
• Name: Name of the table for easy references.

Aside from creating a table, we can also delete is by the use of the Delete Table from Excel File Worksheet block. This requires an item ID, worksheet and Table ID.

Find Row(s) in Excel Worksheet Table

Two blocks serve to find a matching row in an Excel Table. These blocks are Find Row in Excel Worksheet Table and Find Rows in Excel Worksheet Table. The first one will only return the first row found, the second one will return all rows found matching these criteria. The following input parameters are required:

• Drive ID: This is a lookup that will query a user's drive.
• Item ID: ID of an item. Using the lookup a user can query a specific folder to search for excel sheets
• Worksheet: When item is selected, a lookup can be used to search for the different sheets in which the table has to be placed. You can also provide the name or ID of the worksheet.
• Table ID: Can be obtained using the lookup once all above fields have been filled out.
• Column Index For Search: The index of the column that is being searched for a value. The indexes are zero based.
• Search Value: The value to search for. Only fully matching values will work.

Sharing workbooks

Functionality to share workbooks is not included in the Microsoft Excel connector. These actions can be done using the Microsoft Onedrive or Sharepoint connector.

Limitations

• Cannot create a new excel file.

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.

Loading data from Oracle may fail on a full load with the error:

ORA-01555: snapshot too old: rollback segment number string with name "string" too small

Resolution

This is an Oracle configuration issue which must be resolved for the task to be able to continue.

In Automatic Undo Management mode, increase the setting of UNDO_RETENTION. Otherwise, use larger rollback segments.

You can verify your current settings:

SHO PARAMETER UNDO;
SELECT SUM(BYTES)/1024/1024 "MB", TABLESPACE_NAME FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME

Verify how large the problematic table is and what the current settings are. Then increase the sizes as per your findings. 

Oracle references: 

http://www.dba-oracle.com/t_ora_01555_snapshot_old.htm
https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:275215756923
http://www.dba-oracle.com/oracle_tips_rollback_segments.htm

Cause

It caused by rollback records needed by a reader being overwritten by other writers.

Environment:

Qlik Replicate 

 
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  

A log stream from SQL was being loaded into Microsoft Azure Databricks Delta Target, but the process failed.  The error occurred during a full load of a table:

00007080: 2023-02-20T19:32:08 [TARGET_LOAD ]E: Failed (retcode -1) to execute statement: 'COPY INTO `raw_iso_les`.`text_translation` FROM(SELECT cast(_c0 as INT) as `TextID`, cast(_c1 as INT) as `LanguageID`, _c2 as `Micro`, _c3 as `Short`, _c4 as `Medium`, _c5 as `Extended`, _c6 as `Text`, _c7 as `MicroAudioURL`, _c8 as `ShortAudioURL`, _c9 as `MediumAudioURL`, _c10 as `LongAudioURL`, _c11 as `TextAudioURL`, _c12 as `SmallIconURL`, _c13 as `MediumIconURL`, _c14 as `LargeIconURL`, cast(_c15 as INT) as `OrgChecksum`, cast(_c16 as INT) as `CustChecksum`, cast(_c17 as INT) as `ReferenceID`, cast(_c18 as TIMESTAMP) as `LastUpdateOn`, _c19 as `LastUpdatedBy`, cast(_c20 as TIMESTAMP) as `CreatedOn`, _c21 as `CreatedBy`, cast(_c22 as BOOLEAN) as `Active`, cast(_c23 as TIMESTAMP) as `LastDeleteOn`, _c24 as `LastDeletedBy`, cast(_c25 as TIMESTAMP) as `LastReactivateOn`, _c26 as `LastReactivatedBy`, cast(_c27 as INT) as `ArchiveID`, cast(_c28 as TIMESTAMP) as `LastArchiveOn`, _c29 as `LastArchivedBy`, cast(_c30 as TIMESTAMP) as `LastRestoreOn`, _c31 as `LastRestoredBy`, cast(_c32 as INT) as `RowVersionStamp` from 'abfss://XXXX') FILEFORMAT = CSV FILES = ('/X/X/X/X/12/X.csv.gz') FORMAT_OPTIONS('nullValue' = 'attrep_null', 'multiLine'='true') COPY_OPTIONS('force' = 'true')' [1022502] (ar_odbc_stmt.c:4906)
00007080: 2023-02-20T19:32:08 [TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: HY000 NativeError: 35 Message: [Simba][Hardy] (35) Error from server: error code: '0' error message: 'org.apache.hive.service.cli.HiveSQLException: Error running query: org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 3805190.0 failed 4 times, most recent failure: Lost task 0.3 in stage 3805190.0 (TID 32173534) (10.139.64.145 executor 2621): com.univocity.parsers.common.TextParsingException: java.lang.ArrayIndexOutOfBoundsException - 20480
Identified line separator characters in the parsed content. This may be the cause of the error. The line separator in your parser settings is set to '[lf]'. Parsed content: ... [1022502] (ar_odbc_stmt.c:4913)
00007080: 2023-02-20T19:32:08 [TARGET_LOAD ]E: Failed to copy data of file x\x.csv to database [1022502] (cloud_imp.c:6497)

Resolution

To resolve the issue, the user updated Qlik Replicate to the November 2022 version and reloaded the table. This will resolve the current issue and prevent the table from failing again in the future. 

Environment

Qlik Replicate 
Microsoft Azure Databricks Delta Target

To connect to Snowflake using ODBC with keypair authentication, you can use the following connection string format:

Driver={SnowflakeDSIIDriver};Server=<account_name>.<region_name>.snowflakecomputing.com;User=<username>;PrivateKey=<path_to_private_key>;Db=<database_name>;Schema=<schema_name>

Each part of the connection string represents:

• Driver: The ODBC driver name for Snowflake.
• Server: The name of your Snowflake account with the region where your account is located (e.g. us-west-2).
• User: Your Snowflake username.
• PrivateKey: The path to the private key file on your local machine.
• Db: The name of the Snowflake database you want to connect to.
• Schema: The name of the Snowflake schema you want to use.

Note that you may also need to include additional connection parameters, such as Warehouse, Role, and SSL. Here's an example connection string that includes these parameters:

Driver={SnowflakeDSIIDriver};Server=<account_name>.<region_name>.snowflakecomputing.com;User=<username>;PrivateKey=<path_to_private_key>;Db=<database_name>;Schema=<schema_name>;Warehouse=<warehouse_name>;Role=<role_name>;SSL=on

Replace the placeholders in the connection string with the appropriate values for your Snowflake account and keypair authentication setup.

Environment

Qlik Replicate 
Snowflake Target

Due a product defect, users deleted in mid-March 2023 might still keep a license assigned to them.

Environment

• Qlik Cloud 

Resolution

The issue was solved on March 21st, and deleting users correctly deallocates licenses.

Qlik is working on finding a solution for removing licenses still allocated to users that were deleted during this period for both Qlik Sense Enterprise and Qlik Sense Business subscriptions.
To speed up things, customers on Qlik Sense Enterprise can import and run the attached automation.