Learning Forum

[taylo1ml]

We've obtained a trial license for Academic Research EM and added it to our current license server that contains Teaching Mechanical licenses.  The license server is at the latest version (2019 R3).  The trial license successfully installed with the existing license.  The license server correctly shows all available licenses.  

Our problem is that the newly installed electronics software will not obtain a trial license.  The Mechanical licenses continue to work without incident.  The client license configuration is exactly the same for both products.  The electronics software times out when trying to obtain a license and returns "Failover feature 'ANSYS electronics_desktop" specified in license preferences is not available.  FLEXLM server is not responding.  Resource temporarily not available."  The logs in the license server do not show any indication that a license request was received.  The client is successfully pinging the license server.

Does anyone have an idea of what could be wrong and how to fix it?

 

[dsurendr]

Hello,

Please check the ansyslmd.ini file under C:Program FilesAnsysEMShared FilesLicensing to see if the right license server is mentioned

SERVER=1055@

Also, you can try inserting a few TIMEOUT variables under this file:

ANSYSLI_FNP_IP_ENV=1

ANSYSLI_TIMEOUT_FLEXLM=15

ANSYSLI_FLEXLM_TIMEOUT_ENV=10000000

 

[taylo1ml]

The ansyslmd.ini file is correct.  I added the suggested variables, but it did not cause any changes.  I verified the client was correctly talking to the license server.  "Ansysli_util -printavail" produces the correct list  of features and their information (including count).  

When the license fails from the application launch, I select "Diagnose" from the security message window.  I did notice the "FlexNet Publisher Servers" value is blank and "Customer Number" is -1.  It is picking up the rest of the Item Names correctly (Provider Name,  ANSYSLI Version, FLexlm Version, etc).  I'm not sure if this is normal behavior from a client or not as I've not had to use this in the past.

The security message error also indicates 'ANSYS electronics_desktop' is not available.  The correct feature is electronics_desktop (without the ANSYS).  I'm assuming electronics_desktop is the match that it is looking for and 'ANSYS' was added as a user identifier but not actually used as part of the checkout feature match?

Any additional things to try?

[dsurendr]

Hello,

Yes electronics_desktop is the feature used for opening Electronics Desktop.

Have you tried disabling the Firewall on the license server?

If it's a Windows license server, you can make sure to add these exceptions:

[tsiriaks]

Check the license.log file on the license server to see if you see OUT and followed by IN right away for each time that client is having the licensing issue.

If so, on client side, try increase the values of these two ANSYSLI_TIMEOUT_FLEXLM ,  ANSYSLI_FLEXLM_TIMEOUT_ENV

Also, what is the current content of AnsysEMShared FilesLicensingansyslmd.ini  on client machine ?

[taylo1ml]

Thanks.  It was the firewall on the server.  Even though the same license server was working for structures,  electronics required me to make a manually entry for ansyslmd even though an entry for "Ansys license server" existed  (haven't had the time to see what this rule was explicitly defining).

[tsiriaks]

because they use different licensing mechanisms, see my posts in this thread that explain in details

https://forum.ansys.com/forums/topic/ansys-license-manager-technical-questions/

However, starting from AnsysEM (AEDT) 2019 R2, it has used a new licensing mechanism called ACL. All of the licensing interconnect portion that is used with Mech/Fluids products between client-server is now locally on client side only. Then, between client and server, it uses pure FlexNet licensing like previous AEDT versions.

The error that you saw is from licensing interconnect portion waiting too long to get licenses from FlexNet, so it's timed out. We've seen this issue plenty of times with Mech/Fluids licensing and what dsurendr suggested on the first post would have helped but when this issue happened, the FlexNet log always shows OUT and then IN right away (meaning the checkout from FlexNet is actually successful but licensing interconnect timed out before that happened). If you can confirm that your FlexNet log (license.log) also has these OUT and IN right away when the issue happened, it would be great info for us that the same trick doesn't work for ACL.If you don't have those in the log, it just means that your issue was different than what we thought (just same error message).