Licence Manager

Copyright © 2019 Dassault Systèmes GEOVIA Inc.
All rights reserved. Dassault Systèmes GEOVIA Inc. publishes this documentation for the sole use of
GEOVIA product licensees.
Without written permission, you may not sell, reproduce, store in a retrieval system, or transmit
any part of this documentation. For such permission, or to obtain extra copies please contact your
local GEOVIA office, or visit www.3ds.com/GEOVIA.
This software and documentation is proprietary to Dassault Systèmes GEOVIA Inc. and, except
where expressly provided otherwise, does not form part of any contract. Changes may be made in
products or services at any time without notice.
While every precaution has been taken in the preparation of this manual, neither the authors nor
GEOVIA assumes responsibility for errors or omissions. Neither will be held liable for any damages
caused or alleged to be caused from the use of the information contained herein.
Dassault Systèmes GEOVIA Inc. offers complete 3D software tools that let you create, simulate,
publish, and manage your data.
GEOVIA, the GEOVIA logo, combinations thereof, and GEMS, Surpac, Minex, MineSched, Whittle,
PCBC, InSite, and Hub are either trademarks or registered trademarks of Dassault Systèmes or its
subsidiaries in the US and/or other countries.
Product
GEOVIA Licence Manager™ 14.9.4
Last modified: 07 October 2019
Table of Contents
Introduction 6
Licence Manager Permissions 6
Requirements 6
Workflow 8
Licence Manager Concepts 9
Licence Types 9
Licence Classes 10
Requesting a Licence Class 10
Licence Manager Folder Paths 10
User Defaults Folder 10
Licence Manager Installation Path 11
Setting Up the Licence Manager Server 12
Downloading Licence Manager Installer 12
Download the Licence Manager Installer 12
Upgrading Licence Manager 13
Upgrade Licence Manager on the Server Computer 14
Installing Licence Manager 14
Install Licence Manager 14
Starting Licence Manager 15
Adding or Updating Licences Using Self-Service Licensing 15
Adding and Updating Tokens 18
Adding or Updating Tokens Using a .udt File 18
Add or Update Tokens Using a .udt File 19
Adding or Updating Tokens Using an HTML File 20
Add or Update Tokens Using an HTML File 21
Adding or Updating Tokens Using a .licz File 22
Add or Update Tokens Using a .licz File 22
Moving a Token to a Class 24
Running Reports 25
Viewing the Log File 25
View the Log File 25
Setting up the Client to Use a Network Licence 26
Setting Up Surpac or Minex to Use the Licence Server 26
Set up the Client to use the Licence Server 26
Reacquire Your Licence 27
Licence Manager Window 31
Menu Commands 32
File Menu 32
New 33
Open 33
Save 33
Save As 33
Edit Menu 34
Properties 34
Fields on the Edit Configuration form 34
New Token 36
New Class 36
Fields on the Create/Delete Class form 37
Delete Token 37
Delete Class 37
Change Token Class 38
View Menu 38
Toolbar 38
Status Bar 39
Log 39
Service Menu 39
Install 40
Uninstall 40
Start 40
Stop 40
Reporting 40
Administration Menu 41
Request License 41
Revoke 41
Restart 42
Reload 42
Reconfigure 42
Shortcut Menu 42
Functions on Licence Classes 42
Functions on Token Numbers 43
Troubleshooting - Overview 44
Common Issues 45
Installation 45
Licence Manager Service 46
Client Licences 49
Frequently Asked Questions 52
Dongle 52
Licence Manager Service 53
Licence Information 54
Client Licences 55
Other 56
Licence Manager glossary 58
Introduction
Introduction
GEOVIA Licence Manager is a program that enables a site using GEOVIA programs to administer all its
licences from a central server computer. Licences managed by Licence Manager are not “tied” to one
specific computer. This concept is referred to as floating licences. Floating licences permit companies
to share licences among users, which is a cost effective means of purchasing GEOVIA programs.
Licence Manager has two components: the Licence Manager window and the Licence Manager
service.
Licence Manager Window
An administrator manages licences using the Licence Manager window. From the Licence Manager
window, the administrator performs the following activities:
l manage the use of various GEOVIA programs

l run reports that show the:
l various classes of licences defined in the tokens file
l usage of various classes of licences
l availability of licences
l the usage of functions within GEOVIA program
l revoke licences for specified users

l start and stop the licence server
Licence Manager Service

The administrator starts the service so that licences are available among the client computers on the
local area network (LAN). The Licence Manager service enforces the licensing conditions on a site,
such as number of simultaneous users and options enabled.
Licence Manager Permissions

To perform a task within Licence Manager, you must have the appropriate permissions.
For organizations that have many licences, GEOVIA recommends that only a few selected persons
have access to perform the administrative tasks in Licence Manager. This guideline ensures that only
the persons with permissions can change the Licence Manager server process.
To run the Licence Manager program or start the service, you must be an administrator with the
appropriate permissions.
Requirements
When you install Licence Manager, you can use the default settings in the wizard unless the
installation procedure explicitly states that you should change the settings.
To use GEOVIA network licences, you must install Licence Manager on one computer on the LAN that
is the Licence Manager server. In some situations, the network administrator (the person
responsible for network administration) might choose to have more than one licence server for
backup purposes, such as in the case of a computer malfunction or network outage on a large
network.
Note: Each computer can run only one instance of Licence Manager.
Installation Prerequisites
The person who is the licence administrator must have administrator permission on the computer
that is the Licence Manager server.
GEOVIA Licence Manager™ 14.9.4 Page 6 of 61 Complete Reference Guide

Introduction
The Licence Manager server computer must have:
l a hardware dongle for Licence Manager

Nearly all Licence Manager dongles plug into USB ports. Some older dongles plug into
parallel ports.
l a current GEOVIA dongle (or sentinel)
l one of the following operating systems (32-bit or 64-bit):
l Windows 7
l Windows Server 2008
l Windows Server 2012
l the TCP/IP networking protocol installed

If the TCP/IP network protocol is not installed, you must install it: In the Windows
Control Panel, double-click the Network icon to install TCP/IP.
l a static IP address
The computer must not have its IP address dynamically allocated using DHCP. Char-
acteristics of using dynamic IP addresses are:
l failure for a client to locate a licence server
l excessive delays in the licence server responding to and granting licence
requests
l loss of licences while using a GEOVIA program
l the dongle driver software installed

l the Licence Manager program on the licence server computer installed
l the Licence Manager server configured using the Licence Manager window
The network must have one of the following:
l a fully functional DNS server to permit the translation from host names to IP addresses
GEOVIA recommends using a DNS server rather than relying on entries in hosts files. A
DNS server is a more robust system for name resolution than the system of relying on
entries in hosts files.
l an entry in the hosts file of each computer in the network that defines the host name
and IP address for each computer in the network
All client computers running GEOVIA programs must have:
l the TCP/IP networking protocol installed

If the TCP/IP network protocol is not installed, then you must install it: In the Windows
Control Panel, double-click the Network icon to install TCP/IP.
l the GEOVIA programs (for example, GEMS, Minex, Whittle, MineSched, or Surpac)
installed

Introduction
Workflow
Note: This workflow is not intended to be complete in scope, but shows the activities needed to
achieve a result.

Licence Manager Concepts
Licence Manager Concepts

The following concepts are important for you to understand in order to use Licence Manager
effectively.
l Licence Types on page 9

l Licence Classes on page 10
l Licence Manager Folder Paths on page 10
Licence Types
To use any GEOVIA program, you must obtain a licence. The types of licence that are available are:
l A demonstration licence that does not require a dongle (or sentinel) , but has reduced
functionality.
l A single-user licence (also known as a roaming licence) that requires you to install a
GEOVIA dongle driver on your computer. For this licence type, you use a token number
that is for the specific dongle attached to the computer.
l A network licence for which you need Licence Manager installed and running on a com-
puter on the local area network (LAN). The computer running the Licence Manager
must have a dongle attached. Any other computer on that network can run GEOVIA
programs without the dongle, and have fully licensed functionality.
Note: To use a network licence, the computer running the GEOVIA program must
always have a connection to the Licence Manager server computer while the program is
in use. The Licence Manager program is a service on the Licence Manager server
computer. If the Licence Manager service fails or stops responding, the person who is
using the network licence loses their licence. That person cannot continue using the full
features of the GEOVIA program. Also, a message appears to inform the person that
the copy of the GEOVIA program does not have a licence.

Licence Manager Concepts Requesting a Licence Class
Licence Classes
For Surpac, GEMS, Minex, MineSched, or Whittle, you can set up different licence classes. A licence
class is the name for a grouping of options or modules for a program. Program users request a
particular licence class from Licence Manager when they use Surpac, Minex, MineSched, or Whittle.
By requesting a specific licence class, the users ensure that the licence they get includes the modules,
that is the commands or functions, needed to do their job.
When a tokens file is first installed in Licence Manager, all licences are assigned the default class. In
GEMS, the default class is the seat number of each licence. In Surpac, Minex, MineSched, and
Whittle, the default class is named default.
The person who administers Licence Manager can define the class names using any combination of
alphanumeric characters. If a site uses licence classes, the administrator determines the class to
which a licence token belongs.
For example, if you have three licences for Surpac, you might have three licence classes, one for each
licence. One class could include all modules and have the class name all. A second class could include
modules that relate specifically to surveying functions and have the class name survey. And the third
class could include modules that relate specifically to geology functions and have the class name
geology. A surveyor using Surpac can specifically request the licence class named survey, which is the
licence that includes all the modules needed perform their job.
Requesting a Licence Class
The procedure to request a licence class differs for each GEOVIA program:
l For Surpac or Minex to use a specific licence class, add the -class <classname> com-
mand-line option to the desktop shortcut, otherwise the default licence class is used.
Note: If you renamed all instances of the default class when you set up the classes,
you must add the -class <classname> option to use a specific licence. If you do not add
the -class <classname> option, you will not get a licence.
l For Whittle to use a specific licence class, choose File > Licence Validation and select
the licence class you want to use.
l For GEMS to use a specific licence class, choose File > Switch Seat and select the seat
you want to use.
l For MineSched to use a specific licence class, choose Scenario > Licensing... and select
the licence class you want to use.
Caution: If the tokens give you access to different modules, GEOVIA recommends that you put
only one token into a licence class. If more than one token is put in a licence class, users can never be
certain which modules they are licensed to use.
Note: If you have more than one token for a single version of a program, you must put the tokens
into separate licence classes, for Licence Manager to correctly distribute licences.
Licence Manager Folder Paths

The following information describes the location of the User Defaults folder and the path for Licence
Manager when you install it with a GEOVIA program.
User Defaults Folder
The User Defaults folder contains user settings and customized files. When you install Licence
Manager, you can change the default location of the User Defaults folder. The default location is

Licence Manager Concepts Licence Manager Installation Path
C:\Users\Public\GEOVIA\LicenceManager\share\etc for the following operating systems: Windows

