Activating a Qlik GeoAnalytics license using the license tool may display the following warning:

The type initializer for 'Qlik.Sense.Lef.LefParser' threw an exception.

Only LEF licenses are affected. Signed key license keys will apply without a warning.

Resolution

This warning does not affect any functionality. It refers to an additional check failing, but still applies the license as expected. The warning can be safely ignored. 

Cause

The defect QB-29901 is, as of the writing of this article, still under investigation. 

Internal Investigation ID(s)

QB-29901

Environment

• Qlik Geo Analytics

This document explains the differences between Talend license levels, and describes important steps that must be completed before lowering your license level with Talend products. Talend offers three different license levels: listed from advanced to basic, they are Master Data Management, Management, and Data Integration/ESB. Talend projects, Jobs, and components are not compatible across each of the licenses available, so if you lower a license without first performing the proper steps, the potential for critical problems is high. This document will help you successfully lower your license level with Talend products.

This article is relating to downgrading Talend Data Fabric license to Talend Real-Time Big Data Platform. The difference between the licenses is that the MDM features/user type is removed for RTBDP licenses. If you have a Talend Data Fabric license with any MDM projects, you'll need to proceed with the following steps below.

Understanding the three licenses and how they are layered

Licenses

The license used in Talend Administration Center enables an administrator to create and administer projects and users of different types. You can see what licenses you have available in Talend Administration Center by navigating to the Menu tree > Settings > Licenses.

The table below describes what you can do in your product according to your user type and license

Preparation & Migration

The example used here will be downgrading from Master Data Management to Data Management. If you are downgrading from Master Data Management or Data Management to Data Integration/ESB, the concept will be the same

Projects

You must create new projects inside of TAC with the project type of Data Management, or to the level of the license you are downgrading to. To complete this part, you must log into TAC and locate Projects under the Menu tree. Since you are not able to change the project type on an existing project, you may duplicate a project, then select the correct project type. If you are connecting to GIT, verify that the settings and URL are correct under the Advanced Settings after duplicating or creating a new project.


 

Authorization

After the new project with the correct license level is created, you will not be able to see the project available in Studio until you provide the users with permissions. Inside of TAC, you will need to locate Project Authorizations under the Menu tree. Here you must choose the new project and provide the users with the desired permissions on the right side. In the Rights column, you can choose to give either Read Only or Read/Write by choosing the icon with the person and pencil. If you have any groups, you will need to choose the tab at the top center Authorization by User/Group to make sure the groups also have the proper permissions.


 

Users

Log into TAC, navigate to the Menu tree, and locate Users. You must lower the users from MDM to DM (or the desired license level) on the right-side panel of each user that is selected. If applicable, you should verify that their GIT user is correct.

During this process, you should keep one user at your current license level until the end of the downgrading project, preferably the admin user.

If you are unable to change the user type, you may not have the proper permissions or the user may still be logged in.

To verify if the user is logged in, check the Users page of Talend Administration Center. You can see which users are logged into the Talend Studio, Talend Data Preparation, and Talend Administration Center. Log them out if needed.

Data Preparation and Talend Data Stewardship will not be covered in depth, but if the user is a Data Preparation or TDS user be sure to check the Data Preparation User box and select their desired roles.

Migration

To begin this portion, log in as the user at your current license level, as discussed in the Users section.

When you start up your Studio, be sure to choose the existing projects that have your current license level. If you are doing remote, you can verify the user that you are logging in with, so you know you are entering the correct projects and have proper permissions.



Once you have logged in to your current project, you will need to begin exporting your Jobs into a specified location.

To export a Job:

1. Right-click the Job, and select Export Job.
2. To the right of Select archive file, click Browse to choose the destination and name for the Job ZIP archive.
3. Select the Job Version.
4. Check the box to Export Dependencies.
5. Check all Options.
6. Click Finish.

You will then want to log into the new project, which should be empty and have the license level you will be downgrading to. Once you have logged in to that project, you will need to import the jobs you previously exported.


To import a Job:

1. Right-click Job Designs in the Repository, then select the Import items option.
2. In the next window, browse to a root directory or an archive file path where your exported items are stored. A list of items appears in the table.
3. Select the items you want to import. Choose the Overwrite existing items option if the items already exist in your repository and you want to overwrite them.
4. Click Finish.
5. If the newly-imported items do not appear, click Refresh to refresh the Repository.

