Issue
When logging into Workstation one of the following error codes is given.
- Invalid returned data from license server system. (Error code: -12)
- Cannot connect to license server system. (Error code: -15)
- License server system does not support this feature (Error code: -18)
- The desired vendor daemon is down. (Error code: -97)
Product Line
EcoStruxure Building Operation
Environment
- Workstation
- License Server
Cause
These type of issues are contributed to the License Server, Vender Daemon being down or not having a valid license for the application which is used.
Here is a complete list of error codes
Resolution
If Workstation is installed on a different PC than the license server, refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96).
If you get license error -18 refer to Error "Requested license is not available on the license Server" even though the license for the Str....
Start by working through the troubleshooting steps below. In some cases the Building Operation License Server was unable to start due to antivirus programs on the computer.
Cannot connect to FlexNet License Admin
Using your internet browser and go to localhost:8888. If you are unable to connect to this address then the License Server is not running.
- Ensure that the Building Operation X.X License Server is running as a service.
- Right Click on the Computer icon on the desktop and click on manage.
- In the system tree on the left, go to Services and Applications > Services.
- Scroll through the list and select Building Operation X.X License Server. Click start in the top left corner of the window.
- Some times the following Windows Error 1067 is given when trying to start the License Server.
Note: In the past this error has been caused by antivirus software on the computer. In this situation the antivirus program had to be uninstalled in order to allow the License Server to start.
- If the Building Operation License Server will not start then it may be due to another program using TCP port 8888. Use TCPView to search for programs running on local port 8888 and stop the other program.
Vendor Daemon is Down
Note: If working with a 32 bit PC, replace "Program Files (x86)" with "Program Files" in the file paths below.
- Using your internet browser go to the address localhost:8888. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password.
- Click on the Vendor Daemon Configuration tab and then select the taclic daemon.
- Verify that the path in the License File or Directory field matches the location of the taclic.lic file.
- The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the License File or Directory field.
- The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the License File or Directory field.
- Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field.
- The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the Vendor Daemon Location field.
- The first half of the file path is C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\License Server\ followed by what is in the Vendor Daemon Location field.
- If changes were made then click Save and then Start.
Vendor Daemon is Down issue caused by ipv6
Cases have been seen where having ipv6 enabled on the same computer where the license server is running causes the Daemon is down error. Often there will be entries in the license server logs that are similar to:
17:46:44 (demo) Lost connection to lmgrd, heartbeat timeout expired, exiting.
17:46:44 (demo) EXITING DUE TO SIGNAL 37 Exit reason 5
17:46:44 (demo) IN: "f1" user1@host1 (SHUTDOWN)
17:46:44 (lmgrd) demo exited with status 37 (Communications error)To confirm whether this is the issue ask the site if it is OK to disable ipv6 on the machine temporarily.
- In Windows control panel disable ipv6
- Reboot the computer.
- In some cases, it might be needed to disable IPv6 completely in the registry: https://tweaks.com/windows/40099/how-to-properly-disable-ipv6/
- If the issue is resolved then inquire with the site if it is OK to leave ipv6 disabled.
- If SIGNAL 37 errors are seen in the license server logs, these can be caused by having the localhost name associated with the IPv6 loopback address in the hosts file. This can cause communication problems between the license server daemon (lmgrd) and the vendor daemon, resulting in shutdown of the latter. If you have a line like the following in the /etc/hosts file:
::1 localhost ip6-localhost ip6-loopbackplease change it to
::1 localhost6 ip6-localhost ip6-loopbackso that the localhost name is associated only with the IPv4 127.0.0.1 address. Please note that modifying this file requires Windows administrative privileges.
