Most Ansys users make use of floating licensing setups, and I would say the majority of those actually make use of licenses that are hosted nonlocally but on their network. Within this licensing scheme, there are quite a few different tools and utilities that we can use to specify where we pull our licenses, too. One of the methods that is making a comeback (in my recent experience) as far as success in troubleshooting and overall reliability is specifying the environment variable ANSYSLMD_LICENSE_FILE.
This variable allows you to point directly towards one or more license servers using a port@address definition for the FlexNet port. With just this defined, the interconnect port will default to 2325, but if your server setup requires another interconnect port then you can also specify this using the ANSYSLI_SERVERS environment variable with the same format.
The downside is that this is a completely separate license server specification from the typical ansyslmd.ini approach, so any values specified this way will not be visible in the “Ansys Client License Settings” utility. On the upside, this is a completely separate license server specification! Meaning, if there are permission issues associated with ansyslmd.ini, or the other license utilities experienced some unknown errors on installation, this may be able to circumvent those issues entirely.
Also, for more advanced setups this can be used to assign specific license servers to individual users on a machine or to potentially help with controlling the priority of license access if multiple license servers are present. Anyway, this may be worth looking into if you encounter issues with client-side licensing!
Were you so excited to jump on your analysis only to have a “server is down or not responsive” message pop out and alienate you from the fun like a prestigiously exclusive club would make their patrons wait at the door? It might have been your manager running a reverse psychology trick on you or maybe not.
If it is the latter, you are not alone. As a matter of fact, licensing questions come to us on a regular basis. And even though there are plenty of information on the web, we figured it would be beneficial to have the most frequent answers gathered into one place: an FAQ document (attached on this blog).
The Table of Contents includes the following topics:
- Server down or not responsive
- TECS and license expiry
- Versions compatibility
- Overuse of licenses
- Include list
- Virtual server
ANSYS LICENSING FAQ
Download the PDF here.
The document was written with the assumption of the reader having no prior experience with ANSYS or licensing in general. It is formatted in an easy step by step format with photos. The table of contents has hyperlinks embedded in it and can be used to easily navigate to the relevant sections.
We do hope that this document will bring value in solving your licensing issues, and we are always here to help if it doesn’t:
1-800-293-PADT or 480-813-4884
PADT’s webinar covering Mechanical APDL & HPC available in ANSYS 18 will be going live tomorrow at 12:00 PM MST.
Don’t miss this opportunity, sign up today!
With the release of ANSYS 18 comes a plethora of new HPC product packages, each uniquely positioned at a competitive price to ensure that you receive the option that is right for you.
For more information, join us as PADT covers the specifics of the available licensing options, followed by a live Q & A session with simulation support manager Ted Harris.
By watching this webinar you will learn:
About the four main product packages available with ANSYS 18
What licensing options are available under each package
How price scaling works with ANSYS 18
The solving capabilities for each package and licensing option