Components

Once you have imported your Jobs, you will want to test them in the new project and verify that the components work and are not a part of the higher-level license that you plan to downgrade from. To confirm that your components function properly, review the Component Reference Guide

If you have any schedules, it would be a best practice to verify the Jobs run on the schedulers and any other unique designs you may have implemented.

Once you have verified that your Jobs run successfully on the new license platform, request the downgraded license from your Customer Success Manager.

Environment

Talend Administration Center 

Talend Studio 

Qlik NPrinting SLK License cannot be applied or updated after the upgrade.

Licensing fails with:

The Licence Service is not responding. Restart the Qlik NPrinting License service

The Qlik NPrinting log files read:

"errorMessage":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": dial tcp: lookup license.qlikcloud.com: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.","errorType":"LICENSES-InternalServerError","level":"info","logTraceId":"bf71fd0bcf272dd3528824ac4fb5f3a6","statusCode":500

"error":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": context canceled","level":"error","logTraceId":"d7c48ffd76242e3522db613652462ee5","message":"Failed to fetch license definition."

"errorMessage":"Too much time has passed since the last license update","errorType":"LICENSES-OutdatedLicense","level":"info","logTraceId":"e7c3a2cc454f5dc843b68e5bb5e6840c","statusCode":403

Resolution

This issue is being caused by the license server being unreachable. If the server has internet connectivity, then the likely root cause is a proxy being deployed.

Follow these steps to troubleshoot and resolve the issue:

1. Login to Qlik NPrinting Server with  Service Account and open Qlik NPrinting Web Console with NPrinting Service Account.
   
   
2. Verify that the Qlik NPrinting License service is up and running.
   
   
3. Try to restart the Qlik NPrinting License service and try to apply for the Qlik NPrinting SLK License before going to the next step.
   
   
4. Verify that the Qlik NPrinting server has an active internet connection and that connectivity to license.qlikcloud.com on port 443 is possible from the server running the Qlik NPrinting licensing service.  (You must get "default backend - 404" in the browser when accessed to license.qlikcloud.com)
   
   
5. In some rare cases, the 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 seem to be performed, there is a way to force the sync: remove one/more characters from the SLK License and click to "apply".
   
   The license will be refused as it's an incorrect one. This action will force the license synchronization. Now, try to apply with an actual SLK License.
   
   
6. If the above did not resolve the issue, check if you have a proxy configured in the NPrinting Server.
   
   
   1. Open Internet Options from Control Panel and check for Proxy IP/URL
      
      
      
      
   2. If the Proxy is configured, do the changes accordingly in %Program Files%\NPrintingServer\NPrinting\License\license.configusing Licensing service proxy Setup 
      
      
   3. Make sure to Stop and Start the Qlik NPrinting licensing service before and after performing the changes.

Cause

When you upgrade the Qlik Nprinting Server, the existing configurations files will be overwritten to default configurations files, and any changes done before the upgrade have to be updated again.

So make sure to take a backup of the Files (Eg: Config) and Folders before performing the upgrade.

Environment

Qlik NPrinting 

Related Content

Licensing service proxy authentication 
Licensing Qlik NPrinting offline 

Question I

What is the expiration period for a license token?

90 days. This is not guaranteed though and it may differ among customers.
Also, the 90 days may change in the future, so please check with a license specialist if not certain.

Question II

Can the license validate automatically after renewal?

In the reference below, it mentions that “you may have to validate it manually from the Talend Administration Center web application.". There is a chance that it may not validate automatically, and if that is the case, they would have to manually validate their license.

For more information about How to validate a license after renewal, please refer to Qlik Talend Documentation: validate-license-after-renewal 

Question III

What is the URL/port to open to access the Internet and validate the license from TAC?

The URL is not required. The port is 443.

Question Ⅳ

What is the validation token form URL?

You will get the validation token form here:

https://www.talend.com/api/get_tis_validation_token_form.php

Environment

Talend Studio 

Talend Administration Center 

Talend Cloud 

Content

• Background
• Qlik Licensing Service (QLS)
• Signed License Key (JWT)
• What is a JSON Web Token?
• What’s in this for me as a Customer?
• Activation Using the Signed License Key
• Frequency in which license information is updated
• Data Transmitted by an Activation Request
• Activation Reply
• Analyzer Capacity License Report Process
• Data Transmitted
• Sync Reply
• User Assignment Sync Process
• Data Transmitted
• Reply fromLicense Backend

