You are on page 1of 85

RISA Installation and Licensing

General Reference Manual
Last Revised 4/23/2013

26632 Towne Centre Drive, Suite 210
Foothill Ranch, California 92610
(949) 951-5815
(949) 951-5848 (FAX)
www.risa.com

Copyright 2013 by RISA Technologies, LLC All rights reserved. No portion of the contents of
this publication may be reproduced or transmitted in any means without the express written
permission of RISA Technologies, LLC.

We have done our best to insure that the material found in this publication is both useful and
accurate. However, please be aware that errors may exist in this publication, and that RISA
Technologies, LLC makes no guarantees concerning accuracy of the information found here or
in the use to which it may be put.

Table of Contents

Table of Contents
Before You Begin
System Requirements
Standalone Installation Instructions

1
1
2

Limiting the Number of
Commutable Licenses
Network Client Install

36
37

Where to get the Install

2

Where to get the Install

37

Installation Instructions

2

Installation Instructions

37

Check for Updates

16

Installation Options

17

Standalone Licensing

18

Launching the RISA Product

18

Removing the Key

18

Remote Desktop

19

Network Server Installation Instructions

20

Installing From a CD

20

Installing from an E-mail Link

21

License Service Updater

28

Sentinel Service Overview

28

License Service Updater

28

Configuring Software Licensing on the Client
41
Performing a Silent Client Installation Using
the SETUP.INI File
42
Performing a Silent Install Using the
Setup.ISS File
Network Licensing

43
46

Launching the RISA Product on a Client
Machine

46

Pointing a Client Machine to a License
Server

46

Losing Network Connection

47

License Commuting

49

Local Commuting

49

Remote Commuting

50

Returning Commuted Licenses

54

Sentinel Service

30

Compatibility

30

Loading (Adding) the Sentinel Service

30

Unloading (Removing) a Sentinel Service

30

Initializing the Program for Commuted
Licenses

56

31

Cleansing a Commuted License

56

License Administration

Loading (Adding) a License File Using the
Sub-Net Server Tree
31
Loading a License Using the Defined Server
List
32
Server Information

33

Feature Information

33

Detailed Information

33

Trouble Shooting License Administration

34

Advanced Network Features

35

Usage Reports and License Monitoring

35

Reserving Licenses for Specific Clients

36

General Reference Manual

Sentinel USB Key

57

Key Driver

57

SSD Cleanup

58

RISA Key Manager

59

RISA Key Manager Shows up Blank

59

Uses For the RISA Key Manager

60

Demonstration Mode
Launching in Demo Mode
Appendix A - Licensing Error Messages

63
63
64

Appendix B - Network Installation Error Messages
73

I

Table of Contents

II

Appendix C - Standalone Installation Error
Messages

77

Technical Support

79

RISA Licensing

Note l l l You can not have multiple versions of the Sentinel license manager service on a single server. Thus.5. Before you install this software please review the following system requirements below: System Requirements Standalone / Network Client Operating System Requirements One of the following operating systems is required: l l l l Microsoft Microsoft Microsoft Microsoft Windows Windows Windows Windows 8 (32 bit or 64 bit) 7 SP1 (32 bit or 64 bit) Vista SP2 (32 bit or 64 bit) XP SP3 (32 bit only) Network Server Operating System Requirements One of the following operating systems is required: l l l l l l l l Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Windows Windows Windows Windows Windows Windows Windows Windows Server 2012 Server 2008 R2 SP1 Server 2008 SP2 Server 2003 SP2 8 (32 bit or 64 bit) 7 SP1 (32 bit or 64 bit) Vista SP2 (32 bit or 64 bit) XP SP3 (32 bit only) License Manager Requirements RISA requires and provides the Sentinel RMS 8. nearly all other software that uses the Sentinel license manager can be run from the RISA customized version. RISA uses a customized version of the Sentinel RMS 8.Before You Begin Before You Begin Thank you for purchasing RISA Software. General Reference Manual 1 .1 license management service. to run RISA on your server you must install RISA's license manager. However. or the license manager will not properly work.1 license manager in the installation.5. If you are running an older version of the license manager then you will be prompted to update using the License Server Update utility. There is one license manager called Sentinel HASP that can be run concurrently with RISA's customized license manager.

If you misplace this CD and are still under maintenance. Note: l Our FTP site is always updated to only contain the most recent installations. Insert the install CD into your CD drive.Standalone Installation Instructions Standalone Installation Instructions These instructions are intended for the standalone versions of the software. If the CD does not start automatically after 10 seconds. therefore. RISA Technologies will automatically send you each new major update on an installation CD and a red sheet which lists your RUS Password for updating the key authorization. Make sure that your Sentinel USB key is unplugged during the installation process. please see the Network Server Install and the Network Client Install topics.com) for a link to the full version installation link. If the CD starts automatically. Where to get the Install If you are current with your maintenance. The minor updates (third digit updates) are not automatically mailed out. 2. we can only email you an installation link for the most current version.com to request an installation link and RUS Password. which we can email you right away. Below are the step-by-step instructions for both. go to step #3 below. RISA Technologies does not keep updates available for older versions. Installing from the CD 1. Note: l You must be an Administrator on the machine in order to run this install. Installation Instructions The Standalone install will walk you through each step. but are uploaded to our public website and are therefore available for anyone to install as long as you have the previous major update already installed. If you have a network license. You may run this install from the CD or from the email link that our licensing department has sent you. you can always email our licensing department (license@risa. Doubleclick the RISA icon: 2 RISA Licensing . If you do not have the previous version installed. you can also contact license@risa. click the Windows Start button and select My Computer.

Standalone Installation Instructions 3. Select the Standalone option: General Reference Manual 3 . Click on Install Products: 4.

Accept the terms of the license agreement and click Next again: 4 RISA Licensing .Standalone Installation Instructions 5. From the Welcome screen. click Next: 6.

RISA-3D or RISAFloor installations.Standalone Installation Instructions 7. The following Default Region Setting dialog only occurs for RISA-2D. 8. If you are running one of these installations select your Region. and click Next. then continue onto number 8 below to via the next dialog. If not. Click Next to accept the default installation destination and continue the installation: General Reference Manual 5 .

Standalone Installation Instructions 9. If you have a previous version installed. Click Yes to continue. 10. you will get the following dialog that confirms the upgrade. Click Next: 6 RISA Licensing .

Click Next and the installation will proceed. Make sure your Sentinel USB key is unplugged and click OK. General Reference Manual 7 . or Back to change the previously entered settings:: 12.Standalone Installation Instructions 11.

Standalone Installation Instructions This will automatically launch the Sentinel System Driver Installer that will install the key driver. - 13. After the installation is complete. and then click Finish: 8 RISA Licensing . check the box to have the installation routine check RISA's website for available updates.

15. startup your RISA program and plug your Sentinel USB key back in. 2. it will ask you for your RUS Password. Now. Enter the RUS Password and click Upgrade: 16. Now you are ready to use the program.Standalone Installation Instructions 14. If you have not already updated your key through the RISA Key Manager. Installing from an Email Link 1. Click on the link from our email and go to the FTP Installation webpage: General Reference Manual 9 . Make sure that your Sentinel USB key is unplugged during the installation process.

From the Welcome screen. If you receive a Security Warning. click Run again to continue with the installation: 5. Click on the Standalone installation file and select Run: 4.Standalone Installation Instructions 3. click Next: 10 RISA Licensing .

Standalone Installation Instructions 6. Select your Region and click Next: General Reference Manual 11 . Accept the terms of the license agreement and click Next again: 7.

If you have a previous version installed. Click Next to accept the default installation destination and continue the installation: 9. you will get the following dialog that confirms the upgrade.Standalone Installation Instructions 8. 12 RISA Licensing . Click Yes to continue.

Click Next: 11. Click Install: General Reference Manual 13 .Standalone Installation Instructions 10.

Standalone Installation Instructions 12. 14 RISA Licensing . This will automatically launch the Sentinel System Driver Installer that will install the key driver. Make sure your Sentinel USB key is unplugged and click OK.

Enter the RUS Password and click Upgrade: General Reference Manual 15 . it will ask you for your RUS Password. Now. startup your RISA program and plug your Sentinel USB key back in.Standalone Installation Instructions - 13. After the installation is complete. 15. If you have not already updated your key through the RISA Key Manager. select Yes to check for program updates and then click Finish: 14.

Check for Updates The Check for Updates feature will compare the installed version on your computer to the most current update listed on our RISA Technologies website.Standalone Installation Instructions 16. 16 RISA Licensing . Simply go to Help . You can also access this feature from within the RISA program. it will offer you the option to open your Internet Explorer to our Updates page where you can download the install. Now you are ready to use the program. If it finds a newer version.Check for Updates to run this feature from within your program.

