Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When

...

CSI

...

Software uses

...

a network

...

license

...

, it broadcasts

...

a

...

signal

...

to

...

the

...

network in effort to locate the license server and then retrieve the network license file. You may use the LMHOST.INI file, the LSHOST (no extension) file, or the LSFORCEHOST system environment variable to either help the software locate the license server more quickly, or to resolve problems when the broadcast fails to locate the license server. These options are described as follows:

 On this page:

Table of Contents

LMHOST.INI file

Create a text file named LMHOST.INI which lists either the network name, or the IP address of the machine running the License Manager, then save this file to the folder in which the software is installed. This will be the software installation folder (i.e C: > Program Files….\Computers and Structures > [PRODUCT NAME]) in the local PC. If more than one machine serves licensing, enter each name or IP address on a separate line of text. This file will then speed the time it takes the software to locate the network license.

Resolution of common problems

  • Ensure that you are running the correct EXE. If the shortcut is pointing to one location, and the LMHOST.INI another, problems will occur.
  • Ensure there is not a LEVEL.TXT file, in the same folder, that is pointing to a different license level.
  • Ensure the shortcut does not include the /L command line parameter that is pointing to another level.
  • Ensure there are no LSFORCEHOST or LSHOST system environment variables that are interfering.
  • Adding a copy of LMHOST.INI and calling it LSHOST (no extension) to the same folder sometimes helps.
  • Run WLMAdmin and make sure that you can see the license on the server from the client machine. This may require the addition of the named server.

LSHOST file

The LSHOST file procedure is the same as that for the LMHOST.INI file except for the difference in file name. Users should use the LMHOST.INI file instead of this. If more than one machine serves licensing, enter each name or IP address on a separate line of text.

LSFORCEHOST system environment variable

In general, the LSFORCEHOST system environment variable is unnecessary. It may be useful to override failures which occur during the previously described procedures for LMHOST.INI and LSHOST files.

When using the LSFORCEHOST system environment variable, set its value either to the IP address, or to the name of the license manager server. The procedure for creating the LSFORCEHOST will vary according to the operating system. Please refer to the LSFORCEHOST system environment variable page for details.

LSHOST system environment variable

As with an LSFORCEHOST system environment variable, a LSHOST system environment variable is usually unnecessary but may be useful to override failures which occur during the previously described procedures for LMHOST.INI and LSHOST files.

Unlike using LSFORCEHOST, which forces the product to look for license on a single server only, LSHOST allows the product to look for a license on multiple servers. Please refer to the LSHOST system environment variable page for details on the specific notation required.

See also

External links

Show if
groupeditors

Relevant emails:

  • Email LSFORCEHOST, lmhost.ini, lshost: Clarification of LSFORCEHOST, lmhost.ini, lshost. (bm → ok, 8/31/2012, ID 9537863)
  • Email LSFORCEHOST, lmhost.ini FOLLOW-UP 1, lshost: Clarification of LSFORCEHOST, lmhost.ini FOLLOW-UP 1, lshost. (bm → ok, 8/31/2012, ID 9537879)
  • Email LSFORCEHOST, lmhost.ini FOLLOW-UP 2, lshost: Clarification of LSFORCEHOST, lmhost.ini FOLLOW-UP 2, lshost. (fh → ok, 8/31/2012, ID 9537880)