Background

Qlik Products have generally utilized license keys to enforce license entitlements and use rights.  During activation, the licensed entitlement is downloaded to the product in the format of a Licensing Enabler File (LEF). Activation requires internet connectivity to the deployment and is triggered by entering a 16-digit serial number and a corresponding control number. Offline activation is also supported using a manual LEF by copying and pasting a text file into the activation user dialog. Communication is through an http protocol.

Qlik Licensing Service (QLS)

Introduced with the February 2019 release[GM1]  of Qlik Sense Enterprise, Qlik has developed an alternative process for product activation. There have been several drivers for this change, including a move to an https protocol for a more secure connection between the Customer deployment and Qlik infrastructure. More information follows below. 
 
To allow for Customers to make the decision when to move, Qlik has introduced the use of a Signed License Key to determine which activation method to use. Over time Qlik Licensing Service will replace the current activation process, but for now both methods of activations will work.

Signed License Key (JWT)

As mentioned above, Qlik has added one additional way to activate Qlik products. 

What is a JSON Web Token?

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWT’s can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
 
Although JWT’s can be encrypted to also provide secrecy between parties, we will focus on signed tokens. Signed tokens can verify the integrity of the claims contained within it, while encrypted tokens hide those claims from other parties. When tokens are signed using public/private key pairs, the signature also certifies that only the party holding the private key is the one that signed it. That is why we refer to this as the Signed License Key.

What’s in this for me as a Customer?

With the use of a Signed License Key, there are more Product and deployment offers to use.

• Use of multi-site deployments, such as connecting a Qlik Sense Enterprise site with a QlikView Server deployment using Qlik Sense Enterprise license options. This is enabled by accepting a Dual-Use offer for each QlikView deployment that should be enabled for a Unified License scenario.
• Use of multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
• Use of the consumption-based license, Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.

All of the above is enabled by the use of the Signed License Key. This made possible as the local deployment will sync entitlement data with all deployment’s using the same Signed License Key through an online database, License Backend, hosted by Qlik within Qlik Cloud.

Activation Using the Signed License Key

This is initiated by entering a Signed License Key to the Control Panel. The request is performed by the service Licenses using port 443 (https protocol procedures applies).

Frequency in which license information is updated

Assignment information (what user has what type of access assigned) is synchronized from the license service to license.qlikcloud.com every 10 minutes. 
Changes to a license (such as adding additional analyzer capacity) can take up to 24 hours to be retrieved.

Data Transmitted by an Activation Request

Activation Reply

Analyzer Capacity License Report Process

(Time schedule is not disclosed and includes grace time to support outages in the internet connection, a/k/a Optimistic Delegation.)

Data Transmitted

Sync Reply

User Assignment Sync Process

Data Transmitted

Reply from License Backend 

 
This Reference Guide is intended solely for general informational purposes and its contents do not form part of the product documentation.  The information in this guide is subject to change without notice.  ALL INFORMATION IN THIS GUIDE IS BELIEVED TO BE ACCURATE BUT IS PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.  Qlik makes no commitment to deliver any future functionality and purchasing decisions should not be based upon any future expectation.

Analyzer Capacity Licenses can be assigned automatically based on Analyzer Capacity License Rules. These rules can be set up to provide Analyzer Capacity to users, groups, or anonymous users.

This article covers what function the license type has, how to assign it, and how to track usage. 

Index:

• What is an Analyzer Capacity license?
• How to assign Analyzer Capacity Licenses
• Assigning Analyzer Capacity in Qlik Sense Enterprise SaaS:
• Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:
• How to monitor Analyzer Capacity usage
• Qlik Cloud
• Qlik Sense Enterprise on Windows Client Managed
• In QlikView
• How Qlik Sense Analyzer Capacity Works (video)
• Related Content
• Environment

What is an Analyzer Capacity license?

The Qlik Sense Analyzer Capacity license type is automatically assigned to users not assigned a Professional or Analyzer license and consumes time during an active session with the minimum session length set to 6 minutes.

Overview:

• An Analyzer Capacity license type would typically be used by users not assigned to any of the available named user types (Professional or Analyzer).
• The capabilities for the Analyzer Capacity license type are similar to the current Analyzer user type and supports the same features. 
• Analyzer Capacity is available for:
  • Qlik Cloud 
  • Qlik Sense Enterprise on Windows
  • QlikView.
