Keil Logo

LICENSE: Getting "No Licenses Found, Disabling Flex"


Information in this knowledgebase article applies to:

  • MDK V5.12 or later

QUESTION

When setting up a FlexNet license in µVision on a Client PC, after entering the port number and server name or checking the Use Flex Server checkbox I get the following message:

No License Found Message

What causes this message? How can I correct it?

ANSWER

This message displays whenever the µVision cannot connect to the port and file server you specified because it is either unreachable or non-existent.

This message can be caused by:

  • The file "license.dat" is missing a port number on the SERVER line. — "license.dat" is the default name for the FlexNet license file. Click here to learn more about adapting the license file. If this file is edited, stop and re-start the Flex server, to re-read the file.
  • The Port number is incorrect — The port in the client's License Management dialog should be the same as the port used at the end of the SERVER line in "license.dat". "lmgrd.exe" will try to use this port.
  • The Server name (or IP address) is incorrect, on the client. — This allows the client to resolve the MAC address of the machine running the Flex server to be found. Some networks also require the server name (or IP address), on the client, to match the server name (or IP address) used on the SERVER line in "license.dat".
  • "license.dat" is entirely missing a server name (or IP address). — Specify this between "SERVER" and the MAC address.
  • Switch or router security prohibits using the port number Have your IT department verify that the port number you are using is not being blocked between your PC and the file server. Your IT department can assist you in selecting an acceptable port number.
  • Your firewall or other security software (anti-virus) has denied µVision outgoing access to your LAN or WAN — Check with your IT department. The UV4.EXE and UV4.DLL applications on the client machine must be permitted through its firewall (and any other LAN security applications) for outgoing communications.

    Note: Even after manually disabling a firewall, a security configuration
    may force the firewall to be automatically reactivated.
    
    This can happen after a period of time or triggered by another app.
    
  • Some secure server firewalls also require specifying the port number for the armlmd daemon. You may modify a line in license.dat: (VENDOR armlmd) to:
    VENDOR armlmd port=XXXX
    

    ...where "XXXX" represents the chosen port. Note how "port=" is required, in the VENDOR line, but not used in the SERVER line. Modify the firewall's permissions to allow the vendor daemon on the chosen port.

    Verify that the SERVER and VENDOR ports are different. For a Windows server firewall, select "TCP" for the protocol of the new port rule.
    If a port number was added, stop and re-run the server. Either LMTOOLS (GUI) or the command line dialogs will provide output, showing whether or not armlmd starts OK. If server is OK, you can see both lmgrd and armlmd processes running from the server OS. If there is no error, then attempt to connect from a client PC, again. If adding the port caused is a new server error, like the following output:
  • (lmgrd) armlmd using TCP-port [[port#]]
    //...
    //ends with:
    //...
    (lmgrd) Since this is an unknown status, license server
    (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon.
    (lmgrd) Starting vendor daemon at port [[port#]]
    (lmgrd) Using vendor daemon port [[port#]] specified in license file
    (lmgrd) REStarted armlmd (pid [[pid#]])
    (lmgrd) armlmd using TCP-port 0
    (lmgrd) armlmd exited with status 28 (Communications error)
    (lmgrd) Please correct problem and restart daemons
    
    then the new port may already be actively used, by another program. Try a different (and unused) port. Then stop and start server to test each port.

    There are command-line tools built into an OS to find used ports:

    Windows: netstat -ab
    Linux: netstat -ntup
    

The root cause of the issue is likely one of the above reasons. Stopping and re-starting the server may be required after a security change on the server, and it is also recommended (over a "reread") after editing the server's license file. If these approaches have been attempted, and the issue persists, there are server and client diagnostic scripts in the links below. Run these scripts, open a case with support, and attach the output.

MORE INFORMATION

SEE ALSO

Last Reviewed: Wednesday, July 10, 2019


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.