Learning Forum

[piknockyou]

Dear Experts!

The dangers of using licenses from the company's license server via VPN are: 

a. losing connection & failing to reconnect will abort session/solution after a timeout (default 60 min)

--> makes totally sense!

b. but even after a successful reconnection to the company's license server via VPN, regaining the license is not possible for a period of time!

--> does not make sense at all!

I mean latter never happens, when a CATIA license is lost after a connection interruption. It will always be possible to regain the CATIA license, after successfully reconnecting to the company's license server via VPN. 

Why is Ansys having this extra show?

What is the reason for that? A stuck license? How come? Some kind of address change?

How can one solve this problem?

I mean solve, not bypass by e. g., leaving the Work Station on premise and connect via Remote Desktop. That is not a satisfying solution.

How can one tell the license server: 

“Hi, I am back. It is still ME, not someone else! You need identification? Sure! Look, this my ID (MAC-Address?)! I am sure you are satisfied and know I am eligible to regain the license. Thanks for providing!”

Please help.

Cheers!

[piknockyou]

I guess this is a FLEXlm specific deficit.
This always means that after a 60-minute timeout, the application can no longer be used for another 60 minutes, despite a successful reconnect. Catastrophe!
That was, is and probably always will be a deficit of FLEXlm for all possible applications. Pity! CATIA does it better!

Remedy/workaround:
https://install.simutechgroup.com/how-to-release-a-stuck-license
I was able to apply this successfully and write it into a BAT.
This BAT needs to be run as admin & the respective Ansys application restarted.
It's a little tedious, but better than clicking away dozens of timeout warnings for 60 minutes and then stopping work for 60 minutes.
But fortunately, a VPN interruption (hopefully) is relatively rare anyway - at least a workaround is now known.
Anyway, this FLEXlm feature is very bad compared to CATIA handles it.

[George Karnos]

I apologize for the delay in response, but you are correct as it is a limitation using VPN, and removing stuck licenses..
Good to hear you are able to use the bat to run lmremove.

[piknockyou]

- double-post deleted -

[piknockyou]

I need to correct myself, because I ignorantly repeated what a support employee said.

This is definitely an ANSYS issue, not a FLEXlm issue!
Our company uses FLEXlm for both CATIA Composer and Siemens NX.
Both application issue warnings after the VPN connection is interrupted:
┬ÀCATIA Composer threatens to close down the session after 5 minutes.
┬ÀNX just issues a warning, but will not close down the session.
After reconnecting via VPN, both applications regain the same license and all warnings disappear and you can proceed.

ANSYS does not!
You need to fully close the application and restart .... even Workbench, if you want to start SpaceClaim from the Geometry field.
Why is ANSYS not able to do the same? What is the reason for that? A stuck license? How come? Some kind of address change?
ANSYS, Inc. should solve this, especially after so many people work from home (with a local computer, but remote license via VPN)!

[George Karnos]

What version of FlexLM are Catia and NX using?

[George Karnos]

This is a Flexera defect that is being addressed by our licensing development.
This should be fixed in a newer version of FlexLM and will be implemented in an upcoming version of ANSYS.

[piknockyou]

Iasked my IT department for theFLEXlm versions for both, Catia Composer and Siemens NX. I'lllet you know when I receive them.
Has this problem always persisted with ANSYS incorporating FLEXlm or is this only recent with the newest version?

[piknockyou]

- double-post deleted -

[piknockyou]

- double-post deleted -

[piknockyou]

License Server Dassault Composer:
v11.16.5.1 build 257031 x64_n6

License Server Siemens NX:
v11.16.4.0 build 252457 x64_n6