Licensing, Installation and Environment

How to correct license.lic file for Sesam Patran-Pre

The license.lic file for Sesam Patran-Pre received from the Automated License Responder needs an update before it can be used. Open the file in a text editor that doesn't change the formatting, for example Notepad, then apply the following two changes

  1. On the SERVER line edit the port number from 27500 to 2002 (Sesam default)
  2. Replace the line DAEMON MSC /path_to_msc_daemon with VENDOR MSC
  3. Save the file

Back to top

Can't start Xtract 6.0-01 due to missing or not supported license version

Cant start Xtract 6.0-01, with either of the following error messages:

ERROR: While checking out a license. License server system does not support this version of this feature.

or

Command disabled due to missing license feature even with Flexlm / License Manager version v11.17 installed.

The issue is due to a wrong version date in Xtract 6.0-01 and may occur if the license expires before 2021.1231. An updated version will be released shortly.

Back to top

How to check firewall communication between Flexlm license server and client machine

If the Flexlm/FlexNet license service is running properly on the license server machine, and the client machine has the system environment variable correctly set, but the client still can't check out a license or connect to the license server, this is often due to firewall restrictions. The firewall can restrict communication for certain port numbers and applications (executables). The license service requires two-ways communication between client and server.

Testing communication: One way to check that the client can reach the server is to telnet using a specified port number. Telnet is typically installed, but not enabled on Win7 and Win10 machines. To enable telnet go to Programs and Features -> Turn Windows features on or off -> Check Telnet Client (and Server if available). See also attached screendump.

From a cmd window one can try to telnet the server using relevant address name and specifying the port, for example: telnet servername 2002 telnet ip.ip.ip.ip 2002 (The port number 2002 used here is the default for Sesam and Nauticus licenses.) If an error message shows, the port is blocked. If a blank page saying Telnet at the top shows instead, that port is open. Define firewall exception rules Firewall exception rules have to cover the port numbers used by

both lmgrd and any vendor daemon like dnvslm, msc and marintek (typically 2002 and one or more varying port numbers) OR the lmgrd.exe and dnvslm.exe vendor daemon (possibly also msc.exe and marintek.exe) executables. It is common to open up for the executables instead of the port numbers. To find the port numbers used by the vendor daemons, search the dnvs.log file looking for lines like: 17:34:16 (lmgrd) dnvslm using TCP-port 49161 The MSC and MARINTEK vendor daemons port numbers are reported in a similar way.

Common problems: The path to the installation folder changed name from DNV to DNV GL going from FlexNet v11.17 to v11.18. The firewall exception rule must thus also be updated. The vendor daemons may use a different port number after restart. If this creates problem for the firewall exception rules, one can assign a static port number in the license file itself to the vendor daemons, ie:

SERVER myservername hostid 2002 VENDOR dnvslm port =yyyy

where yyyy is the port number used with the exception rule.

Back to top

How to set environment variable to connect to network license server

The following system environment variable has to be set on end user and client machines to have Nauticus Hull and Sesam programs connect to a network license server:

DNVSLM_LICENSE_FILE = 2002@Servername; C:Flexlm

How to edit the system environment variable:

Go to Control Panel -> System -> Advanced System Settings -> Environment variables -> System variables -> New or Edit

Replace Servername with the relevant network name of the license server. Sometimes the full domain name or IP adress may be required.

You need local admin privileges to edit the system environment variables.

Several licenses can be listed and will then be searched in the listed order. In this example two different license servers are tried before looking for a local license file:

DNVSLM_LICENSE_FILE = 2002@Servername1;

2002@Servername2; C:Flexlm

Note that 3rd party programs from Sintef Ocean (using the MARINTEK vendor daemon), Sima and Patran-Pre (using the MSC vendor daemon) require the following separate system environment variables:

MARINTEK_LICENSE_FILE = 2002@Servername

Sima_LICENSE_FILE = 2002@Servername

MSC_LICENSE_FILE = 2002Servername

Back to top

How to solve a Windows installer error during DNV Software programs installation

When installing one of the DNV Software programs, you get the following error message:

You must install a Windows Service Pack which contains a newer version of the Windows Installer Service.

This error is commonly caused by either missing redistributables or not having the latest version of the Windows Installer installed. The below link takes you to the latest version of the Windows Installer from Microsoft's website.

Download and install the version appropriate for your operating system specifying either a 32bit or 64bit version. Then restart the Sesam installation.

Back to top

License file error when upgrading to License Manager Flexlm v11.17

Can't start license service after upgrading the License Manager to Flexlm v11.17 for Sesam and Nauticus Hull.

Get the following error:

Unsupported license file encoding. Please ensure that the file is either ASCII or UTF-8 encoded and try again

This is due to a bug in lmgrd v11.17, whereby some license files with certain characters will not work. We've seen this issue for a license file with the Norwegian character ø, and it may occur for other such characters too. The issue will nevertheless not occur as long as lmgrd is started from license manager.

