In this article we explain license manager error:

This error will be reported in the geoslope.log file on the license manager if both the lmadmin license manager and Vendor Daemon (the geoslope-lmadmin service) fail to start.

Cause

• There are multiple instances of the license manager running, and they are conflicting with each other.

Before You Start

• You should have direct administrator access to the computer the license manager is running on.
• This process assumes the host operating system is Windows Server 2019.

Steps to Resolve

Only One License Manager Installed on the Computer

1. On the 'Windows Taskbar', click on the 'Start' button (shortcut:  Windows logo key or Ctrl + Esc).
2. Open the 'Windows System' folder.
3. Click on 'Run'.
4. Enter the following command to start the 'Task Manager':
   taskmgr
   
5. If there's a 'More details' button, press it.
   
6. Using 'Task Manager', stop any running license manager processes (i.e. FNPLicensingService, lmadmin, lmgrd, mvsn).
   1. Click on the 'Performance' tab.
      
   2. Click on 'Open Resource Monitor'.
      
   3. Click on the 'Image' column heading to sort by process name.
      
   4. Find a process you want to end, and right-click it.
      
   5. Click on 'End Process'.
   6. Repeat for all license manager processes in the list.
7. Restart the license server.

Multiple License Managers Installed on the Computer

• It is likely that the license manager port assignments are conflicting with each other. 
• You may need to change the port assignments of one or more of your license managers.  See article:
  Changing the FlexNet Publisher License Server Manager Port Number
• General network license troubleshooting can be found in article:
  Troubleshooting Network License Problems