7, Windows Server 2008, and Window Server 2012.
Licence Manager Installation Path
The default installation path for Licence Manager changed in version 14.7. For Licence Manager 14.7
and later, the default installation path is:
C:\Program Files (x86)\Dassault Systemes\GEOVIA LicenceManager\<version
number>\Bin\NLMAdmin.exe
For Licence Manager 14.6 and earlier, the default installation path is:
C:\Program Files (x86)\Gemcom\LicenceManager\nt_i386\bin\NLMAdmin.exe
Note: When you install GEOVIA Surpac, GEOVIA Minex, or GEOVIA Whittle, NLMAdmin.exe and
NetworkLicenceManager.exe are installed in the binary directory of the Surpac, Minex, or Whittle
program installation folder. There is no function within Surpac, Minex, or Whitle to check the
number of licences available on the network. Instead, Licence Manager is installed with these
programs by default, so you can run reports to determine the number of licences available.

Setting Up the Licence Manager Server Download the Licence Manager Installer
Setting Up the Licence Manager Server

Follow this general process for the initial setup of the Licence Manager server.
1. Install Licence Manager from the GEOVIA installation disc.

Alternatively, use the installation file that you downloaded from the GEOVIA Support web-
site (See Downloading Licence Manager Installer on page 12).
2. Stop the Licence Manager service.
3. If you have a LICZ file, add or update tokens using a .licz File
If you have a tokens file (.udt), add or update the tokens using the .udt file.
If you have an HTML file, add or update the tokens using the HTML file.
4. Start the Licence Manager service.
Note: After you have set up the server (and started the service), the licence server automatically
distributes licences on your network. For help about using a network licence on a client, see Setting
Up Surpac or Minex to Use the Licence Server on page 26 or Setting Up GEMS to Use the Licence
Server.
Downloading Licence Manager Installer

Licence Manager is available on every installation disk. Alternatively, go to the GEOVIA support
website and download the Licence Manager installer.
Note: GEOVIA recommends that you install the latest version of Licence Manager when you
upgrade your program.
Download the Licence Manager Installer
1. Type https://www.GEOVIAsupport.com into the web browser, and press Enter.
2. If you have a user name and password, enter them and click Login In.
Note: If you do not have any logon credentials, click Create an account and follow the
prompts.
3. Click Downloads.

Setting Up the Licence Manager Server Download the Licence Manager Installer
4. If you are downloading Licence Manager for the most recent release of a program, under
the program heading, click Current Version.
If you are downloading Licence Manager for a previous release of a program, under the
program heading, click Previous Versions, and then click the version you need.
5. In the list of files that appear, find a link named GEOVIA Licence Manager <version num-
ber>. Click the link, which prompts you to save the installation file to your computer.
This file appears below a section name Utilities Installation Files (as in the following
image) or Required Installations.
Note: The file that you save to your computer can be a .zip file or a .msi file.
6. Using Windows Explorer, go to the folder where the Licence Manager Installer is saved.
7. To run the installer, double-click the file, and follow the prompts.
If the file that you saved is a .zip file, extract the .msi file before running the installer.
Upgrading Licence Manager

Note: When you upgrade from Licence Manager 14.x and earlier to Licence Manager 14.7, you
MUST uninstall the previous version before installing the latest version. Usually when you upgrade
Licence Manager, you run the installation file. However, uninstalling the previous version of Licence
Manager is important because there are significant changes in the installer for Licence Manager 14.7.
When you upgrade Licence Manager 14.7 and later, the installer automatically removes the previous
version and loads all the licences from the previous version into the new version. This part of the
installation process ensures that you do not have multiple versions of Licence Manager on the same
computer.
Tip: Licence Manager 14.7 and later references a different share\etc path for the ssilm.tok file.
For your licences to be available in Licence Manager 14.7 and later, you can copy the ssilm.tok file

Setting Up the Licence Manager Server Upgrade Licence Manager on the Server Computer
from the share\etc directory of the existing installation and copy it to the share\etc directory of the
Licence Manager 14.7 and later installation. If both the previous version of Licence Manager and
Licence Manager GEOVIA Licence Manager are installed to the default directories, this means copying
the file from C:\Users\Public\Gemcom\LicenceManager\share\etc and pasting it to
C:\Users\Public\GEOVIA\LicenceManager\share\etc.
Upgrade Licence Manager on the Server Computer
2. Run the Licence Manager installer file from the installation disc.
Or if you downloaded the installer file, browse to the folder where you saved the file, and
double-click it.
3. Follow the prompts for the installation wizard to install Licence Manager to the default loc-
ation.
4. Start the Licence Manager service.
Installing Licence Manager

For the installation prerequisites, see Requirements on page 6.
The User Defaults folder contains user settings and customized files. When you install Licence
Manager, you can change the default location of the User Defaults folder. The default location is
C:\Users\Public\GEOVIA\LicenceManager\share\etc for the following operating systems: Windows
7, Windows Server 2008, and Window Server 2012.
Install Licence Manager
2. If the dongle (or sentinel) is plugged into the computer, unplug it.
Caution: When you install the dongle driver, ensure that you remove the dongle from
the computer. If the dongle is plugged into the computer, the data saved on the dongle
could be erased.
3. Insert the installation disc for the GEOVIA program into the disc drive on the computer.
4. Run the Licence Manager installation file.
l Surpac - Click Install, click Utilities, and then click Licence Manager
5. Continue clicking Next in the wizard, making the following changes:

l accept the terms of the licence agreement
l if you are prompted for a seat number, enter the seat number that GEOVIA
provided
l on the Custom Setup page, select the setting for the Sentinel Device Driver
to be installed on the local hard drive

Setting Up the Licence Manager Server Install Licence Manager
6. Click Install.
7. When the installation finishes, click Finish.
To start Licence Manager, use the desktop icon that is automatically created, or go to Start > All
Programs > GEOVIA > GEOVIA Licence Manager.
Starting Licence Manager

Start Licence Manager using one of the following methods:
l Double-click the desktop icon

l Click Start, select All Programs > GEOVIA > GEOVIA Licence Manager <version>.
Adding or Updating Licences Using Self-Service Licensing

GEOVIA introduced the self-service licensing feature in Licence Manager 14.0. All versions of Licence
Manager after Licence Manager 14.0 have this feature.
Self-service licensing permits you to download all the network licences your company has purchased
as a single .licz file, from the GEOVIA support website.
To use self-service licensing, you need a GEOVIA dongle and a GEOVIA support account. If you do not
have a GEOVIA support account, you can create one.
1. Insert the GEOVIA dongle into a port on the computer.

Caution: If you have a parallel dongle, and a printer is connected to the parallel port,
turn on the printer. Do not connect backup tape units or other similar devices to a
parallel dongle. If you must use such a device, first remove the parallel dongle. Devices
such as these can damage the dongle. Any dongle damaged by such actions incurs a
replacement cost.
2. Start GEOVIA Licence Manager by double-clicking the desktop icon or choosing Start > All
Programs > GEOVIA > GEOVIA Licence Manager <version>.
If Licence Manager has no tokens, the Request Licence form appears. If Licence Manager
has at least one token already, the right pane of the Licence Manager window shows the
token with a green check mark beside it.

3. In Licence Manager, choose Service > Stop to stop the Licence Manager service.
Licence Manager stops distributing licences, and anyone who has a network licence loses
it within a few moments.
4. If you do not have an updated tokens file (.licz file) saved to the computer, request one
and download it to the computer:
a. If the Request Licence form is not visible, choose Administration > Request
licence.
b. Click Request licence.

The DS Passport page appears.
c. Sign in to the GEOVIA Support website using your DS passport and GEOVIA
support user name and password.
If your company has at least one network licence, you will receive the
following message and license is sent to your email.
d. Save the .licz file to a local folder.

5. After saving .licz file to the computer, return to Licence Manager.
6. Choose File > Open.
7. In the File name box, select SSILM LICZ Files (*.licz), find and select the .licz file.

8. Click Open.
The Update Tokens form appears.
The form displays a list of tokens, products, and versions contained in the update file.
You select the versions you want to add or update.
9. Select the boxes for the tokens you want to update.

If the tokens in a particular program version are already defined in Licence Manager,
Licence Manager automatically updates the existing tokens to the new tokens.

Setting Up the Licence Manager Server Adding or Updating Tokens Using a .udt File
If the tokens in a particular program version do not exist, Licence Manager adds the
tokens to the "default" class.
10. Click OK.
The right pane of the Licence Manager window is updated to show the new token
information.
11. Save the changes to the tokens file.

12. To reinstall the Licence Manager service, choose Service > Install.
13. To restart the service so that all licenses are distributed on the network, choose Service >
Start.
Adding and Updating Tokens

To make licences available, you add tokens to Licence Manager. You add tokens using one of the
following methods:
l Adding or Updating Licences Using Self-Service Licensing on page 15

l Adding or Updating Tokens Using an HTML File on page 20
l Adding or Updating Tokens Using a .udt File on page 18
l Adding or Updating Tokens Using a .licz File on page 22
Updating tokens does not affect or change any previously defined classes.
Note: If you log on remotely to the Licence Manager server to add or update the tokens file, the
dongle must be plugged into the computer that is running Licence Manager.
Adding or Updating Tokens Using a .udt File
When you add or update tokens, you use a .udt file that you receive from GEOVIA to load the
licences into Licence Manager and make them available to all client computers. Updating tokens
does not affect or change any previously defined classes. Also, using a .udt file minimizes the chances
of typographical errors.
Tip: Before you add or update the tokens, create a backup copy of the previous version of the
.udt file (if you have one).

Setting Up the Licence Manager Server Adding or Updating Tokens Using a .udt File
Add or Update Tokens Using a .udt File
1. Save the new .udt file to a location on the Licence Manager server computer.
2. Insert the dongle into a port on the computer.
replacement cost.
3. Start Licence Manager.
The Licence Manager window opens.
If you are starting Licence Manager for the first time, the following information message
appears.
4. Choose Service > Stop.

5. Choose Service > Uninstall.
7. In the File name box, select SSILM Update Files (*.udt), find and select the .udt file.

Setting Up the Licence Manager Server Adding or Updating Tokens Using an HTML File
8. Click Open.

10. Click OK.
information.

Start.
Adding or Updating Tokens Using an HTML File

Before you begin, obtain written token update information by visiting the GEOVIA support website
or contacting your local GEOVIA support office.

Setting Up the Licence Manager Server Adding or Updating Tokens Using an HTML File
When you add or update tokens using an HTML file, you copy the tokens from the file, and paste the
tokens into Licence Manager. Updating tokens does not affect or change any previously defined
classes.
Tip: Before you add or update the tokens, print a summary report of the current classes, by
choosing Report > Classes.
Add or Update Tokens Using an HTML File

replacement cost.
appears.
3. Click Service > Stop.

4. Click Service > Uninstall.
5. Choose Edit > New Class.
The Create/Delete Class form appears.
6. Select the Product and the Version of that product.

7. Ensure Release type is set to Normal.

Setting Up the Licence Manager Server Adding or Updating Tokens Using a .licz File
8. In Class, leave the value as default, or if you are setting up different licences for different
groups of users, type a class name.
For more information on classes, see Licence Classes on page 10.
9. Click OK.
The right pane of the Licence Manager window is updated with new token information.
10. Choose Edit > New Token.

