LMTOOLS giving error about not finding license file

[jweiss1313]

I upgraded our Autodesk Network License server to v11.14.1.3 back in August of 2018. I installed a brand new license file and everything was working fine.

I just opened LMTOOLS Utility yesterday and performed a status enquiry and I'm getting an error that says it can't find the license file.  It's looking for the license file in a strange location (see attached pdf file that describes the issue in detail.

My users are able to get licenses for our Autodesk products, but I'm concerned that this error will cause issues in the future.

Please help solve this issue for us.

[Mark.Lancaster]

@jweiss1313

Did you get my personal email to you?

Check this registry entry on the machine hosting the license manager

[robBouch]

Hello @jweiss1313

Welcome to the community!

I have seen strange issues like this with version 11.14 of the NLM if it is installed in a directory other than the default. I've also seen strange behavior if the license file is in a non-default directory.

I would suggest that you stop of the license service, uninstall 11.14 from the Control Panel, and reinstall it to the default location of C:\Autodesk\Network License Manager. Be sure to copy over the license file to the same location, configure the service with the new license file location, and start the service back up.

If one or more of these posts helped answer your question, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

[jweiss1313]

Hi Mark,

I did not get your email.  I checked the registry setting and the path is incorrect and is probably why I'm getting this error.  See my attachment for a screen capture.

I checked my license server in Poland and it does not list the FLEXlm License Manager under software in the registry.

So should I change the path to be correct or do I delete the FLEXlm License Manager key completely so its like it is in Poland?

[Mark.Lancaster]

@jweiss1313

It was an email about the case you put in yesterday.. 

The registry entry should only contain the server name (server name;ip of server) but if the license manager is on the same box as Vault you'll need to have the value sent to "@localhost;@127.0.0.1" without the quotes

[jweiss1313]

Hi Mark,

I decided to partially accept your advice and Rob's advice.  I was curious why our Poland server did not have that registry key at all.  So, I did an uninstall and deleted the key totally.  I reinstalled and everything is work fine now without any error.  When it did the reinstall it did not create that registry key at all.

I believe that the registry key may have been a remnant from the old version since it was referencing a "2018" folder path.

Later in the year when we upgrade to all the 2020 products I will change the install folder to the default location.

Thanks for all your help!

[Mark.Lancaster · Accepted solution]

@jweiss1313

Here's the structure in how licensing works..

Looks for the license location in the licpath.lic file.  In the past that use to be stored in the C:\Program Files\Autodesk\Autodesk product folder.   Since 2017, the licpath.lic is now located in the C:\Programdata\Autodesk\CLS\LGS related folder to the product and year.

The 2nd level is the system variable called ADSKFLEX_LICENSE_FILE which points to the server name.

The top level is the registry entry that I indicated.  When the registry value is in place, that trumps any other information.  So that's why sometimes the registry value is there and other times its not.  However when the value becomes too long, odd things start to happen.  I also recommend the registry entry since its the top level and trumps everything unless you select the option in the license manager to ignore the environment variable.

[jweiss1313]

Thanks Mark for all your help.  I couldn't have fixed it without you!  You can close my helpdesk case too.  Have a great rest of the week and have a happy new year!