Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
After the Qlik GeoAnalytics installation, an activation of the product is required. During the use of the Qlik GeoAnalytics License Activation Tool you might see the error message:
Could not communicate with the license server. Check your internet connection.
Environment
Resolution
The best way to resolve the issue is to install a version post November 2020. Until the upgrade here is a workaround:
Create a file called GeoAnalyticsLicenseTool.exe.config in the same folder as the license tool executable, C:\Program Files (x86)\QlikView\GeoAnalyticsLicenseTool .
Paste this inside:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<runtime>
<AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false"/>
</runtime>
</configuration>
Cause
The LEF license servers have been moved to another location and are now using TLS 1.2 as a default.
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:
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:
Details:
No setup is required. If no Professional or Analyzer License was assigned, Analyzer Capacity is automatically allocated.
See Enabling dynamic license assignment for details.
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:
The Entitlement Analyzer is only available for Qlik Cloud.
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:
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
Due a product defect, users deleted in mid-March 2023 might still keep a license assigned to them.
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.
Unable to remove or de-allocate user license, the license is reassigned to the user
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:
If Qlik Sense Enterprise on Windows was licensed using a Signed License Key, it will retrieve its License Definition File:
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:
Users are not synchronized.
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.
If QlikView was licensed using a Signed License Key, it will retrieve its License Definition File:
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:
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.
Qlik Sense Enterprise on Windows
Qlik Cloud
Qlik Sense Business
QlikView
The instructions apply to obtaining your control number and LEF. Signed License Keys (SLK) are sent by email and need to be requested from Qlik Support.
Transcript
This video will demonstrate how to view a license Enabler File or LEF and Control Number.
If you are looking for a Signed License Key,
this has been sent via email.
If you can’t find your Signed License Key, contact Support.
First visit Qliksupport.force.com/QS_Logininfo and login with your QlikID email address and password.
Click on License Information at the top of the page
and verify the account.
You will be shown a list of Active and Expired Licenses.
You can use the filter to search for a specific license.
Click the checkbox next to the license.
Then click on Request Control Number" or "Download LEF"
Clicking Download LEF provides the LEF immediately.
Make sure that no pop up blockers are enabled that prevent the pop up from showing.
Request Control Number triggers an email that will arrive in a few minutes.
I hope this helped.
If you'd like more information
Take advantage of the expertise of peers, product experts, Community MVPs and technical support engineers
by asking a question in a Qlik Product Forum.
Hiding in plain sight is perhaps the most powerful feature on the Community:
the Search tool.
This engine allows you to search Qlik Knowledge Base Articles,
Or across the Qlik Community,
Help dot Qlik dot com, Qlik Gallery,
multiple Qlik YouTube channels and more, all from one place.
There’s also the Support space.
We recommend you subscribe to the Support Updates Blog,
And learn directly from Qlik experts via a Support webinar, like Techspert Talks or Q&A with Qlik.
Nialed it.
When authenticating the Qlik Sense Desktop, an active network connection is required. This may be a connection to a Qlik Sense Enterprise Server on Windows or an active Internet Connection to the Qlik Sense SaaS backend.
This article provides steps to resolve if the error message "Failed to authenticate against the selected server. Please make sure your internet connection is working and try again." is displayed when attempting to authenticate against Qlik Sense Business.
The message is displayed after an attempt to authenticate from the start screen.
This issue is usually caused by a network connectivity problem. The most common causes are:
Contact your local IT/network administrator and ensure that the following URLs can be reached using https (port 443): *qlik.com, *.auth0.com and *qlikcloud.com.
Run an up to date version of Qlik Sense Desktop
Verify that you have the most up to date version of Qlik Sense Desktop installed. Download and install the latest version.
Are you using a Proxy?
Check if a Proxy is used to access the internet. This can be verified by going to:
If a Proxy is used, it may be necessary to bypass the Proxy to log on and authenticate. If the Proxy cannot be bypassed, contact your local IT/network administrator and ensure that the following URLs can be reached using https (port 443): *qlik.com, *.auth0.com and *qlikcloud.com.
It may be necessary to use a private internet connection to unlock the client if the required ports and addresses cannot be unlocked.
Are you using a VPN?
VPNs may block the required ports and URLs. Disconnect from the VPN or contact your local IT/network administrator and ensure that the following URLs can be reached using https (port 443): *qlik.com, *.auth0.com and *qlikcloud.com.
Qlik Replicate can be licensed using RepCtl. For instructions on how to license Qlik Replicate using the standard user interface, see Registering a license.
{
"cmd.license":
{
"license_type": "EVALUATION_LICENSE",
"licensed_to": "QLIK CUSTOMER",
"licensed_by": "Attunity US",
"serial_no": "60035964",
"expiration_date": "2023-12-01",
"hosts": "xxx.xxxx",
"source_types": "oracle",
"target_types": "target",
"features": "yyyy",
"version": "2023.11",
"issue_date": "2023-10-31",
"checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
}
}
{
"cmd.license":
{
"license_type": "EVALUATION_LICENSE",
"licensed_to": "QLIK CUSTOMER",
"licensed_by": "Attunity US",
"serial_no": "60035964",
"expiration_date": "2023-12-01",
"hosts": "xxx.xxxx",
"source_types": "oracle",
"target_types": "target",
"features": "yyyy",
"version": "2023.11",
"issue_date": "2023-10-31",
"checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
}
}
Upgrading QlikView fails with the Warning:
You need a valid maintenance contract to be allowed to install and use this Software
Proceeding with upgrades without an updated maintenance contract will lead to the QlikView Server license being invalidated. The server will enter Off Duty state.
Attempting to license a QlikView server with an outdated license will lead to
Server failed to set license: QVS@qlikviewserver: This license key has expired!
The maintenance data for the license key has expired prior to the release date of the product version you are updating too.
See the Maintenance contract on upgrade for more details.
Example:
000000000000000
NUMBER_OF_USERCALS;5;;
NAMED_CAL_BY_MACHINE_ID;NO;;
PRODUCTLEVEL;10;;2016-12-30
000000000000000
If the maintenance date is correct and you have attempted to update the license, verify if no old LEF.txt files are stored in your system. See Where do all the QlikView LEF files go? for information on where they are stored. Carry the check out on all nodes if you have a multi node environment.
If you do not have an up-to-date maintenance date, contact your Qlik Account Manager to renew the license and repeat steps 1 and 2 above.
Assigned Qlik Cloud licenses and entitlements can be deallocated using the Qlik Command Line Interface. This method is specifically useful when the user with the allocated entitlement or license is no longer visible in the system and can therefore not be configured in the Management Console.
[
{
"created": "2023-04-03T11:24:05.101Z",
"excess": false,
"name": “Enzo Bearzot”,
"subject": "auth0|12345678”,
"type": "professional",
"userId": “userid1”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Vittorio Pozzo”,
"subject": "auth0|910111213”,
"type": “analyzer”,
"userId": “userid2”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Ferruccio Valcareggi”,
"subject": "auth0|14151617”,
"type": "professional",
"userId": “userid3”
},
{
"created": "2022-06-07T11:36:15.704Z",
"excess": false,
"subject": “18192021”,
"type": “professional”
},
{
"created": "2022-06-03T13:50:14.105Z",
"excess": false,
"subject": “22232425”,
"type": "analyzer"
},
]
The syntax below is for Unix shells. For usage in Windows Powershell add a "backslash" before each "doublequote" sign. '[{"subject"... will have to become '[{\"subject\"...
'[{"subject":"USERSUBJECT","type":"ASSIGNEDLICENSE"}]'
Example: Using the last user in the list provided above, the string would be:
'[{"subject":"22232425","type":"analyzer"}]'
Feed the string into this command:
.\qlik.exe license assignment delete --delete STRING
With the example above you will run:
Example using the last user in the list above:
.\qlik.exe license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
Run the command and wait for the result.
A status returned as 200 will confirm the removal worked:
% qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
[
{
"status": 200,
"subject": "22232425",
"type": "analyzer"
}
]
Verify the allocation was removed by navigating to the Qlik Cloud Management Console's Home section.
Qlik Cloud tenants are the highest level of logical isolation provided to our customers. The subscriptions and associated entitlements (also known as licenses) that customers purchase from Qlik are not fixed to these tenants. When needed, a customer can update the entitlement used by their tenant. This article covers how to do this, as well as all considerations before moving.
You should not attempt to update your tenant entitlement unless directed to do so by Qlik, or you are an OEM customer who is managing multiple entitlements for their estate.
Content:
There are three scenarios where you might need to update your entitlement:
If you are an OEM or Enterprise customer leveraging multiple tenants in Qlik Cloud, please also consider reviewing the Platform Operations series on qlik.dev to learn more about managing these estates prior to changing your entitlements.
Before you begin migrating your subscription or entitlement, consider:
Updating the entitlement requires four steps:
Your SLK is available through:
When you migrate between entitlements, any user assignments will be reset. You will need to export any current assignments if you wish to reassign them.
There are three ways of doing this:
If you have many users, both option a and b will require you to paginate to get all results.
Results will look like:
If required, reassign entitlements which were exported in step 2. You can do this in two ways:
curl -L -X POST 'https://<hostname>.<region>.qlikcloud.com/api/v1/licenses/assignments/actions/add' \
-H 'Authorization: Bearer ey...' \
-H 'Content-type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"add": [
{
"subject": "1ef2caed0dbe0a66a24ccadf61546099",
"type": "professional"
}
]
}'
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.
As part of the agreement of granting a customer offline license usage, the customer is required to regularly upload User Assignment log files. This essentially replicates the user assignment data which is sent to Qlik in a manual process.
Qlik Sense Enterprise on Windows
QlikView
Licensed with a long term offline license.
⚠️ FYI: All information regarding user subject (user information) is hashed using SHA256 to prevent Qlik from accessing the original data. (The information is encrypted both in transit and at rest). ⚠️
Data Element |
Comment |
Sample Data |
Signed License Key |
|
See above |
Allotment name |
Professional / Analyzer |
“professional” |
Subject |
Domain / User ID; |
“acme\bob” user name included in hashed form in the log files and will show as something like: “a24a2f2b67c5e051bcb6cd2d7a9f7ebe” |
User agent |
Build by the License service version (operating system) and Product (e.g. QSEfW, QCS, QSEfE, ADBI, Qlik Core, QV) |
Licenses/1.6.4 (windows) QSEfW |
Source |
Hashed ID to make each deployment unique, e.g. a Qlik Sense Enterprise on Windows and a Qlik Sense Enterprise on Kubernetes will have different Source ID's |
fbe89d02-6d24-4595-915e-c52ce76f2195 |
Sync metadata |
Versioning information about the subjects and list of subjects to manage the synchronization process. |
{ "source": "my assignments", |
Upon launch, the Qlik Sense Desktop needs to be authenticated against either the Qlik Sense SaaS backend or a Qlik Sense Enterprise server.
This authentication is done using an authentication link.
Clicking Add authentication link brings up instructions:
Click here for video transcript
Also see How to authenticate Qlik Sense Desktop against SaaS editions.
If you have user access for Qlik Sense Enterprise, you can authenticate against the Qlik Sense Enterprise server when you start Qlik Sense Desktop.
! Client authentication is not supported on test servers.
Before you can authenticate, the Qlik Sense Enterprise authentication link must be generated by your administrator in the Qlik Management Console.
Your Qlik Sense administrator will provide you with information about how you can receive the link using one of the following methods:
Qlik Sense Desktop must be installed on your computer before you start any of the following procedures.
Do the following:
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.
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.
Do the following:
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.
A dialog box opens asking you to confirm that you want to open the authentication link using the Qlik Sense. Confirm the dialog.
Qlik Sense Desktop opens and the authentication link is added to the welcome page under Authenticate against Qlik Sense Enterprise.
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.
Do the following:
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.
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
As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).
This allows for analyzer capacity to be shared across all systems using the same license.
QlikView
Qlik Sense Enterprise on Windows
With a Signed License Key (SLK) applied as a unified license across multiple environments
Here is an example;
A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.)
This can be accessed through: System > Licenses > Professional and Analyzer access.
If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up to date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.
This can be accessed in the Qlik Sense Management Console > License Management > License usage summary
The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.
For local consumption data, each server will store its own consumption and user information.
For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.
For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:
RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe
Your Qlik Cloud license includes information on what licenses and features are enabled for you. You will receive a list of all your enabled features in your original license email and we always recommend to store the email for future reference.
However, you can also call the License APIs in your browser and obtain information on what features are included in your license from there.
{"name":"qvNodes","valid":"./.","values":{"count":3}},
{"name":"reportingService","valid":"./.","values":{"quantity":1000,"value":""}}]
Before you can start using Qlik Sense Desktop, you need to authenticate yourself against a Qlik Sense Enterprise server. You need to have a working network connection to enable authentication.
The following requirements need to be met:
After you have been authenticated once, internet access is not required to continue using Qlik Sense Desktop. However, you have to re-authenticate yourself if thirty days have passed since you last authenticated.
Qlik Sense Desktop
Qlik Cloud
Qlik Sense Enterprise on Windows
Qlik Sense Business
Starting Qlik Sense Desktop | Qlik Sense on Windows Help
Starting Qlik Sense Desktop | Qlik Cloud Help
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
This video demonstrates the basics on how to switch from Client Access Licenses (CALs) to the new Professional and Analyzer Access licensing.
Talend Data Catalog のライセンスリニューアル時における更新作業手順
1. 弊社担当営業へ、ライセンス更新の手続きを申請します。
2. ライセンス更新についてのご案内が記載された、Welcome to Talend Data Catalog メールが送付されます。
例:
差出人: Talend - Support <support@talend.com> 件名: Welcome to Talend Data Catalog - Talend Data Catalog Advanced Edition 7.3.1 - Definitive - Production - Q-XXXXXX」
3. Talend Data Catalog へ Administrator ユーザーでログインし、管理 > ライセンス へ移動します。
4. 「ライセンス情報をダウンロード」をクリックし、HostInfo.xml を取得します。
5. 上記2.のメールに記載されている専用URLより、HostInfo.xml をアップロードします。
6. システムでの処理が行われ、ライセンスファイルがメールにて返送されます。(発行までに数時間程度要する場合がございます)
7. Talend Data Catalog へ Administrator ユーザーでログインし、管理 > ライセンス へ移動します。
8. 「ライセンスをアップデート」をクリックします。
9. 確認画面が表示されますので、内容をご確認の上、「はい」をクリックします。
10. ライセンスファイルをファイルピッカーより選択し、アップロードします。エラーが表示されていないことを確認します。
11. 有効期限が延長されていることを確認します。
以上でライセンスの更新が完了です。
エラーが表示された場合は、エラーメッセージを添えてサポート部門へお問い合わせください。
When your Qlik Sense server is behind a proxy you will need to add the proxy in the License service:
Configuring a proxy for Qlik License Service communication in Qlik Sense Enterprise on Windows
Qlik Sense Enterprise on Windows
{"caller":"handler.go:53","errorMessage":"invalid license error, no license found, tenant not found","errorType":"LICENSES-ForbiddenRequest","level":"info","logTraceId":"XXXXXXXXXXd674e50adef83","statusCode":403,"timestamp":"2021-09-23T09:17:27.1566729Z"}
This 403 forbidden error doesn't tell us more than that something is forbidden.
If we want to check this Proxy and be sure it is really working from the Qlik Sense server, we can use PowerShell and test the connection.
If you are using a Proxy with no authentication required, you can use below command:
Where "myproxy" = the proxy IP address or hostname set in the Qlik Sense dispatcher service
And where "8080" = the port number used for the Proxy
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$Site="https://license.qlikcloud.com"
$Test=Invoke-WebRequest -URI $Site -Proxy 'http://myproxy:8080'
$Test.Links
If your proxy requires authentication, you can use below command (run PowerShell as Administrator).
Where "172.16.16.101" = the proxy IP address or hostname set in the Qlik Sense dispatcher service
And where "808" = the port number used for the Proxy
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
netsh winhttp set proxy "172.16.16.101:808"
$Wcl=New-Object System.Net.WebClient
$Creds=Get-Credential
$Wcl.Proxy.Credentials=$Creds
$Site="https://license.qlikcloud.com"
$Test=Invoke-WebRequest -URI $Site
$Test.Links
The above command will prompt a Window where you need to put the login name and the password for the proxy authentication.
The result of the two above PowerShell scripts should show below result:
If you have any other result like for example "Your system policy has denied the requested action", or "proxy denied access", or similar, contact your IT security team to allow access to https://license.qlikcloud.com (port 443) through your Proxy.