During use of the RISA program. all features will be installed. databases. and load combinations show up in the program. so by default it is installed into the C:\RISA folder which has less permissions restrictions than Program Files. the program will need to read from and write to this folder. you will have the additional step to select which features you want to be installed. Program Folder This selection controls which folder the program will show up under in the Windows Start menu.Standalone Installation Instructions Installation Options In general. Destination Folder This setting controls what folder your program files are installed into. and load combinations to also update. 99% of users will want to use the default installation options. Overwrite Existing Defaults If you change the region from a previous install and want all the default codes. General Reference Manual 17 . If you select Custom. each option is described below for the more advanced users: Region This setting controls what default design codes. Custom Install This setting controls what features are going to be installed. However. If you select Complete. shape databases. please select the Overwrite Existing Defaults option. This will delete and replace all the previously installed default files. Complete vs.

Removing the Key RISA Products periodically check to ensure that the Sentinel USB Key is plugged in. Clicking the No button on the dialog box displayed above will automatically save the file (overwriting the previous version of the file) and exit the program immediately.Standalone Licensing Standalone Licensing RISA standalone products use a Sentinel USB Key for licensing. In order to run a RISA product the key must be plugged in at all times. Removing the Sentinel USB Key during the operation of a RISA standalone product will eventually cause the following dialog box to be displayed: Once this dialog box is displayed. no additional work may be done within the RISA Product until the key is inserted. This key allows the owner to install RISA products on many different machines without violating the license agreement. Launching the RISA Product When launching a RISA standalone product the product will search for a connected Sentinel USB Key. 18 RISA Licensing . If no key is found then the following dialog box is displayed: Clicking the Continue button will launch the RISA Product in a Demo mode.

General Reference Manual 19 .Standalone Licensing Remote Desktop Currently RISA does not support the use of Remote Desktop for standalone licensing.

go to step #2 below. Installing From a CD Installing from the CD 1. At the end of this install you may be prompted for whether or not you want to run the Network License Service Install.Network Server Installation Instructions Network Server Installation Instructions This topic is meant to provide step by step instrutions for the installation of the Network Server version of the RISA programs. If the CD starts automatically. click the Windows Start button and select My Computer. Insert the install CD into your CD drive. If the CD does not start automatically after 10 seconds. Click on Install Products: 20 RISA Licensing . Doubleclick the RISA icon: 2. This Network Server Install unpacks a number of folders which will be used for either a Network Client Install or the Network License Service Install.

