Licensing

On this page

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

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. [2002@LICSERVER](mailto:2002@LICSERVER))

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

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, see How do I install the DNV Software License Manager? for details.

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 How do I create/edit environment variables? if you are unfamiliar with environment variables.

Back to top

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 https://sesam.dnv.com/download/windows64/DongleDriver64_111501_inst_w64.zip. Alternatively, for 3rd party produts using MARINTEK vendor daemon, download and install the latest version of the https://sesam.dnv.com/download/windows64/licensemanager64_111501_inst_w64.zip. 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: https://sesam.dnv.com/download/windows64/programs.html

Back to top

How to borrow a network license on a local machine?

Sometimes, DNV Software users with a network license will want to use a local license while they are not connected to or cannot connect to their license server.

To support this, DNV Software uses the Borrowing feature of the DNV Software License Manager tool.

The attached document includes instructions for using this Borrowing option.

Please see the attached document 00003459 How to borrow a network license on a local machine.

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 GL to DNV 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 fix problems with dongle licenses

Using a FLEXLM license dongle requires installation of a driver, either by downloading, unzipping and installing:

https://sesam.dnv.com/download/windows64/DongleDriver64_111700_inst_w64.zip

(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:

https://sesam.dnv.com/download/windows64/LicenseManager_111700_inst_w64.zip

(only x64)

Newer versions may be available in: Sesam Downloads

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:

http://localhost:1947/int/devices.html

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. 2002@this_host.

Relevant system environment variables:

DNVSLM_LICENSE_FILE = C:\Flexlm

MARINTEK_LICENSE_FILE = 2002@this_host

SIMA_LICENSE_FILE = 2002@this_host

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

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 00003451 Sesam and Nauticus Network License Installation.

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 networklicense 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

I have installed the HASP dongle drivers, but the dongle is still not recognised

There are occasions where a dongle is attached to a PC, the HASP dongle drivers are installed, you have a valid license file, but the dongle FLEXID does not show up in the System Settings tab of the FLEXLM License Manager tool. You will also receive a license error message when you try to use any of the programs included in the license file.

To get around this issue, please uninstall the HASP drivers by going to Control Panel -> Programs and Features.

After you have uninstalled the HASP drivers, remove the dongle from your PC, wait a few seconds and then re-attach it again. 

Windows should now indicate that it has found new hardware and will try to find and install drivers for it. After Windows has confirmed that the drivers have been successfully installed, open the System Settings tab of the FLEXLM License Manager tool again. The dongle's FLEXID should now show up in the FLEXID field.

Start any of the programs that are included in the dongle license file to verify it is now working.

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

New license servers for those terminated for DNVGL users from January 2019

Many of the old Sesam/Nauticus  license servers for DNVGL users have been terminated from January 2019.

The new servers are listed in the table below.

For further details please contact 8989 (8989@dnv.com )

**Old server   County located  New Server   Users                 Usage**
OSL1151      Norway          OSL3002      OSLO                  Sesam/Nauticus
OSL1112      Norway          OSL3001      OSLO/Global           CPN - Sesam/Nauticus  SPP_Patran
OSL2314      Norway          OSL3002      OSLO                  SPP_Patran
OSL1657      Norway          OSL3003      Nederland             CPN – 6 licenses UK – 1 -license
OSL1678      Norway          OSL3003      Nederland             USFOS for HAMBURG Sesam/Nauticus SPP_Patran
OSL1876      Norway          OSL3004      UK                    Dubai - UsFos,
SHA1112      China           SHA1170      China                 Sesam/Nauticus  SPP_Patran
HOU1112      USA             HOU1170      America               Sesam/Nauticus  SPP_Patran
HOU1101      USA             HOU1173      America               Sesam/Nauticus  SPP_Patran
HOU1118      USA             HOU1173      America               Sesam/Nauticus  SPP_Patran
SNG1112      Singapore       SNG1170      SE Asia & Australia   Sesam/Nauticus  SPP_Patran

You need to edit the environment variable DNVSLM_LICENSE_FILE.

Go to Control Panel / System / Advanced System Settings / Environment variables - System variables

In the strings “2002@ change the reference to , e.g. from “2002@OSL1151” to “2002@OSL3002”.

Separate multiple entries with semicolon (;), e.g. 2002@OSL3002;2002@SHA1170;2002@HOU1170;2002@SNG1170

You need local admin privilegesto your PC to do this.

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 Sesam Downloads

Back to top

Pipeline Tools (All Versions): 'Licence failure! Closing down' error when opening spreadsheet

For the Stablelines and Fatfree spreadsheets, please note that if you are trying to open them with Microsoft Excel 2010 64 bit, you may receive the error message: 'Licence failure! Closing down'

This error occurs, because these spreadsheets only support Microsoft Excel 2003, 2007 or 32 bits version of 2010.

Back to top

Sesam and Nauticus License Troubleshooting

This web page on the Sesam portal provides users self-help and guidance on troubleshooting common license problems, as well as important information about license types, installation, environment variables, firewall, borrowing and remote access.

Network LicenseDongle LicenseStandalone License

Back to top

TCP_NODELAY NOT enabled

If the error or warning message "TCP_NODELAY NOT enabled" occurs in the license log file, this is not critical. The explanation is given below:

When a FLEXnet licensing session is established, TCP/IP sends data between the server and client by using packets. By default, the TCP/IP processing kernel delays small packet transmissions to gain an efficiency advantage. The advantage occurs by using a buffer to coalesce many small packets before sending them across the network. The delays can result in artificially high latency times for the small packets that are related to most FLEXnet licensing operations.

Set the TCP_NODELAY system setting (as a FLEXnet license server environment variable) to overcome the delay behavior and to reduce the licensing wait period. Usin g this setting causes data packets to be sent through the network more frequently. As a result, there is less of a delay in the licensing process due to TCP/IP operations. However, network traffic can increase as a result of smaller and more frequent licensing-related packet transmissions.

Back to top

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