This document explains how to upload the license using a powershell/CMD terminal.

1. Download your license.txt file
2. Open a powershell terminal with admin permissions and move to the folder that contains the license 
   
   
   
   
3. Open a notepad, copy the following python script, and save it with the name “txt2json.py”
   

   import sys
   import json
   
   file_path = sys.argv[1]
   
   with open(file_path, 'r') as file:
       contents = file.read().replace('\r', '')
   
   lines = contents.split('\n')
   
   data = {}
   
   for line in lines:
       if '=' in line:
           key, value = line.split('=')
           data[key] = value
   
   result = {"cmd.license": data}
   
   json_data = json.dumps(result,indent=4)
   
   with open("./license.json", "w", newline='\n') as output_file:
       output_file.write(json_data)​

   
   
   
   
4. Run the script in the powershell terminal
   

   Python.exe .\txt2json.py <#path-where-the-license-is-located #e.g. C:\Users\user\Destop\licence.txt#>​

5. You’ll see a new file is generated (license.json).
   
   
   
   
6. Change the directory to the Qlik Replicate folder in the powershell terminal
   

   cd <#path-where-replicate-is-installed #e.g. C:\Program Files\Attunity\Replicate\bin #>​

7. Connect to the replicate server
   

   repctl.exe connect​

8. Import the license.json file
   

   repctl.exe [-d <replicate_data_dir>] importlicense license_file=<location>license.json​

   
   

Environment

• Qlik Replicate 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content 

repctl.sh importlicense format: This explains repctl.sh in a Linux deployment. There is a slight difference because the script is written in Perl instead of Python.

An error is displayed when licensing the QlikView server in the QlikView Management Console:

Unable to acquire valid license information

This error may also be seen when attempting to license a QlikView Publisher.

Root cause: Expired license.

Verify if your license has expired. The date in your LEF must extend past the version you are attempting to license.

Example: PRODUCTLEVEL;3;;2018-04-30

In this example, no release (including service releases) after 2018 can be licensed with the provided license. 

Root cause: Time limit

Similarly, verify if your license has a time limit. 

Example: TIMELIMIT;;;2018-04-30

Resolution

Contact your account owner or the partner you have purchased the license from.

Internal Investigation ID(s) 

000002784 (article)

Environment

QlikView 

Applying a Signed License Key (SLK) fails with the following error message:

The datetime property is too low for the following property: updated

Environment

Qlik Sense Enterprise on Windows November 2022 IR to Patch 1

Resolution

Upgrade to November 2022 Patch 2.

See Release Notes for ID QB-17039.

Cause

Product Defect ID: QB-17039
Internal Article: 000007375

This error is thrown by the QRS when the validator for the License property update fails on the condition:

if (date < DateTimeUtilities.SQLMinValue)

The DateTimeUtilities.SQLMinValue derives from new DateTime(SqlDateTime.MinValue.Value.Ticks, DateTimeKind.Utc);

When applying the license a DateTime lower than the min value is attempted to be set in the updated property.

Qlik Sense Desktop can authenticate against Qlik Sense Enterprise Client-Managed, Qlik Sense Enterprise SaaS and Qlik Sense Business.  This is how customers can continue to use Qlik Sense Desktop, and it provides a very economical option when paired with Qlik Sense Business. 

The following requirements need to be met:

• A functioning network connection to the Qlik Sense Enterprise Client-Managed Server or Enterprise SaaS/Business tenant.
• Use of a Professional license. Analyzer licenses do not support Desktop Authentication
  For legacy token license: User and Login Passes allow Desktop Authentication
• No TEST license. Test licenses disallow the use of authentication links 

Environment

• Qlik Sense Desktop 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
• Qlik Sense Business 

Related Content 

Configuring Qlik Sense Desktop authentication link 
How to authenticate Qlik Sense Desktop against SaaS editions 
How to authenticate Qlik Sense Desktop against a Qlik Sense Enterprise on Windows server  

How to purchase

You can purcahse Qlik Replicate, Qlik Compose, and Qlik Enterprise Manager by contacting a local sales office.

How to obtain the license

Once you have completed the order and a deal has been signed, a license is delivered by email. You will receive a license.txt file. This file contains details such as the product expiration date (if any).

This usually happens within a day of Qlik receiving the order.

Where do I find my license?

If you lose access to the email holding the license, you can instead log on to the Qlik Support Portal an access the original case which includes your license details.

You can also find your license directly in the product after you have licensed it.

What does my license include?

Your license will allow you to:

• Run tasks using the endpoints specified. Example, if you have purchased an Oracle endpoint, you will be able to run tasks using an Oracle endpoint. 
• Grant you general access (not able to use the tool for QEM nor Compose)

To get a better understanding of what your individual license allows, review your license.txt file.