• Analyzer Capacity works with Both Signed License Key and Signed License Definition.

Details:

• The minutes are based on a monthly subscription, which resets at 0:00 UTC time on the first day of the calendar month.
• Consumption is in 6-minute blocks. No consumption during idleness.
• Overage can be added to the subscription. See How to manage Overage for Analyzer Capacity.

How to assign Analyzer Capacity Licenses

Assigning Analyzer Capacity in Qlik Sense Enterprise SaaS:

No setup is required. If no Professional or Analyzer License was assigned, Analyzer Capacity is automatically allocated. 

See Enabling dynamic license assignment for details. 

Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:

1. Open the Qlik Sense Management Console
2. Go to Licenses Management
3. Open Analyzer Capacity Rules in the right-hand menu (See fig 1)
4. Click Create new 
   
   Fig 1
   
   
5. Provide details for your rule. In our example, we are enabling users in the group capacity to receive Analyzer Capacity Licenses. 
   
   Name: Name of your rule
   Description: Description of your rule
   Actions: Allow access 
   
   Populate the conditions accordingly. See Fig 2.
   
   Fig 2
   
   If you are looking to provide access for anonymous users, see How to allow Anonymous Hub access in Qlik Sense Enterprise on Windows.
   
   
6. Click Apply
7. All users in the defined group will now receive an Analyzer Capacity License. 
   
   
   

How to monitor Analyzer Capacity usage

Qlik Cloud

The Entitlement Analyzer for Qlik Cloud provides detailed usage data for Analyzer Capacity, but a tenant admin can gain an overview through the Management Console at any time:

1. Open the Qlik Cloud Management Console
2. Open the User allocation tab
3. Open the Overview tab
4. Review the current Analyzer capacity usage 
   
   
   
   

The Entitlement Analyzer is only available for Qlik Cloud.

Qlik Sense Enterprise on Windows Client Managed

The bundled License Monitoring app provides usage data for Analyzer Capacity, but an administrator can gain an overview through the Qlik Sense Management Console at any time:

1. Open the Qlik Sense Enterprise on Windows Management Console
2. Go to License Management
3. The License usage summary tab (a) lists the current Analyzer capacity usage (b)
   
   
   
   

In QlikView

1. Open the QlikView Management Console and go to System
2. Open the Licenses tab
3. Select License 
4. Switch to the Professional and Analyzer access tab.
5. The General tab lists the current Analyzer Capacity usage 
   
   

How Qlik Sense Analyzer Capacity Works (video)

Related Content

Analyzer capacity license and monitoring (Client Managed)
Qlik Licensing Service Reference Guide 
Assigning user allocation (Qlik Cloud)
Analyzer capacity license (Qlik Cloud)
Top 5 things to know about modern Qlik Licensing

Environment

QlikView 
Qlik Sense Enterprise on Windows 
Qlik Cloud 

Introduction

As a Talend Test Migration License is generated for a period of 60 days (2 months) at a time, how to extend your Talend Test Migration License when it is expiring or already expired in Talend Studio/Talend Administration Center?

Resolution

Please create a new case in Qlik Customer Support Portal so that our Support can generate a new test migration license for you. As long as there is a current subscription of the account, a test migration license will be provided.

Please keep in mind that a Talend Test Migration License is valid for 60 days(2 months) a time.

If you are looking to obtain a Test Migration license, see How to Request and Utilize a Talend Test Migration License.

If you are looking for Qlik Support Case Portal, see How to contact Qlik Support 

Environments

Talend Studio 

Talend Administration Center 

When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ depending on your requirements or the version of the product.

You’ll have two activation options:

• The Signed License key (SLK), available for most Qlik products
• (legacy) And a combination of the 16-digit key, a control number, and the License Enabler File (LEF)

These license activation methods cannot be mixed. A license activated with an SLK cannot also be activated using the key + control number method.

In this blog post, we will cover the differences between the two activation methods, as well as what benefits the Signed License key brings to the table. Details on how to activate them will follow in the second post to this short series.

What is a Signed License Key (SLK)?

