Qlik Community

Ask a Question

Support Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Join us March 10th, 7 ways modern analytics can help you take smarter action. REGISTER NOW

QlikView Server Failed To Set License

Digital Support
Digital Support

QlikView Server Failed To Set License

When applying a QlikView Server license in the QlikView Management Console the error Failed to Set License is displayed. 

The error comes in the following variations:

  • Server failed to set license: Unable to contact the QlikView License Enabling Server. Please verify that you are connected to the Internet and try again or contact QlikView support for assistance.
  • Server failed to set license: The license key specified in License Enabler File does no match your license key.
  • Server failed to set license: QVS@xxx: Failed to connect to server.
  • Server failed to set license: QVS@xxx: Invalid license key or control number.
  • Server failed to set license: QVS@xxx: Unable to obtain License Information for your license key. Please contact QlikView Support for assistance. 
  • Server failed to set license: License is not applicable for this product.
  • Server failed to set license: QVS@xxx: The checksum is invalid.

When clicked on the QlikView Management console > System > Setup > Management Services > QlikView servers > qvs@xxxxx then it is throwing, Error : 'Object reference not set to instance of an object' 

As seen, there are more options should be available under QlikView Management console > System > Setup > Management Services > QlikView servers > qvs@xxxxx but only 2 options are coming (General and Login) 

See also QlikView Server License Problem - "Error: Server failed to set license"



Steps to take in order to resolve the error message: 

  1. Check the Internet access of the QVS
  • Does the QlikView Server have access to the Internet? If so, ensure that Port 80 is turned on in order to access Qlik's LEF database to retrieve the License Enabler File
  • If the QVS does not have Internet access or it cannot reach the LEF database, even with Internet access, customers can contact the Customer Support team to request a manual copy of the LEF
  • Copy and paste the LEF-file information in the "Paste the contents of the LEF file here (optional)" box, make sure there are no spaces at the end of each line, and make sure there are no extra blank lines between the lines of information. Enter a carriage return (press the 'Enter' key) after the last row.
  • Partners and customers can generate LEFs via the Support Portal. Please see the article on How to request a control number and LEF if needed.
  1. Restart the QlikView services:
  • Remember to restart the QlikView services after applying the license details
  1. Verify the license information:
  • Is it the correct license key and control number?
  • Does the LEF file display correct and valid date (e.g. PRODUCTLEVEL;10;;2013-12-31)?
  • If pasting license information into the fields such as LEF file, make sure to delete spaces and not to miss any semicolons.
  • Make sure that the license key is not applied elsewhere at the same time
  • Check the following row in your LEF file:
    If YYYY-MM-DD is before the release of v11 then you need to update the LEF as the license isn't valid for this major version. If you don't have internet access on the QVS you can generate a new LEF from any computer with QlikView Desktop with internet access:
    1. Open QlikView Desktop and go to Help -> License Update
    2. Press CTRL+SHIFT and left-click just above Cancel in the LEF Editor
    3. Enter the license number and a new LEF will be generated
    4. Copy this into the QVS LEF editor
    If the above date isn't updating when requesting a new LEF, please contact QlikView Support for assistance
  1. Check the account running the QlikView services:
  • Is it a domain account?
  • Is the account a member of local administrators and QlikView administrators?
  • Is it a new account? Remember to log out and in again in order to complete the creation of the account
  • Still the same issue? Change account; create a new domain account with  membership of local administrators and QlikView administrator
  • Make sure that the services account is the member of local ADMIN and QlikView ADMIN group. 
  • Re-enter Services account login credentials on each service and restart the server.
  • Run the services as DOMAIN account (revert the changes after successfully applying the license)
  1. Check the configuration of the host OS:
  • Does the Service Account have access and permission to the default Root folder? (c:\programdata\qliktech\documents)
  • Is the machine name longer than 15 characters? Note that Microsoft Windows has a NetBIOS restriction of 15 characters. Anything above will not allow the server to be licensed. ?
  • Confirm that computer name and NetBios name are identical, otherwise, this will lead to communication errors.
  • Verify port 4747 is opened or not. (can verify by opening a command prompt and typing netstat -an, and make sure that it is in LISTENING status. It looks like TCP
  1. Check if the QlikView Server requires login in the QMC in System/Setup/QlikView Server/Login and remove the login credentials (login/password)
  1. Check the name of the server
  • It was identified that Server\Computer name and Net Bios names are different. Once after making sure that both names are same, then the license got applied successfully and all other errors disappeared. 
  • Note: QlikView server picks up NetBios name by default. So if computer name is different to NetBios name, then there will be communication error and nothing works. So make sure both names are same. 
  • For more information please see following articles: QlikView Server License Problem - "Error: Server failed to set license"
  • Compare local SERVER name with QVS@SERVER name in QMC. The SERVER name must be the same.
  1. Check that the license is not already in use



Labels (2)
Version history
Revision #:
4 of 4
Last update:
‎2020-11-04 06:52 AM
Updated by: