Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Feb 13, 2023 6:29:42 AM
Dec 11, 2014 6:02:57 PM
This article covers how to license a QlikView Server and how to update the license.
We will cover signed license keys (QlikView Infrastructure add-ons to Qlik Sense Enterprise SaaS) as well as legacy QlikView serial numbers and LEF licenses.
Content:
Requirement: A legacy QlikView serial number, Control Number (and optional LEF).
No action is necessary. The license will be updated against the license backend.
Requirement: A new legacy QlikView serial number, Control Number (and optional LEF).
The common scenarios of changing the QlikView license details are:
It is recommended to do a backup of license related files on the QlikView server prior to updating license details. This allows for reverting to the previous license if necessary.
QlikView license information is stored in two locations. Files from both locations, as specified below, must be copied to a safe location prior to updating or applying a new license.
NOTE: Applying license requires a restart of QlikView service(s) and not the physical server itself. QlikView will be temporarily unavailable during the restart of the service(s).
Once the requirements are met:
Requirement: An existing, unchanged legacy QlikView serial number.
To update the license:
If your QlikView server does not have access to the internet, you will need to replace the current LEF with the new one and click Apply License.
Please note: When you update the license, do NOT clear the license.
Hey @Andre_Sostizzo
do you know why I still have the LEF expiring warning? I have updated both publisher and OEM server license.
Best regards,
Susan
Hello @Huiying
If both have been successfully updated and show the correct date after a service restart, I would recommend reviewing the .lef files in the \QlikTech folder. There should be one in the Distribution Service Folder as well as the QlikView Server folder (and I think one in the root). Check if it is all updated in those files, too.
Otherwise, review the log files for both services, see if you can notice anything that helps you further investigate.
If not, you may want to head over to the QlikView community forums and post there for greater visibly - or contact Support.