Manually Starting the License Server Manager

You can start the license server using one of the following methods:

•

Windows platforms: If the conf folder has been installed in the same location as lmadmin.exe, open the installation directory in Windows Explorer and double-click the lmadmin.exe file. This mechanism does not allow you to specify non-default command-line arguments.

•

Execute the lmadmin command from the root installation directory. To see a list of available command-line arguments, execute the command:

lmadmin -help

The help display identifies the default arguments and which arguments are persistent, options that will remain in effect for later instances of lmadmin.

•

Create a shell script file (UNIX) or a batch file (Windows) that will run the lmadmin command with your desired command-line arguments and then execute that file. For a default installation on a Windows platform, specify the location of the conf folder.

Note:If either the default license server port or the HTTP port for the user interface is in use, the license server manager will not start. For instructions see License Server Manager Not Starting.

Important:In addition, ensure that the http/https ports and the licensing ports (required by lmadmin) and the vendor daemon ports are opened on the firewall, so that remote clients can checkout licenses and the HTTP clients/browsers can connect to the lmadmin web GUI.

License Server Manager Not Starting

Incorrect Port

The license server manager will not start if either of the following ports are in use:

•

Default license server port (no ports in range 27000 to 27009 available)

•

Default HTTP port for the license server manager user interface (port 8090)

To check for this error and correct it:

Run lmadmin from the command line using the -foreground argument:

lmadmin -configDir <conf_path> -foreground

Examine the output at the command prompt. The following shows typical output when there is a clash on the HTTP port:

•

Non-Windows systems:

<OS 10048>Only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 0.0.0.0:8090
no listening sockets available, shutting down
Unable to open logs

•

Windows systems:

<OS 10048>Only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 0.0.0.0:8090

Note that on Windows, the error message is displayed despite the fact that it is possible to run two instances of lmadmin on the same port (using an IPv4 and an IPv6 socket). In this case, no remedial action is required.

However, if a third instance of lmadmin is started, the following error message is displayed:

In this case, proceed with Step 3.

Reconfigure any port where there is a clash:

•

Use the -licPort argument for the license server port.

•

Use the -webPort argument for the HTTP port.

For example, the following command reconfigures the HTTP port to 8091:

lmadmin -configDir <conf_path> -webPort 8091

When you have reconfigured the HTTP port, you access the license server management interface using the new port number. For example, lmadmin -configDir <conf_path> -webPort 8091 connects to the URL
http://<server>:8091.

Insufficient Privileges (Windows only)

If the lmadmin service does not start due to an “Access denied” error, ensure that it has sufficient privileges.

The lmadmin folders that are updated during run time should be installed under ProgramData, to allow the service, which has Local Service privileges, to modify these files.