Other programs use LSFORCEHOST, like Aspen. This variable might hold multiple values, separated by a semicolon. In my experince, Aspen won't work unless it comes first in the list. (2008-03-20 thartman) An issue has surfaced when this method of licensing is used on the same machine running Aspen Engineering. The environment variable appears to expose a problem in Aspen Icarus Process Evaluator (or the Sentinel LM library code), causing it to fail to acquire a license when you attempt to evaluate a project. If Aspen is installed ( unlikely), the current solution is to remove the global environment variable and replace the SAP 2000 start menu icon with a batch file mechanism that sets LSFORCEHOST and calls the SAP 2000 executable.
Database free vector icons in SVG, PSD, PNG, EPS format or as ICON FONT. Thousands of free icons on the largest database of free vector icons! Download over 6,363 icons of database in SVG, PSD, PNG, EPS format or as webfonts.
See and for more details. When you run the network license utility, it will search for license servers. It won't find any. You'll have to click Server List and type the name of the license server for it to find the correct license server. It will show you a list of available licenses. Choose any available license not listed here. The license server is specified in the shortcut used to start the program.
A command-line argument does it. It's best not to specify the server, letting users choose an available one when they start the program. HKEYLOCALMACHINE System CurrentControlSet Control Session Manager Environment If you change one of those, the user's desktop won't be affected until it looks for environment variables, which happens primarily when the process starts. If the user needs to use the software without rebooting, you must send a Windows message to his desktop.
The simplest way to do this is to connect to the remote machine (via psexec or some othe remote shell that doesn't require taking control of the desktop) and set the environment variable with a tool like. Here's a command that will show you the global environment variables on a remote machine. Be sure to make the hostname the last argument to perl. Frequently, applications will refer to a file containing information about the license server.
The most reliable way to discover which file is used for this purpose is to search for the files containing the CNAME of the license server. They are almost always in the program directory, but occasionally may be found in another program directory for a product made by the same vendor (e.g. Inventor may look in the AutoCAD directory if both are installed). If this proves fruitless, running Filemon or Procmon ( utilities) when you start the program will tell you which files are being accessed.
License files are frequently named license.dat or license.lic. Registry Value. Search the registry for the license server you know it's using (i.e. From the DNS cache). I suggest searching in this order (to limit the search space and minimize search time):.
HKEYLOCALMACHINE SOFTWARE. HKEYLOCALMACHINE SOFTWARE. HKEYCURRENTUSER SOFTWARE Altering registry settings will almost always require restarting any programs that use them. Infrequently, logging off or restarting the computer may be necessary for the change to take effect (e.g. Some portion of the product runs as a Windows service on the machine). Environment Variable These are some commonly-used environment variables for licensing:.
LSFORCEHOST. LMLICENSEFILE. LMLICENSESERVER. License Configuration Utility. If the product has one, it's usually accessible in the same group as the program in the Start Menu.
![Database Database](http://www.crct.polymtl.ca/fact/facthelp/Images_FS71New/Browser_All_PDs.png)
Ensure that your modification worked. If you make a change that you think worked, test it by undoing what you did and verifying that the application uses the old license server CNAME. When you are confident that you've got a fix, please. I will update this documentation. Please note: All documentation becomes dated, and this document is no exception. Desktop Engineering Tools and Documentation are constantly evolving to meet customer needs, so some actual dialogs and/or tool descriptions may differ from those in this document.
Please refer to to obtain the latest documentation available. If you experience problems with the contents of these web pages, please visit the and submit a ticket with information relevant to the problem.