Netfabb 2025 - Network license issue

[dfulle14]

We have a network deployment for Netfabb Premium 2025 created, but when we do the install on a client computer, it's not getting the network license server info and fails to get a license. The deployment installer's Collection.xml file is correct, has the proper license server / product key / serial number. It doesn't matter if you try to specify the license server info manually, it returns an error 11010 "Server Not Responding". The server is fine, though (see below). 

The problem seems to be that the licpath.lic file in C:\ProgramData\Autodesk\AdskLicensingService\A96Q1_2025.0.0.F has "SERVER single 000000000000" and not <servername>

The strange thing is that if I quit Netfabb, and run a a different Autodesk program (AutoCAD, Inventor...) and have no problem getting a license (proving that the earlier error message is inaccurate), then run Netfabb again, it has no problem finding the license server and getting a license. There is a file, nlm-server-info.json that does not get created when running Netfabb first, but is created after running another Autodesk app. When running Netfabb the second time, it will append it's own info to that file.

Any idea why the Netfabb install isn't applying the correct info in the licpath.lic file, or otherwise properly getting a license from the server unless another application has been launched first?

[deepti_bhardwaj · Accepted solution]

Hi @dfulle14,

Thanks for the detailed description, this is very helpful.

Based on what you’re seeing, the behavior points to an initialization timing issue with AdskLicensingService rather than a problem with your license server or deployment configuration. Your observations actually confirm this:

• The license server is reachable (other Autodesk products acquire licenses successfully).
• The deployment XML contains the correct server and product information.
• Netfabb only fails when it is the first Autodesk product launched on the machine.
• The nlm-server-info.json file is not created until another Autodesk product initializes the licensing stack.

What’s happening is that Netfabb 2025 does not always trigger creation of the shared licensing cache on first launch, so it falls back to a default placeholder entry:

SERVER single 000000000000

Once another Autodesk application runs, the licensing service initializes correctly, creates nlm-server-info.json, and Netfabb can then append its own entry and obtain a license normally. This is why the “Server Not Responding (11010)” message is misleading in this scenario, the server is fine, but the client-side licensing context isn’t fully initialized yet. 

Recommended Workarounds (Supported)

Until this is addressed in a product update, the following workarounds are recommended:

Option 1 – Pre‑initialize licensing

• Launch any other network‑licensed Autodesk product once after installation (AutoCAD, Inventor, etc.).
• This forces AdskLicensingService to create nlm-server-info.json.
• After that, Netfabb will consistently acquire a license.

Option 2 – Restart AdskLicensingService

• Restart the Autodesk Desktop Licensing Service (AdskLicensingService) after installation and before first launch of Netfabb.
• This achieves the same initialization effect without launching another product.

Option 3 – Validate service version

• Ensure the latest supported version of Autodesk Licensing Service is installed on the client.
• Netfabb 2025 relies on the shared licensing service, and older builds can exhibit this exact behavior.

What is not required

• No changes to the license file
• No changes to the license server
• No firewall or port changes
• No re‑deployment of Netfabb

[mari.shimode]

Hi @dfulle14, did the information provided answer your question? If so, please click the Accept Solution button on a post you find useful so that others may find this in the future. Thank you very much!

[dfulle14]

Ultimately, yes, running another Autodesk application before Netfabb addresses the problem.