The workaround is to open the license file in a text editor and save it as UTF-8 and not ANSI, then restart the license service.

Back to top

Licensing: Can I use more than one Flex-ID dongle on a single machine?

Multiple USB dongles can be plugged into a USB port with the following limitation:

FlexID 9 is limited to one dongle on Windows x64 for programs built with the old Sesam licensing component. This applies to all program version released before 2016 and some program version released later.

Back to top

Licensing: How do I create/edit license environment variables

To create or edit a license environment variable, follow the below steps:

Right-click on My Computer, and choose "Properties" from the menu. (or go to Control Panel and select System)

Click "Advanced system settings". (or click on the tab "Advanced")

Click the button "Environment Variables".

If you are the only user for this computer, update "User variables", otherwise go to System variables (or "Environment Variables"). Click the button "New".

If you are modifying an existing environment variable or the environment variable already exists, select it and click "Edit".

Fill in the details as follows:

          Variable name : DNVSLM_LICENSE_FILE

          Variable value : port number@your server name (e.g.)

          You can add several values by separating them with a semi colon ;

Note: DNV uses the following environment variables:

Nauticus and Sesam: DNVSLM_LICENSE_FILE

SIMO/RIFLEX: MARINTEK_LICENSE_FILE

Patran-Pre: MSC_LICENSE_FILE

Back to top

Licensing: How do I define a "License Path" on my (client) computer

The license path tells the DNV Software applications where to look for licenses. Licenses are typically located on a license server in your network (network license) and/or on a license file that is stored on your computer (local license). If the local license is tied to a dongle, this dongle needs to be mounted to your computer.

The DNV Software License Manager creates the license path during installation.

You may also define/change the license path manually by defining/changing environment variable(s):

Nauticus and Sesam: DNVSLM_LICENSE_FILE=c:\flexlm;2002@optional-network-license-server

SIMO/RIFLEX: MARINTEK_LICENSE_FILE=c:\flexlm;2002@localhost;2002@optional-network-license-server

Patran-Pre: MSC_LICENSE_FILE=c:\flexlm;2002@localhost;2002@optional-network-license-server

See "" if you are unfamiliar with environment variables.

Back to top

Licensing: How do I use a dongle on a different computer

To use a dongle on a different computer, please follow these steps:

  1. Copy the license file from C:\Flexlm to the new computer and paste it in the C:\Flexlm folder. Please create this folder if it does not exist.
  2. Download and install the latest version of the license dongle driver. Alternatively, for 3rd party produts using MARINTEK vendor daemon, download and install the latest version of the. Remember to check the 'USB dongle driver for FLEXID 9 (Aladdin Knowledge Systems)' option to install the dongle drivers.
  3. Attach the dongle to the new PC.
  4. Install the applications you would like to run.
  5. Start your application.

Please note that newer versions may be available in:

Back to top

Licensing: How to fix problems with dongle licenses

Using a FLEXLM license dongle requires installation of a driver, either by downloading, unzipping and installing: (HASP HL Pro drivers for both x86 and x64) OR by checking the option 'USB dongle driver for FLEXID 9' during installation of the license manager: (only x64)

Newer versions may be available in:

If you get error message about invalid host the dongle has not been recognized. Check that the dongle lamp is lit. Installing the dongle driver usually fixes the problem.

Driver should be installed before mounting the dongle the first time (to avoid auto-installation of driver found on Windows update). You may try the dongle in different a USB port, and also remove other dongles.

If the dongle still doesn't work, use the following link to check the dongle is recognized:

or LMTOOLS (part of the licenses manager installation):

Start C:\Program Files\DNVGL\Flexlm\bin\lmtools.exe Select the "System Settings" tab. The FLEXID window should now display the dongle number

Note that licenses for the third party products using the MARINTEK vendor daemon also require a running license service (install license manager). Check that the license manager is installed and that the service is running (see C:\Flexlm\dnvs.log fil). The dongle must be mounted before restarting service or rebooting. Use this_host for server name, e.g. .

Relevant system environment variables:

DNVSLM_LICENSE_FILE = C:\Flexlm

MARINTEK_LICENSE_FILE = 2002@this_host

Sima_LICENSE_FILE =

Whilst most new program versions (possibly since 2016) has the new common licensing component that supports multiple dongles, programs built with the old licening (auxlib) component only supports one dongle mounted at the time.

Contact software support if you require further help.

Back to top

Licensing: How to install or update a network license on a license server

The attached document is a step by step guide on how to install and update a network license including firewall settings. Please see the attached document.

Back to top

Licensing: Why do I need to install DNV Software license Manager on my computer when I have a local license?

You need to install the DNV Software License Manager if:

  • the license is tied to a dongle (to install the dongle driver)
  • you have a local license of SIMO/Riflex or PatranPre

