QV9 License Lease from Server breaks for some users
We are running QV9 SR3 and have individuals with named User CALs doing thick client development via the license lease feature. They have been doing this successfully for months (as in 14+ months), and then one day it breaks (on a per user basis). I've noticed that a broken user will open their QlikView Thick Client to see it is in "Personal Edition" mode. They then use the "Open in Server" option to open an application they have access to -- this should and has in the past switched the licensing mode of the thick client from Personal Edition to "leasing license from <server name>". The application opens successfully, however, the licensing of their thick client does not change - they do not lease a license and switch out of Personal Edition.
Key observations:
1) License lease works for most everyone at the company.
2) When the user experiences the problem, then have been successfully leasing a license for quite some time (14+ months).
3) This issue is on a per user basis. When a given user has the problem others are working fine.
4) Issue is very rare. About 4 out of our 200+ users have experienced this, and they are our 4 most active users doing QV development using the Thick Client.
5) Removing the QlikView thick client and reinstalling it fixes the issue.
6) Applying one of our thick client license keys (left over from the 8.5 days) also resolves the issue.
Has anyone else experienced this, and is there are better resolution than a reinstall?
Using the OSUser() and QVUser() function we noticed that the OS was supplying user identity in the format of ‘DOMAIN\userid’ (notice the case-sensitivity). We then noticed that we could enter the Named CAL assignment (in the QEMC) in any type of mixed-case that we wanted; however, it would be displayed in the QEMC as ‘DOMAIN\USERID’. We wondered if the QEMC was actually converting to all upper case, or storing and displaying the user identity differently. We deleted the Named CAL assignment for a user experiencing this issue, and reassigned using the correct case ‘DOMAIN\userid’ and the issue was resolved. This seems to confirm our suspicions that the QEMC stores the user identity exactly how you enter it, however, displays the identity in all uppercase. Reviewing other posts on QlikCommunity we learned that the user identity is case sensitive for license leasing. We are running QV 9 SR7.
Using the OSUser() and QVUser() function we noticed that the OS was supplying user identity in the format of ‘DOMAIN\userid’ (notice the case-sensitivity). We then noticed that we could enter the Named CAL assignment (in the QEMC) in any type of mixed-case that we wanted; however, it would be displayed in the QEMC as ‘DOMAIN\USERID’. We wondered if the QEMC was actually converting to all upper case, or storing and displaying the user identity differently. We deleted the Named CAL assignment for a user experiencing this issue, and reassigned using the correct case ‘DOMAIN\userid’ and the issue was resolved. This seems to confirm our suspicions that the QEMC stores the user identity exactly how you enter it, however, displays the identity in all uppercase. Reviewing other posts on QlikCommunity we learned that the user identity is case sensitive for license leasing. We are running QV 9 SR7.
