Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Feb 2, 2024 7:04:34 AM
Dec 15, 2011 3:39:12 AM
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 Se... .
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
Hello @Vica
If you are attempting to lease a license from a QlikView server, please follow the instructions in How To Lease A License From QlikView Server To QlikView Desktop Client - you will not get this error message if you are leasing a license. This error you are showing is meant to appear if you are attempting to license the client directly with a serial number.
All the best,
Sonja
Had a license lease issue with a client, checking all steps nothing helped.
And the end I've discovered that the user had an Analyzer and an Professional license.
Remove the Analyzer license and License lease worked