Nauticus and Sesam license licenses do not require an installation of the DNV Software License Manager.

However, we recommend that you always install DNV Software License Manager. The reason for this is that the installation defines the license path and installs a few license utilities.

If you choose not to install DNV Software license Manager, you need to define the licensepath manually, see xxx for details.

Back to top

Nauticus Hull: Jan 2018 requires minimum DNV Software License Manager 11.14-01

If you get the following license error message when trying to run next generation Nauticus Hull (v20.3 or later) or some component in old Nauticus Hull (i.e. Rule Calculator):

No valid license found. Closing down. Application name Nauticus Hull ERROR: While checking out a license.

Then note that next generation Nauticus Hull (v20) requires DNV Software License Manager 11.14-01 or later on the license server machine for network (floating) licenses.

Client machines (for network licenses) and machines with standalone unlimited licenses do not require such installation, but only setting the system environment variable DNVSLM_LICENSE_FILE correctly.

Minimum version of both lmgrd.exe and dnvslm.exe is v11.14.1.1. The license manager is supported only on 64 bit systems (since 2017).

The license manager can be installed either from the Nauticus Hull Rulecheck or FEA Package, or downloaded from the Sesam Knowledge Centre.

Back to top

No license found for Prefem (for internal DNV users)

Starting 2019, Prefem is NOT added to the Network license on the DNV license servers, such as OSL3001, OSL3002, SHA1170, HOU1170, HOU1173 AND SNG1112.

Prefem is a discontinued product that was last compiled 15 years ago. (Similarly, Prewad was also discontinued many years ago.) GeniE (or Patran-Pre) has replaced modelling of plate type structures. Prefem has been removed from the self-service for DNV O&G and Maritime, from 2019.

However, we can provide standalone licenses/local network license if you reply to the following: Prefem used to be part of the Sesam suite of programs, but was discontinued many years ago. The last version was compiled in 2003. Other products are also discontinued like Prewad. We can provide you with a license, but please confirm that you acknowledge, for the discontinued products, that we:

  • do not provide support
  • do not take responsibility for the results/compatibility on newer operating systems
  • that we potentially in the future cannot provide licenses given changes in e.g. license manager/license generator/license components compatibility with updates to operating system

Back to top

No valid license found or ERROR: While checking out license. Version of vendor daemon is too old.

If you get the following license error message when trying to run new versions of Sesam or Nauticus Hull:

No valid license found or Unable to check out any license

Application name : xxx

ERROR: While checking out a license.

Version of vendor daemon is too old.

then note that new versions of Sesam and Nauticus Hull are created with new versions of FlexNet licensing, requiring license manager or dongle driver on the same version level.

The fix is to upgrade the license manager (for server licenses) or dongle driver (for dongle licenses) to the latest version.

The FlexLM version listed further down in the error message shows the minimum required level of the license manager, e.g.: FlexLM version: 11.17.0.0

The license manager is supported only on 64 bit systems (since 2017). The latest version of the license manager is always included in the Sesam and Nauticus Hull packages, and can also be directly downloaded from the DNV website.

Back to top

Patran-Pre: License error about missing MSC.Patran license after installing Patran-Pre v2010r2 and later

When starting Patran-Pre 2010r2 or later the first time after installing it, an Error reported from application Security is displayed and no license is found. If the error message is about a missing MSC.Patran license, the last step of the installation is missing.

Without this last step, Patran-Pre tries to obtain native MSC.Patran licenses instead of Patran-Pre licenses. This can be fixed by doing either of these steps:

Add -iam Sesam to the PatranPre 2010 shortcut. e.g. C:\MSC.Software\Patran_x64\20102\bin\patran.exe -stdout -iam Sesam

Or, you may create the environment variable P3_IAM and give it the value Sesam (P3_IAM=Sesam).

More details can be found in the Patran-Pre release notes.

Back to top

Usfos: User being prompted insufficient license as below

Error message:

User being prompted insufficient license as below

Question:

Does insufficient license error means that the license is not valid or program cant fetch the license file?

Answer:

This is not a license error. Instead, this is installation error where the user installed Usfos version from and not using DNV version for Usfos. Usfos license file only works with DNV installation files. Solution to this:

  • Uninstall the Usfos version
  • Download Usfos installation file
  • Unzip the file and use setup.exe to install the program
  • Launch Usfos

Back to top

Usfos lacks license to run a command

There are features in Usfos which are locked from usage as they are mainly used for development work .

Unfortunately some of these features are described in the user Manual without any reference to the fact that they are locked from the user.

This is not locked by DNV, nor are there aditional modules that can be bought from DNV to give access to these features.

The known commands without user access are:

General - CompSpri and TensSpri options
Subshell
Windhist
APPI_soil - cyclic option

Notice that from Usfos 8.8 it is possible to use the Subshell command with the 'dumpfem' option. See the attached release notes for more details.

Back to top