Schlumberger Licensing User Guide
Schlumberger Licensing User Guide
Schlumberger Licensing User Guide
User Guide
Proprietary notice
Copyright (c) 2013 Schlumberger. All rights reserved. Reproduction or alteration without prior
written permission is prohibited, except as allowed under applicable law.
Use of this product is governed by the License Agreement. Schlumberger makes no warranties,
express, implied, or statutory, with respect to the product described herein and disclaims without
limitations any warranties of merchantability or fitness for a particular purpose.
Trademarks & service marks
"Schlumberger," the Schlumberger logotype, and other words or symbols used to identify the
products and services described herein are either trademarks, trade names, or service marks of
Schlumberger and its licensors, or are the property of their respective owners. These marks may
not be copied, imitated, or used, in whole or in part, without the express prior written permission of
their owners. In addition, covers, page headers, custom graphics, icons, and other design
elements may be service marks, trademarks, and/or trade dress of Schlumberger and may not be
copied, imitated, or used, in whole or in part, without the express prior written permission of
Schlumberger.
Table of Contents
About Schlumberger Licensing ....................................................................................... 1
The Schlumberger Licensing Tool ........................................................................................................... 2
License Server Quorum ............................................................................................................................. 3
Setting up a Quorum ................................................................................................................................. 3
Supported Platforms for Licensing .......................................................................................................... 4
Support for HASP Dongle Licenses .......................................................................................................... 4
ii
The license above is for Petrel, has an expiry date of August 9 2014, and allows one concurrent
user to run the application.
If you install Schlumberger licensing on Windows, Schlumberger provides a licensing tool that is
installed at the same folder as the FlexNet license server and associated utilities.
Note: The Schlumberger License tool is intended as a single user tool for use on a Windows
Desktop PC. It may work on Windows Server Platforms, however it does not support multiple users
setting up a license server on the same machine. If there is a need for multiple users to be able to
access and control the license server we recommend the use of a single shared administrator
account.
The upper panel is used for adding and removing license files, and starting or stopping the local
license server.
The lower panel is used to configure the user environment and check if licenses are available,
both locally and on other servers.
If you may have many Schlumberger products on your system, the Licensing tool is the
recommended management method because it will let you use multiple license files with different
hostids, something that is not possible with lmtools, the standard FLEXnet license administration
tool.
Note: With the Licensing tool the only logging option available for logging users and modules is the
Flexlm debug log.
Using the Licensing tool does not preclude running other Flexlm/FlexNet licenses on your system
from other vendors using the standard Flex tools like lmtools. The standard administration tools for
FlexNet license servers are installed along with Schlumberger Licensing. You can find out more
information about these tools in the FlexNet End User Guide.
Setting up a Quorum
Setting up is much the same as setting up three servers individually. However, in addition to
requiring three servers, the quorum must also be setup on a reliable local network. This
functionality does not work well over slow or large latency links.
The Schlumberger License Tool is not able to install quorum licenses, so they must be setup by
hand. The lmtools program can be used, and can be found in the following location if the
Schlumberger License Tool has been installed:
C:\Program Files (x86)\Schlumberger\Schlumberger Licensing\20XX.X
Note: An expired license can cause a quorum to shut down under the following conditions.
The expired licenses contain unsupported characters such as "/" and "-".
To avoid this, move everything on to one type of host (either MAC or dongle), or separate the
servers to two quora.
To setup a license server quorum, follow the instructions from Flexera Software
Windows Vista64
Windows 7 64-bit
Windows 8 64-bit
Linux
Red Hat Enterprise Linux Server version 5 Update 1 or later (x86_64).
Note: Only command line utilities are available of Linux platforms, there is no licensing user
interface.
Managing Licenses on
Windows
Installing the Licensing Software
1. If you are installing the license tool as part of installing another Schlumberger application, click
Install SLB Licensing on the Schlumberger panel. Alternatively, navigate to 3rdparty\PC
\resource\Slblicensing and double-click SlbLicenseInstallerXXX.exe
2. When the installation wizard opens, follow the instructions clicking Next on each window to
proceed.
3. By default, the licensing server is installed into C:\Program Files\Schlumberger
\Schlumberger Licensing\2013.1. To change the installation location, in the Destination
Folder window, click Change, select your preferred location and click Next.
4. In the Ready to Install the Program window, click Install, and when installation has completed
click Finish.
In the configuration tool you should now see that your license file has been added to the list of
license files. If you want the license to be automatically available every time you restart your
computer, select Start Automatically with Windows.
4. Click Start to launch the license service. Then click on OK to apply the changes.
At the bottom of the window you will see that the license server is set to @localhost This is the
address that the application will use when trying to find licenses. With this setting it will look for the
license on your local computer. You do not need to make any changes to this as long as you have
just a local license server.
To verify that a license is available you can click Status. This will show you which licenses are
available and if there is a problem with any of the license features.
If there is a problem with any license feature, click Diagnostics to get more information. This will
list the license file(s), information about the license server and enable access to the FlexNet debug
log file.
The Troubleshooting appendix describes known issues that may be encountered, and their
solutions. If you cannot solve the problem and you need to contact Schlumberger support, please
always send the contents of the diagnostics to the support.
See also:
License files are managed through the Local license server (p.7) panel.
Connections to external license servers are managed through the All license servers (p.8)
panel
Start
Starts the license server on your local computer.
Stop
Stops the local license server.
Reread
Reinitializes the licenses running on the local license server without stopping the license
server. This can be used, for example, if have edited your license file and want to update
the server.
Request
Shows all the host IDs on the system and each text box displays the following:
Flex dongle or HASP dongle ID rarely used, except for older applications.
Click Request license via email (Outlook only) to format an email that you can send to
your license administrator or account manager. You can also click Copy to copy the
information into clipboard.
Diagnostics
Shows the various settings on your machine related to FlexNet. The Diagnostics window
shows the following information:
Use the text box next to the magnifying glass to search for a string within the diagnostic
log.
Click Open flex log to display the flex log to which your local license server writes
information. The information found in the diagnostics is very useful for locating the source
of any problem. If you require support for the license server, this information should be
supplied to Schlumberger support.
License Servers
This panel shows all the license servers you wish to access for licenses for different Schlumberger
products. The panel shows the available servers set using the SLBSLS_LICENSE_FILE
environment variable. Other environment variables can be configured through the Advanced
Options dialog, see Environment Variables to Set (p.10) for more information.
If you wish to add a license server, this can be done by typing port@servername into the
highlighted box and then clicking on the Add license server button. If you wish to remove a
license server, highlight the server and click on Remove license server.
Important: This will only remove the server from the user environment variable; if you wish to
remove the system variable, you must do so manually.
Some applications require the license server that they are checking out from to be the first in a long
list of license servers, to do this, highlight the server that the application will be checking a license
out from and click on the up arrow to move it to the top of the list.
Add license server
Adds a new server from which licenses can be drawn.
Remove license server
Removes the selected license server from the list of servers provided licenses.
Status
Shows which licenses are available from the servers in the license server list.
The text box next to the magnifying glass allows you to search for a string within the log by
clicking on the magnifying glass button. The Open flex log button will display the file that
the local license server writes its output to.
Read all server paths
Uses all the license servers in the panel.
Only read first server path
Only use the first line of servers in the panel.
Only read second server path
Only use the second line of servers in the panel.
OK
Saves the changes made and closes the Schlumberger License tool.
Cancel
Closes the Schlumberger License tool without saving any of the changes made.
Apply
Saves the changes made, but does not close the Schlumberger License tool.
Settings tab
Environment Variables to Set
Sets the user environment variable to which external license server information is added.
You should select the appropriate variable for the application for which you require a
license:
If a system variable of the same name is set, the user environment variable overrides the
system variable settings. If the variable is changed, the license servers panel is updated to
reflect that environment variable. To remove the content of the user environment variables,
select the variable and click Remove variable.
CAUTION: It is strongly recommended that you do not use the LM_LICENSE_FILE
variable; this variable could be used by all applications using the FlexNet license server,
including non-Schlumberger applications.
Log File Settings
Determines whether to append to, or overwrite, the existing log file every time license
server starts.
The Log file path is the directory in which license server log files are stored. Click Browse
to change the log file path, and click Remove old diag file to delete the existing flex
debug log files.
Note: You must stop the license server to make any changes to the log file settings.
Diagnostics settings
Sets the location where diagnostic files are stored. Click Remove old diag file to remove
all diagnostic files.
These diagnostics files provide useful information for Schlumberger support in the event of
any problems.
CodeMeter settings
Note: The CodeMeter detector can only be used with a local license service using the
Schlumberger Licensing tool.
10
Select Install CodeMeter detector to install the CodeMeter detector service. The service
detects whether a CodeMeter dongle is plugged in, and will perform a reread on the local
license server so that any licenses connected to the dongle will be enabled for checkout.
Use Update CodeMeter dongle times to update the time on all CodeMeter dongles. This
may resolve problems when you see errors in the flex log file indicating that the daemon
cannot get the CodeMeter dongle ID. Your computer will need an Internet connection in
order to be able to update the time on the CodeMeter dongles.
License usage settings
Determines the type of license used by the local license server:
Folder - the license server uses all license files in a specified folder. If this option is
selected, license files must use a .lic.
If Check hostID is selected, the license tool will verify that the hostID in any new license
file is valid for the server.
Note: You must stop the license server to make any changes to the license usage
settings.
Vendor Port settings
Sets the port on the VENDOR line in all license files, this may improve performance in
checkouts when the user points directly to the VENDOR port.
Note: If you set one of the environment variables to point directly to the vendor daemon,
quorum and lmstat functionality will not work.
Reread or stop/start the license server to configure the license server to use the vendor
port.
11
Reset tab
This tab allows you to remove FlexNet license settings from your machine.
Clear SIS License Settings
Removes the User and System variables and registry entries for the Schlumberger
SLBSLS_LICENSE_FILE, CLBFD_LICENSE_FILE, and LMGRD.SLB_LICENSE_FILE
license variables.
Clear LM_LICENSE_FILE License Settings
Removes the User and System variables and registry entries for the LM_LICENSE_FILE
license variables.
CAUTION: The LM_LICENSE_FILE is the default license file for the FlexNet server.
Deleting this file may affect all applications that use this FlexNet server for licensing.
12
CodeMeter drivers version 4.50 or later, available on the installation disc or can be downloaded
from WIBU systems.
Note: If you are using the CodeMeter drivers for dongle licenses you may need to restart the
server following installation.
13
If this command finds any scripts containing the string lmgrd, the name will be shown on the
screen.
5. Once you find the script move it to /tmp using the following command:
mv <filename> /tmp
3. If you are installing the CodeMeter Runtime, go to the directory into which the package was
extracted, for example:
cd flex11.8
4. Copy the CodeMeter Runtime rpm package from the software DVD, or download the
appropriate package from the WIBU systems website (http://wibu.com/download_user.php) into
this location.
5. Extract the runtime using the following command:
rpm -ivh CodeMeter64-4.X-XXX.x86_64.rpm
14
When altered, the file should look something like the following. The change has been made to the
second line of the file:
SERVER this_host 0123456789
VENDOR slbsls
USE_SERVER
INCREMENT gasfield slbfd 2006.0 1-jun-2006 1 SUPERSEDE=gasfield \
NOTICE="0738198 A2GF-P1" START=12-jun-2006 AUTH={ slbfd=( \
SIGN="003E 9B74 A1DC 645B D177 B400 A079 E400 1D40 09BC 2C27
9800 B0AE DA4B FC48") lmgrd_slb=( LK=7689E5620621 SIGN="008D\
3799 4265 25A4 25C5 DA12 534D A800 4331 A349 9740 7B86 36BF \
A613 FBF6" SIGN2="00F9 B765 0F28 3BEE 6179 6718 22C7 0D00 B1E0 \
7030 1CEB B59E D3CB D5C8 E569") }
All license files need to be updated with the VENDOR change, and saved into a common directory.
Replace the phrase this_host with the name of the license server.
4. Create links in both the /etc/rc3.d and /etc/rc5.d folders so the script is run at system
startup.
15
Change to the appropriate directory (for example /etc/rc3.d) and create a link.
cd /etc/rc3.d
ln -s /etc/init.d/slbslsflexstart S99slbslsflexstart
If the server has started successfully, a log file called /tmp/flex.log will be generated containing
information similar to that shown below. If any problems are encountered during operation or
startup, these are also output to the log file.
20:41:34 (lmgrd) FLEXnet Licensing (v11.8.0.1 build 19446) started on abgkickstart (linux) (7/13/2006)
20:41:34 (lmgrd) Copyright (c) 1988-2005 Macrovision Europe Ltd. and/or
Macrovision Corporation. All Rights Reserved.
20:41:34 (lmgrd) US Patents 5,390,297 and 5,671,412.
20:41:34 (lmgrd) World Wide Web: http://www.macrovision.com
20:41:34 (lmgrd) License file(s): /ecl/macros/license.dat
20:41:34 (lmgrd) lmgrd tcp-port 1700
20:41:34 (lmgrd) Starting vendor daemons ...
20:41:34 (lmgrd) Started slbsls (internet tcp_port 51231 pid 10394)
20:41:34 (slbsls) FLEXnet Licensing version v11.8.0.1 build 23943
20:41:34 (slbsls) Server started on abg-kickstart for: co2seq
20:41:34 (slbsls) cougar_multiresponse fs_patternbalance cougar
20:41:34 (slbsls) prodopt waterservices r2sl_gap
20:41:34 (slbsls) r2sl_tanks r2sl_lookup resopt
20:41:34 (slbsls) uncertainty multiple_realisation cbm_template
20:41:34 (slbsls) cmt_template h2o_template hf_template
20:41:34 (slbsls) coalbed compositional datacheck
20:41:34 (slbsls) eclipse eclipse4d eclipselite
20:41:34 (slbsls) flux foam friction
20:41:34 (slbsls) frontsim fs_iorscale gasfield
20:41:34 (slbsls) gaslift gasquality geomechanics
20:41:34 (slbsls) gf_fg_analysis gf_fg_openspirit gf_fg_populate
20:41:34 (slbsls) gf_flogeo gf_flogrid gf_floviz
20:41:34 (slbsls) gf_petragrid gf_scal gioption
20:41:34 (slbsls) graf grid gridsim
20:41:34 (slbsls) lgr multisegwells nearwellborem
20:41:34 (slbsls) networks office openeclipse
20:41:34 (slbsls) parallel planopt polymers
20:41:34 (slbsls) pvt rescoupling schedule
20:41:34 (slbsls) simopt simopt4d solvents
20:41:34 (slbsls) surfactant thermal tracer
20:41:34 (slbsls) unencodedhmd vfp sma
20:41:34 (slbsls) proppantflow WELLTEST weltest200
20:41:34 (slbsls) r2sl
20:41:34 (lmgrd) slbsls using TCP-port 51231
20:41:34 (slbsls) Serving features for the following vendor names:
slbsls slbsls lmgrd_slb
16
Troubleshooting /FAQ
The following are known issues and lists some useful tips and information.
Performance Issues and Incorrect License Counts Caused by Mixed MAC (hostid) and Dongle
Licenses (p.17)
Wrong hostid on SERVER Line for License File: with CodeMeter Dongle (p.18)
17
This problem occurs when the Visual Studio runtime is not installed. Solution is to install it from the
Microsoft download site (http://www.microsoft.com/).
This occurs if the dongle is not plugged in or the time needs to be updated on the dongle. See
CodeMeter settings. (p.10).
18
19
DEBUGLOG
DEBUGLOG [+]debug_log_path
Specifies a location for the debug log output from the vendor daemon associated with this
options file. To append log entries rather than overwrite the file every time the daemon
starts, place a + character before the debug_log_path
Note: This only affects output from the vendor daemon associated with this options file.
The debug log output of lmgrd and any other vendor daemons in the same license file is
not captured in this file.
On Windows, path names which include spaces have to be enclosed in double quotes. If
lmgrd is started as a service, the default location for the report log file is the C:\winnt
\System32 folder unless a fully qualified path is specified.
EXCLUDE
EXCLUDE feature[:keyword=value] type {name | group_name}
Excludes a user or predefined group of users, etc., from the list of who is allowed to use
the feature. EXCLUDE supersedes INCLUDE; conflicts between the EXCLUDE list and
the INCLUDE list are resolved by the EXCLUDE taking precedence.
feature
keyword=value
type
name
group_name
For example, to exclude the user "hank" from the list of users able to use feature "f1":
EXCLUDE f1 USER hank
INCLUDE
INCLUDE feature[:keyword=value] type {name | group_name}
Includes a user or pre-defined group of users, etc., in the list of who is allowed to use
licenses for this feature. Anyone not in an INCLUDE statement is not allowed to use that
feature. EXCLUDE supersedes INCLUDE; conflicts between the EXCLUDE list and the
INCLUDE list are resolved by the EXCLUDE taking precedence.
feature
keyword=value
type
20
name
group_name
For example, to include user "bob" in the list of users able to use feature "f1":
INCLUDE f1 USER bob
Sets the time after which an inactive license is freed and reclaimed by the vendor daemon
Note: The vendor must have enabled this feature in the FlexNet enabled application for it
to work. Contact your software vendor to find out if this feature is implemented. The vendor
must have enabled this feature in the FlexNet enabled application for it to work. Contact
your software vendor to find out if this feature is implemented.
feature
keyword=value
seconds
For example, to set the timeout for feature "f1" to one hour (3600 seconds):
TIMEOUT f1 3600
TIMEOUT checks in the licenses if the FlexNet enabled application has been inactive for a
period longer than the specified time period. The daemon declares a process inactive
when it has not received heartbeats from it; whereas, an active FlexNet enabled
application sends heartbeats.
A TIMEOUT line must be present in the options file in order to take advantage of the
vendor-enabled timeout feature.
The minimum timeout that can be set is 900 seconds.
TIMEOUTALL seconds has the same functionality as TIMEOUT, but applies to all
features.
REPORTLOG
This specifies a path where the binary file will be created. This binary log file is used by the
PPU service.
21
Label
----0
1
4
2
5
13
11
12
3
Prefix
-------------------------------::1/128
::/0
::ffff:0:0/96
2002::/16
2001::/32
fc00::/7
fec0::/10
3ffe::/16
::/96
The above table shows the default entries for Windows 8, and the line ending /128 means that
IPv6 is the default. To change to IPv4, a registry key needs to either be created or edited if it
already exists.
Note: Always backup any data and edit the registry with extreme caution.
The registry key you need to create is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters
\DisabledComponents
If this is not currently set, create the dword key with a hex value of 20. If the key already exists,
add 20(hex) to the current setting. Once updated, you will need to reboot to make the setting
active.
You can find more information about IPv6 in Windows on the Networking and Access Technologies
section of Microsoft TechNet.
22
If the message is displayed, you can click OK and ignore the message as it has no effect on the
upgrade or uninstall process.
If the license server fails to start and shows a status 123 error in the log, it is likely there is a
problem with the runtimes on the system.
1. Uninstall Schlumberger Licensing.
2. Delete the following files:
C:\Windows\syswow64\msvcp100.dll
C:\Windows\syswow64\msvcr100.dll
23
3. Right-click Schlumberger License Server, select Properties, and set the Startup type to
"Automatic (Delayed Start)."
24