🎉 We're happy to announce new public releases 🎉

  • TriCore v6.2r2 Inspector v1.0r8 - An automated method for identifying toolset issues in compiled output code
  • VX-toolset for Arm - v8.0r1 - A certified compiler toolset for safety critical embedded software development on Arm cores
Contact us to get access

FLEXlm Error: Multiple TASKING servers running

27-Jan-2026

If you are using a TASKING floating license together with another vendor’s license daemon, you need to use two individual license files, each referring to its appropriate daemon.

A common setup might look like this:

  • c:\flexlm (FLEXlm directory)
  • c:\flexlm\vendorx\vendorx.dat (Vendor X license)
  • c:\flexlm\tasking\tasking.dat (TASKING license)

The LM_LICENSE_FILE environment variable is also set to reference both license files.

Although the configuration is done correctly, sometimes launching lmgrd may result in the following error message:

MULTIPLE “TASKING” servers running

However, checking the system process list confirms that no TASKING daemon is actually active. When attempting to build a project, the TASKING tools also report:

cannot connect to license server

The root cause is that when the TASKING daemon is launched, it creates a temporary file called tasking to prevent itself from launching more than once. In this case, a directory carrying the same name as the temporary file, tasking, is used to store the license file, which caused it to abort its own launch.


Possible solution

To make it launch:

1. Choose a directory name other than tasking to store your license file.

2. Adapt the paths as stored in the TASKING license file and LM_LICENSE_FILE

3. After making these adjustments,  relaunch lmgrd and the TASKING daemon. 


More resources

Was this answer helpful?