Intermittent licensing issues

[Anonymous]

We have recently replaced our licensing server for our AutoDesk products and we are now experiencing intermittent inability to obtain licenses for our products.  This is not consistent to single users or specific PC's or products.  As this is intermittent, I am unsure how to discover where the issue exists and would appreciate some assistance.

When starting an application we get the errors attached in this sequence, if a user keeps cancelling, they will sometimes get a session, actually entering the server or license details do not help.

Thanks, Daryl.

[Mark.Lancaster]

@Anonymous

Without your debug log file (as specified in the config service tab of LMTOOLS) we can only speculate what's going on.  In addition error code -96 means the service is not running.  Anyhow attach your debug log file here and we can review it.   Note:  Although the debug log file contains names of server and/or machines, there's no impact to your infrastructure if your share here.  However if you don't feel like sharing on an open forum, private message me the log file and we can go from there.

[natasha.l]

Hello @Anonymous, 

Try the steps outlined below regarding a connectivity issue, you can try to resolve it by verifying the NLM version, setting a timeout & opening ports. 

Network License Not Available with error code -96.491.0 

Thank you for posting. Please “Accept As Solution” if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous]

Hi,

Just to clarify, we have a number of users that are working OK, and some who are not.  As far as I know all are using application from the same license server.

I have attached the log file in case that assists.

I think that I can reasonably assume that the service is running OK, it says it is on the server, also, if it wasn't, how are some users getting a license?

Regards, Daryl.

[natasha.l]

Hello @Anonymous

What type of server are you running LMtools on? What are the specifications & setup? 

Please “Accept As Solution” if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous]

Hi,

This is running on a Virtual Server, Windows Server 2008 R2 SP1.

I have attached a snip of the config, this server only acts as a License server for a number of applications, no actual processing or other applications etc. are done on the server.

Regards, Daryl.

[natasha.l · Accepted solution]

Hello @

Thank you for providing this information. Can you verify that you meet the correct requirements for the version of LMtools & VMware? 

 NLM requirements

• LMtools 11.13.1.2
• Virtual Machine Support VMWare ESXi 5.x (License Manager only) Windows Server 2008 R2 or Windows Server 2012

Also, note if the physical address as changed a new license file needs to be generated or requested here: 

1. Generate a Network License File in Autodesk Account or Requesting a Network License File

Then, the NLM needs to be installed and setup:  

2. Install & Configure it 

3. Then, on each Client computer at launch, specify a License Server "2080@ServerName"

4. If the issue persists Open port 2080 for adskflex, and open ports 27000 through 27009 for lmgrd. Or Bind a port to the license file 

Let us know how it goes.

Please “Accept As Solution” if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous · Accepted solution]

Hi,

Thanks for the advice, the version of LMTools is 11.13.1.4, I will have to pass this info on to our Teech Team for VMWare version etc. I will also ask them to run through the suggestions you have provided and advise what happens from there.  Recently, we did replace our server, likely has a different IP Address and MAC Address, though did not expect this to be the problem given that some users are not having any issues, this is not affecting all users.  I will get them to generate a new license fiel as well in case though.

What is interesting is that if I use "2080@ServerName" manually on a device that is not getting a license it seems to overcome the problem.

regards, Daryl.