11. In the Token Number field, type the token number provided, and click OK.
A token for Licence Manager has at least 24 digits in total. For example, 191e86aa89-
744a8c9e8c1b363e.
Tip: To reduce typing errors, copy the token number from the HTML file, and paste it
to the Token Number field.
13. To install the Licence Manager service, choose Service > Install.
The server status in the status bar changes from Not installed to Installed
14. Click OK.
15. To start the service so that all licenses are distributed on the network, choose Service >
Start.
The server status in the status bar changes from Stopped to Started. In addition,
the service will automatically start when the computer starts.
16. Click OK.
Adding or Updating Tokens Using a .licz File

When you add or update tokens, you use a .licz file that you receive from GEOVIA to load the
licences into Licence Manager and make them available to all client computers. Updating tokens
does not affect or change any previously defined classes. Also, using a .licz file minimizes the chances
of typographical errors.
Tip: Before you add or update the tokens, create a backup copy of the previous version of the
.licz file (if you have one).
Add or Update Tokens Using a .licz File
1. Save the new .licz file to a location on the Licence Manager server computer.

replacement cost.
appears.
4. Choose Service > Stop.

5. Choose Service > Uninstall.
7. In the File name box, select SSILM LICZ Files (*.licz), find and select the .licz file.
8. Click Open.



10. Click OK.
information.

Start.
Moving a Token to a Class

Being able to move a token class, enables you to manage the licences that you have better.
To move a token from an existing class to another class:

Setting Up the Licence Manager Server Viewing the Log File

2. Choose Edit > Change Token Class.
3. Select the Token Number you want to reclassify, and click OK.
4. In Class Name, type the name of the class to which you want to change the token, and
click OK.
Running Reports
You can run reports that show the following information on licences and Licence Manager:
l log file
Viewing the Log File

This reporting function helps the administrator and technical support staff from GEOVIA to
investigate the activity of the Licence Manager.
The detailed log file is in the share directory, share\etc\ssilm.log. For each entry in the log file, there
is a date/time stamp and a diagnostic message that indicates the activity.
GEOVIA support staff might request this information to diagnose and correct issues that you
experience with the Licence Manager.
The following image is an example of the log file.
View the Log File
1. Choose View > Log to display the Licence Manager usage log report.
Note: This report might take a few moments to appear while the Licence Manager
server is being queried.

Setting up the Client to Use a Network Licence Set up the Client to use the Licence Server
Setting up the Client to Use a Network Licence

Before you can use a network licence, ensure that the Licence Manager service is installed and
running on a computer on your local area network.
If the Licence Manager server is running on the same subnet of your local area network, the GEOVIA
program automatically uses a network licence.
For information about using a network licence, see:
l Setting Up Surpac or Minex to Use the Licence Server

l Reacquire Your Licence
Setting Up Surpac or Minex to Use the Licence Server

When you start a GEOVIA program, the program by default searches for a local dongle and licence
first, and then searches for a network licence. If you want to force the program to use a particular
licence server for licensing, you can change the desktop shortcut for the program.
Set up the Client to use the Licence Server
1. Install a GEOVIA program on a computer that can contact the Licence Manager through
the network.
A desktop shortcut for the program appears on the desktop.
2. Right-click the desktop shortcut, and choose Properties.
3. In the Shortcut tab, edit the Target box using the following format:
<path of the GEOVIA program executable> -lm <name or IP address of Licence
Server>
Note: If the Licence Manager server has class names, you must include the class name
information using the –class switch. For more information, see the section named Specify
the Licence Class.
4. Click OK.
You can change the parameters of the desktop shortcut in the following ways.
Specify the Licence Manager Server
To specify the Licence Manager server, add -lm <servername> to the desktop shortcut. By using the
-lm <servername> option, the client computer sends the licence request to a specific Licence
Manager server. The request is not broadcast to all computers in the network. Depending on the
state of the local network and the traffic load in the network, there might be a delay before a licence
is granted.
For example:
When 64-bit Surpac is installed on 64-bit Windows:
"C:\Program Files\GEOVIA\Surpac\<version>\x64\bin\surpac2.exe" -lm
licserv
When Minex is installed on 64-bit Windows:
Notes:
l Firewalls on a client or server computer can be set up to block specific broadcast

requests and only allow requests when a specific computer has been nominated. If a cli-
ent fails to receive a licence, you can try temporarily turning the firewall off to find out if
the firewall is blocking communication.

l If the Licence Manager server is on a different subnet from the client, the client does
not automatically receive a licence. Instead you must add -lm <name or IP address of
the Licence Server> to the desktop shortcut.
Reconfigure the Port

Every server 'listens' to the network using a particular port number. The default port for Licence
Manager is 1234, but any number in the range of 0 to 65535 can be used. If the server is configured
to use another port, use the command -lm <servername>:<port number>.
For example:
licServer:1235
Specify the Licence Class
All licences in a Licence Manager installation can be added to classes. For more information about
classes, see Licence Classes on page 10.
To use the class named default, you do not need to add -class <classname> to the desktop
shortcut. Double-click the desktop shortcut for the program, select to use a network licence, and the
program automatically selects the default class.
If you require a specific class, or a class named default does not exist, you must add -class
<classname> to the desktop shortcut. If you do not specify a class, and the default class does not
exist, the licence is not granted.
For example:
licServer -class survey
Reacquire Your Licence

If the licence you were using is lost or revoked and you try to run another function, the Licence Type
form appears. From the form, you can run the GEOVIA program without a licence or you can try to
reacquire a licence.
l If you choose to run the GEOVIA program without a licence, you can save your work
and attempt to reacquire a licence later. When you start Surpac and the Request a
Licence in Surpac form appears, select None. If you want to get a licence later, choose
File > Licensing > Change/Inspect Licence.
l If you try to reacquire a licence, but all licences are in use by others, the form
reappears. You can then continue trying to access a licence using the form.
Reacquire a Licence in Surpac
1. Choose File > Licencing > Change/Inspect Licence.

The Update licence form appears.
2. In the Licence type field, select the network option.

3. Click Apply.
The Surpac Network Licence Request form appears. You use this form to request a new
licence.

4. Edit the Licence Server field, for example server1.company.priv:1221, and click Apply.
5. To check which modules you are licensed to use, choose File > Licencing > Change/In-
spect Licence again, and click Apply.


Licence Manager Window Set up the Client to use the Licence Server
Licence Manager Window

In Licence Manager, the main window provides you with information about your tokens in a way
that is easy for you to access and see. In this window, you can see whether tokens are working
correctly, and whether the Licence Manager service is installed and running correctly.
Menu Bar
The menu bar contains all the functions available, sorted into appropriate menus. You use the menu
functions to manage your tokens.
Toolbar
The Toolbar makes available the most common tasks as buttons.
Left Pane
The left pane shows the products for which you have tokens. It shows the host ID or the dongle
number with a +/- icon to expand or collapse. You select:
l the + icon to expand a host, that is dongle, to show the programs for which you have
tokens
l the + icon to expand a program to show the versions of the program to which the
tokens apply
l a version to show, in the right pane, the tokens available for the selected version
Right Pane
The right pane shows the list of tokens that you have entered into the Licence Manager, and shows
important information for each token.The information in this pane includes:

Licence Manager Window File Menu
Column Description
The class name. Token files can have one or more classes of licences. A licence class is the name of a group
of modules of functionality for a GEOVIA program. Users request and receive a particular licence class from
Licence Manager, and they can then use the functionality that the modules of that class provide.
Below the class name is the token status:
Class
l A green check mark indicates that the licence is enabled.
l A red cross indicates that the licence is disabled.
A licence can be disabled for a number of reasons, for more information read Why is my
licence disabled?
The licence identification. The licence identification provides a way for a GEOVIA program to reference the
Licence
tokens you have with GEOVIA's internal distribution database. It is also used for easily updating tokens and
ID
can be used to create "Update" tokens.
The token numbers that you have currently entered into the Licence Manager. Both the master tokens and
update tokens appear in the list. The master token is always the top token displayed for any licence ID, and
the update tokens are below it.
Token
(s) For each licence ID, you can have only one master token, but several update tokens can exist. Update tokens
add modules to an existing master token for a short period of time, for example, a trial period to see if you
want to buy the licence. Permanent changes in your licence are granted through a new master token. For
more information on update tokens, see UDT file in the glossary.
The expiry date for the token.
Expires
Tip: To ensure that users have continued use of their GEOVIA programs, contact your local GEOVIA
office before the token number expires.
Max
The maximum number of users who can use the licences provided by the token at the same time.
Users
The licence modules made available by the token number. The information shows the complete list of
Options modules that are available in the master token and any update tokens.
If you do not see modules that you have purchased, contact your local GEOVIA support office.
Status bar
The status bar is located in the lower right corner and has two important indicators. The first displays
Not installed or Installed to indicate the state of the Licence Manager service. The second indicator
displays Stopped or Running to indicate whether the Licence Manager service is running or not. The
Licence Manager service can only respond to licence requests if it is installed and running.
Menu Commands
Licence Manager is designed to give you a simple and quick way of determining the status of your
licences and licence server. You can manage your licences using the following menus:
l File
l Edit
l View
l Service
l Administration
File Menu
The functions in the File menu permit you to load and save the tokens file used by the Licence
Manager. The default name of the tokens file is ssilm.tok. It is located in the share\etc directory. The
File functions also permit you to import an Update Tokens File (.udt) or .licz file.

Licence Manager Window File Menu
Note: You can use tokens files with different names, but the file must reside in the share\etc
directory. Also, Licence Manager can use only one tokens file at a time.
Tip: You can test changes to the tokens file before implementing the changes to the live
environment using the Save As function.
New
When you use this function, Licence Manager creates a tokens file in the memory of the computer.
You then add licences tokens to this file.
Note: To save the new tokens file, choose File > Save.
When the Licence Manager is installed as a service for the first time, Licence Manager creates the
default tokens file share\etc\ssilm.tok. As a result, this function is rarely used.
Open
You use this function to open a tokens file and load the contents of that tokens file into Licence
Manager. When Licence Manager starts, it automatically loads the default tokens file
share\etc\ssilm.tok. You also use this function to load an Update Tokens File (.udt) or .licz file. The
.udt or .licz file allows you to add and update tokens that exist in your Licence Manager.
You use this function only when you use a tokens file that is not named ssilm.tok, or when you are
importing an update file.
Note: GEOVIA does not recommend that you use a tokens file named anything other than
ssilm.tok in a live environment.
Save
You use this function to save the current tokens file to the computer. After you save the tokens file,
the Licence Manager server reloads and then reconfigures itself to use the changes from the tokens
file.
You edit the tokens file using one of the following functions:
l Edit > Properties

l Edit > New Token
l Edit > New Class
After you edit the tokens file, you must save it so that the licence server process is able to recognise
the changes.
Note: If the licence server process does not recognise the changes, you might have to restart the
Licence Manager server to serve the licences correctly. To stop the license server, use (Service >
Stop), and then to start the server use (Service > Start).
Save As
You use this function to save the current tokens file with a different name.
You edit the tokens file using one of the following functions:

Licence Manager Window Edit Menu
l Edit > Properties

