Unable to configure new license server

There are a few distinct issues tangled together here — let me untangle them.

1. Which daemons belong in your license file VENDOR lines

You need both alterad and saltd in the VENDOR lines, and they can co-exist on the same server. You can only have one vendor daemon running at a time of each type — for example, alterad and saltd can co-exist, but you cannot have two running daemons of alterad. Altera FPGA Software Installation and Licensing

The daemon-to-product mapping is:

• alterad — Quartus Prime software; saltd — Questa Altera FPGA Edition software. Altera FPGA Software Installation and Licensing

2. The mgcld situation — critical point

If the VENDOR line mentions mgcld, you must manually change it to saltd. mgcld is no longer supported in the Questa Altera FPGA Edition version 2024.1 and later. Altera FPGA Software Installation and Licensing

However — and this is the part that trips most people up — only change the VENDOR line, not the INCREMENT lines. Do not change any of the INCREMENT lines. Leave the INCREMENT lines with the original vendor daemon name (mgcld). Setting up a License File in the License Server

So your license file VENDOR section should look like this:

VENDOR alterad /path/to/alterad [port=]
VENDOR saltd /path/to/saltd [port=]

…with all INCREMENT lines left exactly as received.

3. Where to get the daemon executables

You don't need to install a separate Siemens license manager to get both daemons. To support network licensing, the Altera FPGA software requires FLEXlm license manager server software version 11.19.5.0 or later. The installation process for Quartus Prime software installs FLEXlm version 11.19.5.0. You should also verify that the FLEXlm software version on the license server is 11.19.5.0 or later. Upgrading the FLEXlm License Manager Server Software

The Quartus Prime installation provides lmgrd and alterad:

• Windows: \quartus\bin64\alterad.exe and lmgrd.exe
• Linux: /quartus/linux64/alterad and lmgrd

For saltd, upgrade to the Siemens FlexLM (SALTD) daemon from the download page. Error : FLEXlm version of vendor daemon is too old You only need to drop the saltd binary into a known path and reference that path in the VENDOR line — you do not need to run the full Siemens license manager installer.

4. Step-by-step: setting up the license file on the server

1. Save license.dat in the preferred location:
   Windows: :\flexlm Linux: /usr/local/flexlm/licenses Setting up a License File in the License Server
2. Edit the SERVER line to include the correct hostname and port:
   If the license server uses Windows, specify the port number for the licensing manager. Choose a number outside of the 27000–28000 range, and unique on the machine. In Linux systems, the FLEXlm license manager automatically chooses a free port between 27000 and 27009. Setting up a License File in the License Server
3. Edit the VENDOR lines:
   • Change mgcld → saltd on the VENDOR line only
   • Set the correct path to each daemon executable
   • Optionally specify a static port per daemon (recommended if you have a firewall)
   Example: SERVER myServer 0123456789ab 1800
VENDOR alterad ./alterad port=1801
VENDOR saltd ./saltd port=1802 Setting up a License File in the License Server
4. Leave all INCREMENT lines untouched.
5. Start the server:
   At a command prompt, type:
   Windows: \bin64\lmgrd -c \path\to\license.dat
   Linux: /linux/lmgrd -c /path/to/license.dat Launching the Licensing Server

5. The "Cannot connect to license server" error

This error almost always means one of three things: lmgrd hasn't been started successfully, the port@host string the client is using doesn't match what's in the license file, or a firewall is blocking the port. On Windows in particular, Quartus Prime software release version 12.0 and later does not recognise a FLEXlm license server specification that does not contain an explicit port number (e.g., @mylicsrv). To resolve this, specify an explicit port number (for example, 27000@mylicserv on Windows clients). The Quartus II software does not recognize a FLEXlm license server specification without an explicit port number

Also verify the lmgrd daemon itself started cleanly by checking the log file. If you change the license file, you must reread the license file or restart the license server before you can run the Quartus Prime software again. Rereading an Existing License File on a License Server

6. The multiple license files you received

This is expected behaviour when you have licenses for multiple software versions assigned to one server. An Altera license file contains FEATURE and INCREMENT lines with the same product name but different maintenance dates if multiple floating network licenses for different software versions are assigned to a single computer or triple-redundant server group. FEATURE lines have the latest maintenance date; INCREMENT lines are for the same product with older maintenance dates. The use of FEATURE and INCREMENT lines allows older and newer Altera licenses to be hosted on a single license server. Why does my license file contain FEATURE and INCREMENT lines with the same product name? You should use the file that was generated most recently (highest maintenance date on the FEATURE lines), or if the SSLC gave you separate files for different entitlements, if you have an Altera FPGA software license and Questa Altera FPGA Edition software license and also have other Siemens EDA QuestaSim software licenses, you can either merge all of them into a single file or put all Siemens EDA QuestaSim software licenses in a single file. Altera FPGA Software Installation and Licensing

Quick sanity check after getting the server running:

Note: To continue using AI Responder, please start your next inquiry with ai_responder

Disclaimer (Beta): The AI Responder is currently provided as a beta feature. AI-generated responses may contain errors or omissions. Please verify technical guidance with official Altera documentation before implementation.

Thank you very much.