Qlik Replicate: 

license_type= (evaluation or permanent)
licensed_to= (your company name)
licensed_by= (the Qlik region responsible for providing the license)
serial_no= (serial internal reference)
expiration_date= (date of expiration)
hosts= (host names in which Replicate will run. If blank, means that any host can run)
source_types= (the source endpoints purchased by customer)
target_types= (the target endpoints purchased by customer)
features= (additional features)
version= (version of Replicate)
issue_date= (issue date)
checksum= (check sum so the engine can check validity)

Qlik Compose will in addition include: 

host_role: (DEV, TEST, PROD or “*” for all)
source_db_types: (applicable for Compose for Data Warehouses only)
dwh_type: (Databases that’ll be used as DWH)
dl_type: (Databases that’ll be used as DL)
number_of_dms: (total number of Data Marts)
number_of_developers: (available if host_role is DEV)
managed_dwh_size: (size of the DWH)

Qlik Enterprise Manager is similar to Qlik Replicate

There is one license for Qlik Enterprise Manager Monitoring and another license for Qlik Enterprise Analytics. 

Please note that in order to have Qlik Replicate servers added to your Qlik Enterprise Manager monitoring, they need also to have a valid license, otherwise you will get an “Unauthorized” error when adding a Qlik Replicate server.

How to I extend or modify my license?

Qlik Replicate allows you to modify your license directly through the Qlik Replicate UI. See Requesting a license.

How do I apply the license?

• Qlik Replicate: Registering a license 
• Qlik Enterprise Manager: Replication Management license 
• Qlik Compose: License settings 

You can also apply licenses to Qlik Replicate servers programmatically by using the QEM API REST calls as seen in PutServerLicense 

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.

When buying a QlikView Client Managed license with SaaS add-on together with a Qlik Sense Enterprise license for the cloud, changes applied to one of the environment are not reflected in the other ones.

So, it is not possible to understand, from one single window, how many Professional and Analyzer seats have been assigned in total. Customers need therefore to check both environments and count the assigned license manually.

Environment

• Qlik Cloud 
• QlikView, any

Resolution

As of September 2022, the QlikView with-SaaS-add-on and the Qlik Cloud licenses are tied only by contractual agreement.
There is no technical integration between the two.

It's the customer's contractual responsibility to make sure that the number of allocated professional and analyser licenses are not exceeded. As of now, there is no technical functionality, for the customer, at the moment, to cross-verify the two serial numbers or to block allocating more seats than what was agreed contractually.

Upon launch, the Qlik Sense Desktop needs to be authenticated against either the Qlik Sense SaaS backend or a Qlik Sense Enterprise server.

! Client authentication is not supported on test servers.

This authentication is done using an authentication link.

Clicking Add authentication link brings up instructions:

If you have user access for Qlik Sense Enterprise, you can authenticate against the Qlik Sense Enterprise server when you start Qlik Sense Desktop.

Your Qlik Sense administrator will provide you with information about how you can receive the link using one of the following methods:

• Retrieving the client authentication link from your Qlik Sense Enterprise hub .
• Receiving the client authentication link from your administrator.
• Receiving a hubs.ini file from your administrator that contains the authentication link.

Qlik Sense Desktop must be installed on your computer before you start any of the following procedures.

Retrieving a client authentication link from the Qlik Sense Enterprise hub

Do the following:

1. Go to the Qlik Sense Enterprise Hub.
2. Click the three dots in the top toolbar of the hub, and then click Client authentication.
   
   
   
   

   Why do I not see the Client authentication option?

   Before you can authenticate, the Qlik Sense Enterprise authentication link must be generated by your administrator in the Qlik Management Console. See Generate and distribute an authentication link (Help.com).

3. A dialogue box opens asking you to confirm that you want to open the authentication link using Qlik Sense Desktop (QlikSenseBrowser). Confirm the dialogue.
   
   

   

    

   Qlik Sense Desktop opens and a new authentication button for the enterprise server is added to the welcome page under Authenticate against Qlik Sense Enterprise.
   
   

   

    

4. Click the authentication button to log in. You may be asked to enter your Qlik Sense Enterprise credentials.
   
   
   

   

    

   You are now authenticated and Qlik Sense Desktop opens.

After this, when you launch Qlik Sense Desktop, you can click the authentication button and log in using your Qlik Sense Enterprise credentials.

Receiving the client authentication link from your administrator

Your administrator can provide you with the authentication link. For instructions on how the administrator can obtain the link, see Generate and distribute an authentication link (Help.com). 

Client-side, do the following:

1. Click the authentication link provided by your Qlik Sense administrator.

   If you cannot click the link, copy the link into your browser and press return.

   If you are using Google Chrome, you must select the link option from the address bar that does not say Google Search.