et cetera). This will launch your web browser and take you to a Downloads page on the RISA Technologies website as shown below. This should be of the form WebXX_vvv_net.Network Server Installation Instructions 4.1. Select the Network Server option: At this point installing from the CD and installing from an e-mail link are identical. FL. Installing from an E-mail Link 1.2. for RISAFloor et cetera) and vvv is a one to three digit code for the version (912 for version 9. This will normally bring up a File Download dialog similar to the one shown below. Click on the Network installation file. Click on the e-mail link. So.exe" where XX is a two digit code for the program (3D for RISA-3D. follow the instructions from item #3 below to continue on with the network installation. RF for RISAFoot. Click Save to download the install routine to your computer (to run later) or select Run to download and run the installation General Reference Manual 21 . 2.

3.Network Server Installation Instructions routine now. Some computer or security settings may not allow the file to be run directly from the web browser and will require that the install routine first be saved to the local computer. From the Welcome screen. In future releases RISA will add a digital signature to our programs to prevent this type of warning from being displayed. If you receive a Security Warning regarding an "unknown publisher". click Run again to continue with the installation. click Next: 22 RISA Licensing .

Network Server Installation Instructions 4. Select the destinatin folder (the default location is C:\RISA\) and click Next: General Reference Manual 23 . Accept the terms of the license agreement and click Next again. 5. If the License Agreement is not accepted then the install routine will be canceled.

Network Server Installation Instructions 6.: The RISA Network Client (Directory and Files) option will install all the files needed to perform a client install as described in the Network Client Install topic. Choose which components to install and clickNext. 24 RISA Licensing .

7. The Setup Status window will open up as shown below: General Reference Manual 25 .Network Server Installation Instructions The RISA License Server (Directory and Files) will install the "RISA Licesnse Server" folder and all the files needed to get the license management service up and running. The Update Key Driver component check box only appears if the installation routine has detected that the driver for the Sentinel SuperPro hardware key is iether not installed or is too old to function with the license management server. Click Next on the Ready to Install confirmation screen: 8. The Update Sentinel License Management service gives you an option to launch a utility that evaluates the license management service(s) on your server and determine if an update is rerquired. It is recommended that you leave the default settings (all boxes checked) before clicking Next to continue with the install.

26 RISA Licensing . When you reach the Installation Complete dialog you have the choice for whether or not to check the RISA website to see if there are any updates available. 9.Network Server Installation Instructions The Installation routine will then install the directory and files necessary for the network server and client installs.

Refer to the topic titled License Service Updater for more information on using this utility. 12. Administering the licenses by adding the new license file by running the WLMAdmin utility. General Reference Manual 27 . If the Update Sentinel License Management Service feature was chosen in step 5.Network Server Installation Instructions 10. Installing the program on a client machine. This is described in the Network Client Install topic. 11. there will still be two steps to completing a network install. After the License Service Updater is finished running. then the License Service Updater utility will automatically launch. This is described in the License Administration topic.

4.5. The non-customized version of Sentinel RMS. Double-click on the Service to be unloaded. However. Run the LoadLS. If you hae an existing Sentinel LM service then the License Server Updater (described in the next section) will automatically evaluate / assess your existing license services to determine compatibility with RISA's customized service.1\) 4. Open the list of Services. 1. However. This utility. Run the LoadLS. 28 RISA Licensing . This can be accessed through the Administrative Tools portion of the Windows Control Panel. then click OK License Service Updater As part of the install routine.5.1 required to run the latest RISA software. the customized version of Sentinel RMS is typically compatible with the licensing of other software vendors. shown below.1' sub-directory of the server install directory. Confirm that no existing Sentinel services (i. Eagle Point) Loading (Adding) the Sentinel Service The steps below describe the process to load the Sentinel Service. Compatibility The RISA customized version of Sentinel RMS cannot be run in conjunction with any of the following services: l l l Non-customized versions of Sentinel RMS Any version of Sentinel LM Any version of Sentinel LM or RMS which has been customized by other third parties (e. If any such service is running then it must be unloaded (removed). This can be accessed through the Administrative Tools portion of the Windows Control Panel. 3. Open the list of Services. 2. then click OK Unloading (Removing) a Sentinel Service The steps below describe the process to unload a Sentinel Service. Sentinel LM or RMS) are running. Check for the service's Path to Executable and navigate to that folder in Windows Explorer. It is a custom made diagnostic tool designed to examine the license management systems running on the computer and determine if any of them will cause conflicts with RISA's customized version of Sentinel RMS version 8. Click the Remove button. the License Service Updater (ServerUpdate. This utility can be found in the 'Sentinel RMS 8. : 1. analyzes the computer and gives a summary of the Sentinel LM or Sentinel RMS license management services that are currently loaded. 3. is not compatible with RISA licensing.exe Utility which should be present in that folder 5.exe Utility (default installation folder is C:\RISA\Sentinel RMS 8. Click the Add button.exe) will run.e. this process is now automated with the License Service Updater utlity described in the section below.License Service Updater License Service Updater Sentinel Service Overview RISA uses a customized version of the Sentinel RMS 8.g.1 license manager to maintain and distribute licenses.5. which is used by other software vendors. 2.5.

If you wish to exit out of this dialog without making any changes click the the dialog. this utility will do the following:  l l l Unload or Remove the existing Sentinel LM and Sentinel RMS license Management Services. stopped. If the path is blank. What Happens When Update Is Clicked? When the user clicks the Update button.1. or disabled). Copy the license file information from these older services into the license file for the new license management service. Load the new version of the license management service which is a RISA customized version of Sentinel RMS version 8. when updating from a previous version of the Sentinel Licensing service. button on the upper right hand of the dialog to cancel out of Generally. General Reference Manual 29 .EXE executable resides). a message will be provided that instructs the user to click Update to install the new version of the license service. that means that that particular license service was not detected on the computer. If Info data gives basic information about the detected license service. the version of the service.License Service Updater Path and Info This Path data gives the directory path of the Sentinel LM or Sentinel RMS license services where they were loaded from (and where the LSERVNT. Status The Status section provides a summary of the analysis and instructions for continuing. just click the button on the upper right hand of the dialog to cancel out of the dialog. If this happens.5. This includes the status of the service (whether it is currently running. If the License Service is up to date and does not need to be updated at all then this Update button will be grayed out. and whether that version has been customized by RISA Technologies.

This can be accessed through the Administrative Tools portion of the Windows Control Panel. This can be accessed through the Administrative Tools portion of the Windows Control Panel. Open the list of Services. 3. is not compatible with RISA licensing. Check for the service's Path to Executable and navigate to that folder in Windows Explorer.exe Utility (default installation folder is C:\RISA\Sentinel RMS 8. Open the list of Services. If any such service is running then it must be unloaded (removed).exe Utility which should be present in that folder 5.5.1 license manager to maintain and distribute licenses. Double-click on the Service to be unloaded. Run the LoadLS. the customized version of Sentinel RMS is typically compatible with the licensing of other software vendors. Run the LoadLS. Sentinel LM or RMS) are running. which is used by other software vendors. Compatibility The RISA customized version of Sentinel RMS cannot be run in conjunction with any of the following services: l l l Non-customized versions of Sentinel RMS Any version of Sentinel LM Any version of Sentinel LM or RMS which has been customized by other third parties (e. 3. The non-customized version of Sentinel RMS. 2. Eagle Point) Loading (Adding) the Sentinel Service The steps below describe the process to load the Sentinel Service: 1. However. Click the Add button. Click the Remove button. Confirm that no existing Sentinel services (i.5. 4. then click OK 30 RISA Licensing . 2.1\) 4. then click OK Unloading (Removing) a Sentinel Service The steps below describe the process to unload a Sentinel Service: 1.g.Sentinel Service Sentinel Service RISA uses a customized version of the Sentinel RMS 8.e.

Loading (Adding) a License File Using the Sub-Net Server Tree To add in a new license file for a new program or a new version of an existing program: General Reference Manual 31 . However. This utility will also be located on the network Client computer in the "\Sentinel LM\Utilities\" sub-directory of the main install directory (usually C:\RISA\).exe.License Administration License Administration The utility used for administering licenses on the license management server is WLMAdmin. This utility will be located on the License Management Server in the "\Sentinel RMS\" sub-directory of the main install directory (usually C:\RISA\). This utility is primarily used for adding new programs (or versions) onto the existing license management server. it may also be used for reviewing which users have a license checked out and whether that license is a commuted license and when it is scheduled to be returned. The utility may be run from either location.

e-mail license@risa. 2. then click Add and OK. 4. If the Sentinel RMS license management service is up and running on the server. If you do not have a copy of this license file.License Administration 1. a message indicating how many licenses were successfully loaded will be displayed similar to what is shown below. Make sure that you have a copy of your new license file in an accessible location. refer to the section below titled Using the Defined Server List for more information. The server should now appear in the Defined Server list. Loading a License Using the Defined Server List There are many reasons why the License Management Server may not listed under the list of subnet servers. Make sure that you have a copy of your new license file in an accessible location. An Open dialog will come up. or that there may be some firewall which is preventing communication between the client and the server. Run WlmAdmin utility and select Edit -=> Defined Server List from the Main Menu Toolbar to bring up the dialog shown below: 3.com to request a license file. If the license file loads successfully. In these cases. see Appendix B .com to request a license file. 5. Type in either the IP address or the DNS name of the license management server. Right click on the name of the License Server and select 32 RISA Licensing . 2. the easiest solution is to add the License Management Server to the list of defined servers. If it is not listed. Right click on the name of the License Server and select (as shown in the image above): Add Feature => From a File => To Server and its File 4. then the name of the server should now be shown in the sub-net server tree. e-mail license@risa. This can be done by double-clicking on the Subnet Servers text or by clicking the plus sign next to the text.Network Installation Error Messages. 6. Sentinel RMS should now be able to issue network license tokens for your RISA programs. Execute the WlmAdmin utility and open the Subnet Servers tree on the left hand side of the WlmAdmin dialog. Browse to the license file and open it. Chief among them is that the computer running the WLMAdmin utility may not reside on the same subnet. The name of the license file should be "RISA_LM_KeyID" where KeyID is the ID number of your SuperPro USB key. 3. This can be accomplished by doing the following: 1. Note: If the License Server is accessible by subnet broadcast that computer should appear under Subnet Servers. If you do not have a copy of this license file. Once the license has been accepted. If the licensing file is not accepted.

License Administration

Add Feature => From a File => To Server and its File
5. If the license file loads successfully, a message indicating how many licenses were successfully loaded will
be displayed similar to what is shown below. If the licensing file is not accepted, see see Appendix B - Network Installation Error Messages.
6. Once the license has been accepted, Sentinel RMS should now be able to issue network license tokens for
your RISA programs.

Server Information

This is a section of the WLMAdmin window that reports information about the license management server. It
reports the version of the license management server, the name and the IP address.

Feature Information

This section of the WlmAdmin window reports specific information about the licensing for that program and version. For example, the above image shows that RISASection version 2.0 is loaded on the license management
server. The total number of licenses is 5, only one of which is currently being used.
This section will also give a quick summary of how many of these licenses are commuted licenses and how many
licenses are reserved (unavailable for commuting) .

Detailed Information
Using the WLMAdmin utility it is possible to find out additional detailed information about the program version,
or about the users who have currently checked out a license. In the image below, the selected feature is RISASection 2.0 and the selected user is joshp.

General Reference Manual

33

License Administration

License Info
The license info gives information about the feature / program, not about the user. Most of this information will
not be directly used. However, the "Allow commuter license" flag and the End date can be useful when reviewing
feature / program information from non-RISA vendors.

Client Info
The client info section of the WLMAdmin is only available when a specific user has been selected under the feature / program. This information lets us know when the license was checked out, who checked it out (user login
name and well as the host name of the computer), and whether or not the license was a commuted license.

Trouble Shooting License Administration
Appendix B: WLMAdmin Error Messages contains explanations for most of the common error message codes that
may occur when adding a license file. Chief among these are:
l
l

34

WLMAdmin returns Error Codes 19, 92, or 150 when attempting to add in the license file
WLMAdmin cannot locate the Sentinel RMS License Management server, even when using the Defined
Server List. See error code 3 in Appendix B for more information on resolving this issue.

RISA Licensing

Advanced Network Features

Advanced Network Features
RISA Network licensing includes advanced utilities which can be run on the license server.

Usage Reports and License Monitoring
The WLMadmin.exe utility offers a real-time account of which users have checked out licenses, however there
are more advanced utilities available to track the usage of licenses over a given time period. Below are instructions to create a Usage Report.

Creating a Usage Log Report (text file)
For 32-bit Operating Systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Rainbow Technologies\SentinelLM\CurrentVersion
For 64-bit Operating Systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Rainbow Technologies\SentinelLM\CurrentVersion

Create a String value within the CurrentVersion key and give it the name CommandLineOpts
Assign a value of -l "C:\RISA\Sentinel RMS 8.5.1\Lserv.log" (the second character is a lowercase L, not the number one)
The Sentinel RMS service must be restarted before logging will begin. This can be done by manually stopping
and starting the service through the Windows Control Panel, or it will happen automatically the next time the
server is rebooted.
Note:
l

The path specified in the registry sting value is the location where the usage log report will be created.
The file name will be whatever is specified in the registry entry (i.e. Lserv.log)

Converting a Usage Log Report to a Database Table (CSV file)
The Usage Log Report can be cumbersome to review. Therefore, Sentinel has provided a utility to convert it into
a database table readable by Microsoft Access. This utility can be found in the following location:
C:\RISA\Sentinel RMS 8.5.1\Utilities\
Execute the following command (either from a DOS Command Prompt, a batch file, or using the Windows Run
command). If executing from a command promple, you will need to first navigate to the folder.
lsusage -l "C:\RISA\Sentinel RMS 8.5.1\Lserv.log" -c Lserv.csv (the tenth character is a lowercase L, not a One)
The Access Database Table file (Lserv.csv) will then be created in the Utilities folder (where the LSUsage.exe
utility resides). For simplicity a LSERVLOG.BAT file. When executed, this batch file will automatically launch the
lsusage utility and place a Lserv.csv file in the utilities subdirectory. This file may be edited with notepad if the
Lserv log exists in a different folver or if the lserv.csv needs to be placed in a different location.

Reading the Access Database Table
The Database Table (Lserv.csv) is most useful when read into MS Access using the process described below.
First, launch Microsoft Access and open the following file:
C:\RISA\Sentinel RMS 8.5.1\Utilities\ReportDB.mdb
Note: 

General Reference Manual

35

Advanced Network Features

l

Access will sometimes give error messages about needed to convert the file to a newer file format or
about a missing *.OCX file. Click OK or Continue to ignore those error messages as they should not affect
the function of the utiltiies.

Once the file above has been opened, choose to Import a Text File. In the dialog that pops up, select text file you
will be importing as the Lserv.csv that was created above in the step titled Converting a Usage Log File Into an
Access Table. Also, be sure to "Append a copy of the records" to an existing table called Lservlog. The Lservlog
table will then contain the entire information of all of the features on the License Server (including non-RISA features).
Note: 
l

Occasionally, you may wish to create a new lservlog table rather than append to an existing Lservlog
table. The only way to do this is to first, delete rows from the existing Lservlog table before importing
new data.

The reporting utility within Access can then be used to generate various types of reports (e.g. Total Minutes
Used Per Feature Per User).

Reserving Licenses for Specific Clients
Sentinel RMS contains the ability to reserve a number of licenses for selected groups of client machines. At this
time RISA does not provide support for this feature.

Limiting the Number of Commutable Licenses
The network administrator can restrict the number of licenses which may be commuted, or even restrict users
from commuting licenses altogether.
Note:
l

This is a blanket setting for all licenses of all licenses on the server. You cannot restrict some products
and not others.

Setting Start Parameters for the Service
For 32-bit Operating Systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Rainbow Technologies\SentinelLM\CurrentVersion
For 64-bit Operating Systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Rainbow Technologies\SentinelLM\CurrentVersion
Create a String value within the CurrentVersion key and give it the name CommandLineOpts
Assign a value of-com 50 {Which limits the commuted licenses to 50% of the total number of licenses}
The Sentinel RMS service must be restarted before logging will begin. This can be done by manually stopping
and starting the service through the Windows Control Panel, or it will happen automatically the next time the
server is rebooted.
To prohibit any licenses from being commuted set the value to -COM 0.
Note:
l

36

If setting multiple switches (logging and commuting, for example) in CommandLIneOpts use a space
between eqch command. For example, the entry below will set both the log file and limit the number of
commuted licenses available: -l "C:\RISA\Sentinel RMS 8.5.1\Lserv.log" -com 50

RISA Licensing

Find the installation folder on the server and run Setup. Review the License Agreement and click I Accept. 3D. Click Next at the Welcome Screen 3. then click Next. Where to get the Install The network client install is placed on the License Server during the Network Server Install.Network Client Install Network Client Install These instructions are intended for the network client versions of the software.exe 2. The default installation folder on the license server is: C:\RISA\xxxServer\vv_vv_vv Where xxx is the name of the program (2D. If this is the case then please check with your network administrator for their location. Floor. etc) and vv is the version number. the Network Client install for RISABase 2. General Reference Manual 37 .4 would be at C:\RISA\BaseServer\2_04_00 Note: l If the network client install files are not in this default location it is possible that your network administrator has moved them to another location. Installation Instructions The Network Client install will walk you through each step.0. If you have a standalone license. Note l You must be an Administrator on the Client Machine in order to run this install 1. For example. please see the Standalone Install topic.

and RISAFloor) comes with regional default settings. Then click Next. The default is C:\RISA. Choose a destination folder for the program on the Client Machine. Click Next. 5. Some RISA software (RISA-2D. 38 RISA Licensing . Choose the region which is most appropriate for you.Network Client Install 4. Check the Overwrite Existing Defaults box to have the program replace default settings from a previous installation with the latest ones. RISA-3D.

Choose a destination folder in the Windows Start Menu where the launch icon for the program should go. then click Next.Network Client Install 6. 7. If a previous version of the program already exists on the client machine then you will be notified and given an option to have the installer replace it with the latest version. Click Yes to do so. General Reference Manual 39 .

A final confirmation screen will appear next. 9. then click Finish. 40 RISA Licensing . Click Install to begin the installation.Network Client Install 8. The installation may take several minutes. Choose whether the installer should take this last step. Once the installation is complete you may have the program check for updates.

Click OK to launch the RISA Release Notes website in your web browser. 11. Please have your IT administrator contact RISA Technologies to get this update. This ensures that all of the program's settings are properly initialized Configuring Software Licensing on the Client For information on registry settings which control communication between the client machine and the server see Network Licensing General Reference Manual 41 . If RISA has released a newer version of the software than the one you've just installed you will be notified with this dialog message.Network Client Install 10. Be sure to launch the program as an Administrator the first time you run it. This means that a newer version of the program must be installed on your server. and review what new features are available.

0 or higher.ini to have the License Server’s address automatically written to the end user’s registry by following these steps: l l l l Network. This usually ends up being the the <C:\RISA> directory on the server. Older versions of the install routine can still perform a silent install.1 or higher. execute the setup.ISS File.52 Performing a Silent Client Installation Using the SETUP. Editing the SETUP.exe file with the “/s” switch. the procedure will be described in the section titled Performing a Silent Install using the Setup. Region and Overwrite optionse. Silent setup uses the SETUP.5.INI File If you wish to change the Install Directory. To execute the silent installation from the client. the installation will write <License Server Address> as the value in the “LS Query List” registry entry For a new install: o In the Application Registry Key.exe used to launch the client install. However. Note: l This procedure is only valid for installation routines created using the Install Aware installation package.Network Client Install Using the network. This can be called through a DOS prompt on the client. This entry is necessary for wide area networks where the client and the server do not reside on the same subnet. Network. which gets installed into the 'Sentinel RMS 8. you can do so by editing the SETUP. and RISA-3D version 11.168. So for the following Network.ini File to set Advanced Registry Entries There is a file. If it finds that file it searches for the section header [LS Query List] and the parameter Initialize=<License Server Address>. The client installation looks for Network.1' subdirectory on the server. This file is capable of storing installation 42 RISA Licensing . a log-on script or client registry entry.INI File You may use a silent installation to avoid interacting with the client installation dialogs and you may automatically run the silent setup in a log-on script or through the registry.100. Program Folder. For update installations: o If the “LS Query List” registry entry under the Application Registry Key does not already contain the address of a license sever.INI file in the <VersionNumber> subdirectory.ini file: [LS Query List] Initialize='192. You may use network. However.52' The “LS Query List” registry entry gets set to the value 192. it can be used to speed up license validation between client and server for any type of network.II file in <C:\RISA>\<ProgramServer> \<VersionNumber> to guide the client installation. This file.ini must be placed two folders up from the setup. This file can be used to automate the setting of the “LS Query List” registry value on the Client machines. will install the above files to the client’s C:\RISA directory and place a program shortcut in the RISA folder on the Start-Programs menu.exe /s Where <C:\RISA> is the mapped drive and directory on the file server containing the <ProgramServer> \<VersionNumber>\ directories.ini. That includes RISABase version 2.ini. The entire command line would look something like this: <C:\RISA>\<ProgramServer> \<VersionNumber>\setup.168. as provided.100. the “LS Query List” value is set to <License Server Address>.

3 – Europe. Newer versions of the install routine can still perform a silent install. The SETUP. 1 – Yes).e. 1 – Canada. 8 – Saudia Arabia). RISA-3D and RISAFloor. For example. The entire command line would look something like this: <C:\RISA>\<ProgramServer> \<VersionNumber>\setup. (0 – No. 7 – Mexico. 5 – Australia. you will probably have to redirect the SETUP.New Zealand.exe /s INIFILE="C:\Share\RISA_setup.exe /s Where <C:\RISA> is the mapped drive and directory on the file server containing the <ProgramServer> \<VersionNumber>\ directories. 2 – Great Britain.0. This entry only exists for RISA-2D.ISS File You may use a silent installation to avoid interacting with the client installation dialogs and you may automatically run the silent setup in a log-on script or through the registry. <C:\RISA>\<ProgramServer> \<VersionNumber>\setup. You may wish to rename the SETUP.INI file or store it in a common location for all RISA programs (i. you can use the “/r” switch. However. a log-on script or client registry entry.ISS file will need to be copied from the C:\WINDOWS folder on the client computer to the <ProgramServer> \<VersionNumber> directory before it can be used for a silent install. the procedure will be described in the previous section titled Performing a Silent Client Installation using the SETUP. 2012 (RISA-3D version 10. you will want to locate the section header for the program installation you wish to modify. Region is a number indicating the progam's region settings (0 – United States. This can be done with the "/f1" switch. This initiates a new client setup and will record all the information that you enter during the setup. 4 – India. [RISA-3D] szDir=C:\RISA szGroup=RISA Region=0 DefOverwrite=0 The options and there descriptions are listed below: szDir is the target directory of installation. szGroup is the program group folder (under All Programs in the Windows Start Menu) where the shortcuts will be placed.ini" Performing a Silent Install Using the Setup.ini file in a different location than that containing setup. 6 .ISS file away from the C:\WINDOWS folder. C:\RISA\ instead of C:\RISA\<Program server>\<VersionNumber>\). execute the setup.ISS file in <C:\RISA>\<ProgramServer> \<VersionNumber> to guide the client installation.ISS file. as provided. use the following syntax: setup.1 or lower).Network Client Install information for mulitple programs. This can be called through a DOS prompt on the client. Note: l This procedure is only valid for installation routines created using the Install Shield Wizard. This file. In addition. This entry only exists for RISA-2D.exe. Silent setup uses the SETUP. To record a new or customized SETUP. RISA-3D and RISAFloor. below is the infromation block fore RISA-3D. So. That includes any install routine created prior to October.exe /r General Reference Manual 43 . To execute the silent installation from the client. To specify a setup.exe file with the “/s” switch.INI File. will install the above files to the client’s C:\RISA directory and place a program shortcut in the RISA folder on the Start-Programs menu. DefOverwrite is a setting that controls whether you wish to overwrite existing defaults.

