It may be useful to override failures which occur during the previously described procedures for LMHOST.INI and LSHOST files. In general, the LSFORCEHOST system environment variable is unnecessary. 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. The LSHOST file procedure is the same as that for the LMHOST.INI file except for the difference in file name. This may require the addition of the named server. Run WLMAdmin and make sure that you can see the license on the server from the client machine.Adding a copy of LMHOST.INI and calling it LSHOST (no extension) to the same folder sometimes helps.Ensure there are no LSFORCEHOST or LSHOST system environment variables that are interfering.Ensure the shortcut does not include the /L command line parameter that is pointing to another level.Ensure there is not a LEVEL.TXT file, in the same folder, that is pointing to a different license level.If the shortcut is pointing to one location, and the LMHOST.INI another, problems will occur. Ensure that you are running the correct EXE.This file will then speed the time it takes the software to locate the network license. If more than one machine serves licensing, enter each name or IP address on a separate line of text. This will be the software installation folder (i.e C: > Program Files….\Computers and Structures > ) in the local PC.
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.
0 kommentar(er)