2. A dialogue box opens asking you to confirm that you want to open the authentication link using the Qlik Sense. Confirm the dialogue.

   Qlik Sense Desktop opens and the authentication link is added to the welcome page under Authenticate against Qlik Sense Enterprise.

3. Click the authentication link. You may be asked to enter your Qlik Sense Enterprise credentials.

   You are now authenticated and Qlik Sense Desktop opens.

After this, when you launch Qlik Sense Desktop, you can click the authentication button and log in using your Qlik Sense Enterprise credentials.

Receiving a hubs.ini file from your administrator

Do the following:

1. Copy the hubs.ini file that was provided to you by your administrator to the following location: C:\Users\<user name>\Documents\Qlik\Sense\Hubs\.

   The next time that you launch Qlik Sense Desktop, an authentication link will be added to the welcome page under Authenticate against Qlik Sense Enterprise.

2. Click on the authentication link. You may be asked to enter your Qlik Sense Enterprise credentials.

   You are now authenticated and Qlik Sense Desktop opens.

After this, when you launch Qlik Sense Desktop, you can click the authentication button and log in using your Qlik Sense Enterprise credentials.

Source: Starting Qlik Sense Desktop 

When applying a Qlik Sense License Key to Qlik Sense Enterprise, the license cannot be activated.

An error is returned:

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

When the issue is connectivity related, the following string may also be registered among the log lines:
...
wsarecv: An existing connection was forcibly closed by the remote host.","errorType":"*url.Error"},...

OR, in the Repository Trace System logs:

...

ERROR QlikServer1 System.Repository.Repository.Core.Licensing.LicenseServer.LicenseServerFacade 29 58250808-d4f0-40d8-ba4c-73290bc63979 DOMAIN\qvservice There was an error when getting license information from the license service. LicenseDefinition: {"error":"LICENSES-InternalServerError","message":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)","errors":[{"code":"LICENSES-030","title":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}]}, LicenseOverview: The remote server returned an error: (500) Internal Server Error.

...

Environment:

• Qlik Sense Enterprise on Windows , with Signed License Key (SLK)

Resolution:

Internet Access

Make sure the HTTPS port for outbound connections is opened (example: port 443 - mostly used - but the port number might differ for the end-user). The port is used for accessing the endpoint at https://license.qlikcloud.com  which is required to activate the license key. See Testing connection to license.qlikcloud.com should return HTTP 404 Not Found  

If a Web proxy is required for Internet access,  see steps in image below which are documented under proxy configuration for Qlik License Service communication.

Proxy configured

If the license cannot be applied even though HTTPS port (example: port 443) is opened, or the proxy configured for Qlik License Service communication correctly; please reach out to the technical Product Support team. (How to raise a Technical case).

Verify what product the license is for

Verify that the license you purchased is for the correct product. 

Example: Signed License Keys cannot be used if a license is Token-based Only. In this case, a license number and Control Number need to be used.  

A token license looks like:

00000000000000
OVERAGE;NO;;
PRODUCTLEVEL;50;;2020-12-31
SPECIAL_EDITION;TEST;;
TEST_EDITION;YES;;
TOKENS;3000;;

Related Content:

• List of IP Addresses behind license.qlikcloud.com and lef.qliktech.com  
• Top 5 Things to Know About Modern Qlik Licensing  
• Qlik Licensing Service Reference Guide 
• How to license a QlikView or Qlik Sense server without Internet access  

End users lost their license assignments and the Qlik Sense Enterprise on Windows management console prompts for the signed license key.

Attempting to relicense the system may fail with either:

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

Only one license per product level is allowed

Environment

Qlik Sense Enterprise on Windows 

Resolution

If reapplying the license to Qlik Sense fails, please contact Qlik Support through our LIVE chat to have your license verified for possible issues.

Cause 

The license backend may have been unavailable for too long or a license has been disabled. 

Internal Investigation ID(s) 

00036071

After purchasing a license with Analyzer Capacity, no analyzer minutes can be found in the license. 

Resolution

Review your LEF (License Enabler File) to verify if the license correctly includes the following tags:

ANALYZER_TIME;1000;;
ANALYZER_TIME_UNIT;6;;

Both tags are required. Note that the TIME; value in your instance may differ.

If these tags are missing, contact us through chat so that the license status can be resolved.

Related Content 

How to request a control number and LEF 
What is a Analyzer Capacity license?  
How to Assign an Analyzer Capacity License 

Environment

Qlik Sense Enterprise on Windows 
Qlik Cloud 

Entering the Qlik Catalog license fails with:

core.error.code.INVALID_LICENSE_KEY_PROVIDED The license key is invalid. Please contact Qlik Catalog support or your team administrator.

Environment

Qlik Catalog 