ISS file would be created in the G:\OKFolder\ directory. If you wanted India to be the selected country you would change the Region=4.ISS file in the <VersionNumber> subdirectory. To verify if a silent setup succeeded. look at the ResultCode value in the [ResponseResult] keyname. 6=New Zealand. 4=India. 7=Mexico This file is setup for United States because the option Region=0. InstallShield places one of the following return values after the ResultCode keyname: 0 Success -1 General Error -2 Invalid Mode -3 Required Data not found in the Setup. You may view the Setup.log file to determine the result of the setup. If you wish to manually change the Path or Country options. you can do this by editing the SETUP. you would edit the “szDir” value in the following block: [{E7AF3A4F-BAAC-42CD-A90D-275454A68751}-SdSetupType2-0] szDir=C:\RISA\RISA-3D Network To change the Country option. To change the PATH into which the client version gets installed. 5=Australia.Network Client Install /f1g:\okfolder\setup. 2=British. the SETUP.iss file -4 Not enough memory available -5 File does not exist -6 Cannot write to the response file -7 Unable to write to the log file (see below) -8 Invalid path to the response file -9 Not a valid list type -10 Data type is invalid -11 Unknown error during setup -12 Dialog boxes are out of order -51 Cannot create the specified folder -52 Invalid option selected 44 RISA Licensing . 3=Europe. you modify “Region” value in the following block: [{E7AF3A4F-BAAC-42CD-A90D-275454A68751}-RdAskRegion-0] Result=1 Region=0 DefOverwrite=0 Where the region values are: 0=United States. 1=Canada. SILENT INSTALLATION ERROR MESSAGES Be aware that no messages are displayed when running a silent installation.iss In this case.