l Edit > New Token
l Edit > New Class
After you edit the tokens file, you must save it so that the licence server process is able to recognise
the changes.
Tip: You can use this function to add new tokens to a different tokens file as a test before
implementing the changes to the ssilm.tok file and live environment.
Edit Menu
The functions in the Edit menu permit you to modify the tokens file by adding and deleting tokens
and adding and deleting classes.
Also, you can change various properties of the Licence Manager. Changing these properties modifies
the behaviour of the Licence Manager server process.
Tip: You can access these functions through the shortcut menu when you right-click a tokens file.
Properties
You use this function to view, and if necessary, change various properties of the Licence Manager.
When you change these properties, you modify the behaviour of the Licence Manager server
process.
All properties for the Licence Manager are saved to the configuration file share\etc\ssilm.cnf. When
you select this function, the Edit Configuration form appears showing the properties currently saved
in the configuration file. If you change a property and click OK, the changed properties are saved to
the same file.
After you save the properties to the configuration file, the licence server process receives a
reconfigure signal. After receiving the signal, the licence server process reads the configuration file
and then operates with the new parameters.
You cannot change all properties in this way because active licences restrict the ability to change
some of the characteristics of the licence.
After you change the values on the form, click OK to reconfigure the licence server.
Fields on the Edit Configuration form
Field Description
The name of the file to which all reports are sent. When you request a report, the report details are
sent to this file first and the contents of the file are then displayed. By default, the log file is
Log File Path- always called share\etc\ssilm.log.
name
Tip: Because the log file can become large, you can restrict its size using the Max. Log file size
option.
The number of seconds that a licence held by a client can be idle before the licence state changes
to standby. When a licence state becomes standby and if there are no other available licences,
other clients can take the licence. This property prevents a user who forgets to exit a program from
Standby Timeout
holding a licence forever.
If you leave the value at 0, Licence Manager treats it as an infinite period (that is, the licence never
becomes a standby licence). The recommended value is 600 seconds (which is 10 minutes).

Field Description
l Selected: Includes a line for each entry and each exit of a function from a GEOVIA
program in the log file report.
An administrator might find this information useful to record statistics of the
Function Logging usage of the installed GEOVIA programs.
Note: With this option selected, the log file might become large quickly.
l Cleared: Does not include information on function usage from GEOVIA programs in
the log file report.
Each client process session (for example, Surpac or Minex) that uses the licence manager for
authorisation sends a heartbeat message to the licence server at regular intervals. These heartbeat
messages indicate to the licence server that the licence is active. If the license server computer
stops receiving these heartbeat messages, it is assumed the client has failed or stopped respond-
ing. The licence is then released for reuse. These heartbeat messages are sent even when the cli-
ent is busy processing data.
Heartbeat The heartbeat interval is the time delay between these regular messages sent by the client
computer to the server computer.
Ideally, the heartbeat is between 10 and 300 seconds. Greater values reduce network traffic.
However, if a client computer fails, the licence is still held for a longer time. Lower values increase
network traffic, and allows the server computer to detect client computer failures faster. The
recommended value is 30 seconds.
The maximum file size for the log file. The log file that is generated can become large quickly, espe-
cially with Function Logging enabled. However, it is unlikely that you need more than the last few
messages to troubleshoot any problems that you experience, so a very large file is not required.
This option gives you the ability to limit the size of the log file. The default size is 100 KB.
Max Log file size When the log file reaches the maximum file size limit, it backs up the current log to ssilm.bak, and
starts a brand new log file. In this way, it is easy to see the last several hundred messages, without
using large amounts of disk space. Be aware, however, that because the old log is backed up, the
disk space you use may be up to double the size you specify in this box. Any previous logs called
ssilm.bak are erased.
The maximum number of heartbeat messages a client allows to be unacknowledged before it
assumes that it has lost its licence.
Maximum Unac- Licence Manager uses a client/server protocol that is layered on top of UDP/IP (a protocol that is
knowledged Pack- inherently not completely reliable). As a result, it is normal to lose some heartbeat messages.
ets The "heartbeat interval" multiplied by "maximum unacknowledged heartbeats" must be less than
300 seconds. The recommended value for this property is 3. This value gives the best mix of "usual
events" security, while still allowing the server to respond to a failed client in a timely fashion.
The reverse DNS lookup is a useful feature, but it can cause problems on some incorrectly con-
figured networks. This option allows you to turn off the feature to see if that is the cause of the
Enable Reverse
problem. If you are having no problems with Licence Manager, leave this option enabled.
DNS lookup
For more information on this feature, see What is a Reverse DNS lookup? in the Frequently Asked
Questions.

Field Description
The Universal Datagram Packet (UDP) port number that you want to use for two-way com-
munication between the client and server processes. It is recommended that you use the default
value of 1234, unless using the default value causes a conflict with another program that uses the
UDP Port same port number.
If you change the UDP port number, you must restart the Licence Manager service for the change to
take effect.
For more information, see UDP ports in the glossary.
If Server to Administer is blank, and you run a function from the Report menu, the report shows
information for all instances of Licence Manager that are currently running on your subnet of the
local network. If you specify the server in this box, the report shows information for the specified
licence server only.
Server to Administer is useful because it enables you to run reports across virtual private networks
(VPN) and across wide area networks (WAN). It is also useful when several Licence Manager server
Server to Admin- computers are running on the same network, or the network configuration is blocking the message.
ister The format of the server definition is <server name or IP address>[:<port number>].
Some examples are:
LMserver
127.0.0.1
LMserver:1234
127.0.0.1:1234
New Token
You use this function to add or update licence tokens to the tokens file. You add or update the
licence tokens when you:
l install a new version of a GEOVIA program

l purchase more program modules
l purchase more program licences
When you run this function, you enter tokens into the tokens file. The token is a hexadecimal
number that consists of the numbers 0 to 9 inclusive and the letters a to f inclusive. You can obtain
valid tokens only from an authorized GEOVIA support office.
When you enter a new token, the token is added to the currently selected class. When you enter a
token that is a modification to an existing token, the existing token is updated to the new modules
and values.
After you enter a new token, save the changes to the tokens file using File > Save. The licence server
then reloads the tokens file so that the new tokens are immediately available for use.
New Class
You use this function to create licence classes and assign tokens to the licence classes that are
created. Licence classes are useful for sites to have more control over the usage of GEOVIA products.
When you create a class, you define the host, GEOVIA product version, and the name of the licence
class.
After you create a class, save the changes to the tokens file using File > Save. The licence server then
reloads the tokens file so that the class you created is available.

Fields on the Create/Delete Class form
Field Description
Host
The number of the dongle (or sentinel) connected to the computer on which the licence service is running.
This value MUST not be changed.
Sentinel Administrators who are experienced with maintaining Licence Manager servers might find this field useful
ID because they can enter the dongle number of a dongle other than the one connected to the licence server
computer. When you enter the dongle number of another dongle, you can enter the details of classes and
tokens for a second licence server into the one tokens file. You can then use the tokens file on both Licence
Manager servers that are running on different computers.
Licence Ensure that you leave this check box selected. For Licence Manager to function correctly, this check box
Manager must be selected.
License
The name of the class that you are creating or deleting. The default value is default.
When you create a class, you can set this value to any name you want. However, it is conventional to
choose licence class names that match department usage of the program. For example, geology, survey,
engineering are common names.
Class Tip: It is useful in large installations to spread the available licences across departments so that no
department can use all the available licences.
Note: For Surpac or Minex to use a specific licence class, you can add the -class <classname> command-
line option to the desktop shortcut. For more information on classes, see Licence Classes on page 10.
If you require assistance in creating multiple licence classes, contact GEOVIA.
Release
The name of the GEOVIA program for which the class is being created or deleted.
Product Note: This program name must match the name of the program for which the token has been
generated.
The version number, in the form major.minor, for which the licence class is being created or deleted.
Version Note: The version number is the version number of the program for which the token was generated. It is
not the version of Licence Manager.
Release The release type for the licence class.
type Note: The release type must match that for which the licence was generated.
Delete Token
You use this function to delete a token from the tokens file. When you run this function, you select
the token to remove from the tokens file, and then click OK.
After you delete a token, save the changes to the tokens file using File > Save. The licence server
then reloads the tokens file so that the tokens you deleted are no longer available.
Tip: You can run this function from the shortcut menu, by right-clicking the token and choosing
Delete Token. When you run this function from the shortcut menu, the Token form does not appear
because the function is run directly from the token.
Delete Class
You use this function to delete a class from the view. All tokens in the deleted class are still available
from the default class.

