A user opens the QlikView Desktop and attempts to lease a license from the QlikView Server. However, after successfully connecting and authenticating ...
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).
Review the relevant log file
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.
Common License Lease issue root causes
License lease has not been properly enabled in QlikView Management Console.
See How To Lease License From QlikView Server To QlikView Desktop Client for more details.
Test license is applied in QlikView server
License lease is not allowed for test license, see QlikView Test Server FAQ for more details on test licenses.
Multiple versions of QlikView desktop installed
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.
License lease only allows a borrowed CAL to be used twice in a 7 day period
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.
Clients using multiple or roaming profiles
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.
You can also open via QlikView Desktop Client > Help> Document Support Information and search for the parameters above, as below:
License Lease is prohibited by the QlikView Server license
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.
Deleting of the folder ConnectionsMRU und LeasedLicenseMRU in the Registry
Verify that the following registry key is present:
Registry > HKEY_CURRENT_USER > Software > QlikTech > QlikView
The user is logged into a temporary profile
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 blocked
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.
Solve assignment issues
Before reassigning licenses, do the following:
- Open the QlikView Management Console
- Go to System
- Open Licenses
- Switch to the active QlikView Server
- Open the Client Access Licenses (CALs) tab
- Open the History tab
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.
Reassign, Part 1: Remove CAL and Quarantine for 7 days
- Open the QlikView Management Console
- Remove the manually assigned Named CAL. See How to assign and remove a Named CAL
- 7 days are required as a 'quarantine' period
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.
Reassign, Part 2: after 7 full days has passed
- Check that the affected user's account has not be manually assigned a CAL. If you find the CAL is assigned again, you need to remove it and wait another 7 days.
- At this point, you would want to investigate why the CAL is being assigned given that dynamic assignment is turned off in your QlikView Server
- If no named CAL has been assigned, go ahead and manually assign the user a Name CAL in the QlikView Management Console.
- If you have temporarily allocated a QlikView Desktop License provided by your Qlik Account manager, go ahead and remove the client desktop license from the users QlikView desktop and sign out (not just disconnect) from the windows computer desktop session.
Follow steps 1 through 3 of the following article to remove the desktop license. Transfer QlikView Desktop license from old to new machine
- Reboot the user's computer
- User then Log into the computer after reboot
- Open QlikView desktop
- Go to File and click Open in server... to get the license CAL from the server
- Personal Edition should disappear from the QlikView desktop title bar and they can then work normally again.
- Have the user perform some simple tasks in QlikView to ensure they have normal access to the QVWs once again.
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