exe /s /f2g:\okfolder\setup.log General Reference Manual 45 .Network Client Install If the log file cannot be written to the C:\Windows directory (because of read only privileges) you will have to redirect the log file to a directory with write permission using the following switch: /f2<path\LogFile> (don’t type the <> symbols) To redirect the log file the example above would now look like this: <C:\RISA>\<ProgramServer> \<VersionNumber>\setup.

If a License Server is found then the program will check out a license (if available). clicking in the Search box. If you believe that this is happening in error the two general problems are: l l A firewall is blocking communication. If you are running a different version of Windows then the procedure may be slightly different. Note: l The instructions above are valid for Windows 7. and typing regedit. Find the Registry Key Path to the following registry key on the left side of the Registry Editor: 32-bit and 64-bit Operating Systems: HKEY_LOCAL_MACHINE\SOFTWARE\RISA Technologies\RISAxxx Network\vv 64-bit Operating Systems running RISAFoot. Pointing a Client Machine to a License Server If no license server is found by the Client Machine then it may be necessary to point the Client Machine to the License Server. or RISAConnection: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\RISA Technologies\RISAxxx Network\vv 46 RISA Licensing . If no key is found then the program will search the subnet for a License Server. open the Registry Editor on the Client Machine by clicking on the Windows Start Button. you are presented with the option to enter Demo mode. then hit Enter. To fix this follow the Pointing a Client Machine to a License Server section below. To fix this problem you must set an exception for UDP port 5093 on both the server and client for both inbound and outbound. To do this. or if no licenses are available. RISASection. The license broadcast is timing out. This server distributes licenses to the Client Machines. Launching the RISA Product on a Client Machine When launching a RISA network product the program will search for a connected Standalone Sentinel USB Key.Network Licensing Network Licensing RISA network products are licensed with a License Server. If no license server is found.

This will point your client machine directly at the license server. RISA-3D V11 and later.0 would be . Losing Network Connection RISA Products periodically check the connection to the License Server.1 and later all have both 32-bit and 64-bit capabilities and will be installed appropriately on 32 and 64-bit operating systems.0 Note: l l RISAFloor V7 and later. For example. Set the LS Query List Entry Double-click on the LS Query List registry entry to edit it: Under Value Data enter either the DNS Name or IP address of your license server. RISAFoundation V5 and later. and RISAFoot are all 32-bit applications that will go into the Wow6432Node location on 64-bit operating systems.Network Licensing Where xxx is the name of the RISA product in question and vv is the version number of the product in question. Then hit OK and exit the registry editor. RISA-2D V12 and later.\RISA Technologies\RISABase Network\2. Severing this connection during the operation of a RISA network product will eventually cause the following dialog box to be displayed: General Reference Manual 47 . RISAConnection... RISABase Version 2. RISASection. Older versions of these programs were always 32-bit. and RISABase V2. If a 32-bit application is installed on a 64-bit operating system then the registry location is in the Wow6432Node location.

Network Licensing Once this dialog box is displayed. Click Yes to have the program search for a license. Clicking the No button on the dialog box displayed above will present the option to save the file (overwriting the previous version of the file) and exit the program immediately. If you point the client directly to a license server machine this can remedy this problem. no additional work may be done within the RISA Product until the network connection (and the license from the License Server) is restored. 48 RISA Licensing .

RISA-3D) must be installed on the client machine. This feature is commonly used on laptops which need to borrow licenses to be used in remote locations where a network connection to the license server is not possible. This process is called "commuting".License Commuting License Commuting Licenses may be checked out from the license server onto client machines in such a way that the client machine does not need to remain connected to the license server. There are two methods for commuting licenses: Local Commuting This commuting method is preferable as it allows the licensing administrator more control over the commuted license. General Reference Manual 49 . It does require the client machine to be connected to the network at the time of license check-out. Prerequisites l l l The client machine must be connected to the network. The license server must have at least one available license for the product which is to be commuted. Procedure On the client machine. run the following utility: C:\RISA\Sentinel RMS\Commute\WCommute. The appropriate RISA product (i.e. This must be a Network Client Install.exe This will launch the following dialog box: l To have the WCommute utility search the entire subnet for license servers. so it cannot be done if the client's machine cannot be connected the network at the time that the license is checked out (borrowed). with direct access to the license server. click the Search Subnet button.

Note: 50 RISA Licensing . If a commuted license is not checked in by its expiration date then that license disappears from the client machine and reappears on the license server. and is unavailable on the license server until it is checked back in. A red check mark will appear next to the Feature. You can then close the WCommute utility. A commuted license is retained by the client machine. The license server should now appear. with all of the available RISA products branched out underneath it as shown below: Click on the program which you would like to commute a license for.License Commuting l To point the WCommute utility directly to a license server (nessecary if the server is on a different subnet than the client machine) click the Single Server button and enter that server's name or IP address. Note: l It is recommended that you immediately disconnect the client machine from the network and launch the RISA program which a license has been checked out for. indicated that a license has been checked out. Then click the Check Out button. Remote Commuting This method of commuting should only be used in the circumstance where it is not possible to connect the client machine directly to the license server at the time of checking out the license. Do this before leaving the office to confirm that the license has been correctly commuted. Note: l l Licenses for each program must be commuted independently Do not check the Check out authorization for remote machine box. and installing the authorization code on the remote machine. Enter a number of days which the commuted license will be valid for. or until it expires. There are three main steps: retrieving locking code data from the remote machine. retrieving the authorization code and checking out a license on the local machine.

This step can be done from any local client machine which has access to the license server. run the following utility: C:\RISA\Sentinel RMS\Commute\WCommute. This must be a Network Client Install.exe This will launch the following dialog box: Click on the Get Locking Code tab. On the local client machine. RISA-3D) must be installed on the remote client machine.e. In order to do this the license server needs a locking code for that client machine. Then send the Locking Code File to a user who has a local client machine (connected to the license server). Save the Locking Code File to a temporary location. On the remore client machine.License Commuting l Remotely commuted licenses cannot be Checked-In!! They will remain commuted until their expiration date. Prerequisites l l l The license server must have at least one available license for the product which is to be commuted. and click the button. There must be a local client machine (connected to the license server) with any current Network Client Install of a RISA product installed.exe This will launch the following dialog box: General Reference Manual 51 . Retrieving the Authorization Code (Local Client Machine) The license server can use the Locking Code to generate an Authorization Code which the remote client machine will need in order to remotely commute a license. Retrieving the Locking Code (Remote Client Machine) The commuted license will be locked to a specific remote client machine. run the following utility: C:\RISA\Sentinel RMS\Commute\WRCommute. The appropriate RISA product (i.

with all of the available RISA products branched out underneath it as shown below: Click on the program which you would like to commute a license for. Note: 52 RISA Licensing . To point the WCommute utility directly to a license server (nessecary if the server is on a different subnet than the client machine) click the Single Server button and enter that server's name or IP address. click the Search Subnet button.License Commuting l l To have the WCommute utility search the entire subnet for license servers. The license server should now appear.

Then click the OK button. On the remore client machine. Enter a number of days which the commuted license will be valid for. The following dialog box will appear: Click the button. Click OK. then exit the WCommute utility. Browse to the Locking Code File which was generated by the remote client machine and click Open.exe Click on the Install Remote Authorization tab which is shown below: General Reference Manual 53 .License Commuting l l Licenses for each program must be commuted independently You must check the Check out authorization for remote machine box. Save the Authorization Code File to a temporary location. Then click the Check Out button. The following dialog box will be launched: Click on the Get locking code string for remote machine from file button. then click the button. Installing the Authorization Code (Remote Client Machine) The Authorization Code must be installed on the remote client machine to activate the commuted license. Send the Authorization Code File to the remote user. run the following utility: C:\RISA\Sentinel RMS\Commute\WRCommute.

then click the button. based on the expiration date entered at the time that the license was commuted. Licenses which were commuted using the Local Commuting procedure may be returned at any time prior to their expiration date (which was entered at the time that the license was commuted).License Commuting Click on the Get remote authoirzation code(s) from file button. run the following utility: C:\RISA\Sentinel RMS\Commute\WCommute. Browse to the Authroization Code File which was generated by the local client machine and click Open.exe This will launch the following dialog box: 54 RISA Licensing . Returning Commuted Licenses Licenses which were commuted using the Remote Commuting procedure may not be returned. The remote client machine will now be able to use the commuted license until it expires. Test this by launching the RISA program for which a license was commuted. Procedure On the client machine. They will remain commuted until they expire. The following dialog box will appear: Close the WRCommute utility. Then click the Install button.

The license server which the license was commuted from should now appear. The red check mark will disappear. with all of the available RISA products branched out underneath it. The commuted license for each RISA program should show a red check mark next to it as shown below: Click on the license to be returned and then click on the Check In button.License Commuting l l To have the WCommute utility search the entire subnet for license servers. click the Search Subnet button. General Reference Manual 55 . To point the WCommute utility directly to the license server which the license was commuted from (nessecary if the server is on a different subnet than the client machine) click the Single Server button and enter that server's name or IP address. indicating that the license is no longer commuted. Close the WCommute utility.

dat or cleanse_client. Run the initialization routine.License Commuting Initializing the Program for Commuted Licenses  In order for Commuted Licenses (or emergency license files for stand-alone programs) to work a special initialization routine must be run. This should be located in the C:\RISA\Utilities sub-directory. there is a way to "cleanse" the commuted license information off of the server. if the initialization is not run properly then the 'time-tampering' check will prevent the commuted licenses from checking out properly. be sure to select yes. Technical support will then use this locking information to e-mail a "cleansing" file to be run on that computer. Usually this will be called something like cleanse_server.exe (for RISA-3D version 10) o initRF40. Login to the end-user computer with full administrative permissions. This utility will need to be run from a DOS prompt referencing the cleansing file obtained in item #2. However.5. so you will need to contact RISA technical support in order to complete. In the past.0) 3. However.dat 3. 2. this initialization should always occur automatically. Therefore.exe. in the event that a commuted license cannot be returned to the license server. Cleansing a Commuted License There are a number of issues that can cause a commuted license to not function properly. the initialization routine may need to be run again before the commuted license can be successfully run.exe (for RISAFoot version 4. If this occurs.dat 56 RISA Licensing . If a User Account Control message asks if you want to allow the this program (from an unknown publisher) to be allowed to make changes to your computer. To run this utility do the following: 1. It will be given a program and version specific name similar to the following:  o init3D10.com). Contacting RISA Technical support (support@risatech. They will give instructions on obtaining a locking code for the client or server computer upon which the commuted license has been stuck. In the Utilities sub folder (on the client or the server) there will be a utility called lsclean. 2. With the update to Sentinel RMS 8. The basic process involves the following: 1. it's believed that these were normally caused by a partial incompatibility between Windows Vista (or Windows 7) and the older version of the Sentinel License service that was used to commute the license. The initialization routine will not complete successfully unless it has been run with administrative permissions. This routine is run as part of both the Client network installation and the standalone installation routines. This is not a simple or straight forward process. An example of this command line would be the following:  lsclean cleanse_server. this should no longer occur.1. Locate the initialization utility.

The latest Sentinel System Driver (also called the Sentinel Protection Installer) can be obtained from the RISA Technologies website. This driver must be installed prior to plugging in the key.exe located in the RISA\Sentinel Protection Installer folder). To confirm that your machine is running the latest driver open the Device Manager. When functioning properly the key will light up green when plugged into a running machine. and typically do not have an adhesive label attached.Sentinel USB Key Sentinel USB Key RISA uses a Sentinel USB Key for licensing. The design of Sentinel's keys has changed over the years. and is always included in both the Server and Standalone installs (this install is ran from the SetupSPI. See the image below: Key Driver A Sentinel driver is necessary for the machine to read the USB key. If the key is plugged in and the correct driver is installed then it will be listed under the Universal Serial Bus controllers as a SafeNet USB SuperPro/UltraPro device General Reference Manual 57 . which is accessible through the Windows Control Panel. Older Sentinel USB Keys are purple. Newer ones are black and typically have an adhesive label designating their Key ID. This key may be plugged into any USB port on the machine.

