How to clean up the Autodesk ADSKFLEX_LICENSE_FILE setting in the Windows Registry

ISSUE:

Why would you want to clean up the registry?  Well, because sometimes it prevents us from obtaining a network license.  Sometimes it makes the program open much slower.

Solution:

This one can be a bit tricky.  I've seen a variety of entries in the registry but not all of them would apply for network licensing.

NOTE:  This blog is intended for System Administrators or super users that are familiar with the Windows Registry only! 

 Warning! Problems caused by improperly editing the Windows registry could render your computer/operating system unusable. Microsoft provides a wealth of critical information that you need to know about the registry in the Microsoft Knowledge Base.  Use the Microsoft® Registry Editor only at your own risk and only after backing up the registry as well as the system.dat and user.dat files as outlined for your operating system in the Microsoft Knowledge Base.  Additional information about the registry is also contained in the Help topics in the Microsoft Registry Editor.

What we want to see is something like what we put in the Windows Environment variable where the value = 2080@servername

IMPORTANT: You need to replace the servername after the @ in each instance with your actual servers name that has the Autodesk Network License Manager on it.

Let's search!

  1. Open the Registry Editor.  If you don't know how to do that, then please see the Warning above.
  2. Select "Computer" and bring up the Find dialog (Control+F)
  3. Enter ADSKFLEX_LICENSE_FILE and hit enter.

The search takes a while.  You will typically find 1 to 7 entries.  You can hit the function key F3 to go to the Next hit.

I've seen up to 6 or 7 entries, some are fine, some are incorrect or hold additional information that will slow things down.  If it is being slowed down enough, you won't obtain a network license.

I found one!

Once you can see the full name, ensure it stops at _FILE and does not have anything after FILE.

This one is correct.  Of course, you need to replace the server name after the @ in each instance with your actual servers name.

Now hit F3 to go to the next one.  This one needs to be cleaned up.  I'd change it to 2080@Server1;2080@server2;@2080@server3

So does this one:

Again, I'd change it to be our servers:  2080@Server1;2080@server2;@2080@server3

Now, be careful because there are some that should not be touched.  Here are a few examples:

 And this one that I showed earlier:

Exit the registry editor and try the software again.

 Warning!

Problems caused by improperly editing the Windows Registry could render your computer operating system unusable. Microsoft provides a wealth of critical information that you need to know about the Registry in theMicrosoft Knowledge Base. Use the Microsoft Registry Editor only at your own risk and only after backing up the Registry as outlined for your operating system in the Microsoft article How to back up and restore the Registry in Windows and in the related solution How to backup the system Registry . Additional information about the Registry is also contained in the Help topics in the Microsoft Registry Editor.

About the Author

Jeff Lotan

Sr. Technical Support Specialist - Licensing<br><br>I am charged with mentoring and training team members in the proper use our systems and tools, documenting NSC processes, and providing feedback and ideas to the management team towards improving the customer experience. I am also a major contributor to our technical support blog and internal knowledge base.

Follow on Linkedin More Content by Jeff Lotan
Previous Article
SUDAS Gravity Library Updates
SUDAS Gravity Library Updates

Due to the supplements made to the 2024 edition of the Iowa Statewide Urban Design and Specifications, we h...

Next Article
Bad Request Licensing error 400 activating the IMAGINiT Utilities
Bad Request Licensing error 400 activating the IMAGINiT Utilities

When attempting to activate the IMAGINiT Utilities, you receive the following error. “Utilities licensing e...

Need tech support? Let us help!

Learn More