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.
Content
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.
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.
As mentioned above, Qlik has added one additional way to activate Qlik products.
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.
With the use of a Signed License Key, there are more Product and deployment offers to use.
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.
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).
Signed license Key
|
Example data |
A Signed License Key based on one of Qlik’s internal keys.
|
eyJhbGciOiJSUzUxMiIsInR5cCI6IkpXVCIsImtpZCI6ImEzMzdhZDE3LTk1ODctNGNhOS05M2I3LTBi MmI5ZTNlOWI0OCJ9.eyJqdGkiOiI2MjNhYTlhZi05NTBmLTQ3ZjctOGJmMC1mNGQzOWY0MmQ5N mMiLCJsaWNlbnNlIjoiOTk5OTAwMDAwMDAwMTI1MyJ9.YJqTct2ngqLfl2VP3jxW4RsDNK2MTL-BpJ WnBdIfF5gGbJcX0hc__tfIa2ab5ZrL9h6tsZxTwgucTFiRTAOz8PaOQP7JTnhPCyrBZwpnmhvCrSHx2 C-HbCARFUIueBzMg8fgvWH-3HxBuxx6jnDhekDTUbb12vBq7CySampJkgMT7QsDdUkeJy5E7O0U 8yhd1RtEDeuTbeX35eIdQUN4DyJWHHPiT9qZt1AV0_Ofe1iLKxYZMa5jC0kIsVwYnRCJzibZlrLE7mS VlNitxmcm8OoUrR_ZIk8VuOkoz_qqy8N_wwrt7FcT2slWz50XzuL8TIWY9mcGIL |
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 Element | Comment | Example Data |
Signed License Key | See above | |
Cause | Initial or Update | “Initial” |
User agent | build by the License service version (operating system) and Product (e.g. QSEfW, QCS, QSEfE, QV) | Licenses/1.6.4 (windows) QSEfW |
Data Element | Comment | Sample Data |
License definition | content variable based on product and entitlement | "name": "analyzer_time", "usage": {"class": "time", "minimum": 5}, "provisions": [{ "accessType":"analyzer"} ],"units": [{"count": 200, "valid": "2018-06-01/2018-12-31"}]}, "name": "professional", "usage": { "class": "assigned", "minimum": 1 }, "provisions": [{ "accessType": "professional" }],"units": [{ "count": 10, "valid": "" }]} |
(Time schedule is not disclosed and includes grace time to support outages in the internet connection, a/k/a Optimistic Delegation.)
Data Element | Comment | Sample Data |
Signed License Key |
See above | |
Array Element id | Used for internal match only | 1 |
Allotment name | alternatives are Analyzer_Time, Core_Time | “analyzer_time” |
Year/Month | YYYY-MM | 2018-11 |
Consumption | for this deployment since last sync | 242 |
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 |
User agent | same construct as for as activation request | Licenses/1.6.4 (windows) QSEfW |
Data Element | Comment | Sample Data |
Total consumption | Used by the Product for enforcement. Deny access will be executed if quota has been exceeded. Quota is set in the LEF. Additional quota for the month could be managed as Overage in the LEF. This would contain an Overage Value (COUNT) or the value YES. Total quota for the month is calculated as licensed quota + Overage quota. If the LEF contains the value YES, there will be no cap on the capacity for the Year/Month. |
12345 |
Data Element | Comment | Sample Data |
Signed License Key | See above | |
Allotment name | Professional / Analyzer | “professional” |
Subject | Domain / User ID; if this an add or delete transaction. By delete the subject will be removed immediately. An internal id will be used to secure sync to other deployments using the same Signed License Key. The internal id will disappear within 60 days after a delete transaction. (This information is stored for all assigned users until such a time that the assignment is deleted at which point it is deleted. The information is used for synchronizing assignments across deployments in order to facilitate the single-license-multi-deployment scenario. It is encrypted in transit and at rest.) |
“acme\bob”
(For information on how data is submitted and stored in the audit logs see here) |
User agent | Build by the License service version (operating system) and Product (e.g. QSEfW, QCS, QSEfE, 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", "bases": [{ "license": "1234 1234 1234 1234", "version": 0 }], "patches": [{ "instance": "", "version": 0, "license": "1234 1234 1234 1234", "allotment": "analyzer", "subject": \\generated4, "created": "2019-04-18T10:01:35.024031Z" } |
Data Element | Comment | Sample Data |
Signed License Key | See above | |
Subject | Including subjects changed by other deployments | “acme\bob” |
Sync metadata | Versioning information about the subjects and list of subjects to manage the synchronization process | { "bases": [{ "license": "1234 1234 1234 1234", "version": 17 }], "patches": [{ "instance": "5382018630938057025", "version": 14, "license": "1234 1234 1234 1234", "allotment": "analyzer", "subject": ACME\\bob", "created": "2019-04-18T10:01:35.024Z", "rejection": "" }] |
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:
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
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:
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
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!
These changes will need to be done on all nodes running the Service Dispatcher. Not only the Central node.
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.
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
Qlik has identified a defect in the initial February 2024 release as well as patch 1 (QB-25231).
Change the -offline parameter position in the configuration file.
Previous versions of Qlik Sense allowed for the -offline parameter to be situated anywhere. February 2024 requires it in this order.
QB-25231 is expected to be fixed in Qlik Sense Enterprise on Windows February 2024 Patch 2.
QB-25231
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.
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:
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
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.
Reloading the Qlik Sense Connector in Qlik Lineage Connector Client Managed may fail with:
Connector of type 'QlikSense' not included in license. Canceling execution
You will also see an "Invalid License" error on the Cloud link.
#Qlik Lineage Connector
This document explains how to upload the license using a powershell/CMD terminal.
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)
Python.exe .\txt2json.py <#path-where-the-license-is-located #e.g. C:\Users\user\Destop\licence.txt#>
cd <#path-where-replicate-is-installed #e.g. C:\Program Files\Attunity\Replicate\bin #>
repctl.exe connect
repctl.exe [-d <replicate_data_dir>] importlicense license_file=<location>license.json
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.
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.
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
After correctly de-allocating a user license, the license does not stay unassigned.
This applies to different user-type licenses, such as Professional and Analyzer licenses or legacy tokens or CALs.
Possible scenario:
A professional license has been removed from a user in Qlik Cloud using the management console or a supported API call. A day later, the entitlement is assigned again.
Qlik Cloud
Qlik Sense Enterprise on Windows
QlikView
Verify if auto assignment has been enabled.
Qlik Cloud: Enabling dynamic assignment of entitlements
Qlik Sense Enterprise on Windows: License management
QlikView: How to Allow Dynamic CAL, Professional, and Analyzer Access Licenses in QlikView
Qlik Cloud: license remains assigned to deleted user
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."
Please, reach out to your account manager to have that fixed.
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
Applying a Qlik Sense License Key to Qlik Sense Enterprise on Windows fails. The license cannot be activated.
Two possible error messages are displayed:
There was an error when getting license information from the license server
If the error is caused by an invalid license key, log files read:
"errorMessage":"invalid license error, no license found, tenant not found"
"errorType":"LICENSES-ForbiddenRequest"
"statusCode":403,"
If the error is caused by connectivity issues, log files read:
wsarecv: An existing connection was forcibly closed by the remote host.","errorType":"*url.Error"},...
LicenseOverview: The remote server returned an error: (500) Internal Server Error.
From Qlik Sense Enterprise on Windows November 2023 onwards, an invalid license returns the following error:
The license is not applicable to this product.
"errorMessage":"License is not valid in the current environment, (invalid product level)"
"errorType":"LICENSES-InvalidLicense"
"statusCode":403
Resolution
Depending on the root cause, different solutions apply.
Verify that the license you purchased is for the correct product.
You cannot apply the SaaS-Only subscription License in Qlik Sense Enterprise on Windows. If the Product level is 51, then the License is meant for SaaS only.
00000000000000
OVERAGE;NO;;
PRODUCTLEVEL;51;;2024-12-31
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.
00000000000000
OVERAGE;NO;;
PRODUCTLEVEL;50;;2020-12-31
TOKENS;3000;;
To check your product level and license information, obtain a LEF using Manual LEF. If you don't know your 16-digit Product Key, see Find your Qlik Cloud Subscription ID and Tenant Hostname and ID or contact Qlik Support.
Information about product levels and LEF features are documented in Qlik Product Levels and Supported Activation Methods (License Service vs LEF)
Verify that 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 proxy configuration for Qlik License Service communication for steps on how to achieve this.
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.
Qlik Sense Enterprise on Windows , with Signed License Key (SLK)
A user opens the QlikView Desktop and attempts to lease a license from the QlikView Server. However, after successfully connecting and authenticating and even opening a QlikView document, the Desktop client remains unlicensed (Personal Edition).
Content:
The relevant log file to review on the QlikView server to verify if the user has arrived and has attempted to lease a license is the QlikView Server Event log. Note that it will only log the relevant lines when set to High logging level.
Example results:
See How To Lease License From QlikView Server To QlikView Desktop Client for more details.
License lease is not allowed for test license, see QlikView Test Server FAQ for more details on test licenses.
Uncapped licenses have unlimited Session CALs but no Named User CALs.
You may have multiple QlikView versions installed, or have incompletely uninstalled versions still present in the registry. This means that if the user is opening QlikView from the correct shortcut everything is fine, but if a .qvw file is double clicked, a different QlikView client may launch, invalidating the lease.
See How To Associate .QVW Extension To A Specific Version Of QlikView for detail on changing the QVW file association in Windows.
This can cause problems if the user connects to many different servers. For example, if the Windows machine are run on a Citrix farm or other terminal services/virtual desktops.
A single user can lease up to two licenses to two separate workstations within a 7 day period.
An attempt to lease the third license in a 7 day period will be revoked if the same User ID is used. Additionally, the existing license lease of the third machine, should there be one previously existing, will be revoked in the case where the same User ID has leased a license from two other workstations in the previous 7 day period. The third machine will, however, be able to lease a license after 7 days have passed.
The Lease info is stored locally in the profile, so if they no longer have access to it they will lose the lease. Look for root cause details in the LeasedLicense section of C:\Users\\AppData\Roaming\QlikTech\QlikView\Settings.ini. The LeasedLicenseCheck value shows more details on why the license lease has failed.
LeasedLicenseExpiry=
LeasedLicenseServer=
LeasedLicenseCheck= INVALID
You can also open via QlikView Desktop Client > Help> Document Support Information and search for the parameters above, as below:
License lease may not be allowed on the QlikView Server. A QlikView Server license which only allows for a certain amount of documents to be loaded has the functionality disabled by default.
This is specified as a NUMBER_OF_DOCUMENTS tag in the license LEF file.
Verify that the following registry key is present:
Registry > HKEY_CURRENT_USER > Software > QlikTech > QlikView
This will allow the license to lease initially, but the lease will be removed once the temporary profile is cleared out. You can check for this after the user logs in by going to C:\Users and looking for the login name. If it's not there, and there is a Temp folder, check there. One fix would be to disable temp profiles.
Port 4747 is required for QlikView to establish a connection. If Port 4747 is blocked when attempting to lease a license, then no connection can be made and no license can be obtained.
This is typically the case when error Connected to server OK, Negotiations Timed Out Switching to HTTP tunneling is returned.
QlikView May 2023 (12.80) now uses AES256 encryption instead of AES128, which was used in QlikView May 2022 (12.70) and earlier. If the QlikView Server and QlikView Desktop are different build versions, with one or the other running May 2023, the QVP protocol will not connect between QlikView Desktop and QlikView Server. The discrepancy in the session algorithm causes the error.
To resolve the issue, ensure both QlikView Desktop and QlikView Server are running the same build versions or edit the QlikView Desktop Settings.ini file as detailed in QlikView 12.80: set a different Session Algorithm for QVP communication and Open in Server fails using QlikView Desktop May 2023 or later against earlier version of QlikView Server .
Before reassigning licenses, do the following:
Look for multiple user account entries for the affected user in the History tab. If the history shows multiple entries for single user, proceed with Reassign, Part 1. When the history is clear for the affected user, proceed with Reassign, Solution 2.
NOTE: Check during the course of the week that the affected user's credentials have not been allocated a CAL on the QlikView server again. If yes, please remove the Named CAL again and wait 7 another days.
NOTE: If using Citrix, log the user off of all it's sessions from the Citrix management panel before proceeding above. See https://support.citrix.com/article/CTX124949/citrix-session-management-tool
After licensing a new Qlik Replicate Endpoint that requires an Endpoint Server (such as Salesforce, MongoDB, BigQuery) one or more Endpoint Servers cannot be reached.
The message One or more Endpoint Servers cannot be reached is displayed and the individual servers are listed as disconnected in the status column.
~\bin>repctl -d "D:\attuntity\replicate\data" exportrepository
Note: "D:\attunity\replicate\data" is an example of the data folder location. "endpoint_servers": [{
"name": "Local",
"host": "localhost",
"port": 3560,
"password": "{ZASomeRandomLettersAndNumbersHereXXXXXXXXXXXXXXXXXXX}",
...
}]
Edit the password for that section, by changing it to say:
"endpoint_servers": [{
"name": "Local",
"host": "localhost",
"port": 3560,
"password": "password",
...
}]
repctl -d "D:\attunity\replicate\data" importrepository json_file=Replication_Definition.json
Log back into the Qlik Replicate console and verify that your local endpoint server reports as running in the status column.
Qlik Replicate 7.0 and later