General Licensing

Maya on Linux hangs and cannot be restarted after force quit

Some users have reported that Maya licensing hangs after it has been force quit. Trying to relaunch Maya results in Maya just hanging.

This appears due to Maya's process keeping the adlmmutex file locked (AdlmMutex::Lock). To get around this issue, we can set up the following system variable:


Usually a variable can be setup at system level. But Maya is particularly helpful in letting us set up Maya-specific variables directly in the Maya.env file, to avoid cluttering the system settings with customised variables. Location of Maya.env changes depending on our system. On Linux, it usually is located in either one of these paths:

  • ~/maya/version
  • ~/maya/

More information on how to work with/edit Maya.env file can be found here: Setting environment variables using Maya.env

This workaround can be also found on the Autodesk Knowledge Network

Autodesk 2017 Software running as Restricted user Certificate revocation check fail

Some customers have reported Autodesk 2017 product crash on initial launch for certain users with restricted permissions and certain group policies applied.

After some research we found the root cause of the failure is an invalid registry value set,  with Group Policy (from old .adm file) or other scripts.


"This error occurs when the 'State' value of below mentioned registry key is incorrectly set. This value corresponds to the Internet Explorer security setting "Check for publisher’s certificate Revocation" and "Check for signatures on downloaded programs"

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
You can find a key with the name ‘State’. By default the values is set to – ‘23c00’"


more details on this key.




What does the license error -97 error mean exactly?

In this episode of tenacious troubleshooting, we are focused on the -97 error.

1.  The easy part is finding what the FlexNet error codes mean.  It is noted here:

Describe -97 Error

2. When this error happens on the license server, just look at the server log file to determine what the problem is. You can also check out this blog post for more info as well.

Server -97 Error

3.  In this instance, on the client workstations, when we launched the product, the FlexNet Finder window would keep on looping and the error was 0.0.0.

a.  We confirmed that the license server at the site was running the current version of NLM (11.12).

This is also noted in the log file on the license server.


b. We then increased the error messages for licensing by adding this environment variable on the workstation.

c. We finally get the dreaded -97 error message.

Client -97 Error

In the dialog box, we confirmed that client was looking at the correct server and the Windows Firewall was correctly configured as noted in steps 4-6 in the Quick Start Setting up a License Server blog post.

The client machine indicated that the server was not running.  A known issue is having with other 'vendors' on the server along with Autodesk products.   The symptom is that the server log file will appear like it is running but it is not actually running.  The solution is basically to stop the Autodesk license server and edit the license file and add a port to the license file as noted below:

SERVER TOR2UA13809X0 3CD92B5B4B2E 27001
VENDOR adskflex port=2080


Once the file has been edited, just restart the license server and the software should launch correctly.

For more info on the this issue, please check out the following posts/articles:

Thanks to Sean Couture for confirming this workflow was indeed the problem.

License Manager 11.12 and The Foundry License Tools

We are receiving few cases where customers have problems running our 2015 network versions and The Foundry software (e.g. Nuke).
If you have installed License Manager 11.12 for the 2015 products (e.g. Maya) on a server that is already hosting the license server for The Foundry products, you may also experience these issues.
The Foundry products currently use a different version of the License Manager (10.8). In some cases, launching both services prevents one of them to run correctly and therefore licenses for that services are not available.

The cause we identified in collaboration with The Foundry Support Team (thanks Jake) is likely because both services use by default the same TCP port that is 27000.
This can generate a conflict and results in one of the services to shut down or not start at all.

It is possible to avoid or prevent this to happen simply changing the default port used by one of the services. You can do this adding the port to the first line of the license file:


SERVER MyServer 000000000000 27001

Note: if on any clients you are using pointers to specify the license server, you may need to also change or add the port there.

See Also    
FLEXnet: don’t like 27000 or 2080 port numbers? Change them

Autodesk Products that require IPv6 NLM

Using empirical data, the 3 products that have historically required IPv6 NLM [Network License Manager] are:

  • Autodesk Inventor
  • Autodesk Vault
  • Autodesk Simulation CFD

In this licensing scenario, the user had Product Design Suite and all the products were working except for Autodesk Inventor, we just swapped out the IPv4 versions of NLM with the IPv6 version and all the products in the Suite worked perfectly.