Clicking on the Driver tab will reveal the Driver Version: SSD Cleanup There are instances when uninstalling the key driver will leave remnants of information in the registry. Run the SSD Cleanup utility (SSDCleanup. 3. This file is called SSDCleanup. 2.exe). Uninstall the key driver from the machine. Re-install the key driver by running the SetupSPI. It is located here (by default) for 32-bit operating systems: C:\RISA\Sentinel System Driver It is located here (by default) for 64-bit operating systems: C:\RISA\Sentinel System Driver\x64 So the typical way to fix key driver issues is as follows: 1.exe. This will sometimes cause problems in reading the key when a new version of the key driver is installed.exe or SSDCleanupx64.Sentinel USB Key Double-click on the SafeNet USB SuperPro/UltraPro device to view its properties. In this instance it may be required to run the SSD Cleanup utility to fix this problem.exe from the C:\RISA\Sentinel System Driver folder 58 RISA Licensing .

RISA Key Manager RISA Key Manager The RISA Key Manager is a program that allows you to interact with your USB licensing key. This program works for both standalone and network (server) keys and is used mainly for these purposes: l l Upgrading a standalone key for a new version Upgrading a network key for a new program There are also many other uses for this program that most users will never run into. Note: l The Features button is only applicable to tnxTower. This program (RISA Key Manager.exe) is found in the RISA directory in the RISA\RISA Key Manager\ folder. RISA Key Manager Shows up Blank If this happens the RISA Key Manager will look like this: General Reference Manual 59 . but let's first talk about what to do if the Key Manager doesn't read your key. Those include: l l l Copying the locking data from a computer Converting a key from standalone to network and vice versa Removing a feature from the key and sending RISA a removal confirmation code We will go through each of these processes.

RISA Key Manager If you are opening the RISA Key Manager just to view the Locking Data then this is how it should look. pressing the Upgrade button and inputting the RUS password. Sometimes some of the weaker USB ports (on a monitor for example) may not have enough power to run a key. A view of the key is shown in the Sentinel Key topic. If this is the case. If you are using the key. then press Upgrade and the key will then be upgraded. The key driver is not installed or is not working properly. this is a problem. Note: 60 RISA Licensing . You can check this by looking at the Device Manager and there is information on this also in the Sentinel Key topic. Try moving the key to a different USB port and make sure that the light on the key is on. Typical reasons why the RISA Key Manager would show up blank: l l l The key is not plugged into the computer. Uses For the RISA Key Manager Here are the two primary uses for this program. This can be done by clicking the radio button of the program you are updating. To install or modify your install of the driver see the Key Driver section of the Sentinel Key topic. The RUS password is located in the upgrade packet shipped to you or may be in an e-mail you received from us. Once you have input the RUS password. Upgrading a Standalone Key for a New Version For each major version of the program the key must be upgraded to the newer version. plug in the key and press the Refresh button. The USB port is not able to read the key. After this process you should then see the updated version next to that program and your key is then upgraded. however.

Note: l There is a New Style Codes checkbox.0 to 10. You can then open up an e-mail and paste (CTRL-V) the locking data into an e-mail. After the key is authorized. or any other programs you will want to uncheck the box. except make sure to check the "Change Key Type. this means that the key is already up to date for the version of the RUS password you entered. an update of RISA-3D from 10. The currently authorized program version exceeds the upgrade version. To do this follow the Upgrade procedure above. This is done by clicking the radio button of the program you are updating. The RUS password is located in the upgrade packet shipped to you or may be in an e-mail you received from us. Copying the Locking Data from a Computer The locking data is basically a code that is specific to your computer.0. Converting a Key from Standalone to Network and Vice-Versa If your company switches from standalone keys to network or vice versa then RISA will send you an RUS password to convert your key. Once you have input the RUS password." checkbox.1 will not require an update to the key. Upgrading a Network Key for a New Program A network key only has to be authorized for a program once.0. Whether you check this checkbox when copying locking data depends on what vetsions of RISA programs you are working with. RISA-3D 10. The currently authorized program version exceeds the upgrade version.0 and RISAFoot 4. If you upgrade the key and you get a message stating Unable to update Sentinel key. For example.0. Note: l If you upgrade the key and you get a message stating Unable to update Sentinel key.RISA Key Manager l l Minor releases do not require an update to the key. RISAConnection 2.. RISAFoundation 4. If you own a network version of RISA-3D and then purchase a network version of RISAFloor. Removing a Feature/Program from the Key and Sending RISA a Removal Confirmation Code When reconfiguring licenses sometimes there is a need to remove a program from the key. If you are using older versions. pressing the Upgrade button and inputting the RUS password. If you ever need this locking data (we at RISA may ask for it in rare instances). This can be done by: General Reference Manual 61 .0. this means that the key is already been authorized for that program. then upgrades do NOT require the key to be updated. then you will want to check the box. then you WILL need to update your key for RISAFloor.0. If you are using RISAFloor 6.. then you can press the "Copy Locking Data" button and it will paste this information to your clipboard. then press Upgrade and the key will then be upgraded. Miscellaneous Uses Here are some other uses that are much less common.

RISA Licensing . You be asked if you wish to continue. It will then tell you that the program has been uninstalled. Press the Yes button. Enter the RUS Uninstall Password that has been e-mailed to you from RISA and press the Uninstall but- ton.RISA Key Manager l l l l l 62 Clicking the radio button of the program you wish to install and press the Remove button. A final screen will come up with a Product Return Code that MUST be sent to RISA to confirm that the program has been uninstalled.

