Installing and Configuring Flexlm on WindowsArtwork uses Flexera's software licensing system called Flexlm. Flexlm is used by virtually every EDA company to license software. We recommend you view this 5 minutes video that shows a flexlm installation on Windows: |
Frequently Asked QuestionsQ. Where can I download the flexlm license server for Artwork products? A. It's on our ftp server. You will need a login/password to access the ftp server. ArtworkFlexPkgWindowsV11.14_with_dongle_support.zip 06/15/2017 4.5 MBytes, 32 and 64 bit Q. How to I get the hostid of the license server? A. Use either the ipconfig /all command or the lmtools.exe utility. Details ... Q. How do I install a flexlm license manager on Windows (first time install)? A.View the video at the top of this page or if you prefer follow these instructions Q. Flexera Type 9 key drivers A.Download Flexera Type 9 key drivers for Windows Download Drivers Q. I already have a flexlm server running for another company's product. Can I piggy back on that existing service? A. Generally, Yes. However there are different versions in use and if the versions are different they may not be compatible. follow these instructions Q. I got a strange log file error when installing a flex license server on Windows:
A. We tracked this down to the fact that after editing the license file (license.dat) with Notepad.exe the administrator saved the file with Unicode encoding. This prevented lmgrd.exe from reading the file though one could not see anything unusual in the display. Re-saving the file with ANSI encoding solved the problem. Checking Status of the flexlm license server (Windows) Creating a Second Service of the flexlm license server (Windows) Setting the LM_LICENSE_FILE (Windows) Flexlm license manager and Firewalls lmutil command line options Complete Flexlm Error Code List Artwork daemon won't start (due to directory name) 11-11-2003 Artwork daemon won't start due to samsuite date limitation 7-17-2007 lmtools does not report licensing correctly... 11-18-2003 Program is slow to start up in floating mode. 5-1-2008 FLEXnet Licensing error:-1,359. System Error 5-21-2009 Error: Non-activation-capable daemon 09-09-2009 Problem when vendor path name has spaces 11-04-2009 Flexlm error -16,287:22 "Invalid argument" 11-14-2009 Flexlm error -96 "License server machine is down or not responding. 1-10-2011 Flexlm error -97 "License server error -97. 10-13-2017 Flexlm error Failed to open any default TCP port 10-28-2010 Windows Flexlm Node locked installation 3-15-2011 ports used by license manager and daemon 11-25-2011 lmhostid and hostinfo return incorrect hostid 04-25-2012 Using the options file with Flexlm 1-7-2014 Flexlm reports TCP_NODELAY error 1-30-2018 Ubuntu 14.04.1 error ioctl failed: No such device 4-14-2015 Ubuntu 14.04.1 error hostinfo: No such file or directory 4-14-2015 Configuring the hosts file 5-31-2017 Possible causes for Flexlm Error -5 and -83 5-31-2017 Possible causes for Flexlm Error -96 8-10-2017 Possible causes for lmutil error "no such file or directory" 5-16-2018 Possible causes for error "FlexNet Licensing error:-15 , WinSock: Connection refused" 6-11-2018 Possible causes for error "Invalid License File" 6-15-2018 Flexlm error -15 "Operation Now in Progress" 8-25-2018 artwork daemon error "artwork exited with status 53" 3-3-2020 |
Installation TroubleshootingDirectory naming conflict with daemon name One of our customers installed flexlm (lmgrd and the artwork.exe daemon) in a directory called: c:\flexlm\artwork Upon testing the installation he received an error informing him that the artwork daemon was down or that another instance of artwork was running. The actual problem seemed to be the name of the directory and some locking that the daemon does. Changing the installation directory name to c:\flexlm, or c:\flexlm\artwork_conversion, or any directory path that does not end in artwork fixes the problem. Older lmtools.exe reports no licenses One of our customers installed flexlm version 8.1 on his server. When he tested the available licenses with the lmtools utility he found that it reported no licenses available. Upon further testing and investigation we discovered that he was using an older version of lmtools, 7.0 (or lmutil) which apparently had trouble communicating with lmgrd 8.1 and later. Upon using a current version of lmtools the expected number of licenses were property identified. |