• The SLK is an encrypted JSON web token used to activate Qlik Sense Enterprise or ABDI. It contains product information, available access types for users, and any applicable product add-ons or limitations.
• The SLK is to be used for activating Qlik Sense Enterprise on Windows licenses using the Professional/Analyzer user model. Qlik Sense Core Based and Token based licenses should use the legacy LEF activation method.
• You cannot change from an SLK activated system to a LEF activated system.
• The SLK requires online connectivity to our licensing server for both activation and continued operation.
• For information on how to apply an SLK, see How to Apply a Signed License Key
• The time (Subscription date, Analyzer capacity reset) is on UTC

The SLK is mandatory for:

• The use of Qlik Sense Analyzer Capacity licenses
• Any deployments using Qlik Sense Enterprise on Kubernetes or Qlik Sense Enterprise on Cloud Services, as well as Multi-Cloud (a combination of Qlik Sense Enterprise on Windows and Cloud offerings)
• Unified Licenses, which combine Qlik Sense and QlikView
• See Qlik product licenses for more information.

What is a License Enabler File (LEF)?

• Every license has a LEF. Each 16-digit license number that you get can be translated into a LEF, regardless of the method used to activate the license. The LEF itself contains all the instructions for the Qlik Product, such as license level, numbers of users, access types available for assignment, as well as all the limitations or add-on.
• When applying your license using the license number and control number, the LEF will be downloaded to the product during activation­. It will be updated with each refresh request.
• The first line of the LEF is always your 16-digit license number and it ends with a checksum so that an unauthorized alteration of the content is impossible.
• It requires a control number for activation
• You can change from a LEF activated system to an SLK activated system (but not the other way around). Always use LEF activation if your license has tokens.
• The LEF can be activated offline and used offline, see How to license a QlikView or Qlik Sense server without Internet access for details.
• The time (Subscription date) is on UTC

The LEF activation method is currently required for:

• Qlik Sense
  • Core-based licenses
  • Token-based licenses
  • See Qlik product licenses for more information.
• QlikView
  • CAL-based licenses
  • See Licensing QlikView for more information. 

How do I get an SLK?

• Your signed license key will be sent to you in the license delivery email.
• If you did not receive your SLK via email, please contact Customer Support. Please make sure to provide the corresponding 16-digit license key and the Support team will be able to get the SLK for you.
• There is no way to get the SLK from the Support Portal at this time.

Benefits of using an SLK

Using the Signed License Key makes more product and deployment options available to you.

Examples of these are:

• Multi-site deployments, such as connecting a Qlik Sense Enterprise site with a QlikView Server deployment using Qlik Sense Enterprise license options. This is enabled by accepting a Dual-Use offer for each QlikView deployment that should be enabled for a Unified License scenario.
• Multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
• Qlik Sense Enterprise for Kubernetes and Qlik Cloud Services. Either stand-alone or in a multi-cloud setup.
• Consumption-based licenses, such as Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.

All the above is enabled by the use of the Signed License Key. This is made possible by the local deployment syncing all entitlement data (assigned users access, etc.) with all available deployments sharing the same SLK. The synchronization is done using the Qlik Licensing Services and our license backend hosted in Qlik Cloud.

If you are curious about more information around the Qlik Licensing Service, see the Qlik Licensing Service Reference Guide.

How do I get a LEF?

• You can get the LEF and control number from the Support Portal by following the steps outlined in How to request a control number and LEF

And this is it for an overview of our available license types and activation methods. We’ll follow this up with part two soon, detailing the move from a LEF activated license to an SLK. Until then, give this post a like if you found it helpful! And please let us know if you have any questions or feedback in the comments.

Customer is currently using an EOL (End of Life) Talend version and needs an extension as the license is about to expire. 

Resolution

Please contact your CSM/AE to create an internal request for the EOL license version that needs to be extended. CSM/AE will create an internal ticket (ServiceNow) for this request to be approved internally.

Due to End of Life (“EOL”) Software or Cloud Service Client is not available for sales or support by Talend and does not receive Monthly Releases or Patches, Talend does not guarantee the correction for Third Party software on EOL Software.

At Talend’s discretion, Talend Customer Service may provide support assistance for EOL Software or Cloud Service Client at an agreed upon fee.

Related Content

Talend Products lifecycle 

Environment

#Talend License 7.3 and prior

After license renewal, prior Talend license versions still shows as expiring in a few days. End Date on Prior license versions does not match subscription end date in Subscription page in Talend Cloud. Customer is still using this license version in their local Talend Cloud Studio.

