Third Party Usage Based Licenses Checkout Failure

The render node can fails to checkout the Usage Based Licenses you have purchased from the Marketplace for the Third party Render applications. You may see different errors from different Render Applications, some of the examples are below: 

3DS Max

Error: 3dsmax startup: Error getting connection from 3dsmax: Monitored managed process "3dsmaxProcess" has exited or been terminated. 
2019/02/20 02:10:24 DBG: [02992] [02720] Starting network 
2019/02/20 02:10:24 ERR: [02992] [02720] License Error - Error Code = 22 
2019/02/20 02:10:24 DBG: [02992] [02720] Stop network

Or

2019/07/02 06:01:33 DBG: [00584] [04556] Starting network 
2019/07/02 06:01:33 ERR: [00584] [04556] License Error - Error Code = 51 
2019/07/02 06:01:34 DBG: [00584] [04556] Stop network 

Maya

STDOUT: maya: Autodesk MayaIO 2017Licensing ErrorA licensing error occurred that Autodesk systems were not able to handle for you.

STDOUT: maya: Autodesk MayaIO 2018
STDOUT: A licensing error occurred that Autodesk systems were not able to handle for you. Please contact Autodesk Customer Support for help in resolving this error.
STDOUT: checkoutLicense: Failed to authorize license
STDOUT: The default location for log files to help diagnose the issue is: /usr/tmp

V-Ray

STDOUT: [2021/Oct/2|07:52:32] error: Could not obtain a license (-2): Internal error: Please contact ChaosGroup support.

Here are some of the reason we have seen in the past that could cause this issue: 

1. The licensing limits for the third party UBL is not setup at all and misconfigured. You can follow this documentation to setup a limit.
2. The third party UBL limit is not added to the job and the render node are not able to reach the Cloud License server. This documentation would help you assigning limits to the job.
3. Render Job as User is enabled. The Worker sets its license environment prior to the "Render Job as User" code being run. This can cause the environment to be overwritten. Remove the Environment Variable from Job's Environment. (Right click on Job -> Modify Job Properties -> Environment -> Remove license EVs
4. Certificate files from Flexnet Operations account (can be checked from the Customer Portal) aren't present
5. Worker isn't able to communication to FNO server
6. You have set up on-premise license server path as Job Environment Variable that overrides the License Environment set by Worker. If you have setup BYOL server entries with the same ports that the License Forwarder uses for UBL then the License Forwarder will fail to start the licensing port for the Workers UBL connection due the port already being in use.

7. License environment on some AWS Portal workers are not set. If you do find that the environment variable is being overridden, the possible locations to check are the following form most to least likely:

   • • • Environment variable on the job (possibly set by "IncludeEnvironment=True" in the job info file) or check if you are setting one in the Job's properties. To check right click the job> modify job properties> Environment
       • GlobalJobPreload. Look for "os.environ" or "SetProcessEnvironmentVariable" code. details here
       • JobPreload.py, details are here
       • OnJobStarted event, details are in the docs
       • The render plugin itself, similar process as for OnJobStarted event

Reach out to us If you are unable to figure the issue by following the list above.