Just follow Step 7 via this blog post for an awesome workflow of swapping the lmtools.exe, adskflex.exe, lmgrd.exe, lmutil.exe:


AutoCAD Map 3D 2014 & Civil 2014: Licensing with ESRI ArcGIS

Just a quick note that if plan to setup a license server for an Autodesk 2014 Product and the latest Esri ArcGIS on the same computer, you will need to download, install and configure the 32 bit version of the Autodesk Network License Manager [NLM] on the license server.  The current versions of ESRI ArgGIS still uses a 32 bit NLM and it will not work with the 64 bit version of our NLM.

If you use a 32 bit NLM  for Autodesk and Esri products, it will show up as 2 services in the lmtools.exe.


To setup a license server, please review this blog post:

This is a reference post way back in the 2011 and the solution still applies today.

General Licensing: Activating Autodesk MotionBuilder 2014 on Linux

Most part of our products is activated online automatically. In some cases you may need to manually activate your standalone license product using an activation code provided by Autodesk. When you need an activation code you usually send the request code provided by the software during the activation at launch. The request code is usually displayed on screen and it is a 32 digits alphanumeric string.


MotionBuilder 2014 on a Linux OS uses a different activation method where the activation code is not based on a request code but on an .xml file.
The XML file MOBPRO2014en_USLongCode.xml is created during installation on you filesystem's /tmp folder.
So, if you need an activation code for MotionBuilder 2014 on Linux you have to submit this xml file in order to obtain the activation file (MOBPRO2014authcode.xml), that you have to select once you have pressed the Browse button:


To request an activation code or file either point to or checkout the following article:
General Licensing: Getting an Activation Code Manually

AutoCAD 2014 Cascading with Product Design Suite 2014

Here is an interesting scenario for the point product AutoCAD 2014 cascading with Product Design Suite 2014.  In this test, we are using the following Autodesk Products in the matrix:

  • Point Product AutoCAD 2014 = This is AutoCAD 2014 only!
  • AutoCAD 2014 in the Product Design Suite 2014 = AutoCAD Mechanical 2014 with Vanilla Profile.
  • AutoCAD Mechanical 2014 = One of the products in the Product Design Suite 2014.

1.  You have a network license for the point product AutoCAD 2014 and Product Design Suite 2014 at your site. 

2.  If you install the Product Design Suite 2014 only and launch AutoCAD 2014 from that shortcut, it will always use a Product Design Suite 2014 license. The reason is that this AutoCAD 2014 shortcut is actually using a vanilla profile of AutoCAD Mechanical 2014.


The main advantage is that it is saving you drive space on your computer because you don't need the point product AutoCAD 2014 installed on your computer.

3.  Because you have both the point product AutoCAD 2014 and the Product Design Suite 2014 network license at your location, if you want point product AutoCAD 2014 to cascade from the 'cheapest' license to the 'newest' license, you will need to install the point product AutoCAD 2014 on all  your computers.


4. If the computer has the point product AutoCAD 2014 as well as Product Design Suite 2014 installed, if you launch point product AutoCAD 2014, it will use a point product AutoCAD license.


5.  If you leave the point product AutoCAD 2014 running and then launch AutoCAD Mechanical 2014 that it in the Product Design Suite, it should automatically cascade up to the Product Design Suite 2014 license and return the point product AutoCAD license back into the pool.


Inventor Professional 2014: Hacking the registry to change the license from Network to Standalone.

To change licensing method for Inventor Professional 2014 you need to edit the following registry key.


Change values for the Value keys below:
LicenseType  from Network License change to Stand-Alone License
LicenseMode from 1 change to 2

NOTE:  Always backup the Registry and/or make a note of the values!


Inventor 2012: Hacking the registry to change the license from Standalone to Network

AutoCAD Mechanical 2014: Hacking the registry to change the license from Network to Standalone

To change the licensing method for AutoCAD Mechanical 2014 you can try editing following registry key.


Change Type value key from 1 to 2

NOTE:  Always backup the Registry and/or make a note of the values!


AutoCAD Family 2014: Hacking the registry to change the license from Standalone to Network.

AutoCAD 2012: Hacking the registry to change the license from Standalone to Network.