Resolution

Please reach out to the assigned CSM/AE on the account and inform them on the need to still use this license version. Afterwards, they will submit an internal request (ServiceNow) for this to be active if accepted internally.

Related Content 

Supported version: https://help.talend.com/en-US/customer-support-statements/Cloud/product-end-of-life-planning

Environment

• Talend versions prior to 8.0

This article covers the details of how to license a Qlik Sense Enterprise on Windows server with a Signed License Key (SLK).

Index:

• About the Signed License Key:
• How to apply the license:
• Related Content
• How do I license....?
• Looking for pricing information?

About the Signed License Key:

• It replaces the 16 digits license key and control number.
• It is a JSON Web token.
• It uses secure communication, HTTPS://

To apply a Signed License Key, a secure network connection is required to be established: A signed license key requires connectivity to license.qlikcloud.com. See List of IP Addresses behind license.qlikcloud.com and lef.qliktech.com for details.

It can establish in any of the security scenarios below: 

• Less strict security
  HTTPS port (port 443) is open
  
  
• More secure
  HTTPS port is open outbound only
  
  
• Even more secure
  HTTPS port is open outbound, limited to https://license.qlikcloud.com
  
  
• Most secure
  HTTPS via proxy, with or without proxy authentication
  
  
• No connection
  See Using a Qlik signed license in an offline environment.

All nodes in a Qlik Sense Enterprise on Windows on-premise multi node environment need access to the license server. 

How to apply the license:

1. You receive the Signed License Key via email after a successful purchase
2. Launch the Qlik Sense Management Console
3. If not immediately prompted for a license, go to License Management
   
   
   
   
4. Open Site License in the menu to the right
5. Paste in your full key. Thi sis the JSON token you received in the email.
6. Click Apply
   
   
   
   

Related Content

How do I license....?

• How to license QlikView Server 
• How to license QlikView Desktop
• How to license NPrinting
• Activate Qlik Products without Internet access - April 2020 and onwards

Looking for pricing information?

• Qlik Pricing - Qlik Host and Client Managed 

Issue

• I am unable to login to my NPrinting AWS marketplace server upon initial setup

Resolution

• To assist you with your initial setup install such as login issues where AWS marketplace products are offered, please visit the AWS Marketplace support page at the link below
• AWS Qlik Nprinting - BYOL

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

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

After applying the license, the administrator should review the Engine configuration to ensure that sufficient capacity has been assigned to the Engine(s) in the Qlik Sense site.

In this example, 256 cores are allocated to the license but the Central only has 8 available cores:

 

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.
Customers on Qlik Sense Business can use the Qlik-cli instead by following this other article.

Related Content

Unable to remove or de-allocate user license, the license is reassigned to the user 

Using a Signed License Key with its Signed License Definition in a long term offline environment past the 90 days provided by Delayed Sync requires (besides license modification) additional configuration steps!

• No license has long term offline capability enabled by default. 
• Long term offline capability needs to be specifically approved by Qlik and the conditions of offline use agreed to by the customer. See Request license off-line approval - April 2020 and onwards. Once approval has been obtained through the CSO, the license will be modified with an additional attribute OFFLINE;YES;;
• Additional configuration changes are necessary for long term offline mode to function
• (Delayed Sync requires a Signed License Definition, but does not require additional configuration steps)

Configuration changes needed:

These changes will need to be done on all nodes running the Service Dispatcher. Not only the Central node. 

1. Stop the ServiceDispatcher service
   
   
2. As Administrator, open the Service Dispatcher services.conf file.
   
   Default location Qlik Sense on-prem: C:\Program Files\Qlik\Sense\ServiceDispatcher
   Default location QlikView: C:\Program Files\QlikView\ServiceDispatcher
   
   
3. Locate [Licenses.parameters]and add the parameter -offline 
   
   Example:
   
   [licenses.parameters]
   -qsefw-mode
   -offline
   -app-settings="..\Licenses\appsettings.json"
   
   
   
   The displayed order is required in the February 2024 IR release. Previous and future versions (Patch 2 and later) do not have a fixed order requirement.
   
   
4. Save the file
   
   
5. Start the ServiceDispatcher service

Once the changes has been done you will need to retrieve the updated SLD key from https://license.qlikcloud.com/sld and then apply the same for successful offline activation.

