web
You’re offline. This is a read only version of the page.
close
Thermo Fisher Scientific > Electron Microscopy > Electron Microscopes > 3D Visualization, Analysis and EM Software > Customer Portal > Support Center

VISUALIZATION AND DATA SOLUTIONS

CUSTOMER SUPPORT CENTER

Views:

Issue

When Amira/Avizo displays the following message at startup:
 

"Cannot connect to license server system"

"The license server manager (lmgrd) has not been started yet, the wrong port@host or license file is being used, or the port or hostname in the license file has been changed"

Please follow these suggestions to resolve the issue.

 

Suggested Solutions

 

1. If the page http://localhost:8090/vendor does not display asglmd in 'Up' status on the server machine, or if the expected licenses are not displayed in the lmadmin dashboard

(Refer to article KA-01262 "Manage Floating Licenses: Checking Server Licenses Status with Lmadmin")

  • Apply the suggestions provided in article KA-01298 "Manage Floating Licenses: Vendor Daemon Startup Troubleshooting Suggestions".
  • If these suggestions do not resolve the issue, contact Customer Support and provide:
     
    • The server license file
    • The log files (lmadmin.log, asglmd.log, and/or mcslmd.log) stored by default in the logs folder of your lmadmin installation on the server machine. 

 

2. If the page http://localhost:8090/systeminfo displays a hostname and/or port number on the server machine that does not match the environment variable ASGLMD_LICENSE_FILE on the client machine

  • Run the Thermo Scientific License Manager (LM) on the client machine.
  • Open the Settings Content/Resources/Images/tlm/buttons/icon-settings.jpg 
  • Click Edit   to modify server settings.
  • Enter the hostname and port number exactly as displayed in lmadmin, using the syntax <server hostname>:<port number>.

 

3. If Amira/Avizo still fails to start with the server connection failure message despite the above suggestions

The issue usually comes from the firewall or other network security tools. This can be checked by opening a console on the client machine, navigating to the Amira/Avizo folder share\license\FLEXnet, and running the following commands:

  • On Windows - before 2020.3

.\lmutil lmstat -a -c %APPDATA%\FEI\serverFile.dat
.\lmutil lmstat -a -c "%APPDATA%\Thermo Fisher Scientific\serverFile.dat"

 

  • On Windows - since 2020.3

Check that the path to your license server is correctly set in the system environment variable: echo %ASGLMD_LICENSE_FILE% 

Check the server connection: .\lmutil lmstat -a -c <port number if set>@<server hostname>
Example: .\lmutil lmstat -a -c 27000@FRBOR-9C5GN50

 

  • On Linux - before 2020.3

./lmutil lmstat -a -c $HOME/.config/FEI/serverFile.dat
./lmutil lmstat -a -c $HOME/.config/Thermo Fisher Scientific/serverFile.dat

 

  • On Linux - since 2020.3

Check that the path to your license server is correctly set in the system environment variable: echo $ASGLMD_LICENSE_FILE


Check the server connection: ./lmutil lmstat -a -c <port number if set>@<server hostname>
Example: ./lmutil lmstat -a -c 27000@FRBOR-9C5GN50
 

 

If the above lmstat command fails to display the licenses shown in the lmadmin dashboard, configure the firewall (inbound and outbound rules) on both client and server machines to open the port set in the environment variable ASGLMD_LICENSE_FILE and/or in the client license file.

On the server machine, configure the firewall (inbound and outbound rules) to open the port displayed at http://localhost:8090/vendor. Then, restart Amira/Avizo.

The client/server communication issue could also be due to bad hostname resolution. If so, use the IP address of the server machine in the SERVER line of the server license file, and Thermo Scientific License Manager (LM) on the client machine will solve this issue.


To configure the machines properly to get valid hostname resolution, one has to add the hostName and IP in the file /etc/hosts (Linux) or C:\Windows\System32\drivers\etc\hosts (Windows 10) on both client and server machines.
Refer to the Linux documentation.