This guide provides information to problems that may occur during and after the installation of Autodesk Network License Manager.
All Autodesk Moldflow 2011 products* now use a new licensing system, Autodesk License Manager (Moldflow), which is based on Autodesk’s FLEXlm integration called Autodesk Network License Manager.
With the new licensing system, all licenses are floating and customers will need new license keys which can be obtained from the Autodesk website.
*An exception to this is Autodesk Moldflow Communicator, which is a free product and does not require a license key.
Autodesk Network License Manager supports all Autodesk Moldflow 2011 release products.
Legacy Moldflow products (MPI 6.1, MPA 8.0, or earlier versions) are not supported. Legacy products will continue to be licensed using the MPS licensing system and although it will stay operational for existing customers, new development on MPS is not expected in the future.
The Autodesk Network License Manager cannot be installed on Linux platforms; however, Autodesk Moldflow Insight application software installed on Linux platforms can access licenses which are installed on Windows platforms.
To successfully install
Autodesk Network License Manager, you must
reboot the server after the installation and setup of license keys.
When saving the license key, ensure you save the file using a text-only editor such as Notepad. Using other word processing applications such as Word may add a ‘Carriage Return’ to the file, which FLEXlm cannot read.
When adding a new license, you must restart the license server. These steps should be performed using an administrator-level user account.
When registering licenses, the server machine may show multiple Ethernet addresses in the LMTOOLS System Settings window. When this happens, the command line utility ipconfig /all should be used to identify the main network connection. The Physical Address for this connection can then be mapped back to the Ethernet Address in the LMTOOLS System Settings window, and the correct address can be chosen.
To install Autodesk Network License Manager, you must have administrator privileges. Ensure you are logged in as the Administrator.
On a Vista machines, you need to set UAC (User Account Control) to Run as Administrator so that you can do any of the following:
If you get a CD-StartUp Error, it means that you do not have administrator rights to install the software. Log in as Administrator, or run the installation as Administrator and then try again.
On machines where the user has
limited access permissions, it is
necessary to run the license configuration tools as an Administrator.
This is achieved by right-clicking the tools icon and selecting Run as
Administrator from the list of options. Tools which require this level
of privilege escalation are LMTOOLS and Network License Server Settings.
If these tools are run without administrator-level privileges, user modifications may not be saved correctly.
The computer fails to recognise the installed license after rebooting the computer.
There are two main causes for this:
By default, the Autodesk License Manager (Moldflow) Daemon service does not have any dependent services. It actually depends on the FLEXlm service. Since the name of this service is controlled by the user, this dependency cannot be created automatically during installation or programmatically at runtime. If you find that the licenses are not recognised after rebooting your computer, you can manually create the dependency.
1. Identify the FLEXlm service name using LMTOOLS.
a. Click Start > Programs > Autodesk > Network License Manager > LMTOOLS.
b. Click the Config Services tab.
c. Note the name of the service, where the Path to lmgrd.exe file is:
- x86 operating system C:\Program Files\Autodesk Network License Manager\lmgrd.exe
- x64 operating system C:\Program Files (x86)\Autodesk Network License Manager\lmgrd.exe
2. Edit the dependant services for Autodesk License Manager (Moldflow) Daemon.
Note: You must be logged in as Administrator to make changes.3. Check the dependencies.
a. Click Start > Run and then type Regedit.
b. Navigate to the following directory: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Autodesk License Manager (Moldflow) Daemon.
c. Right-click the mouse and select New > Multi String Value. A new registry value is created.
d. Rename the new file to DependOnService and then double-click the value. The Edit Multi-String dialog appears.
e. In the Value data section, type the name of the FLEXlm service as noted from the LMTOOLS.
a. Click Start > Run > Services.
b. Double click on the Autodesk License Manager (Moldflow) Daemon.
c. Click the Dependencies tab.
d. Expand the FLEXlm service name in the system components section to display the dependencies.
ADLMHEAT has stalled
After installation, the ADLMHEAT process stalls because FLEXlm is not ready.
In Vista, change the ampsd service Startup type to Automatic (Delayed Start).
You must wait at least 35 seconds before requesting a license. It takes time for FLEXlm to respond to queries (usually 1-2 seconds per query), so the more licenses you have, the longer you need to wait.
When either the Autodesk FlexLm server or the Autodesk License Manager (Moldflow) service cannot see the installed Autodesk Moldflow licenses, please check if the registry entries for the Autodesk FlexLm service are set up correctly.
CAUTION: Editing the registry can cause severe system-wide problems. Always backup your registry before making any changes. Visit Microsoft Help and Support for help backing up your registry.
Ensure the following keys exist on the server, and their values are set correctly. Be sure to include the '@' symbol where necessary.
|FLEXlm License Manager||REG_SZ||@<server name>|
|Default||REG_SZ||[Value not set]|
|License||REG_SZ||<path to license file>\<license file name>|
|Lmgrd||REG_SZ||<path to lmgrd>\lmgrd.exe|
|LMGRD_LOG_FILE||REG_SZ||<path to log file>\<log file name>|
If the server status is OK, you should be able to see the server in LMTOOLS.
Check that both the server and the client can ping each other by using both the hostname and IP address (tests DNS and reverse DNS).
When using a firewall, port 6014 TCP must be open on the server to allow clients to reserve licenses. If the port is not open, you will get a License check timed out error when attempting to open the GUI.
Note: Port 6014 is hardcoded and cannot be changed. Consult the documentation provided with your firewall software for instructions on how to open these ports.
When using a local license server, it is best to configure the license server as either the name localhost or as the IP address 127.0.0.1. This ensures that network configuration changes will not affect licensing.
After restarting the license server, it may take up to a minute for the services to re-initialize fully. During this time, attempts to check out licenses from the server may be rejected.
For detailed help about your Moldflow Product Security products, please see the built in on-line help systems. This troubleshooting guide contains only a short list of commonly asked questions about MPS.
If you wish to use Enterprise licensing, you must install an MPS 2.3 license server (or later) on your network. Please be careful when installing Moldflow client software other than MPI 6.1 as this may install an older version of the MPS license server.
Many UNIX systems require a CD-ROM to be explicitly mounted before it can be accessed. Insert the CD into the CD-ROM drive and then enter the appropriate mount command for your system from the following table.
|Operating System||Example command|
|HP-UX||mount -o ro,cdcase /dev/dsk/c1t2d0 /cdrom|
|IRIX||mount -t cdfs -r /dev/rdsk/dks0d4vol /cdrom|
|Linux (Redhat Enterprise)||mount /mnt/cdrom|
|Linux (SUSE 9.2)||mount /dev/cdrom|
|Solaris 2.9 and 10||(CD-ROM is auto-mounted, usually at /cdrom/cdrom0 )|
The device names and mount points may be different on your system. If necessary, consult your system administrator for the actual device names and mount points used at your site.
When a Moldflow client product such as Moldflow Plastics Insight (MPI) or Moldflow Plastics Advisers (MPA) attempts to perform an operation, it first checks whether a required license (node-locked or floating) is available on the license server. If a license is available, the client product reserves the license in a first come, first served order. The license is returned when the operation is complete.
In an Enterprise licensing system, a communal pool of licenses exists on a single license server. These licenses are referred to as Tasks. A user must reserve a task from the communal pool before he or she undertakes an operation in a Moldflow client product. Only the tasks that the user has reserved for his or her personal use are available for that user.
If the user does not have enough tasks to perform an operation, he or she must reserve more tasks. Task reservation is performed using the Enterprise Dashboard. A list of the tasks required to perform particular operations is included in the online help system of the Enterprise Dashboard. See the "What Task do I need?" topic.
If your Moldflow product crashes or you experience a hardware failure while you have a task reserved and in the Active state, the task will be "orphaned" and will not automatically be returned to the communal task pool. You will need to recover any orphaned tasks manually. The orphaned task will be displayed as Active, but in this instance you may return it to the communal task pool.
If, as a result of a hardware failure, you can no longer log into your machine, you may access your tasks from another machine:
This task is currently active. You may only return this task if the analysis and study associated with it are closed. Are you sure you want to continue?
If you have installed license keys on your server but you can not see the server in the MPS Servers tab list, you may need to modify the settings on your firewall. Moldflow Product Security requires UDP port 1576 to be open in addition to TCP port 1576. Consult the documentation provided with your firewall software for instructions on how to open these ports.
You should now be able to see your sever in the MPS Servers tab.
|If you cannot find a file with extension ".key " when you want to install the key files.||
You have either not applied for a license keyfile from Moldflow, or you have not extracted the license keyfile from the email sent to you by Moldflow. If you have not applied for a license keyfile from Moldflow, you should do so by following the steps in the Obtain License Keys wizard (). You should run this wizard on the computer that is to function as the server. When you receive an email from Moldflow regarding keyfiles, you should save the keyfile to your local machine.
|You encounter the following message: "ERROR: Unable to install key on MPS server <IP address>. A key for this module already installed on this server."||
This message indicates that the same license key has already been installed on the Moldflow Product Security server that you specified. You cannot re-install the same license key without first removing the old version.
|You encounter the following message: "ERROR: Unable to install key on MPS server <IP address>. Key is not valid for this server."||
You have attempted to install the license key on a different server to that specified in the license keyfile. The license keyfile can only be installed on the server that is named in the license keyfile. If you are not sure which server this is, click the License Key Administration button. When the display updates, you will find the server name at the far right end of each keyfile line.
After completing the Moldflow Electronic Registration wizard, you will receive a keyfile from Moldflow. If you have renewed or upgraded your Moldflow licenses, you will also receive a new keyfile. This keyfile needs to be installed on a license server.
UTC (Coordinated Universal Time) of the MPS server and all of its client machines must be within 30 minutes of each other. When clocks need to be adjusted for daylight savings, you should not manually adjust the local clock on a machine. Instead you should change the local time zone.
For Moldflow Product Security to operate correctly on Windows machines, you must ensure that the Automatically adjust clock for daylight savings change check-box in the Time Zone tab ( ) is checked on both the server and all client machines.
After completing the registration wizard, you will receive a keyfile from Moldflow. This file needs to be installed on the license server. There are two methods to install a license keyfile on a UNIX/Linux server. The first is to use the Moldflow Main Menu on the UNIX/Linux license server (instructions below ). The second is to install the keys using the Product Security Administrator on a remote Windows machine.
The Moldflow Main Menu appears.
The same user who starts the license server may also configure the license server (for example, turn logging on and off). Only the same user who started the license server can stop the license server, except for ‘root’ who can stop the license server regardless of which user started it.
This variable specifies the name of the license server. It can be set to "localhost" if the current machine is the license server.
With the introduction of MPI 6.1 and MPS 2.3 we have altered the way you change the license server. Previously, to change the license server, you assigned a new value to the MFPSHOST environment variable. With MPI 6.1 you must use the Moldflow Product Security Administrator to change the license server.
Since the release of MPS 2.3, the Product Security Administrator contains the functionality to allow you to change the Moldflow license server that provides your licenses.
You may change the license server () while the Enterprise Dashboard is open. The Enterprise Dashboard will update automatically to show the licenses on the new server.
If you start the Enterprise Dashabord while you are using a server that only has Commercial keys installed, the Dashboard will open but it will be entirely grayed-out. You must ensure that you are using a license server that has Enterprise keys installed for correct operation of the Dashboard.
This is called Mode switching. MPI editions from 6.1 onwards will switch between the Enterprise and Commercial editions, depending upon which type of license keys are installed on the license server you are using. If you are currently using a license server that has Enterprise license keys installed, your edition of MPI will switch to the Enterprise edition when you next run it. If you change your license server to one that has Commercial, Academic or Student keys installed, your edition of MPI will switch to the Commercial, Academic or Student edition when you next run it. .
While you are operating in Commercial mode, there is no Enterprise Dashboard functionality