The user will have to close the model without saving. Example If RISA-3D Standalone is launched without the Sentinel USB Key attached the user is given an option to launch in Demo Mode. then launch the program with the key plugged in to enter Non-Demo Mode. and cannot be recovered. Launching in Demo Mode When a license cannot be found the option is presented to launch in Demonstration Mode. The 50 Joint model will be lost. even if the Sentinel USB Key is plugged in after the fact. General Reference Manual 63 . The Demonstration Mode has certain limitations. If the user creates a model with 50 Joints they cannot save it. and is intended to function both as a reader of existing files and as showcase of product features for those users who do not own the product.Demonstration Mode Demonstration Mode RISA Products all come equipped with a Demonstration Mode which can be accessed when a license cannot be retrieved. When in Demo Mode in RISA-3D no model with more than 40 Joints can be saved. Once the program has been launched in Demonstration Mode it cannot re-enter the regular Non-Demo Mode during the same session. That is because the program cannot switch from Demo Mode back to Non-Demo Mode.

including steps that can be taken to resolve them.Licensing Error Messages Appendix A . Each error has a code displayed in the header of the dialog box. What follows is a list of error messages. Error [1] Cause There is an inherent problem with RISA's customized Sentinel RMS service.Appendix A . Solution Contact RISA Support Error [2] This error is effectively the same as Error 1 64 RISA Licensing . The location of this error code is shown in the image below: Note l If you are commuting a license it is possible that two values will show up in separate brackets next the "RISA Network License Warning" header. within brackets.Licensing Error Messages Errors related to licensing are displayed in RISA dialog boxes.

Licensing Error Messages Error [3] Cause The client machine has been pointed to a specific server with the LS Query List registry entry or the LSFORCEHOST environment variable. Solution Confirm that there is a server with that name or IP address present on the network. If no such server exists then edit the LS Query List registry entry or the LSFORCEHOST environment variable to specify a new license server. however no licensing service (Sentinel RMS) was found running on the license server. and that there is no firewall preventing the client machine from communicating with that server. however that server cannot be found. General Reference Manual 65 . or leave these blank for the client machine to search the entire subnet for a license server. Error [5] Cause The client machine was able to contact the license server.Appendix A .

If it is not then load the sentinel service. This port must be opened up for two-way traffic at all locations between the client machine and the license server by adding port exceptions. UDP port 5093 is blocked at the license server. Contact RISA Support for a new license file and load that new license file. or anywhere on the network. If the key is being correctly read then an outdated license file is currently loaded. Error [11] This error is effectively the same as Error 1 Error [12] This error is effectively the same as Error 1 66 RISA Licensing . If not then resolve that issue. Windows Firewall is commonly overlooked by IT administrators.Appendix A . open the RISA Key Manager and confirm that the key is being correctly read. Error [6] Cause The Sentinel RMS service on the license server is either unable to read the Sentinel Key. but it is a common culprit. the client machine. or the information in the license file which has been loaded into the Sentinel RMS service does not match the information on the Sentinel Key. Solution On the license server. a router.Licensing Error Messages Solution Check the list of Services on the license server and confirm that Sentinel RMS is present and Started. Otherwise it is a firewall issue.

Solution Move the client machine in question to a group which has available licenses.Licensing Error Messages Error [14] Cause Communication between the client machine and license server is present. Contact RISA Sales to purchase additional licenses. If they are connected over a WAN or a VPN then try to increase the speed of the connection. General Reference Manual 67 . Return some licenses to the license server by closing the application on other client machines within the same group. The client machine is part of a group of clients which has exhausted its supply of licenses. or returning commuted licenses. or increase the number of licenses reserved for the group to which the client machine is currently assigned. Error [15] Cause Some licenses on the license server have been reserved by various clients on the network. Solution Decrease network latency between the client machine and the license server. If the client machine is connected wirelessly try using an ethernet cable instead.Appendix A . but is too slow to establish a usable connection.

Appendix A .Licensing Error Messages Error [17] Cause The client machine has searched the entire subnet (if it was allowed to do so) and was unable to find any license servers running the Sentinel RMS service. 68 RISA Licensing . Solution Confirm that the client machine is on the same subnet as the license server. Error [18] Cause The client machine was able to contact the Sentinel RMS service at the license server. If they are on different subnets the point the client machine directly to the license server using the LS Query List registry entry. however the service had no license loaded for the particular program/version of RISA software which the client machine is attempting to launch.

Licensing Error Messages Solution Confirm that the license server referred to in the error message is the correct one. and that the Sentinel RMS service is running on that license server. If both of these things are true then the license file on the license server is probably outdated. Error [37] Cause RISA has issued a trial license file with an expiration date. Contact RISA Support for a new license file and load that new license file. The license file is no longer valid as a result.Appendix A . Error [25] Cause The license server is running the wrong version of Sentinel RMS. Solution See the License Server Updater topic for information on migrating to the newest RISA-customized sentinel service. and that date has passed. General Reference Manual 69 . possibly one that is not customized by RISA.

The process where this may happen: a. c. WRCommute.exe is run on the local client computer. Error [70]: Commuter Code for this Feature Does Not Exist on the Client System Cause This occurs when there is an unknown issue with remote commuting. Cause This message can be caused by loading a bad license file on the license server. and OK is pressed.Licensing Error Messages Solution Contact RISA Support for a new license file. This is when this error is thrown. It means that the commute utility was not able to return unique information about the computer that is used to ensure the security of the commuted license. Error [0xC8001002] This error is effectively the same as Error 1 70 RISA Licensing . You may wish to right-click and "Run as Administrator" on the commuting executables. b. Solution Make sure that you are using the newest versions of the Sentinel commuting programs and make sure that you have and are using Administrator privileges. The string or file to copy string from is entered.exe is run on the remote client computer and the code is saved to a file or the string is copied. d. WCommute. Error [150] This error is effectively the same as Error 6. the "Check out authorizations for remote machine" checkbox is checked. Error [125]: Required Locking Criteria for Local Request is Not Available on Your Machine This error message will typically occur when attempting to commute a license from the license management server. make sure that you have a license available for commuting. and the number of days is selected. Also. Solution Contact RISA Support for a new license file and load the license file onto the license management server using WLMAdmin as described in License Administration. The program for the license that is to be checked out is selected.Appendix A .

Licensing Error Messages Error [0xC8001006] Cause All of the available licenses on the license server have been checked out. Error [0xC8001007] Cause The license machine does not have sufficient memory available to monitor the license file Solution Increase the amount of available memory on the license server by disabling other processes or installing more physical memory (RAM). or returning commuted licenses. No additional licenses may be checked out. Solution Return some licenses to the license server by closing the application on other client machines.Appendix A . Contact RISA Sales to purchase additional licenses. General Reference Manual 71 .

Licensing Error Messages Error [0xC8001008] Cause RISA cannot find an active network connection to the client machine Solution Confirm that the network card on the client machine is operating properly. The license file is no longer valid as a result. 72 RISA Licensing .Appendix A . Solution Contact RISA Support for a new license file. Error [0xC800100D] Cause RISA has issued a license file with an expiration date. and that date has passed. and that it is connected (either through a cable or wireless connection) to a network.

