Ansys Products

Ansys Products

License Manager issues on virtual machine

    • nedwards
      Subscriber

      Dear Forum, I have been given access to a virtual machine (VMware running WinServer2012R2). I am having multiple license manager issues that neither our IT or I can figure out how to troubleshoot and fix.

      For context - I'm using LS-OPT to run optimisations with ANSYS/LS DYNA as the solver (i.e. a batch of approximately 3000 simulations using Ansys academic research dyna)

      I am getting regular

      • -ANSYS License manager error System error 0 "". (See log 2020/09/30 12:39:54
      • Unexpected disconnects, Timeouts and TSL handshake errors which seem to correspond in the licdebug.DYNA_SOLVER.201.out file to the checkout of a strange feature 10017 (see 2020/09/30 12:42:46)
      • licdebug.DYNA_SOLVER.201.out screen shot:
    • tsiriaks
      Ansys Employee
      Can you update version to at least 2020 R1 by any chance ? There is a trick in recent versions that can avoid this issue.nThe VMware is where you host the licenses or run the simulations or both ?nIf you run the simulation on the same machine that hosts licenses, there is another trick that you can use.
    • nedwards
      Subscriber
      Hi, nThe Ansys product is 2020 R1, and I'm told the license file is 2020 however for the Dyna solvers (DYNA_SOLVER and aa_r_dy) it always seems to check out 19.2. (Perhaps when they updated the license file it didn't include updates for LSDyna??)nI run the simulations only on the Vmware VM, as far as I am aware the licenses are hosted on another sever (I'll confirm with IT).nCheersnNathan n
    • nedwards
      Subscriber
      Confirming that the license is hosted on a separate server (accessible to VM). nThe IT team administering the VM have asked the question - how does the licensing work, is it per CPU or not? nIt seems strange to me that the Dyna_solver log file shows license version 19.2 whereas the workbench ANS_WB log file shows version 20.1nCheersnNathan n
    • nedwards
      Subscriber
      Just creating a simple Workbench LS Dyna example using Ansys Workbench 2020 R1, I get a number of license log files which seem to contradict: nlicdebug.ANS_WB.201.out shows license revision 20.1 for ANS_WB (Shared mode) nlicdebug.MECH.201.out shows license revision 20.1 for aa_r_dy and ACT_DYNAnlicdebug.DYNA_SOLVER.201.out shows license revision 19.2 for aa_r_dy and DYNA_Solver
    • tsiriaks
      Ansys Employee
      hmm, this is odd. Can you check your installation directory (default location) C:\Program Files\ANSYS Inc\Shared Files\Licensing\winx64nand see if there is an 'update' folder here ? If so, move all the files in the update folder to replace those in 'winx64' (i.e., move up one level)nthe license is pulled according to what functionality of the software you are using. The fact that it shows 19.2 is concerning, because it means the LS-Dyna solver is using a client-side licensing binary that's from 19.2. The trick won't work with this.n
    • nedwards
      Subscriber
      Hi tsiriaks,nThere is no 'update' folder (presumably as this was a new VM with a clean install of Ansys 2020 R1, not an upgrade).nIT made the comment that the license server supports both 19.2 and 20.1 (There's another VM that runs 19.2... )nnCould it have anything to do with the Dyna executable I am specifying in LS-OPT? (all three below run the simulations but the log shows use the same license)nC:\Program Files\ANSYS Inc\v201\ansys\bin\winx64\lsdyna_sp.exe ornC:\Program Files\ANSYS Inc\v201\ansys\bin\winx64\lsdyna_sp.exe ornC:\Program Files\ANSYS Inc\v201\ansys\bin\winx64\LSDYNA.exen nCheersnNatha
    • tsiriaks
      Ansys Employee
      Hi Nathan,nFor 19.2, I was talking about the trick that won't work with client-side licensing running this version, not its compatibility with license server version.nIn any case, you can try setting the following Windows environment variablen ANSYSLI_LCP=1 nmake sure you restart all ANSYS applications after this is set (if it was running)nLet us know if this makes a difference.nThanks,nWinn
    • nedwards
      Subscriber
      Hi Win,nI tried setting the Environment variable but got a completely new error message:nCapability LS-DYNA Solver does not exist in the ANSYS licensing pool. None of the products enabling this capability are available in the specified license path....nI've changed it back (and after killing through task manager the ANSYS license connect process) it appears to allow the Dyna executable to run now. However when I start a batch run I get the same strange errors that we cannot seem to troubleshoot: nWhat is the 10017 it is trying unsuccessfully to checkout? (Or should I be looking somewhere else to trouble shoot this?nThanks Nathann
    • SilbaM
      Subscriber
      Hii all,nI had installed ANSYS 16 previously, I uninstalled it and installed 2020 version. nHowever, it didn't display the network specifications page (port no. etc) and directly it just started to install the products.n& I am getting the following error message:nnCould not connect to any license server. n The server is down or is not responsive. n ANSYSLI_SERVERS: 2325@license.iitb.ac.inn FLEXlm Servers: 1055@license.iitb.ac.inn Your version of the ANSYS license manager software is out of date. Please download and install the current ANSYS license manager from the ANSYS Customer Portal.n The version of the license server 2325@license [1.6.1 LM1] must be greater or equal to the client ANS_WB version [2.1.1].
    • nedwards
      Subscriber
      Dear Win,nI just checked that log file again - it appears to me that that each time it appears to try to check out aa_r_dy and DYNA_Solver to be trying to checkout one license (from the 1/4/4/25) Each of my simulations is currently set to run with 4 processors, with a current global limit set at 16 at once. Shouldn't that mean that I should be checking out 4 licenses at a time? Would this be causing the System error 0 (with the checkout issue of 10017 in the logs above)? nCheersnNatha
    • tsiriaks
      Ansys Employee
      Hi Nathan,nSolving with 4 cores is totally fine. You only need one solver license.nCan you try updating the ANSYS License Manager version to 2020 R2 ? This must be done on the license server machine that is hosting these aa_r_dy, among others, licenses.nThanks,nWinn
    • nedwards
      Subscriber
      Thanks Win, I've requested IT to update license manager. I'll let you know if they do....n
    • nedwards
      Subscriber
      Hi Win, something I've noticed on the virtual machine is that the time keeps slipping forward (despite pointing at the same NTP time server) I wonder if this is causing issues with the license manager and forcing the drops?n
    • ANSYS_MMadore
      Ansys Employee
      That could certainly contribute to any existing licensing issues.n
    • nedwards
      Subscriber
      Thanks mmadore, nHe managed to get the domain controller of the virtual machines to point at the same NTP as the license server (found it was originally pointing to the CMOS). Am having less issues, but they are generally the same (System Error 0 with attempt to checkout 10017) and one new one which I haven't seen before (Heartbeat) images from licdebug.DYNA_SOLVER.201.out:nCheers,nNathannnn
    • ANSYS_MMadore
      Ansys Employee
      Can you try adding these to the Client and License server ansyslmd.ini files?nANSYSLI_FNP_IP_ENV=1nANSYSLI_TIMEOUT_FLEXLM=10nANSYSLI_FLEXLM_TIMEOUT_ENV=10000000nnThanksnMattn
    • nedwards
      Subscriber
      Thanks Matt, I'll send a request to IT to try adding to the license server side. It may take a while as we're still in lockdown.nn
    • nedwards
      Subscriber
      I was notified by our ITS that the License server ansyslmd.ini file has been changed and I have modified the client side. I am still getting the same issues, with a screenshot of the log attached.nWe've also now tried a second complete new VM with clean installation and are getting the same issues. n n
    • Mangesh Bhide
      Ansys Employee
      HellonVMs - Make sure the bare metal machine has Hyperthreading rutned off and only the physical cores are used for the VM. solving is CPU intensive process, try using 1 fewer cores than the total number of physical cores on the VM and see if helps in stable connections.nLatency: on end user machine please run ping -t -4 LS-ANSYS.ds.swin.edu.au observe ping return times. Over 200ms is not the best connectivity if observed. consider adding bandwidth if feasible. alternatives: check if VM coonnected to network by WiFi of wired. Wired connectons are more robust. Explore remote desktop or remote submit solves to a machine on the same LAN as the license server and run solves there.nPlease request IT for license server and also WinSvr2016.swincloud.swin.edu.au to check if any network port health checks, port flutter monitors etc are running for either of the machines,nLastly try installing ANSYS License Manager 2020 R2 on WinSvr2016.swincloud.swin.edu.au to the default installation path and set these lines in ansyslmd.ini file on that machinenSERVER=1055@LS-ANSYS.ds.swin.edu.aunANSYSLI_SERVERS=2325@WinSvr2016.swincloud.swin.edu.aunANSYSLI_SERVERS=2325@LS-ANSYS.ds.swin.edu.aunCACHE_SERVER=2325@LS-ANSYS.ds.swin.edu.aunANSYSLI_NOFLEX=1nANSYSLI_TIMEOUT_FLEXLM=15nANSYSLI_FLEXLM_TIMEOUT_ENV=15000000nHope one of these helps identify root cause and resolven
    • Mangesh Bhide
      Ansys Employee
      P.S. when you are queuing simulations, are you using a batch queue ? maybe try adding say a 5-10 second delay before the next one starts running and see if it helps ?n
Viewing 20 reply threads
  • You must be logged in to reply to this topic.