Ansys Licensing Troubleshooting
So, you’ve finally gotten your hands on powerful space-time modeling software. Your installation support engineer has been kind enough to email you specific, detailed download and installation instructions. You launch the application and get this message:
What could have gone wrong?!
If you’ve done the tried and true «turn it off and on again» and can’t seem to get it to work, here are some things to check:
1. Incorrect server info
Go ahead an open the Ansys Client Licenses Setting tool. Did you enter the correct information? If your licenses are shared on a network, contact your License Administrator for the correct values; AGI support cannot provide these values. If the Ansys License Manager is running locally, then try using port 1055 (the default) and localhost as the Server1 name.
NOTE: You need to ‘Run as administrator‘ for the Ansys Licensing Client Settings tool; otherwise, you will not be able to save your port/server settings.
2. All licenses in use
Perhaps all the licenses are in use. From the client tool, under FlexNet Publisher, click «Features in use.» See that there are licenses available for you to check out.
You can see the same report from the Ansys License Manager.
For STK, with the hierarchal nature of the licenses, at a minimum you will need stk_mission_level1. All configurations of STK (Pro, Premium, and Enterprise) require this license.
3. Unable to Connect
If the license manager and a valid license have been installed, and it appears that the server is running, but you keep receiving a connection error, try rebooting. Possible causes for this error include:
a. Firewall exceptions: If the server’s firewall is enabled, you may need to tweak firewall settings on the server to allow the following through as exceptions:
Server (lmgrd) — TCP/IP 1055 (unless it was changed in the license file)
Vendor/daemon — ansyslmd.exe or port if entered into the license file
Interconnect — TCP/IP 2325 (fixed, needed if using the Ansys License Manager)
You can modify the server and daemon ports in the license file as follows:
SERVER Servername ServerHostID 1055
VENDOR ansyslmd port= 12345
After editing the license file, you need to stop and then restart the license service for the changes to take effect.
b. Incorrect port and/or server: Perhaps an incorrect port and/or server name was entered into the client utility, or the required values have changed. Contact your license administrator to obtain the correct input values.
c. ANSYSLMD_LICENSE_FILE: Check to see if you have this environment variable set (this is not common). If so, the value should be port@servername. Make sure that this information is correct.
d. The installed license files have expired: Check with your license administrator to see if your licenses are still valid.
e. Incorrect host name file and/or incorrect host ID in the license file: Do not manually edit the host ID information in the license file. Please contact your installation support engineer with the correct information to have the file reissued.
4. License server not running
Sometimes the Ansys License Manager may be stopped. In order to run licensed products, the Ansys License Manager must be running on the license server with a valid license file. A valid license file must be installed prior to launching the license manager. For more information, see How to Set Up the Ansys License Manager.
To start the manager:
1. Open the Ansys License Management Center.
2. Click the green Start button on the right side of the page.
3. Check the Ansys License Manager -> Diagnostics -> Display FlexNet License Status to verify that licenses are available for checking out.
5. Check your system clock: If you are running with temp/eval/lease licenses, there is a security feature built into FlexNet that may be causing your license check out to fail. This may be evident by checking the Ansys License Manager -> Log Files -> View FlexNet Debug Log. If you see that licenses are checked out, then immediately checked in, this is a clue that either your system clock is off or that FlexNet is finding files dated in the future. For example:
21:36:55 (ansyslmd) OUT: «stk_mission_level1» .
21:36:55 (ansyslmd) IN: «stk_mission_level1» .
- Go to this directory: C:\Users\USERNAME\AppData\Local\Temp\.ansys.
- Look for one of these files: ansyscl.xxxxxxxxxxxx.log or licdebug.xxxxxxxxxxxx.STK12.###.out
- Open these files and search for «System Clock». If you see something similar to this,
then it’s a system clock error.
5. License server only partially running
You find that the license server is only partially running .
Licensing Interconnect: running
Licensing Interconnect Monitor: running
FlexNet Licensing: not running
- Open the Task Manager (Run as Administrator).
- From the Task Manager ‘Details’ tab, locate all lmgrd.exe process and ‘End task’
You can then START the Ansys License Manager
FlexNet Debug Log
If all else fails, send a copy of your Ansys License Manager -> Log Files -> View FlexNet Debug Log to your installation support engineer.
Title | Ansys Licensing Troubleshooting |
---|
The FlexNet License Service is not installed. (-213,14703)
The resolution to this issue is to install the FlexNet License Service by running the ‘installanchorservice.exe’ from a command prompt. The executable can be located in the platform folder of your toolkit, for 32 bit machines it will be the i86_n3 folder and for 64bit machines it will be the x64_n6 folder.
The command to run is as followed: installanchorservice.exe
Here is an example of the command: installanchorservice.exe flexera exampleProduct
Cannot connect to license server system — FLEXnet licensing error -15, 10
I received the «Cannot connect to license server system» error received while working on Tekla Structures. What should I do?
This is a common error that you might receive if you have the Tekla Structures licensing service installed/running on Windows Server 2003 and/or if you are using an old version of Tekla Structures License Server.
Solution:
You will need to have the recent version of Tekla Structures license server installed and running on one of the servers/computers with a supported operating system. You can find the latest hardware recommendations here.
If you have already the recent version of the license server installed on your server/computer that is supported, then check if the Tekla.lic file contents are matching with the error message, as the TCP/IP port or host name in the license file might have been changed. You can go through this article and apply the mentioned instructions under «Do the following steps on your server«.
It would be a good practice also to configure your company’s firewall settings in a way to allow the communication between the license server computer and the client workstation(s).
License trouble: ANSLIC_ADMIN, FLEXlm not running, but two lmgrd processes running!
7Likes
License trouble: ANSLIC_ADMIN, FLEXlm not running, but two lmgrd processes running!
New Member
Daniele
Join Date: Sep 2012
Rep Power: 13
hello everybody
I’ve installed Ansys 13 on a AMD 64 bit machine (OS: Xubuntu 11.10) and I got a little problem with license management.
After starting the system, the license manager is not running, thus I can’t use IcemCFD.
So I launch ANSLIC_ADMIN and click on «Start the ANSYS Inc. License Manager», but, even after waiting some minutes, the box in the bottom-left corner displays «FLEXlm: not running».
The log file shows that the problem is the 1055 port already in use, in fact now there are two lmgrd processes running, even if before clicking on «Start the ANSYS Inc. License Manager» there wasn’t any!
If I kill the process using the 1055 port, then everything works and I can use ANSYS ICEM.
May anybody tell me why two lmgrd processes start?
(the license is on my computer!)
New Member
JohnnyJ
Join Date: Aug 2013
Rep Power: 12
1. Run Server ANSLIC_ADMIN utility (as administrator)
2. Click Stop the ANSYS, Inc. License Manager
3. Open command prompt and enter netstat-a. Scroll down and you should find port 1055 in use.
4. From the ADMIN Utility, click Specify the License Server Machine
5. Click Edit Selected Server Machine
6. Change ANSYS FLEXlm port number to any port number other than 1055 (ex. 1056) and click OK
7. Go to the folder \Program Files\ANSYS Inc\Shared Files\Licensing and open license.dat using notepad. Change the port no. to the one you set above and save.
8. From the Server ANSLIC_ADMIN utility, click Install the License File
9. Browse for the edited license.dat file
10. Click Start the ANSYS, Inc. License Manager
sebastian1430, silverra1n, 87682111 and 2 others like this.
New Member
Nakul Dave
Join Date: Nov 2013
Rep Power: 0
Hi,
If port 1055 or whatever was picked for flexlm isnt on the list, what does that mean?
Thanks in advance for any help,
New Member
Burak SUNAN
Join Date: Dec 2012
Rep Power: 13
FlexLm issues can make crazy minds. I tried to change port numbers or many things found from the internet. However, still not succeeded.
Interesting issue here is FlexLm firstly running then chaning to not running a few seconds later. Besides, in task manager, 9 lmgrd is working simultaneously.
Looking forward to your helps
New Member
FordTran
Join Date: Apr 2014
Location: https://t.me/pump_upp
Rep Power: 0
Originally Posted by gaurav_prabhudesai
1. Run Server ANSLIC_ADMIN utility (as administrator)
2. Click Stop the ANSYS, Inc. License Manager
3. Open command prompt and enter netstat-a. Scroll down and you should find port 1055 in use.
4. From the ADMIN Utility, click Specify the License Server Machine
5. Click Edit Selected Server Machine
6. Change ANSYS FLEXlm port number to any port number other than 1055 (ex. 1056) and click OK
7. Go to the folder \Program Files\ANSYS Inc\Shared Files\Licensing and open license.dat using notepad. Change the port no. to the one you set above and save.
8. From the Server ANSLIC_ADMIN utility, click Install the License File
9. Browse for the edited license.dat file
10. Click Start the ANSYS, Inc. License Manager
Thanks gaurav_prabhudesai
I fixed my problems successfully.
flemlm problem too
New Member
Join Date: Mar 2011
Rep Power: 15
Hi I have the same problem but I don’t understand what command prompt I have to open. windows command prompt? I’ve tried but the command netstat-a is not responsive.
New Member
Guido Bonalumi
Join Date: Dec 2013
Rep Power: 12
I have the same problem with FLEXlm not running with ANSYS13 installed on ubuntu 12.04 LTS 64 bit.
I tried the solution proposed by gaurav_prabhudesai, but it did not work for me. Did someone find another solution or have some ideas?
Senior Member
Join Date: Oct 2010
Posts: 1,016
Rep Power: 26
Hi all,
I had this problem in the past with a kubuntu distro (remember that ubuntu/kubuntu distros are not officially supported by ansys); in this thread there is a partial solution, but you have to manually kill one lmgrd process..
New Member
Guido Bonalumi
Join Date: Dec 2013
Rep Power: 12
Thank you for your reply. I tried your solution but, apparently, does not work for me. When I run ps -A before clicking on «start the ansys inc license manager» I have no lmgrd process running, like you. But when I click on «start the ansys inc license manager» and the run ps -A I have only one lmgrd process, not two.
EDIT: This is the output of ps -A after having clicked on «start the ansys inc license manager»:
PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 kthreadd
3 ? 00:00:00 ksoftirqd/0
6 ? 00:00:00 migration/0
7 ? 00:00:00 watchdog/0
8 ? 00:00:00 migration/1
10 ? 00:00:00 ksoftirqd/1
11 ? 00:00:01 kworker/0:1
12 ? 00:00:00 watchdog/1
13 ? 00:00:00 cpuset
14 ? 00:00:00 khelper
15 ? 00:00:00 kdevtmpfs
16 ? 00:00:00 netns
18 ? 00:00:00 sync_supers
19 ? 00:00:00 bdi-default
20 ? 00:00:00 kintegrityd
21 ? 00:00:00 kblockd
22 ? 00:00:00 ata_sff
23 ? 00:00:00 khubd
24 ? 00:00:00 md
26 ? 00:00:00 khungtaskd
27 ? 00:00:00 kswapd0
28 ? 00:00:00 ksmd
29 ? 00:00:00 khugepaged
30 ? 00:00:00 fsnotify_mark
31 ? 00:00:00 ecryptfs-kthrea
32 ? 00:00:00 crypto
40 ? 00:00:00 kthrotld
41 ? 00:00:00 kworker/1:2
43 ? 00:00:00 scsi_eh_0
44 ? 00:00:00 scsi_eh_1
45 ? 00:00:00 scsi_eh_2
46 ? 00:00:00 kworker/u:3
47 ? 00:00:00 scsi_eh_3
48 ? 00:00:00 scsi_eh_4
49 ? 00:00:00 kworker/u:4
50 ? 00:00:00 kworker/u:5
70 ? 00:00:00 devfreq_wq
216 ? 00:00:00 firewire
282 ? 00:00:00 jbd2/sda5-8
283 ? 00:00:00 ext4-dio-unwrit
308 ? 00:00:00 mountall
373 ? 00:00:00 upstart-udev-br
382 ? 00:00:00 udevd
495 ? 00:00:00 kmemstick
535 ? 00:00:00 r592_io
597 ? 00:00:00 cfg80211
664 ? 00:00:00 r852
698 ? 00:00:00 udevd
699 ? 00:00:00 udevd
719 ? 00:00:00 iwl3945
746 ? 00:00:00 kpsmoused
798 ? 00:00:00 rpcbind
876 ? 00:00:00 hd-audio0
886 ? 00:00:00 upstart-socket-
934 ? 00:00:00 rpc.statd
977 ? 00:00:00 kdmflush
980 ? 00:00:03 mount.ntfs-3g
989 ? 00:00:00 kcryptd_io
990 ? 00:00:00 kcryptd
994 ? 00:00:00 jbd2/sda7-8
995 ? 00:00:00 ext4-dio-unwrit
1009 ? 00:00:00 rpciod
1014 ? 00:00:00 nfsiod
1026 ? 00:00:00 dbus-daemon
1041 ? 00:00:00 sshd
1045 ? 00:00:00 rpc.idmapd
1059 ? 00:00:00 modem-manager
1060 ? 00:00:00 bluetoothd
1089 ? 00:00:00 NetworkManager
1093 ? 00:00:00 rsyslogd
1095 ? 00:00:00 polkitd
1103 ? 00:00:00 krfcommd
1107 ? 00:00:00 cupsd
1110 ? 00:00:00 avahi-daemon
1111 ? 00:00:00 avahi-daemon
1197 tty4 00:00:00 getty
1209 tty5 00:00:00 getty
1237 tty2 00:00:00 getty
1241 tty3 00:00:00 getty
1243 ? 00:00:00 console-kit-dae
1307 tty6 00:00:00 getty
1314 ? 00:00:00 acpid
1317 ? 00:00:00 irqbalance
1320 ? 00:00:00 gdm-binary
1332 ? 00:00:00 gdm-simple-slav
1337 tty7 00:00:19 Xorg
1350 ? 00:00:00 cron
1351 ? 00:00:00 atd
1373 ? 00:00:00 hddtemp
1430 ? 00:00:00 wpa_supplicant
1445 tty1 00:00:00 getty
1455 ? 00:00:00 flush-8:0
1489 ? 00:00:00 upowerd
1658 ? 00:00:00 colord
1669 ? 00:00:00 rtkit-daemon
1673 ? 00:00:00 gdm-session-wor
1707 ? 00:00:00 dhclient
1711 ? 00:00:01 teamviewerd
1719 ? 00:00:00 dnsmasq
1859 ? 00:00:00 gnome-keyring-d
1876 ? 00:00:00 gnome-session
1911 ? 00:00:00 ssh-agent
1914 ? 00:00:00 dbus-launch
1915 ? 00:00:00 dbus-daemon
1924 ? 00:00:00 gnome-settings-
1933 ? 00:00:00 gvfsd
1939 ? 00:00:00 gsd-printer
1943 ? 00:00:10 compiz
1947 ? 00:00:00 flush-ecryptfs-
1949 ? 00:00:00 accounts-daemon
1951 ? 00:00:00 syndaemon
1953 ? 00:00:00 gconfd-2
1958 ? 00:00:00 pulseaudio
1961 ? 00:00:00 gvfsd-metadata
1962 ? 00:00:01 gnome-panel
1966 ? 00:00:00 dconf-service
1969 ? 00:00:00 nm-applet
1973 ? 00:00:00 gnome-fallback-
1974 ? 00:00:00 bluetooth-apple
1975 ? 00:00:00 notification-da
1981 ? 00:00:00 gvfs-gdu-volume
1984 ? 00:00:00 udisks-daemon
1987 ? 00:00:00 udisks-daemon
1991 ? 00:00:02 nautilus
2003 ? 00:00:00 polkit-gnome-au
2005 ? 00:00:00 gvfs-afc-volume
2008 ? 00:00:00 gvfs-mtp-volume
2014 ? 00:00:00 gvfs-gphoto2-vo
2021 ? 00:00:00 sh
2022 ? 00:00:00 gtk-window-deco
2025 ? 00:00:00 gvfsd-trash
2028 ? 00:00:00 gvfsd-burn
2036 ? 00:00:00 gdu-notificatio
2061 ? 00:00:00 indicator-apple
2067 ? 00:00:00 indicator-sound
2069 ? 00:00:00 indicator-messa
2071 ? 00:00:00 indicator-print
2073 ? 00:00:00 indicator-datet
2076 ? 00:00:00 indicator-appli
2077 ? 00:00:00 indicator-sessi
2103 ? 00:00:00 geoclue-master
2105 ? 00:00:00 ubuntu-geoip-pr
2111 ? 00:00:00 telepathy-indic
2114 ? 00:00:13 dropbox
2120 ? 00:00:00 mission-control
2126 ? 00:00:00 goa-daemon
2130 ? 00:00:00 zeitgeist-datah
2136 ? 00:00:00 zeitgeist-daemo
2147 ? 00:00:00 zeitgeist-fts
2163 ? 00:00:00 cat
2168 ? 00:00:00 gvfsd-http
2172 ? 00:00:00 gnome-screensav
2179 ? 00:00:00 rpc.statd
2213 ? 00:00:00 update-notifier
2224 ? 00:00:00 system-service-
2251 ? 00:00:01 gnome-terminal
2257 ? 00:00:00 gnome-pty-helpe
2258 pts/2 00:00:00 bash
2445 ? 00:00:00 kworker/1:0
2446 ? 00:00:00 kworker/0:0
2508 ? 00:00:00 kworker/0:2
2587 pts/2 00:00:01 wish
2875 ? 00:00:00 kworker/1:1
2927 ? 00:00:00 kworker/1:3
2941 ? 00:00:00 ansysli_server
2945 ? 00:00:00 ansysli_monitor
2949 ? 00:00:00 lmgrd
3893 pts/2 00:00:00 ps
New Member
Guido Bonalumi
Join Date: Dec 2013
Rep Power: 12
I found my own solution! Finally!
Here is what I have done:
1. Modify the license.txt, changing the host name with its ip address (127.0.1.1 in my case). You can find it in your /etc/hosts.
2. Install the license.
3. Start the license manager.
4. Run ps -A > ~/Desktop/ps.txt. In the ps.txt file you will find two lmgrd processes, kill the first one. In my case killing the second one did not work (I do not know why!).