Network Installation Error Messages Appendix B .Network Installation Error Messages There are a number of common issues that you may encounter while installing or using the network version of the RISA programs. right click the Sentinel RMS License Manager. See the Sentinel Services topic for more information. The solution to this problem is to set up a port exception in the firewall. This can occur for a couple of reasons: l l l The name or IP address of the server was not entered properly. Contact RISA Technologies technical support (support@risatech.Windows Firewall). Note:  l If the license management service shuts down almost immediately after start-up. the cause of this error is a firewall on the client. How to accomplish this is dependent on the type of firewall. Note:  l The port that needs to be open is 5093 and the communication protocol is UDP. this may be caused by a resource conflict between a recent Windows Update and the license management service. The service has not been loaded or is not running. Alternate Solution: The Sentinel RMS service on the license management computer has been stopped: To re-start the service. General Reference Manual 73 . These can be grouped into the following main categories: Firewall Issues or Error Code 3: Failed to resolve the server host.Network and Internet Connections . Solution:  Frequently.Appendix B . server. go to the list of servcies (Control Panel – Administrative Tools – Services) on the license mangement server. There is a network issue which is preventing communication with this computer.com) for more information about resolving this conflict. Below is the Windows XP dialog for setting the port exception (Control Panel . This means that the WLMAdmin utility was not able to communicate with the server listed in the list of Defined Servers. or network.

it is most likely to occur if the information on the Sentinel SuperPro USB key (KeyID and program authorization) does not match the information contained in the license file. However. In either case.Appendix B . See also the write up for error code 19. However. This could mean that the key is not being read. the solution to this problem is to use the Defined Server List to administer the licenses. This can happen for two reasons. or because the key ID doesn’t match. 74 RISA Licensing .Network Installation Error Messages Error Code 17 This message occurs most often when the user double-clicks on the list of subnet servers and the utility does not find any servers on the subnet. the existing (non-customized) copy of Sentinel RMS or Sentinel LM must be removed and replaced with the customized version of Sentinel RMS version 8. the error may also be given for situations where the issues described in the write-ups for error code 92 or 150 exist. The server did not respond to communication. See the Sentinel Services topic for more information. Error Code 93 Duplicate License: The license file could not added because it is a duplicate of one which already existed on that server. Note:  l RISA’s customized version of Sentinel RMS is capable of loading the license files for most other applications (CSI. Error Code 19 This is a generic message that means the adding of the license file failed. et cetera). Solution: Contact RISA technical support (support@risatech. The service has not been loaded or is not running. Therefore. However. This error message can happen for a number of reasons. that the key doesn’t have authorization for the same programs as the license file. this one is more likely to occur if the server is running a non-customized version of the Sentinel License Manager. TEDDS. Error Code 92 This means that the license file was invalid. l l l There are no servers located on the subnet.com) for a new license file or for an RUS password to update the information on your USB key. However. Solution:  RISA uses a CUSTOMIZED version of Sentinel RMS. the error message is really just an informational warning message and can be ignored. See the License Server Updating utility for more information on updating your service. Error Code 150 (Sentinel RMS) Lock Code Invalid: This error message usually means that there is a problem reading the key. any application that requires its own customized version will not function from within RISA’s version of the Sentinel RMS License Manager.5 provided with your RISA installation. This message is very similar to the issue described in the write-up for error code 19. Refer to those error codes for more information. This can occur if the user is adding in a license file that has 2 licenses. In that case. only one of which is new or updated.

type regedit in the Open box. The newer versions of the Sentinel license management software is not compatible with these very old operating systems. General Reference Manual 75 . When it has been plugged in a green light will appear on the key indicating that it is receiving power. If the USB key cannot be read. this may be for one of the following reasons: l l l First verify that the Sentinel Key is plugged into the license management server. Two items to check: 1. Check the permissions on the C:\RISA\Sentinel RMS directory and verify that it has read/write permissions. If you are running a virtual server. click Run. The required version of the Sentinel SuperPro / UltraPro device driver is 7. Most of them are problems specific to your network connectivity or permissions. 2. is a network key and is authorized for the appropriate programs.5. the hardware key may connected to a USB on the host computer. but may not be specifically assigned to the virtual machine. A couple of specific items that can help: Entry Point Not Found Message This message will occur if you are trying to start the Sentinel RMS service on a Windows 2000 operating system or older. The driver for the Sentinel SuperPro key may need to be updated. and then click OK. Problems Loading the Service There are different items that could cause the service not to load. or downgrade your sentinel service to an older Sentinel LM service.1 or higher.Appendix B . Check permission on the registry entry for Sentinel RMS: On the Windows Server 2008-based domain controller. Locate and then right-click the following registry sub-key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sentinel RMS License Manager Choose Permissions. Error 5: Access is denied This likely has something to do with the permission setting on the Sentinel RMS License Manager registry key or possibly the permissions directory where the license manager resides. Your solution is to either upgrade the operating system on your server... and check to make sure you have administrative permissions here. click Start.Network Installation Error Messages Solution: Verify the information on the hardware key using the RISA Key Manager utility to make sure that that the key has the proper KeyID. The version of the driver may be viewed in the Windows Device Manager.

try the install on the other server and it will likely work. For server installs.com/d_updates.html page then it is required that you have the initial install installed (for example v9.Network Installation Error Messages Update Requires Previous Version Be Installed This message typically has two main causes.1). If you are downloading the install from a link specifically sent to you and you are still getting this message. There may be some extraneous registry folders at the root of the problem that can be deleted in this registry location (Start>Run>type Regedit): HKLM\software\microsoft\windows\current version\uninstall\ 76 RISA Licensing . If this is the case you may be trying the install on the opposite server as the one that you did the initial install on.1. the first being much more common than the second.1. Talk with Technical Support for help.0 must be installed before v9. If so.risa. If you still can not figure out what is happening see the Technical Support topic. many times there is the license management server and the file server that are actually different servers.Appendix B . then you may be seeing a registry issue with the Install Shield Wizard. The program checks to see if there is a registry entry for this initial version and if it does not find it then it will produce this error. l l If the install was downloaded from the www.

A defective CD drive may result in good data not being read properly. The Program Files directory is one that requires elevated privileges to work General Reference Manual 77 . go to the C:\Program Files\Common Files\InstallShield\Professional\. Cause 1: Corrupted CD or Defective CD Drive A corrupted CD may result in bad data. but do come up from time to time when trying to install the program. Feature Transfer Error The cause of this error can be a number of things. Rename the “RunTime” folder to “RunTimebak” and then try the install again.com and ask for the install.Standalone Installation Error Messages There are an assortment of installation errors that are very uncommon. folder.Standalone Installation Error Messages Appendix C . Below are some potential causes and possible solutions for each. Here is a listing of a few of these items: Error -5009 0x8002802b This error can happen when installing the standalone version of RISA products. Cause 2: Corrupted Web install. If you do not have access to this e-mail support@risatech. Try to download the install packages again. There are some instances where downloading the install will alter the install file and corrupt it. If this does not work try to uninstall and re-install the program. Cause 3: Installing without Administrative Privileges. If this occurs download and run the web install. To fix this. This is a problem if you are installing to a directory (such a C:\Program Files and its subdirectories) that require administrator privileges.Appendix C .

com/en-us/sysinternals/bb896652. Cause 4: Not Enough Hard Drive Space If the hard drive on this machine is very full then there may not be enough room on the hard drive for temporary files to be placed. This could also be a little more difficult then just this. Cause 5: Size or Restrictions on Temporary Directory There may be problems that occur when the web install extracts its files a temporary location due to size or other restrictions with that directory. To get more information on and download FileMon and RegMon. Cause 7: Lack of Privileges on Network Drive Lack of correct privileges on a network drive where install is located can prevent the install from successfully being run from that location. see the following URLs: http://technet. A solution is to disable anti-virus. install to the C:\RISA directory and this will likely fix the problem. run the install.microsoft.com/en-us/sysinternals/bb896642.exe in that directory to start the install. You can also rerun the install as and administrator and that should fix the problem also. The solution is to copy the install to a local drive and run it from there 78 RISA Licensing .Standalone Installation Error Messages with.microsoft. it may turn out that when the RISA-3D install program attempts to add a shortcut to the folder C:\Documents and Settings\All Users\Desktop that neither you or the administrator group have permission to this folder.Appendix C . Clean your hard drive to remove old temporary files and other files that are no longer necessary and then run the installs again. Cause 6: Anti-Virus Issues It is possible that necessary files that are temporarily placed on system are being deleted by an Anti-Virus or another similar program. and then re-enable anti-virus. You would then add permission to the folder so that your install will not have any access errors. If this is a problem. A solution to this is to run the install from CD or extract the files to a particular directory and click on Setup.aspx http://technet.aspx For example.

not including holidays.Technical Support Technical Support Technical support is an important part of the RISA software package. We will likely need to navigate with you to specific places on your machine to troubleshoot your issue. Most questions asked about RISA Licensing are already answered in the Help File or General Reference Manual. Use the table of contents or index to find specific topics and appropriate sections. the quicker we can get you an effective solution. We go to great lengths to provide extensive written and on-line documentation for the program. Monday through Friday. But please be at the problematic workstation when you call. Technical support is very important to the staff at RISA Technologies. Phone Support:(949) 951-5815: Feel free to call. The more information we get about the problem. serial number or Key ID. including screen captures of any error messages that you are having trouble with. please search the Help File or General Reference Manual.  Email: support@risa. Make sure you tell us your name. Before contacting technical support.com Please give us detailed information about your specific problem. company name. Hours: 6AM to 5PM Pacific Standard Time. We want our users to be able to reach us when they are having difficulties with the program. We do this in order to help you understand the features and make them easier to use. phone number. especially if you need a quick answer. General Reference Manual 79 . and a problem description. There is no charge for technical support for all licensed owners of the current version of RISA software.

.

Index Index B N Blank RISA Key Manager 59 Network Client Install 37 C Check for Updates 16 Converting a Key 61 Copying the Locking Data 61 D Defined Server List 32 Network Installation Error Messages 73 Network Server Install Overview 20 P Phone (support) 79 Pointing the Client to a License Server 46 R Demonstration Mode 63 Remote Commuting 50 E Removing a Feature/Program from the Key 61 Email (support) 79 RISA Key Manager 59 I S Install Network Server from an Email Link 21 Sentinel USB Key 57 Install Standalone from an Email Link 9 SSD Cleanup 58 Installing Standalone from the CD 2. 30 Upgrading a Network Key 61 Upgrading a Standalone Key 60 Usage Reports 35 General Reference Manual i . 20 Standalone Install 2 K Standalone Installation Error Messages 77 Standalone Licensing 18 Key Driver 57 System Requirements 1 L T License Commuting 49 Technical Support 79 License Service Updater 28 Licensing Error Messages 64 Loading (Adding) a License File 31 Local Commuting 49 Losing Network Connection 47 LS Query List 46 U Unloading (Removing) a Sentinel Service 28.