Resolution

The license key used contains invalid characters, such as line breaks. 

Example: Copying a license key out of a PDF adds line breaks at each new line. These are invalid. Please use the full string.

 Troubleshooting the error: Error adding license LEF does not give server permissions when applying a Qlik GeoAnalytics license.

Environment

Qlik GeoAnalytics 

Resolution

1. Check the LEF and make sure it contains the tag GEO_SERVER;YES;;​​
2. If the tag is missing, contact Customer Support via the Support Portal How to create a case and contact Qlik Support
3. If the tag is present, make sure to paste the LEF without any spaces in between or at the end.

Cause 

The LEF must have the property GEO_SERVER;YES;; 

Internal Investigation ID(s) 

000003138

You are a prospective customer and are looking to purchase a Qlik Cloud subscription.

• See How to purchase Qlik Sense SaaS digital subscription.
• If you are looking to manage an active subscription, see Managing Your Subscription in My Qlik.

You are a prospective customer, having never purchased Qlik licenses before and are interested in learning more about Qlik products and making a purchase:

• Go to Qlik.com to browse our available offerings and engage in our Live Chat if you have questions.
• Or contact Sales directly.

You are an existing Customer, having previously purchased a license directly from Qlik and wish to purchase additional licenses or CALs:

• Please contact your Account Manager. If you are unsure who the Account Manager is for your company, contact Support using Live Chat.

You are an existing Customer and purchased your licenses through a third party (not directly from Qlik) and wish to purchase additional licenses or CALs:

• Please contact your Responsible Partner from which you previously purchased licenses. If you are unsure who your Responsible Partner is, contact Support using Live Chat.

Customer sets up Dynamic allocation for Professional Users and explicit allocates their licenses for Analyzer users. They notice users are being assigned both. 

This only concerns QlikView, not Qlik Sense.

Environment

• QlikView server, any

Resolution

This was reported to R&D with ID QV-23240 and assessed as a current design limitation.

If both Professional and Analyzer dynamic allocation are enabled and if the user has been pre-assigned, the user could get an additional user license. For instance: user has been pre-assigned to Analyzer, and Professional and Analyzer dynamic allocations are set: when user requests access and there is a non-empty quota of Professional user licenses, the user will be assigned a Professional user license in addition to the pre-assigned Analyzer license.

R&D is currently considering possible improvement actions around this area.

Description:

• The NPrinting License service has stop running recently and will not start
• The NPrinting License service will not start after fresh installation or upgrade
• The NPrinting License service will not start after restarting the NPrinting Server or individual services
• This article describes how to resolve the issue where the NPrinting License service will not start after restarting the service, upgrading, installing NPrinting for the first time or rebooting the NPrinting Server

Environment:

• NPrinting Server February 2020 and newer versions (the license service does not exist in earlier versions of NPrinting Server)

Diagnosis:

• One or more of the following error appears in the NPrinting_license.log file
• License Log file locations:
  • C:\ProgramData\nprinting\logs
  • C:\ProgramData\nprinting\License\Logs

Unable to start License service. ERROR: System.AggregateException: One or more errors occurred. ---> System.Security.Cryptography.CryptographicException: Keyset does not exist

System.ArgumentException: Basic authentication is enabled but username is missing

Resolution:

• Open the 'Services' panel on the Windows NPrinting Server computer
• Double-click on the Qlik NPrinting License Service service
• On the logon tab: Switch the license service user account to the 'local system' account and restart the license service
• If that account does not work, use the NPrinting engine or scheduler service user account and restart the license service
  

Workaround:

• Activate NPrinting Offline
  • https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/Offline-licensing.htm

Cause:

• Windows Active Directory Group Policy may have changed or become restrictive to the system or user account that is running the NPrinting License Service

Related Content

• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/Updating-license.htm

Internal ID:

• QB-9819

This article details a selection of product levels and related products as well as what license activation methods are supported for the individual license type.

Note that these are for product types only and not for specific features. If you have a question about the content of your LEF, contact us through our live chat and we'll be happy to clarify for you.

The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."

Environment

• QlikView 
• Qlik Cloud 

Resolution

• The license used in Qlik Cloud is missing the QV_NODES tag, which allows the access to QlikView apps from Sense Deployments. For QlikView to distribute to a Qlik Cloud tenant,  the tag must be present in the tenant license.

Please, reach out to your account manager to have that fixed.

• This issue could also occur if there are missing configuration entries in he QVDistributionService.exe.config  file, refer to the following article QlikView Distribute to cloud fails: The type initializer for System.IdentityModel.Tokens.Jwt.JsonExtensions threw an exception.

Environment

• Qlik Sense Desktop, June 2020
• Qlik Sense Business 
• Qlik Sense Enterprise SaaS