Note on upgrading: If using a version of Qlik Sense prior to November 2022, this file may be overwritten during an upgrade.  Please be sure to re-apply this parameter and restart the Service Dispatcher on all nodes after an upgrade. With Qlik Sense November 2022 or later, custom service settings are by default kept during the upgrade. See Considerations about custom configurations. 

Internal Investigation ID(s):

QB-25231

The license used has the required offline tag, but offline licensing after an upgrade of Qlik Sense Enterprise on Windows to February 2024 fails with error:

There was an error when getting license information from the license service

In repository logs you also could have the below error:

There was an error contacting the license service. Keep retrying

Resolution

Qlik has identified a defect in the initial February 2024 release as well as patch 1 (QB-25231).

Workaround

Change the -offline parameter position in the configuration file.

1. Stop the ServiceDispatcher service
   
   
2. As Administrator, open the Service Dispatcher services.conf file.
   
   Default location Qlik Sense on-prem: C:\Program Files\Qlik\Sense\ServiceDispatcher
   Default location QlikView: C:\Program Files\QlikView\ServiceDispatcher
   
   
3. Locate [Licenses.parameters]and add the parameter -offline 
   
   Example:
   
   [licenses.parameters]
   -qsefw-mode
   -offline
   -app-settings="..\Licenses\appsettings.json"
   
   

   
   Previous versions of Qlik Sense allowed for the -offline parameter to be situated anywhere. February 2024 requires it in this order.

4. Save the file
   
   
5. Start the ServiceDispatcher service

Fix Version

QB-25231 is expected to be fixed in Qlik Sense Enterprise on Windows February 2024 Patch 2.

Cause

QB-25231

Related Content

Long term offline use for Qlik Sense and QlikView Signed Licenses 

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes, or contact support with the QB-25231 for reference.

Environment

Qlik Sense Enterprise on Windows February 2024

Qlik Product licenses synchronize with the license servers at different intervals depending on the product and license activation. Obtaining new license information tells the product what features are enabled, while user assignments synchronizes user assignments across multiple sites. 

Content:

• How frequently does Qlik Sense Enterprise on Windows update its license information?
• How frequently does Qlik Cloud update its license information?
• How frequently does QlikView update its license information?

How frequently does Qlik Sense Enterprise on Windows update its license information?

If Qlik Sense Enterprise on Windows was licensed using a Signed License Key, it will retrieve its License Definition File:

• on initial activation
• every 24 hours

User assignments will be synchronized every 10 minutes.

This means a new feature enabled on your license may take up to 24 hours to unlock, while users will synchronize across multiple sites within approximately 10 minutes but no longer than 20.

If Qlik Sense Enterprise on Windows was licensed using the legacy LEF file, it will retrieve an update from the LEF server:

• on initial activation
• on a manual refresh
• every time the services restart (Repository Service)
• every 24 hours after the last refresh (such as Service or Server restart)

Users are not synchronized.

How frequently does Qlik Cloud update its license information?

Qlik Cloud has changes pushed from the license backend to the tenant immediately. Users are synchronized between tenants and on premise sites at a 10 minute interval.

This means a new feature enabled on your license will unlock immediately, while users will synchronize across multiple sites within approximately 10 minutes but no longer than 20.

How frequently does QlikView update its license information?

If QlikView was licensed using a Signed License Key, it will retrieve its License Definition File:

• on initial activation
• every 24 hours

User assignments will be synchronized every 10 minutes.

This means a new feature enabled on your license may take up to 24 hours to unlock, while users will synchronize across multiple sites within approximately 10 minutes but no longer than 20.

If QlikView was licensed using the legacy LEF file, it will retrieve an update from the LEF server:

• every 30 days. The setting DaysToNextLicenseCheck in the settings.ini file is by default set to 30. This can be modified.
• on initial activation (when a local LEF is not presented)
• on manual refresh
• if the LEF is faulty, e.g. checksum error, product level error, expired timelimit etc

Users are not syncronised.

The QlikView Local Client will attempt to contact the Qlik LEF server based on DaysToNextLicenseCheck in the settings.ini This is by default set to 30. This can be modified.

 The above "Every 30 days" does not apply to the Publisher. Publisher license needs to be updated manually.

Environment:

Qlik Sense Enterprise on Windows 
Qlik Cloud 
Qlik Sense Business 
QlikView