Licence Manager Window View Menu
When you run this function from the menu, you enter the details of the class to be deleted from the
tokens file. To be able to delete a class, you must specify the host, GEOVIA product version, and the
name of the licence class. For information on the fields available on the Create/Delete Class form, see
the table above under the New Class function.
Tip: You can run this function from the shortcut menu, by right-clicking the class and choosing
Delete Class. When you run this function from the shortcut menu, the Create/Delete Class form
does not appear because the function is run directly from the class.
After you delete a class, save the changes to the tokens file using File > Save. The licence server then
reloads the tokens file so that the class you deleted is no longer available.
Change Token Class
You use this function to move a token from an existing class to another class.
For example, you have two classes, default and geology. The default class has three tokens allocated
to it, and the geology class has one token allocated to it. On the site, there is usually one geologist
who uses the licence. Occasionally, a second geologist works on the site for a short time. During the
time when two geologists are on the site, you can select a token from the default class that you want
to allocate to the geology class. As a result, the geology class will have two tokens available.
Note: A token can exist in one class only.
After you change a token class, save the changes to the tokens file using File > Save. The licence
server then reloads the tokens file so that the token class exists in the class you specified.
Tip: You can run this function from the shortcut menu, by right-clicking the token and choosing
Change Token Class. When you run this function from the shortcut menu, the Token form does not
appear because the function is run directly from the token. You only have to type the name of the
class to which you want to move the token.
View Menu
The functions in the View menu permit you to change the presentation of the Licence Manager
program. You can:
l show or hide the Toolbar buttons (at the top of the Licence Manager window)
l show or hide the Status bar (at the lower end of the Licence Manager window
l view a log, of the activities of the Licence Manager server process, to monitor com-
munications between the client and Licence Manager
Toolbar
When you use this function, you show or hide the Toolbar at the top of the Licence Manager
window.
A check mark next to this function indicates that this item is selected, and the Toolbar is visible. By
default, the Toolbar is visible. When the Toolbar is visible, you can click a button to run some of the
Licence Manager functions (instead of going to the menu).

Licence Manager Window Service Menu
Status Bar
When you use this function, you show or hide the Status bar at the bottom of the Licence Manager
window.
A check mark next to this function indicates that this item is selected and the Status bar is visible. By
default, the Status bar is visible.
Log
When you use this function, you can view a log of the activities of the Licence Manager server
process.
This reporting function helps the administrator and technical support staff from GEOVIA to
investigate the activity of the Licence Manager.
The detailed log file is in the share directory, share\etc\ssilm.log. For each entry in the log file, there
is a date/time stamp and a diagnostic message that indicates the activity.
For more information, see Viewing the Log File on page 25.
Service Menu
The Windows operating systems have a concept of a system service. A system service is a program
that runs in the background of Windows. A system service starts running when the operating system
starts, and stops again when you turn off the computer.
Licence Manager runs as a service called GEOVIA Licence Manager Service.
After you have configured Licence Manager to your needs, you start the service. Then the Licence
Manager service continues to run automatically whenever the Licence Manager server computer is
running. The service does not stop until you manually force it to stop.
You can use Services to start and stop the Licence Manager service. However, you might find it easier
to use the Licence Manager window to perform all Licence Manager service management tasks
including starting and stopping.
You must have Administrator level permission on the computer to run any of the functions in the
Service menu.
Tip: Alternatively, you can see the state of the GEOVIA Licence Manager service under Services in
the operating system. To access Services quickly, click the Start menu, and in the Search box, type
services.

Licence Manager Window Reporting
Install
You use this function to install the Licence Manager as a service under Microsoft Windows.
Note: Windows 95/98/ME/XP/Vista do not support the services required to run Licence Manager.
You must have Administrator level permission, on the computer, to install Licence Manager as a
service.
If Licence Manager is already installed as a service, a warning message appears.
If the Licence Manager was not previously installed as a service, a confirmation message appears.
Note: Installing the Licence Manager as a service does not start the service. You must choose
Service > Start to start the service. Before starting the service, you must also have a valid licence file.
Uninstall
You use this function to remove the Licence Manager from the installed services.
When you uninstall the Licence Manager service, it stops immediately. Any currently running
sessions of Licence-Manager-enabled programs that rely on that service for authorization lose their
licence soon after the Licence Manager service stops.
You must have Administrator level permission, on the computer, to uninstall Licence Manager.
If Licence Manager is not already installed as a service a warning message appears.
After successful removal of the Licence Manager service, a confirmation message appears.
Start
You use this function to start the Licence Manager program as a service under Microsoft Windows.
If the Licence Manager service is already running, attempting to start it has no effect.
You must have Administrator level permission, on the computer, to start the Licence Manager
service.
The Licence Manager program MUST BE installed as a service before you try to start it as a service.
After successfully starting the service, a confirmation message appears.
Stop
You use this function to stop the Licence Manager program running as a service under Microsoft
Windows.
If the Licence Manager service is already stopped, attempting to stop it has no effect.
You must have Administrator level permission, on the computer, to stop the Licence Manager
service.
The Licence Manager program MUST BE installed as a service before attempting to stop it as a
service.
After successfully stopping the service, a confirmation message appears.
Reporting
You can manage Licence Manager using reports which provide usage statistics of licences currently in
use and currently available.

Licence Manager Window Administration Menu
You can use the Licences report to determine which users hold which licence.
Licence Manager generates the reports by sending requests for information to the licence server
process. The server process then responds by sending the requested information to the Licence
Manager which then displays it in a dialog window.
Network traffic can have an impact on the time to send and receive this information. It may take a
few seconds to collate all of the report data.
All of the following log functions broadcast the log report on the local network, so that all Licence
Managers running within the limits of the broadcast (local network) will send a reply. If there are two
(or more) Licence Managers running on a network, a complete report of all classes, licences and
available licences is available from all Licence Managers. This is useful in diagnosing if all of your
Licence Managers are working correctly.
Administration Menu
The functions in the Administration menu permit you to perform various tasks related to granting
and releasing licences. Tasks include:
l requesting a licence from GEOVIA, or loading the licences you have already received
l revoking a licence that is currently in use
l restarting the licence server process
l reloading the tokens file so that the Licence Manager server can use new tokens that
have been added to the tokens file
l reconfiguring the Licence Manager server process by reloading the configuration file
ssilm.cnf
Note: The functions from the Administration menu do not provide any confirmation messages
when they complete. You can, however, choose View > Log to view the log file after running any of
these functions. If a function completes successfully, a record of the operation appears in the log file.
Request License
When you use this function, a form appears that you use to get the licences you have purchased
from GEOVIA. To get your licences, click the following button:
l Request Licence: To download the licences from the GEOVIA support website, you click
this button.
For detailed steps, see Adding or Updating Licences Using Self-Service Licensing on page
15.
Revoke
You use this function to revoke a licence that is in use. This feature is useful when all licences are in
use and another user requires a licence to complete an urgent task. Revoking a licence requires that
you know the licence ID of the licence you want to revoke.
Tip: If you do not know the licence ID, choose Report > Licences to view a report that includes
the licence ID, the user name, and the state of the licence.
Note: Licences that are in a standby state are automatically revoked by the Licence Manager, and
the licence is granted to satisfy a request for a new licence.

Licence Manager Window Functions on Licence Classes
When revoking a licence, it is recommended that you revoke a licence that is in an idle state because
the licence is not actively being used.
The licence is immediately revoked and is made available for use by a different person.
The user whose licence is revoked can still complete their session. However, the program they are
using has a restricted range of functions so that the user can save any unsaved work and exit
properly.
Note: If the user continues to use the licence that has been revoked, the user receives an
unlicensed error from the program. Also, an error appears in the Licence Manager log file.
Restart
You use this function to restart the licence server process.

After you change the Licence Manager properties (Edit > Properties), it is sometimes necessary to
restart the licence server process so that the updated settings become active.
When you run this function, the Licence Manager service process receives a restart message. The
Licence Manager server then reads the configuration file, share\etc\ssilm.cnf, and uses the new
properties.
Note: If there are active client sessions and you changed the UDP port number, the changes to the
UDP port number do not take effect. The UDP port number property cannot be changed for active
sessions. For the Licence Manager service to use a different port number, you must stop the Licence
Manager service, and then start the Licence Manager service.
Reload
You use this function to reload the tokens file that is used by the Licence Manager server process.
Note: You rarely use this function because the tokens file is automatically reloaded whenever you
choose File > Save to save changes to the tokens file.
Reconfigure
You use this function to make the Licence Manager server process use the properties defined in the
ssilm.cnf file.
Note: When you change the properties using Edit > Properties and then click OK, the Licence
Manager server process is automatically reconfigured. As a result, you rarely use this function.
Shortcut Menu
In the right pane, you can perform functions on a selected licence class or on a selected token
number using the shortcut menu.
Functions on Licence Classes
To access the shortcut menu, select the licence class, and then right-click. The functions you can
perform are:

Licence Manager Window Functions on Token Numbers
Function Description
You use this function to add licence tokens to the tokens file. This functions is the same as
New Token
choosing Edit > New Token.
You use this function to delete a class from the view. All tokens in the deleted class are still
Delete Class available from the default class.
Note: This function is the same as choosing Edit > Delete Class.
Functions on Token Numbers

To access the shortcut menu, select a token number, and then right-click. The functions you can
perform are:
Function Description
You use this function to delete a token from the tokens file. This functions is the same as choos-
Delete Token
ing Edit > Delete Token
You use this function to check across all versions of the selected GEOVIA program to delete all
tokens that have the same licence ID. These tokens are in different versions of the same
Delete All Tokens program as the currently selected token.
with Licence ID For example, you have one licence for Surpac 5.0 and one Surpac 6.0 with the same licence ID.
This function checks across all versions of Surpac and deletes all tokens with the same licence
ID.
You use this function to move a token existing class to another class.
Change Token Class
This functions is the same as choosing Edit > Change Token Class.
You use this function to re-enable a token that was previously disabled.
Enable Token Note: If the reason a token was disabled is because the administrator disabled the token,
then you can use this function to re-enable the token. If the token was disabled for any other
reason, you will not be able to enable the token.
You use this function to disable a token. You might disable a token for any reason. However,
the main purpose for disabling a token is for finding a system error. As a result, this function is
rarely used. For more information, see Why is my token disabled?
Disable Token
Tip: If a token is disabled because the administrator had disabled the token, you can use
the Enable Token function to re-enable the token.
You use this function to view the properties of the selected token. The properties include the
expiry date and creation date of the token, and whether the token is enabled or disabled (and
Properties
the reason why the token is disabled). This information is useful when you must find out why a
token is disabled?.

Troubleshooting - Overview Functions on Token Numbers
Troubleshooting - Overview
When you experience problems with Licence Manager, there are several activities you can perform to
help you identify the problem. Two key activities are:
l reviewing the Licence Manager log file

You can open the log file in Licence Manager or from Windows Explorer. To open the
log file in Licence Manager, choose View > Log. To open the log file from Windows
Explorer, browse to the location where the log file is saved. The default location is
C:\Users\Public\GEOVIA\LicenceManager\share\etc\ssilm.log.
l temporarily turning on user function logging (which logs each function that a user runs
from a GEOVIA program)
To turn on user function logging, choose Edit > Properties and select the Function
Logging check box. Alternatively, you can use a text editor to modify the configuration
file. The default location for the configuration file is also
C:\Users\Public\GEOVIA\LicenceManager\share\etc\ssilm.cnf.
Most errors that cause Licence Manager to fail are recorded in the log file. The log file is the first place
you check when you experience an issue. When trying to troubleshoot possible problems:
l Examine the log file and include it with any queries to your local GEOVIA support office.
l Start the Licence Manager service from the Service > Start function.
To start the Licence Manager service, you require Administrator permissions.
l Run NetworkLicenceManager.exe from the command prompt instead of as a service.
Running NetworkLicenceManager.exe from the command prompt allows you to see
errors that do not usually appear in the log file. Depending your computer setup, you
might require Administrator permissions.
When you install Licence Manager with a GEOVIA program, the
NetworkLicenceManager.exe is installed in the \bin directory of your GEOVIA program.
For the path, see Licence Manager Folder Paths on page 10. When you run
NetworkLicenceManager.exe without parameters, you get a list of the command-line
options available. To start a server, try using NetworkLicenceManager.exe -server,
which generates error messages when something is going wrong.
l Run the Licence Manager as a pseudo-client, which enables you to see whether the
Licence Manager server is granting licences.
By running the Licence Manager server as a pseudo-client, you can determine whether
a separately running Licence Manager is granting licences correctly. If this method
works but the GEOVIA program is still not working correctly, you know that the prob-
lem is not because the Licence Manager server is incorrectly configured.
For example, to run a pseudo-client that pretends to be Surpac 6.0, in a command
prompt type:
networklicencemanager -client surpac2 6.0 -lm <licence-
server>
Note: Licence Manager recognizes surpac2 as the program name for Surpac.
You can try this same command with the name of any program and version in Licence
Manager. If the process finishes running immediately, and you can type more
characters in the command prompt, it means that the licence server you specified for
Surpac 6.0 is not correctly serving licences.
If the process continues running, and you cannot type in the command prompt, it
means that the licence server is serving licences.

Troubleshooting - Overview Installation
Note: To interrupt the process, press Ctrl+C.
Common Issues
Installation
l When using the uninstall option from the DVD, some of the files were not removed
from the Licence Manager install directory
l When attempting to install the Licence Manager from the DVD, some files are not
installed
l Licence Manager service fails to install

l Using the Service > Install function fails to install the service. No error message appears
l Licence Manager does not start
l Licence Manager service stops after it has been started
Client Licences
l Licence Manager fails to grant licences

l The error "Could not get network licence. Could not connect to interlude process"
appears
l The error "Could not get network licence. Unable to send licence request to any server"
appears
l There appears to be no communication between the program and the Licence Manager
server
l Licence Manager does not allocate a licence to a specific client, and the log file displays
"Error - Reading incoming messages"
Installation
When using the uninstall option from the DVD, some of the files were not removed from the
Licence Manager install directory.
If some files are locked during the uninstall process, those files cannot be removed.
Some files are locked when one of the following occurs:
Description: l the Licence Manager service is running

l a program is connected to the Licence Manager server
l a program is using the contents of the Licence Manager directories
Before you uninstall Licence Manager, ensure that Licence Manager is not running and that the Licence
Manager service is stopped. Also ensure that no other programs are connected to the Licence Manager
server or using the contents of the Licence Manager directories.
Note: The uninstall process does not remove the contents of the
C:\Users\Public\GEOVIA\LicenceManager\share\etc folder. As a result, the ssilm.tok
Solution: tokens file is not deleted, and you do not have to re-create your tokens file when you
reinstall Licence Manager.
If you use the Licence Manager functions to stop and uninstall the service, you do not
need to uninstall files from the system directories or the registry. Just delete the
contents of the Program Files (x86) folder containing Licence Manager.

Troubleshooting - Overview Licence Manager Service
When attempting to install the Licence Manager from the DVD, some files are not installed.
If another process has locked some files during the uninstall process, the Licence Manager
installation could fail to install those files.
Some files are locked when one of the following occurs:
Description: l the Licence Manager service is running

l a program is connected to the Licence Manager server
l a program is using the contents of the Licence Manager directories
Before you install Licence Manager, ensure that the Licence Manager service is not running and that no
Solution:
other programs are connected to, or using the contents of the Licence Manager directories.

Licence Manager service fails to install.
The Licence Manager service can fail to install because:
l it has already been installed

Description: You can install the Licence Manager service only once.
Uninstall the existing the service by choosing Service > Uninstall and then install the
Solution:
new service by choosing Service > Install.
l you do not have Administrator permissions

If you are unable to install the Licence Manager service, it may be because you do not
Description: have Administrator permission on the computer. You need Administrator permission to
perform all Licence Manager tasks.
Contact your local site systems administrator and ask to be granted Administrator per-
Solution:
mission.
Using the Service > Install function fails to install the service, and no error message appears.
If Licence Manager has become corrupted because of the accidental removal of some of the required
files, the install function fails to work. In this situation, no message appears to inform you of the
error.

If any of the files required to run Licence Manager functions is missing, you are not able to install the
service. Files required to run Licence Manager are contained in the bin directory and in the share\etc
folder.
The /bin directory contains:
l NetworkLicenceManager.exe
l NLMAdmin.exe
l boost_thread-vc100-mt-1_46_1.dll
l boost_system-vc100-mt-1_46_1.dll
Description:
The share/etc directory contains:
l ssilm.cnf
l ssilm.tok
If any of these files are missing, you must reinstall Licence Manager.
Note: The location of the bin directory depends on the GEOVIA product Licence Manager was
installed with, or the location you selected during deliberate installation of the Licence Manager
program. For more information, see Licence Manager Folder Paths on page 10.
Uninstall Licence Manager and reinstall it using the original GEOVIA installation DVD, or using a down-
Solution:
load of the installation from geoviasupport.com.
Licence Manager does not start.

The most common causes that stop the Licence Manager from running are:
l TCP/IP networking is not installed

GEOVIA programs and the Licence Manager communicate using the TCP/IP networking
Description: protocol. Some Windows installations do not install TCP/IP networking by default.
If TCP/IP networking is not installed, a message appears in the log file.
Solution: Installing dial-up networking usually also installs TCP/IP networking.
l the default port that Licence Manager uses is in use by another process
By default, Licence Manager uses UDP port 1234. You can set Licence Manager to use
any port number, by choosing Edit > Properties and typing a new value in the UDP Port
Description: field. If another process is already using the UDP port that the Licence Manager server
uses, the Licence Manager service exits with an error.
If this issue occurs, a message appears in the log file.
Change the UDP Port setting in the Licence Manager properties to use a UDP port
number that is not used by other processes. Try choosing a number greater than 1000.
After you change the port number, restart the Licence Manager service.
When you use a port other than 1234, you must specify the port number in the target of
the shortcut for the GEOVIA program (Surpac or Minex). If the program requests a
licence using a port that is different from the port that Licence Manager is using, a
Solution: licence is not granted.
If you want to broadcast the request without specifying a particular server, use:
l -lm :<portNumber> in the target
For example, -lm :4567.
If you want to request a licence from a particular server, use:
l -lm <ssilm-server>:<portNumber>
For example, -lm licenceserver:4567.

l the dongle drivers are not correctly installed, the parallel port is not configured cor-
rectly for the dongle, or multiple devices are conflicting on the parallel port
When Licence Manager starts, it checks for a dongle to obtain the host ID for the valid
licences. If a valid dongle is not found, Licence Manager exits with an error. Assuming a
dongle is attached, the dongle would not be found if:
Description:
l the drivers for the dongle are not installed
l the port in which the dongle is inserted is not configured correctly
l the dongle is not the first device attached to the port
If the dongle drivers are not installed, install them using the GEOVIA product
installation.
If you are using a parallel port with multiple devices connected through each other,
make the dongle the first device in the chain (that is, the one connected directly to the
parallel port on the computer).
Solution: GEOVIA supplies a dongle that uses a USB port connector. This dongle is only available
for Windows 7, Windows Server 2008, Windows Server 2012 (Windows NT 4.0 does not
support USB). It resolves all problems that relate to parallel ports. You cannot join
devices together in sequence through the USB dongle, which resolves many hardware
conflicts. If you are having problems with a parallel dongle, contact GEOVIA to acquire a
USB dongle.
l multiple copies of Licence Manager are running

You can run only one Licence Manager process at a time on a single computer. If you
start Licence Manager, and Windows detects that another copy of Licence Manager is
Description: already running, the copy you just started exits.
If you have an existing Licence Manager process running, a message appears in the log
file.
Run Task Manager, select any current instance of Licence Manager, and choose End
Solution:
Task before attempting to start the version of Licence Manager that you want.
l some versions of Windows have an out-of-date MFC42.DLL that does not work with
Licence Manager
You start Licence Manager and see the error message: "The ordinal 6883 could not be
Description: located in the dll MFC42.dll". This message indicates that your version of Windows does
not have a version MFC42.DLL that works with Licence Manager.
Install a current version of MFC42.DLL. To install a current version of MFC42.DLL:
l Install the latest Service Pack for your version of Windows
Solution: l Install the latest version of Internet Explorer
l Go to http://activex.microsoft.com/controls/vc/mfc42.cab save and
install the cab file
l firewalls prevent Licence Manager from working

Description: Licence Manager cannot work across firewalls that have default settings.
To use firewalls and use Licence Manager, configure the firewalls to allow packets for
Solution: the UDP port that Licence Manager uses to pass through the firewall. The default UDP
port for Licence Manager is 1234.
Licence Manager service stops after it has been started.

The Licence Manager service could because:

Troubleshooting - Overview Client Licences
l another program is using the UDP port number that Licence Manager uses
By default, Licence Manager uses UDP port 1234. You can set Licence Manager to use
any port number, by choosing Edit > Properties and typing a new value in the UDP Port
Description: field. If another process is already using the UDP port that the Licence Manager server
uses, the Licence Manager service exits with an error.
Change the UDP Port setting in the Licence Manager properties to use a UDP port
number that is not used by other processes. Try choosing a number greater than 1000.
After you change the port number, restart the Licence Manager service.
When you use a port other than 1234, you must specify the port number in the target of
the shortcut for the GEOVIA program (Surpac or Minex). If the program requests a
licence using a port that is different from the port that Licence Manager is using, a
Solution: licence is not granted.
If you want to broadcast the request without specifying a particular server, use:
Client Licences
Licence Manager fails to grant licences.
If the error message “unable to find requested licence” appears when a user tries to get a network
licence for their GEOVIA program, Licence Manager is not granting licences.
To see which licences Licence Manager is distributing, choose Report > Available.
Licence Manager fails to grant licences because:
l the tokens file was not saved

If you change the tokens file, you must save the file before the change becomes effect-
Description:
ive. If you do not save the file, Licence Manager might not be able to grant licences.
Solution: To save the tokens file, choose File > Save in Licence Manager.
l Licence Manager is not able to resolve its host name or perform a reverse look-up of
the client host name
Licence Manager must perform reverse lookups of client host names for logging
purposes. The API calls that Licence Manager uses can have problems when the host
name is not directly resolvable. When the Licence Manager server performs the reverse
Description:
name lookup, it pauses until it times out, which makes it appear as if the Licence
Manager server has become idle. In particular, sites relying on DHCP could experience
lookup problems.
You can usually add the Licence Manager host name and the client host names and IP
addresses to the Windows hosts file. Depending on how the various name services are
Solution:
managed, you might not need to edit the hosts file. Sites using DNS for name services
tend to have fewer problems with reverse name lookup.
For more information, see What is a Reverse DNS lookup? on page 56

l the Licence Manager server is on a different subnetwork than the client computer
requesting a broadcast licence
When a client computer requests a network licence without a host name specified, it
sends a broadcast request on the local subnetwork. These broadcast requests usually do
Description:
not pass through network bridges or routers. If Licence Manager is on a separate net-
work segment, it does not "hear" the request.
Specify the Licence Manager server host name in the program shortcut using the -lm
switch.
Solution:
For example, for the Surpac shortcut, edit the Target field as follows: "<Surpac
installation directory>\surpac2.exe" -lm licServer
The error "Could not get network licence. Could not connect to interlude process" appears.
This message can appear because:
l of timing errors during startup

This commonly occurs when you have not specified the licence server in the target of
Description:
the program shortcut.
Modify the target of the program shortcut to include the -lm licencerserver option,
Solution:
where licenceserver is the name of the licence manager server.
l all licences maintained by the Licence Manager server have been added to licence
classes other than the default class
This commonly occurs when you have not specified an alternate class name in the tar-
Description:
get of the program shortcut.
Modify the target of the program shortcut to include the -classclassname, where class-
Solution:
name is the name of one of the classes that exist in the tokens file.
l the DNS setup is incorrect

For more information, see Licence Manager does not start. on page 47
l there is no NetworkLicenceManager.exe in the bin directory of your client program
The Licence Manager uses the NetworkLicenceManager.exe file on both sides of the
Description: communication. So if the NetworkLicenceManager.exe does not exist on the client side,
this message appears.
Solution: Ensure that NetworkLicenceManager.exe exists on both the client and server.
The error "Could not get network licence. Unable to send licence request to any server" appears.
This message because:
l the server and/or port number that is being used to acquire a licence are incorrect
Solution: Check that the Licence Manager server name and port number are correct. If
the program is calling the wrong name or port number, correct this information in the
target of the program shortcut.

l the Licence Manager service has stopped

The Licence Manager service must be installed and running for a client to get a network
Description:
licence.
Start Licence Manager by going to /bin folder of your Licence Manager installation, and
double-clicking NLMAdmin.exe. In the Licence Manager window, check that the indic-
Solution: ators in the status bar display Installed and Running. If these status indicators are not
displayed, contact your local site administrator or log a ticket on the GEOVIA support
website.
There appears to be no communication between the GEOVIA program and the Licence Manager
server.
To use a network licence or obtain a licence, the client must be able to communicate with the Licence
Description:
Manager server.
Determine whether any communication is occurring between the client and server computers:
1. On a computer that is running a GEOVIA mining program, open the Command Prompt.
2. Type ping<hostname>, where <hostname> is the name of the computer that is running
Licence Manager.
Solution:
3. Press Enter.
Messages appear in the command prompt to indicate whether the client computer can contact the
server computer. If this test fails, contact your local systems administrator. If this test passes, log a
ticket on the GEOVIA support website.
Licence Manager does not allocate a licence to a specific client, and the log file displays "Error -
Reading incoming messages".
The log file displays this message when both Licence Manager and another program use the same
UDP port.
By default, Licence Manager uses UDP port 1234. You can set Licence Manager to use any port number,
by choosing Edit > Properties and typing a new value in the UDP Port field. If another process is already
Description: using the UDP port that the Licence Manager server uses, the Licence Manager service exits with an
error.
Change the UDP Port setting in the Licence Manager properties to use a UDP port number that is not
used by other processes. Try choosing a number greater than 1000. After you change the port number,
restart the Licence Manager service.
When you use a port other than 1234, you must specify the port number in the target of the shortcut for
the GEOVIA program (Surpac or Minex). If the program requests a licence using a port that is different
from the port that Licence Manager is using, a licence is not granted.
Solution: If you want to broadcast the request without specifying a particular server, use:


Troubleshooting - Overview Dongle
Frequently Asked Questions

Dongle
l Do I still a need a dongle?

l Can the Licence Manager server have more than one dongle plugged in?
l Can I take a dongle from the Licence Manager server, plug it into a client computer and
start using it as a local dongle?
l What networking protocols does Licence Manager support?

l Will Licence Manager work through a firewall?
l What happens when the Licence Manager server fails or stops responding?
l Can I run Licence Manager on a virtual computer?
l How can I check if the Licence Manager Service is installed and running?
l Can I have multiple Licence Manager servers running on the same network?
l What version of Licence Manager do I have?
l Can I install the Licence Manager to the directory c:\ssilm?
Licence Information
l What is the Licence ID?

l Can I update licences on Licence Manager remotely?
l What does the number of available licences mean?
Client Licences
l Why is my token disabled?

l If someone leaves for a long time, can that user tie up a licence by leaving the GEOVIA
program running? For example, the person goes home.
l Can the Licence Manager revoke a licence while the GEOVIA program is processing (for
example, I start a very long dtm intersection function and leave the computer alone to
do its work)?
l If the Licence Manager is on a different subnet from the client, can the client receive a
licence?
Other
l What is a Reverse DNS lookup?

l Can the NetworkLicenceManager.exe utility run from the command line?
Dongle
Do I a need a dongle?
The computer running the Licence Manager server must have a dongle plugged into one of its USB
ports.
The client computers that run GEOVIA programs using a network licence do not need a dongle. This
environment results in a much simpler setup for a multi-licence site because the administrator
maintains only one dongle.
Can the Licence Manager server have more than one dongle plugged in?
No. You should plug in only one dongle into the computer running the Licence Manager server. If

you plug in more than one dongle, Licence Manager might fail to distribute licences correctly.
Can I take a dongle from the Licence Manager server, plug it into a client computer, and start
using it as a local dongle?
If you have a single user licence, then you can use the dongle on the local computer with your single-
user token. The single-user token has 16 digits, whereas the network token has 26 digits. When the
dongle is used to access the single-user licence, network licensing is disabled.

What networking protocols does Licence Manager support?
Licence Manager uses the TCP/IP group of network protocols for communication between client
computers and Licence Manager servers. The amount of network traffic generated by Licence
Manager is minimal (approximately 100 bytes/client every 30 seconds).
Windows platforms require the TCP/IP protocol for networking. You can install TCP/IP using the
Network Connections icon in the Control Panel. Many computers in a network already have TCP/IP
installed. There is no conflict running TCP/IP at the same time as any other network protocol.
Will Licence Manager work through a firewall?

Generally, Licence Manager does not work through a hardware firewall. There are some firewall
products that you can configure to allow Licence Manager traffic through. However, the setup and
maintenance of these configurations is difficult.
GEOVIA does not recommend (nor does GEOVIA support) that you use Licence Manager through a
hardware firewall.
If Licence Manager is installed correctly but fails to issues licences, try temporarily turning off
Windows Firewall. If Licence Manager then successfully issues licences, turn Windows Firewall on
again and add NetworkLicenceManager.exe (in the folder where licence manager is installed) to the
list of program exceptions.
What happens when the Licence Manager server fails or stops responding?
When the Licence Manager server, or the computer running the Licence Manager server, fails or
stops responding, the licences on all client computers lose their network licences. The GEOVIA
program notifies the user that the licence is lost. The user can then obtain a new licence by
connecting to the same Licence Manager server or a different one. The program on the client
computer then continues from the point at which the licence was lost.
If a user cannot regain a licence, the user can still perform some operations, such as saving files,
without a licence. Therefore the user can save any work that was in progress.
Sites can distribute their licences between a number of Licence Manager servers (for example, 20
licences with 2 servers serving 10 licences each). With this type of setup, if one server host becomes
unavailable, the other server can still service requests.
If the computer running Licence Manager has a hardware failure, you can transfer the dongle to
another computer and run the Licence Manager server software on the other computer.
Can I run Licence Manager on a virtual computer?

No. The dongle must be physically plugged in to the licence server computer.

Troubleshooting - Overview Licence Information
How can I check if the Licence Manager Service is installed and running?
You can review the status of the Licence Manager service in the lower right corner of the Status bar of
the Licence Manager window. If the service is installed correctly and running, the indicators in the
Status bar show Started and Running.
You can also check the list of services in the Control Panel.
Can I have multiple Licence Manager servers running on the same network?
Yes. It is possible to have more than one Licence Manager server on the network. Each computer
that has Licence Manager installed requires a dongle and a token number for a specific number of
licences. This type of arrangement is not a mirrored servers arrangement (where all possible licences
can be served by either server when one of the servers becomes unavailable).
When the client program starts, it can either send a broadcast request (to all servers on the local
network segment) or connect to a particular server. When using a broadcast request, more than one
server may respond. Then the client program uses the first licence that is granted receives. The
broadcast requests only work for the local network segment, and generally, do not work between
sites.
What version of Licence Manager do I have?

To view information about the Licence Manager program and its version, choose Help > About.
The About dialog provides version information for both the program and the service. If the versions
of the Licence Manager and the Licence Manager service are not the same, uninstall all versions of
the Licence Manager, and then re-install the most recent version.
If you see the message "No Licence Manager (NetworkLicenceManager.exe) found". Re-install the
most recent version of Licence Manager immediately.
Can I install Licence Manager to the directory c:\ssilm?

You can install Licence Manager to c:\ssilm, but GEOVIA recommends that you install Licence
Manager to a directory with a different name.
In previous versions, installing Licence Manager to c:\ssilm might have caused unexpected issues. As
a result GEOVIA recommends that you follow the Windows convention and install Licence Manager
in a folder with a different name within the C:\Program Files or C:\Program Files (86) directories.
The default directory is: C:\Program Files\Dassault Systemes\GEOVIA
LicenceManager\<versionNumber> for a 32-bit computer or C:\Program Files (x86)\Dassault
Systemes\GEOVIA LicenceManager\<versionNumber> on a 64bit computer.
You can run only a single instance of Licence Manager on a single computer at any one time.
Licence Information
What is the licence ID?
The licence ID has two main uses:
l The licence ID is a unique ID for an individual licence that GEOVIA uses when assisting
customers. The internal licensing system that GEOVIA uses contains all GEOVIA cus-
tomers, and every customer has a list of licences. Each licence is a set of modules and a
number of users who can use the modules. GEOVIA tracks all these licences using a
licence ID.

The licence that the customer sees is not a direct reference to the licence that GEOVIA
has in the customer database. So when a customer experiences issues with a particular
licence, GEOVIA uses the licence ID as the primary method to identify which modules,
the customers have in their classes.
l The Licence ID is used to match licences together when they are in the same class for a
particular version of a product. In a class, there can only be one licence active at any
one time for a licence ID.
For example, in the licence class ENG, there is a licence with the ID 1234 that expires at
the end of the current month. You renew the licence, and GEOVIA support sends you a
new licence with an expiry date at the end of next month. The new licence becomes
active only after the current licence expires.
Can I update licences on Licence Manager remotely?

Yes. To update licences remotely, log on to the computer running Licence Manager remotely, and
update the licences. If a new dongle is required, the dongle must first be attached to the computer
running Licence Manager.
What does the number of available licences mean?

You can generate a report on the available licences using the Reports > Available function. The
following example explains the numbers in the report.
You have 8 users of ProdABC 1.1, but only maintain 4 of the users for ProdABC 2.0. You would then
receive a licence for ProdABC 2.0 for only 4 users. When you run the availability report, you see the
following information:
Two licences for ProdABC 1.1 are being used. When you run the report, you see the following
information:
The number of available users for a GEOVIA program is the maximum of all the available users in all
versions of that program. However, the maximum users for a specific version is determined by the
number defined in the token. In the example, you begin with 8 licences of ProdABC available, but a
maximum of 4 licences could be allocated to users running ProdABC 2.0.
Client Licences
Why is my token disabled?

Troubleshooting - Overview Other
Tokens can be disabled for any of the following reasons:
l the token has been manually disabled

You can disable a token to help diagnose network problems. If a token is disabled
manually, you can re-enable it.
l the token has expired
l the token is not valid
Licence Manager has a licence validation rule that requires all tokens for a particular
program and version to be generated by GEOVIA on the same day. It does not matter
when you install the tokens, but all tokens must be generated on the same day.
As a result, when you update a token (because of a change in modules or other
reason), you must update all tokens for the specific version of the program.
If you do not update all tokens for a program and version, only the tokens that have
the latest creation date are enabled. All other licences are disabled. If this situation
occurs, contact your local GEOVIA support office.
You can check why a token is disabled using the Properties function from the shortcut
menu.
If someone leaves for a long time, can that user "tie up" a licence by leaving the GEOVIA pro-
gram running? For example, if the person goes home.
If a licence has been idle for a specified time, Licence Manager changes the state of the licence to
standby. If any new licence requests are received and there are no free licences, the licences that are
in a standby state are revoked and granted to the client requesting the licence. This means that a
user does not tie up a licence indefinitely while leaving the program idle.
If no other users require a licence, the licence is not revoked, and its state changes to a state other
than standby when the program is active again.
Can the Licence Manager revoke a licence while the GEOVIA program is processing (for example,
I start a very long surface intersection function and leave the computer alone to do its work)?
No. Licences are only revoked if they are in a standby state at the time that a request for a licence
comes from another client computer, and no other licences are available. Licences are changed to a
standby state only when the GEOVIA program is idle for a set amount of time. The program is
considered idle when it has been started, but has had no activity for a particular amount of time.
Processing is an activity, so the licence will not be changed to an idle or standby state while a
function is running.
If the Licence Manager is on a different subnet from the client, can the client receive a licence?
The client does not automatically receive a licence. However, if you use the -lm switch to add the
specific licence server to the shortcut for Surpac or Minex the client will receive a licence.
For example, in the Properties of the Surpac desktop shortcut, in the Target field, add -lm <name or
IP address of the Licence Server> to the end of the current target.
<Surpac Installation Directory>\surpac2.exe -lm licServer
For more information, see Setting Up Surpac or Minex to Use the Licence Server on page 26.
Other
What is a Reverse DNS lookup?

Troubleshooting - Overview Other
Reverse DNS lookup is a process that can cause Licence Manager problems on some network
configurations. In TCP/IP, computers on a network are given an IP address similar to this:
192.100.168.72.
To make these numbers easier to understand, computers are given a name that relates to that
number (for example, FRED). The computer name and the numeric IP address are stored on the
network on a computer called the "Domain Name System" (DNS). A DNS lookup translates the
computer name to the numeric IP address needed to process the request.
When the Licence Manager grants a licence, it returns to the client the numeric IP address of the
server that granted the licence. The client tries to perform a Reverse DNS lookup to find out the
server name from the IP address. When the server name is known, messages related to the user are
output using the server name, not the numeric IP address.
However, on some networks, the reverse DNS lookup is either not possible (due to incorrect or
incomplete network configuration), or it is very slow. In either situation, the client waits for a
response from the server. If the client does not receive a response within a certain amount of time,
the server revokes the licence it just granted. This situation causes problems on some sites.
If you encounter this problem, you can edit the Licence Manager properties to turn off the reverse
DNS lookup.
Can the NetworkLicenceManager.exe utility run from the command line?

Yes. You can use command-line operations to query the Licence Manager server, produce reports, or
simulate a client computer. Users experienced in using command line operations can run requests
from the command prompt to investigate problems with the Licence Manager communication.
When you run the NetworkLicenceManager.exe program with no parameters, you see a summary
of the command-line options. When you run the NetworkLicenceManager.exe program with
parameters, the command passes the directives to the Licence Manager server.
The -client switch is useful for determining if a server is serving licences. When you use this
command, do the following:
1. Start the command prompt.

2. Change the directory to the /bin directory of the Licence Manager installation.
3. Type: networklicencemanager -client "<product name>" <major ver-
sion>.<minor version>
A report of licences granted or refused appears in the command prompt.

Licence Manager glossary Other
Licence Manager glossary

C
client
The client is a GEOVIA program (for example, Surpac, Minex, GEMS, MineSched or Whittle) that is run
on a computer on the network. It is possible for the client to be running on the same computer as the
licence server.
Domain Name System (or Service) (DNS) Server

An Internet service that translates domain names into IP addresses. Because domain names are alpha-
betic words, they are easier to remember. The Internet, however, is based on IP addresses, which are
numeric values. Therefore, every time you use a domain name, a DNS service must translate the name
into the corresponding IP address.
For example, the domain name www.example.com might translate to the IP address 198.105.232.4.
The DNS system is, in fact, its own network. If one DNS server does not know how to translate a par-
ticular domain name, it continues to ask other DNS servers until the correct IP address is returned.
dongle/sentinel
Hardware lock device that plugs into the server computer, in order to run the Licence Manager. The
dongle can be either a parallel device or a USB device.
Dynamic Host Configuration Protocol (DHCP)

The protocol for assigning dynamic IP addresses to devices on a network. With dynamic addressing, a
device can have a different IP address every time it connects to the network. On some systems, the IP
address for the device can even change while it is still connected. DHCP also supports a mix of static
and dynamic IP addresses.
Dynamic addressing simplifies network administration because the program keeps track of IP addresses
rather than requiring an administrator to manage the task. This means that a new computer can be
added to a network without the difficulty of manually assigning it a unique IP address. Many Internet
Service Providers use dynamic IP addressing for dial-up users.
dynamic IP address
An IP address that is assigned to a computer using DHCP. This IP address can change each time the com-
puter connects to the network or even during a network connection.
Internet Protocol (IP) Address

A unique number consisting of four parts separated by dots, for example, 165.113.245.2. Every com-
puter that is on the Internet has a unique IP address. If a computer does not have an IP address, it is not
really on the Internet. Most computers also have one or more Domain Names that are easier for
people to remember.
licence class, class

A licence class is the name of a group of modules of functionality for a GEOVIA program. Users request
and receive a particular licence class from Licence Manager, and they can then use the functionality
that the modules of that class provide .

licence ID
A unique ID for an individual licence. The licence ID identifies the modules allowed for that licence, and
the class name assigned to that licence, if there is one.
Licence Manager
Licence Manager refers to the NLMAdmin.exe that is found in the bin directory after successfully
installing the program. Originally, the file name for Licence Manager was ssilm.exe. Common usage has
found that the term SSILM has been moderately corrupted and people often pronounce it as slim or
the slim. Licence Manager is the same thing as GEOVIA Licence Manager.
Licence Manager Control Panel

The Licence Manager installation includes an administration utility that simplifies the configuration and
management of licences for the licence server.
LICZ file
The LICZ is a zip file with a .licz extension that contains the licensing information.
In case of network licensing, this file contains .udt file, GEOVIA License Summary.pdf file, and licensing
file if any. You can add this file to Licence Manager to make the licences associated with those tokens
available to you on the local area network, or extract files locally and use the .udt file as used earlier.
In case of roaming license, this file contains GEOVIA License Summary.pdf file and licensing file. You
can use this file as a licensing file, or extract its contents locally and use the licensing file as used earlier.
module
A module is a group of functions and commands for a specific functional area of a GEOVIA program. For
example, your organization purchases a licence to run the Block Modelling module in Surpac. The func-
tions and commands that you need for working with block models area available with the purchase of
the module.
Network Licence Server (NLS)

The Network Licence Server refers to the NLMAdmin.exe program that is running and the computer
on which it is running on the network. The licence server is installed as a service on the computer and
responds to licence requests from clients running on other computers on the network.
port
In TCP/IP and UDP networks, different styles of network traffic and different programs 'listen' on dif-
ferent ports. A port is analogous to a TV channel. To receive information, you must be tuned correctly.
Therefore, if a licence server instance is listening on the default "1234", then all clients trying to con-
verse with this server also have to be using the same port. The port number can often identify what
type of port it is. For example, port 80 is used for HTTP (Web) traffic.
sentinel/dongle
Hardware lock device that plugs into the server computer, in order to run the Licence Manager. The
dongle can be either a parallel device or a USB device.

service
A service is a special class of program that exists on Windows computers. Generally, the service is star-
ted each time the computer starts up and the service runs until the computer is turned off. Even when
you log out of a session at the computer, the services continue to run. For Licence Manager, the
Licence Manager service must be running at all times to service licence requests from client com-
puters.

static IP address
An IP address that is fixed and never changes. This is in contrast to a dynamic IP address, which can
change at any time.
Transmission Control Protocol (TCP), TCP/IP

Pronounced as separate letters, TCP is one of the main protocols in TCP/IP networks. Whereas the IP
protocol deals only with packets, TCP enables two hosts to establish a connection and exchange
streams of data. TCP guarantees delivery of data and also guarantees that packets are delivered in the
same order in which they were sent.
token, licence token

A token, also called a licence token, is a hexadecimal number, in two parts, separated by a hyphen. This
hexadecimal number is a sequence of at least 24 numbers or letters (a to f). When you add a token to
Licence Manager, Licence Manager makes available on your local area network, one or more licences
to use specific modules of GEOVIA programs. If the token is delivered in a .udt file, you can add a token
automatically. Or you can type in the details from an HTML file.
If the number contains letters other than a, b, c, d, e, or f, a mistake has been made. For help, contact
your local GEOVIA support office, or go to www.GEOVIAsupport.com.
tokens file
The tokens file (ssilm.tok) is the file that the Licence Manager server uses to save licences. The inform-
ation in the tokens file includes tokens that you have entered and licence classes that you have created
in Licence Manager.
UDP
The Universal Datagram Packet (UDP) port number to use for two-way communication between the cli-
ent and server processes. Ideally, you use the default port value of 1234 unless it conflicts with another
application that is using the default port number. If you use a different port number, it is essential that
you add the -lm switch to the desktop shortcut for the client program. For example, for the Surpac
desktop shortcut, "<Surpac Installation Directory>\surpac2.exe" -lm licServer.
UDT file
An update token (UDT) file is a file with a .udt extension that contains one or more licence tokens. You
add a .udt file to Licence Manager to make the licences associated with those tokens available to users
on the local area network. By adding a .udt file, you can make modules available to users for a period of
time. When the expiry date on the token has passed, those modules are no longer available.

Licence Manager

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Licence Manager

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Licence Manager

Uploaded by

Copyright:

Available Formats

Copyright © 2019 Dassault Systèmes GEOVIA Inc.

l manage the use of various GEOVIA programs

l usage of various classes of licences

l the usage of functions within GEOVIA program

l revoke licences for specified users

Licence Manager Service

Licence Manager Permissions

GEOVIA Licence Manager™ 14.9.4 Page 6 of 61 Complete Reference Guide

The Licence Manager server computer must have:

l a hardware dongle for Licence Manager

l Windows Server 2008

l Windows Server 2012

l the TCP/IP networking protocol installed

l excessive delays in the licence server responding to and granting licence

l the dongle driver software installed

The network must have one of the following:

All client computers running GEOVIA programs must have:

l the TCP/IP networking protocol installed

GEOVIA Licence Manager™ 14.9.4 Page 7 of 61 Complete Reference Guide

GEOVIA Licence Manager™ 14.9.4 Page 8 of 61 Complete Reference Guide

Licence Manager Concepts

l Licence Types on page 9

GEOVIA Licence Manager™ 14.9.4 Page 9 of 61 Complete Reference Guide

Licence Manager Folder Paths

GEOVIA Licence Manager™ 14.9.4 Page 10 of 61 Complete Reference Guide

C:\Users\Public\GEOVIA\LicenceManager\share\etc for the following operating systems: Windows

GEOVIA Licence Manager™ 14.9.4 Page 11 of 61 Complete Reference Guide

Setting Up the Licence Manager Server

1. Install Licence Manager from the GEOVIA installation disc.

Downloading Licence Manager Installer

GEOVIA Licence Manager™ 14.9.4 Page 12 of 61 Complete Reference Guide

Upgrading Licence Manager

GEOVIA Licence Manager™ 14.9.4 Page 13 of 61 Complete Reference Guide

Installing Licence Manager

5. Continue clicking Next in the wizard, making the following changes:

to be installed on the local hard drive

GEOVIA Licence Manager™ 14.9.4 Page 14 of 61 Complete Reference Guide

Starting Licence Manager

l Double-click the desktop icon

Adding or Updating Licences Using Self-Service Licensing

1. Insert the GEOVIA dongle into a port on the computer.

GEOVIA Licence Manager™ 14.9.4 Page 15 of 61 Complete Reference Guide

b. Click Request licence.

d. Save the .licz file to a local folder.

GEOVIA Licence Manager™ 14.9.4 Page 16 of 61 Complete Reference Guide

9. Select the boxes for the tokens you want to update.

GEOVIA Licence Manager™ 14.9.4 Page 17 of 61 Complete Reference Guide

11. Save the changes to the tokens file.

Adding and Updating Tokens

l Adding or Updating Licences Using Self-Service Licensing on page 15

GEOVIA Licence Manager™ 14.9.4 Page 18 of 61 Complete Reference Guide

Add or Update Tokens Using a .udt File

4. Choose Service > Stop.

GEOVIA Licence Manager™ 14.9.4 Page 19 of 61 Complete Reference Guide

9. Select the boxes for the tokens you want to update.

11. Save the changes to the tokens file.

Adding or Updating Tokens Using an HTML File

GEOVIA Licence Manager™ 14.9.4 Page 20 of 61 Complete Reference Guide