network installations instructions

8/20/2019 Network Installations Instructions

1/85


2/85

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.


3/85


4/85

Table of Contents

II RISA Licensing

Appendix C - Standalone Installation Error

Messages 77

Technical Support 79


5/85

Before You Begin

Before You Begin

Thank you for purchasing RISA Software. 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 Microsoft Windows 8 (32 bit or 64 bit)

l Microsoft Windows 7 SP1 (32 bit or 64 bit)

l Microsoft Windows Vista SP2 (32 bit or 64 bit)

l Microsoft Windows XP SP3 (32 bit only)

Network Server Operating System Requirements

One of the following operating systems is required:

l Microsoft Windows Server 2012

l Microsoft Windows Server 2008 R2 SP1

l Microsoft Windows Server 2008 SP2

l Microsoft Windows Server 2003 SP2

l Microsoft Windows 8 (32 bit or 64 bit)

l Microsoft Windows 7 SP1 (32 bit or 64 bit)

l Microsoft Windows Vista SP2 (32 bit or 64 bit)

l Microsoft Windows XP SP3 (32 bit only)

License Manager Requirements

RISA requires and provides the Sentinel RMS 8.5.1 license manager in the installation. If you are running an

older version of the license manager then you will be prompted to update using the License Server Update util-ity.

Note

l You can not have multiple versions of the Sentinel license manager service on a single server , or the

license manager will not properly work.

l RISA uses a customized version of the Sentinel RMS 8.5.1 license management service. Thus, to run RISA

on your server you must install RISA's license manager. However, nearly all other software that uses the

Sentinel license manager can be run from the RISA customized version.

l There is one l icense manager called Sentinel HASP that can be run concurrently with RISA's customized

license manager.

General Reference Manual 1


6/85

Standalone Installation Instructions

These instructions are intended for the standalone versions of the software. If you have a network license,

please see the Network Server Install and the Network Client Install topics.

Where to get the Install

If you are current with your maintenance, 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. If you

misplace this CD and are still under maintenance, you can also contact [email protected] to re quest an install-

ation link and RUS Password, which we can email you right away.

The minor updates (third digit updates) are not automatically mailed out, 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 do not have the previous version installed, you can always email our licensing department

([email protected]) for a link to the full version installation link.

Note:

l Our FTP site is always updated to only contain the most recent installations, therefore, we can only email

you an installation link for the most current version. RISA Technologies does not keep updates availablefor older versions.

Installation Instructions

The Standalone install will walk you through each step. You may run this install from the CD or from the email

link that our licensing department has sent you. Below are the step-by-step instructions for both.

Note:

l You must be an Administrator on the machine in order to run this install.

Installing from the CD

1. Make sure that your Sentinel USB key is unplugged during the inst allation process.

2. Insert t he install CD into your CD drive. If the CD starts automatically, go to step #3 below. If the CD does

not start automatically after 10 seconds, click the Windows Start button and select My Computer. Double-

click the RISA icon:

2 RISA Licensing


mailto:[email protected]?subject=RUS%20Password%20and%20Installation%20Requestmailto:[email protected]?subject=RUS%20Password%20and%20Installation%20Request


7/85

Standalone Installa tion Instructions

3. Click on Install Products:

4. Select the Standalone option:



8/85

5. From the Welcome screen, click Next :

6. Accept the terms of the license agreement and click Next again:

4 RISA Licensing



9/85


7. The following Default Region Setting dialog only occurs for RISA-2D, RISA-3D or RISAFloor installat ions. If

you are running one of these installations select your Region, and click Next . If not, then continue onto

number 8 below to via the next dialog.

8. Click Next to accept the default installation destination and continue the installation:



10/85

9. If you have a previous version installed, you will get the following dialog that confirms the upgrade. Click

Yes to continue.

10. Click Next :

6 RISA Licensing



11/85


11. Click Next and the installation will proceed, or Back to change the previously entered settings::

12. Make sure your Sentinel USB key is unplugged and click OK .



12/85

This will automatically launch the Sentinel System Driver Installer that will install the key driver.

-

13. After the installa tion is complete, check the box to have the installa tion routine check RISA's website for

available updates, and then click Finish:

8 RISA Licensing



13/85


14/85

3. Click on the St andalone installation file and select Run:

4. If you receive a Security Warning, click Run again to continue with the installation:


10 RISA Licensing



15/85


6. Accept the terms of the license agreement and click Next again:

7. Select your Region and click Next :



16/85

8. Click Next to accept the default installation destination and continue the installation:

9. If you have a previous version installed, you will get the following dialog that confirms the upgrade. Click

Yes to continue.

12 RISA Licensing



17/85


10. Click Next :

11. Click Install:



18/85

12. Make sure your Sentinel USB key is unplugged and click OK .

This will automatically launch the Sentinel System Driver Installer that will install the key driver.

14 RISA Licensing



19/85


-

13. After the installation is complete, select Yes to check for program updates and then click Finish:

14. Now, startup your RISA program and plug your Sentinel USB key back in.

15. If you have not already updated your key through the RISA Key Manager, it will ask you for your RUS Pass

word. Enter the RUS Password and click Upgrade:



20/85

16. Now you are ready to use the program.

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.

If it finds a newer version, it will offer you the option to open your Internet Explorer to our Updates page where

you can download the install.

You can also access this feature from within the RISA program. Simply go to Help - Check for Updates to run

this feature from within your program.

16 RISA Licensing


http://www.risatech.com/d_updates.html


21/85


Installation Options

In general, 99% of users will want to use the default installation options. However, each option is described

below for the more advanced users:

Region

This setting controls what default design codes, shape databases, and load combinations show up in the program.

Overwrite Existing Defaults

If you change the region from a previous install and want all the default codes, databases, and load combinations

to also update, please select the Overwrite Existing Defaults option. This will delete and replace all the pre-

viously installed default files.

Complete vs. Custom Install

This setting controls what features are going to be installed. If you select Complete, all features will be

installed. If you select Custom, you will have the additional step to select which features you want to be

installed.

Destination Folder

This setting controls what folder your program files are installed into. During use of the RISA program, the pro-

gram will need to read from and write to this folder, so by default it is installed into the C:\RISA folder which

has less permissions restrictions than Program Files.

Program Folder

This selection controls which folder the program will show up under in the Windows Start menu.



22/85

Standalone Licensing

RISA st andalone products use a Sentinel USB Key for licensing. This key allows the owner to install

RISA products on many different machines without violating the license agreement. In order to run a RISA

product the key must be plugged in at all times.

Launching the RISA ProductWhen launching a RISA standalone product the product will search for a connected Sentinel USB Key. 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.

Removing the Key

RISA Products periodically check to ensure that the Sentinel USB Key is plugged in. Removing the Sentinel

USB Key during the operation of a RISA standalone product will eventually cause the following dialog box to bedisplayed:

Once this dialog box is displayed, no additional work may be done within the RISA Product until the key is inser-

ted. 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.

18 RISA Licensing



23/85


Remote Desktop

Currently RISA does not support the use of Remote Desktop for standalone licensing.



24/85


25/85

Network Server Installation Instructions

4. Select the Network Server option:

At this point installing from the CD and installing from an e-mail link are identical. So, follow the instructions

from item #3 below to continue on with the network installation.

Installing from an E-mail Link

1. Click on the e-mail link. This will launch your web browser and take you to a Downloads page on the RISA

Technologies website as shown below. Click on the Network installation file. This should be of the form

WebXX_vvv_net.exe" where XX is a two digit code for the program (3D for RISA-3D, RF for RISAFoot, FL,

for RISAFloor et cetera) and vvv is a one to three digit code for the version (912 for version 9.1.2, et cet-

era).

2. This will normally bring up a File Download dialog similar to t he one shown below. Click Save to down-

load the install routine to your computer (to run later) or select Run to download and run the installation



26/85

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.

If you receive a Security Warning regarding an "unknown publisher", click Run again to continue with the install-

ation. In future releases RISA will add a digital signature to our programs to prevent this type of warning from

being displayed.


22 RISA Licensing



27/85


28/85

6. Choose which components to install and click Next.:

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.

24 RISA Licensing



29/85


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

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.

It is recommended that you leave the default settings (all boxes checked) before clicking Next to continue with

the install.

7. Click Next on the Ready to Install confirmation screen:

8. The Setup Stat us window will open up as shown below:



30/85

The Installation routine will then install the directory and files necessary for the network server and client

installs.

9. 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.

26 RISA Licensing



31/85


10. If the Update Sentinel License Management Service feature was chosen in step 5, then the License Ser-

vice Updater utility will automatically launch. Refer to the topic titled License Service Updater for more

information on using this utilit y.

After the License Service Updater is finished running, there will still be two steps to completing a network

install.

11. Administering the licenses by adding the new license file by running the WLMAdmin utility. This isdescribed in the License Administration topic.

12. Install ing the program on a client machine. This is described in the Network Client Install topic.



32/85

License Service Updater

Sentinel Service Overview

RISA uses a customized version of the Sentinel RMS 8.5.1 license manager to maintain and distribute licenses.

The non-customized version of Sentinel RMS, which is used by other software vendors, is not compatible with

RISA licensing. However, the customized version of Sentinel RMS is typically compatible with the licensing of

other software vendors.

Compatibility

The RISA customized version of Sentinel RMS cannot be run in conjunction with any of the following services:

l Non-customized versions of Sentinel RMS

l Any version of Sentinel LM

l Any version of Sentinel LM or RMS which has been customized by other third partie s (e.g. Eagle Point)

Loading (Adding) the Sentinel Service

The steps below describe the process to load the Sentinel Service. However, this process is now automated with

the License Service Updater utlity described in the section below. :

1. Open the list of Services. This can be accessed through the Administrative Tools portion of the Windows

Control Panel.

2. Confirm that no existing Sentinel se rvices (i.e. Sentinel LM or RMS) are running. If any such service is r un-

ning then it must be unloaded (removed).

3. Run the LoadLS.exe Utility (default installation folder is C:\RISA\Sentinel RMS 8.5.1\)

4. Click the A dd button, then click OK

Unloading (Removing) a Sentinel Service

The steps below describe the process to unload a Sentinel Service. If you hae an existing Sentinel LM service

then the License Server Updater (described in the next section) will automatically evaluate / assess your exist-

ing license services to determine compatibility with RISA's customized service.


Control Panel.

2. Double-click on the Service to be unloaded.

3. Check for the service's Path to Executable and navigate to that folder in Windows Explorer.

4. Run the LoadLS.exe Utility which should be present in that folder

5. Click the Remove button, then click OK


As part of the install routine, the License Service Updater (ServerUpdate.exe) will run. This utility, shown below,

analyzes the computer and gives a summary of the Sentinel LM or Sentinel RMS license management servicesthat are currently loaded. This utility can be found in the 'Sentinel RMS 8.5.1' sub-directory of the server install

directory. 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.5.1 required to run the latest RISA software.

28 RISA Licensing



33/85


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.EXE executable resides). If the path is blank, that means that that par-

ticular license service was not detected on the computer.

If Info data gives basic information about the detected license service. This includes the status of the service

(whether it is currently running, stopped, or disabled), the version of the service, and whether that version has

been customized by RISA Technologies.

StatusThe Status section provides a summary of the analysis and instructions for continuing. If you wish to exit out of

this dialog without making any changes click the button on the upper right hand of the dialog to cancel out of

the dialog.

Generally, when updating from a previous version of the Sentinel Licensing service, a message will be provided

that instructs the user to click Update to install t he new version of the license service. 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. If this happens, just

click the button on the upper right hand of the dialog to cancel out of the dialog.

What Happens When Update Is Clicked?

When the user clicks the Update button, this utility will do the following:

l Unload or Remove the existing Sentinel LM and Sentinel RMS license Management Ser vices.

l Copy the license file information from these older services into the license file for the new license man-

agement service.

l Load the new version of the license management service which is a RISA customized version of Sentinel

RMS version 8.5.1.



34/85

Sentinel Service

RISA uses a customized version of the Sentinel RMS 8.5.1 license manager to maintain and distribute licenses.

The non-customized version of Sentinel RMS, which is used by other software vendors, is not compatible with

RISA licensing. However, the customized version of Sentinel RMS is typically compatible with the licensing of

other software vendors.

Compatibility

The RISA customized version of Sentinel RMS cannot be run in conjunction with any of the following services:

l Non-customized versions of Sentinel RMS

l Any version of Sentinel LM

l Any version of Sentinel LM or RMS which has been customized by other third partie s (e.g. Eagle Point)

Loading (Adding) the Sentinel Service

The steps below describe the process to load the Sentinel Service:


Control Panel.

2. Confirm that no existing Sentinel se rvices (i.e. Sentinel LM or RMS) are running. If any such service is r un-

ning then it must be unloaded (removed).

3. Run the LoadLS.exe Utility (default installation folder is C:\RISA\Sentinel RMS 8.5.1\)

4. Click the A dd button, then click OK

Unloading (Removing) a Sentinel Service

The steps below describe the process to unload a Sentinel Service:


Control Panel.

2. Double-click on the Service to be unloaded.3. Check for the service's Path to Executable and navigate to that folder in Windows Explorer.

4. Run the LoadLS.exe Utility which should be present in that folder

5. Click the Remove button, then click OK

30 RISA Licensing

Sentinel Service


35/85

License Administrat ion

License Administration

The utility used for administering licenses on the license management server is WLMAdmin.exe. This utility is

primarily used for adding new programs (or versions) onto the existing license management server. However, 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.

This utility will be located on the License Management Server in the "\Sentinel RMS\" sub-directory of the maininstall directory (usually C:\RISA\). 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\). The utility may be run

from either location.

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:



36/85

1. Make sure that you have a copy of your new license file in an accessible location. If you do not have a

copy of this license file, e-mail [email protected] to request a license file.

2. Execute t he WlmAdmin utility and open the Subnet Server s tree on the left hand side of the WlmAdmin

dialog. This can be done by double-clicking on the Subnet Servers text or by clicking the plus sign next to

the text.

Note: If the License Server is accessible by subnet broadcast that computer should appear under Subnet

Servers. If it is not listed, refer to the section below titled Using the Defined Server List for more inform-

ation.

3. If the Sentinel RMS license management service is up and running on the server , then the name of the

server should now be shown in the sub-net server tree. 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. An Open dialog will come up. Browse to the license file and open it. The name of the license file should be

"RISA_LM_KeyID" where KeyID is the ID number of your SuperPro USB key.

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

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.

Chief among them is that the computer running the WLMAdmin utility may not reside on the same subnet, or

that there may be some firewall which is preventing communication between the client and the server. In these

cases, the easiest solution is to add the License Management Server to the list of defined servers. This can be

accomplished by doing t he following:

1. Make sure that you have a copy of your new license file in an accessible location. If you do not have a

copy of this license file, e-mail [email protected] to request a license file.

2. Run WlmAdmin utility and select Edit -=> Defined Server List from the Main Menu Toolbar to bring up the

dialog shown below:

3. Type in either the IP address or the DNS name of the license management server, then click Add and OK.

4. The server should now appear in the Defined Server list. Right click on the name of the License Se rver

and select

32 RISA Licensing


mailto:[email protected]?subject=Please%20Send%20a%20License%20File%20for%20Company%20(xxxx)%20with%20Key%20ID%20(xxxx)mailto:[email protected]?subject=Please%20Send%20a%20License%20File%20for%20Company%20(xxxx)%20with%20Key%20ID%20(xxxx)mailto:[email protected]?subject=Please%20Send%20a%20License%20File%20for%20Company%20(xxxx)%20with%20Key%20ID%20(xxxx)


37/85

License Administrat ion

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

work 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 ver-

sion. 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 RISASec

tion 2.0 and the selected user is joshp.



38/85

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

ture / 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 WLMAdmin ret urns Error Codes 19, 92, or 150 when attempting to add in the license file

l WLMAdmin cannot locate t he Sentinel RMS License Management server, e ven when using the Defined

Server List. See error code 3 in Appendix B for more information on resolving this issue.

34 RISA Licensing



39/85


40/85

l Access will sometimes give error messages about needed to convert t he 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 create d above in the step t itled Converting a Usage Log File Into an

Access T able. 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 fea-tures).

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 l icenses of all licenses on the server. You cannot restr ict 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 stoppingand 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 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

36 RISA Licensing

Advanced Network Features


41/85

Network Client Instal

Network Client Install

These instructions are intended for the network client versions of the software. If you have a standalone license,

please see the Standalone Install topic.

Where to get the Install

The network client install is placed on the License Server during the Network Server Install. The default install-

ation folder on the license server is:

C:\RISA\xxxServer\vv_vv_vv

Where xxx is the name of the program (2D, 3D, Floor, etc) and vv is the version number. For example, the Net-

work Client install for RISABase 2.0.4 would be at C:\RISA\BaseServer\2_04_00

Note:

l If the network client install files ar e not in this default location it is possible that your network admin-

istrator has moved them to another location. If this is the case then please check with your network

administrator for their location.

Installation Instructions

The Network Client install will walk you through each step.

Note

l You must be an Administrator on the Client Machine in order t o run this install

1. Find the installation folder on the server and run Setup.exe

2. Click Next at the Welcome Screen

3. Review the License Agreement and click I Accept , then click Next .



42/85

4. Some RISA software (RISA-2D, RISA-3D, and RISAFloor) comes with regional default settings. Choose the

region which is most appropriate for you. Check the Overwrite Existing Defaults box to have the program

replace default settings from a previous installation with the latest ones. Click Next .

5. Choose a destination folder for the program on the Client Machine. The default is C:\RISA. Then click Next .

38 RISA Licensing



43/85


6. If a previous version of the program alr eady 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.

7. Choose a destination folder in the Windows Sta rt Menu where the launch icon for the program should go,

then click Next .



44/85

8. A final confirmation screen will appear next. Click Install to begin the installation. The installation may

take several minutes.

9. Once the installation is complete you may have the program check for updates. Choose whether the

installer should take t his last step, then click Finish.

40 RISA Licensing



45/85


10. 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. This means that a newer version of the program must be installed on your

server. Please have your IT administrator contact RISA Technologies to get this update. Click OK to launch

the RISA Release Notes website in your web browser, and review what new features are available.

11. Be sure to l aunch the program as an Administrator the first t ime you run it. This ensures that all of theprogram'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



46/85

Using the network.ini File to set Advanced Registry Entries

There is a file, Network.ini, which gets installed into the 'Sentinel RMS 8.5.1' subdirectory on the server. This file

can be used to automate the setting of the “LS Query List” registry value on the Client machines. This entry is

necessary for wide area networks where the client and the server do not reside on the same subnet. However, it

can be used to speed up license validation between client and server for any type of network.

You may use network.ini to have the License Server’s address automatically written to t he end user’s re gistry byfollowing these steps:

l Network.ini must be placed two folders up from the setup.exe used to launch the client install. This usu-

ally ends up being the the directory on the server.

l The client installation looks for Network.ini. If it finds that file it searches for the section header [LS

Query List] and the parameter I nitialize=.

l For update installa tions:o If the “LS Query List” registry entry under the Application Registry Key does not already contain

the address of a license sever, t he installation will write as the value in

the “LS Query List” registry entry

l For a new install :o In the Application Registry Key, the “LS Query List” value is set to .

So for the following Network.ini file:

[LS Query List]

Initialize='192.168.100.52'

The “LS Query List” registry entry gets set to the value 192.168.100.52

Performing a Silent Client Installation Using the SETUP.INI File

You may use a silent installation to avoid interacting with the client installation dialogs and you may auto-

matically run the silent setup in a log-on script or through the registry. Silent setup uses the SETUP.II file in

\ \ to guide the client installation. This file, as provided, will install

the above files to the client’s C:\RISA directory and place a program shortcut in the RISA folder on the Start-Pro-

grams menu.

Note:

l This procedure is only valid for installation routines creat ed using the Install Aware i nstallation package.

That includes RISABase version 2.1 or higher, and RISA-3D version 11.0 or higher. Older versions of the

install routine can still perform a silent install. However, the procedure will be described in the section

titled Performing a Silent Install using the Setup.ISS File.

To execute the silent installation from the client, execute the setup.exe file with the “/s” switch. The entire com-

mand line would look something like this:

\ \\setup.exe /s

Where is the mapped drive and directory on the file server containing the \\ directories. This can be called through a DOS prompt on the client, a log-on script or client

registry e ntry.

Editing the SETUP.INI File

If you wish to change the Install Directory, Program Folder, Region and Overwrite optionse, you can do so by

editing the SETUP.INI file in the subdirectory. This file is capable of storing installation

42 RISA Licensing



47/85


information for mulitple programs. So, you will want to locate the section header for the program installation

you wish to modify. For example, below is the infromation block fore RISA-3D.

[RISA-3D]szDir=C:\RISAszGroup=RISARegion=0DefOverwrite=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.

Region is a number indicating the progam's region settings (0 – United States, 1 – Canada, 2 –

Great Britain, 3 – Europe, 4 – India, 5 – Australia, 6 - New Zealand, 7 – Mexico, 8 – Saudia Arabia).

This entry only exists for RISA-2D, RISA-3D and RISAFloor.

DefOverwrite is a setting that controls whether you wish to overwrite existing defaults. (0 – No, 1

– Yes). This entry only exists for RISA-2D, RISA-3D and RISAFloor.

You may wish to rename the SETUP.INI file or store it in a common location for all RISA programs (i.e.C:\RISA\ instead of C:\RISA\\\). To specify a setup.ini file in a dif-

ferent location than that containing setup.exe, use the following syntax:

setup.exe /s INIFILE= C:\Share\RISA_setup.ini

Performing a Silent Install Using the Setup.ISS File

You may use a silent installation to avoid interacting with the client installation dialogs and you may auto-

matically run the silent set up in a log-on script or through the registry. Silent setup uses the SETUP.ISS file in

\ \ to guide the client installation. This file, as provided, will install

the above files to the client’s C:\RISA directory and place a program shortcut in the RISA folder on the Start-Pro-

grams menu.

Note:

l This procedure is only valid for installation routines cre ated using the Install Shield Wizard. That includes

any install routine created prior to October, 2012 (RISA-3D version 10.0.1 or lower). Newer versions of

the install routine can still perform a silent install. However, the procedure will be described in the pre-

vious section titled Performing a Silent Client Installation using the SETUP.INI File .

To execute the silent installation from the client, execute the setup.exe file with the “/s” switch. The entire com-

mand line would look something like this:

\ \\setup.exe /s

Where is the mapped drive and directory on the file server containing the \\ directories. This can be called through a DOS prompt on the client, a log-on script or client

registry e ntry.

To record a new or customized SETUP.ISS file, you can use the “/r” switch. This initiates a new client setup and

will record all the information that you enter during the setup. The SETUP.ISS file will need to be copied from

the C:\WINDOWS folder on the client computer to the \ directory before it

can be used for a silent install. In addition, you will probably have to redirect the SETUP.ISS file away from the

C:\WINDOWS folder. This can be done with the "/f1" switch.

\ \\setup.exe /r



48/85

/f1g:\okfolder\setup.iss

In this case, the SETUP.ISS file would be created in the G:\OKFolder\ directory.

If you wish to manually change the Path or Country options, you can do this by editing the SETUP.ISS file in the

subdirectory.

To change the PATH into which the client version gets installed, 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, 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, 2=British, 3=Europe, 4=India, 5=Australia,6=New Zealand, 7=Mexico

This file is setup for United States because the option Region=0. If you wanted India to be the selected country

you would change the Region=4.

SILENT INSTALLATION ERROR MESSAGES

Be aware that no messages are displayed when running a silent installation. You may view the Setup.log file to

determine the result of the setup. To verify if a silent setup succeeded, look at the ResultCode value in the

[ResponseResult] keyname. 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.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 t ype

-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 sele cted

44 RISA Licensing



49/85


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 (don’t type the symbols)

To redirect the log file the example above would now look like this:

\ \\setup.exe /s /f2g:\ok

folder\setup.log



50/85

Network Licensing

RISA network products are licensed with a License Server. 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. If

no key is found then the program will search the subnet for a License Server. If a License Server is found then

the program will check out a license (if available).

If no license server is found, or if no licenses are available, you are presented with the option to enter Demo

mode. If you believe that this is happening in error the two general problems are:

l A firewall is blocking communication. To fix this problem you must set an exception for UDP port 5093 on

both the server and client for both inbound and outbound.

l The license broadcast is timing out. To fix this follow the Pointing a Client Machine to a License Server

section below.

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. To do this, open the Registry Editor on the Client Machine by clicking on the Windows Start But-

ton, clicking in the Search box, and typing regedit , then hit Enter.

Note:

l The instructions above are valid for Windows 7. If you are running a different version of Windows then

the procedure may be slightly different.

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, RISASection, or RISAConnection:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\RISA Technologies\RISAxxx Network\vv

46 RISA Licensing

Network Licensing


51/85

Network Licensing

Where xxx is the name of the RISA product in question and vv is the version number of the product in question.

For example, RISABase Version 2.0 would be ...\RISA Technologies\RISABase Network\2.0

Note:

l RISAFloor V7 and later , RISA-3D V11 and later, RISAFoundation V5 and later, RISA-2D V12 and later, and

RISABase V2.1 and later all have both 32-bit and 64-bit capabilities and will be installed appropriately on

32 and 64-bit operating systems. Older versions of these programs were always 32-bit. If a 32-bit applic-

ation is installed on a 64-bit operating system then the registry location is in the Wow6432Node loc-

ation.

l RISASection, RISAConnection, and RISAFoot are all 32-bit applications that will go into the Wow6432Node

location on 64-bit operating syste ms.

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. Then hit OK and exit the

registry editor. This will point your client machine directly at the license server.

Losing Network Connection

RISA Products periodically check the connection to the License Server. Severing this connection during the oper-ation of a RISA network product will eventually cause the following dialog box to be displayed:



52/85

Once this dialog box is displayed, no additional work may be done within the RISA Product until the network con-

nection (and the license from the License Server) is restored. 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.

48 RISA Licensing

Network Licensing


53/85

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. This process is called "commuting". This feature is com-

monly 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.

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. It does require the client machine to be connected to the network at the time of license check-out, 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).

Prerequisites

l The client machine must be connected to the network, with direct access to the license server.

l

The license server must have at least one available license for the product which is to be commuted.l The appropriate RISA product (i.e. RISA-3D) must be installed on the client machine. This must be a Net-

work Client Install .

Procedure

On the client machine, run the following utility:

C:\RISA\Sentinel RMS\Commute\WCommute.exe

This will launch the following dialog box:

l To have the WCommute utility sea rch the entire subnet for license ser vers, click the Search Subnet but-

ton.



54/85

l To point the WCommute utility directly to a license server (nessecary if the server is on a different sub-

net than the client machine) click the Single Server button and enter that server's name or IP address.

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.

Note:

l Licenses for each program must be commuted independently

l

Do not check the Check out authorization for remote machine box.

A commuted license is retained by the client machine, and is unavailable on the license server until it is checked

back in, or until it expires. If a commuted license is not checked in by its expiration date then that license dis-

appears from the client machine and reappears on the license server.

Enter a number of days which the commuted license will be valid for. Then click the Check Out button. A red

check mark will appear next to the Feature, indicated that a license has been checked out. You can then close the

WCommute utility.

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. Do this before leaving the office to confirm that

the license has been correctly commuted.

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. 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, and installing the authorization code on the remote machine.

Note:

50 RISA Licensing

License Commuting


55/85

License Commuting

l Remotely commuted l icenses cannot be Checked-In!! They will remain commuted until t heir e xpiration

date.

Prerequisites

l The license server must have at least one available license for the product which is to be commuted.

l The appropriate RISA product (i.e. RISA-3D) must be installed on the remote client machine. This must be

a Network Client Install.

l There must be a local client machine (connected to t he license server) with any current Network Client

Install of a RISA product installed.

Retrieving the Locking Code (Remote Client Machine)

The commuted license will be locked to a specific remote client machine. In order to do this the license server

needs a locking code for that client machine.

On the remore client machine, run the following utility:

C:\RISA\Sentinel RMS\Commute\WRCommute.exe


Click on the Get Locking Code tab, and click the button. Save the Locking Code File to a temporary location

Then send the Locking Code File to a user who has a local client machine (connected to the license server).

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. This step can be done from any local client machine which has

access to the license server.

On the local client machine, run the following utility:





56/85


ton.

l To point the WCommute utility directly to a license server (nessecary if the server is on a different sub-

net than the client machine) click the Single Server button and enter that server's name or IP address.

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.

Note:

52 RISA Licensing

License Commuting


57/85

License Commuting

l Licenses for each program must be commuted independently

l You must check the Check out authorization for remote machine box.

Enter a number of days which the commuted license will be valid for. Then click the Check Out button. The fol-

lowing dialog box will be launched:

Click on the Get locking code string for remote machine from file button, then click the button. Browse to the

Locking Code File which was generated by the remote client machine and click Open. Then click the OK button.

The following dialog box will appear:

Click the button. Save the Authorization Code File to a temporary location. Click OK , then exit the WCom-

mute utility.

Send the Authorization Code File to the remote user.

Installing the Authorization Code (Remote Client Machine)

The Authorization Code must be installed on the remote client machine to activate the commuted license.

On the remore client machine, run the following utility:

C:\RISA\Sentinel RMS\Commute\WRCommute.exe

Click on the Install Remote Authorization tab which is shown below:



58/85

Click on the Get remote authoirzation code(s) from file button, then click the button. Browse to the Authro-ization Code File which was generated by the local client machine and click Open. Then click the Install button.

The following dialog box will appear:

Close the WRCommute utility. 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.

Returning Commuted Licenses

Licenses which were commuted using the Remote Commuting procedure may not be returned. They will remain

commuted until they expire, 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).

Procedure

On the client machine, run the following ut ility:



54 RISA Licensing

License Commuting


59/85

License Commuting


ton.

l To point t he WCommute utility directly to the license server which the license was commuted from (nesse

cary 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.

The license server which the license was commuted from should now appear, 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. The red check mark will disappear,

indicating that the license is no longer commuted. Close the WCommute utility.



60/85

Initializing the Program for Commuted Licenses

In order for Commuted Licenses (or emergency license files for stand-alone programs) to work a special ini-

tialization routine must be run. This routine is run as part of both the Client network installation and the stand-

alone installation routines. Therefore, this initialization should always occur automatically. However, if the ini-

tialization is not run properly then the 'time-tampering' check will prevent the commuted licenses from checking

out properly. If this occurs, the initialization routine may need to be run again before the commuted license can

be successfully run.

To run this utility do the following:

1. Login to the end-user computer with full administrative permissions.

2. Locate the initialization utility. This should be located in the C:\RISA\Utilit ies sub-directory. It will be

given a program and version specific name similar to the following:o init3D10.exe (for RISA-3D version 10)o initRF40.exe (for RISAFoot version 4.0)

3. Run the initialization routine. If a User Account Control messag e as ks if you want to al low the this pro-

gram (from an unknown publisher) to be allowed to make changes to your computer, be sure to select

yes. The initialization routine will not complete successfully unless it has been run with administrative

permissions.

Cleansing a Commuted License

There are a number of issues that can cause a commuted license to not function properly. In the past, 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. With the update to

Sentinel RMS 8.5.1, this should no longer occur. However, in the event that a commuted license cannot be

returned to the license server, there is a way to "cleanse" the commuted license information off of the server.

This is not a simple or straight forward process, so you will need to contact RISA technical support in order to

complete. The basic process involves the following:

1. Contacting RISA Technical support ([email protected]). They will g ive instructions on obtaining a lock-

ing code for the client or server computer upon which the commuted license has been stuck.

2. Technical support will then use this locking information to e-mail a "cleansing" file to be run on that com-

puter. Usually this will be called something like cleanse_server.dat or cleanse_client.dat

3. In the Utilities sub folder (on the client or the server) there will be a utility called lsclean.exe. This utility

will need to be run from a DOS prompt referencing the cleansing file obtained in item #2. An example of

this command line would be the following:

lsclean cleanse_server.dat

56 RISA Licensing

License Commuting


61/85

Sentinel USB Key

Sentinel USB Key

RISA uses a Sentinel USB Key for licensing. This key may be plugged into any USB port on the machine. When

functioning properly the key will light up green when plugged into a running machine.

The design of Sentinel's keys has changed over the years. Older Sentinel USB Keys are purple, and typically do

not have an adhesive label attached. Newer ones are black and typically have an adhesive label designating

their Key ID. See the image below:

Key Driver

A Sentinel driver is necessary for the machine to read the USB key. This driver must be installed prior to plug-

ging in the key. The latest Sentinel System Driver (also called the Sentinel Protection Installer) can be

obtained from the RISA Technologies website, and is always included in both the Server and Standalone installs

(this install is ran from the SetupSPI.exe located in the RISA\Sentinel Protection Installer folder).

To confirm that your machine is running the latest driver open the Device Manager, which is accessible through

the Windows Control Panel. 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


http://www.risatech.com/http://www.risatech.com/http://www.risatech.com/


62/85

Double-click on the SafeNet USB SuperPro/UltraPro device to view its properties. 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. This

will sometimes cause problems in reading the key when a new version of the key driver is installed. In this

instance it may be required to run the SSD Cleanup utility to fix this problem. This file is called SSDCleanup.exe.

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 t ypical way t o fix key driver issues is as follows:

1. Uninstall the key driver from the machine.

2. Run the SSD Cleanup utility (SSDCleanup.exe or SSDCleanupx64.exe).

3. Re-install t he key driver by running the SetupSPI.exe from the C:\RISA\Sentinel System Driver folder

58 RISA Licensing

Sentinel USB Key


63/85

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

Key Manager.exe) is found in the RISA directory in the RISA\RISA Key Manager\ folder.

This program works for both standalone and network (server) keys and is used mainly for these purposes:

l Upgrading a standalone key for a new version

l Upgrading a network key for a new program

There are also many other uses for this program that most users will never run into. Those include:

l Copying the locking data from a computer

l Converting a key from standalone to network and vice versa

l Removing a feature from the key and sending RISA a removal confirmation code

We will go t hrough each of t hese processes, but let's first talk about what to do if the Key Manager doesn't read

your key.

Note:

l The Feat ures button is only applicable t o tnxTower.

RISA Key Manager Shows up Blank

If this happens the RISA Key Manager will look like this:



64/85

If you are opening the RISA Key Manager just to view the Locking Data then this is how it should look. If you are

using the key, however, this is a problem.

Typical reasons why the RISA Key Manager would show up blank:

l The key is not plugged into the computer. If this is the case, plug in the key and press the Refresh button.

A view of the key is shown in the Sentinel Key topic.

l The key driver is not installe d or is not working properly. To install or modify your install of the driver

see the Key Driver section of the Sentinel Key topic.

l The USB port is not able to re ad the key. 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. Sometimes some of the weaker USB ports (on a monitor for example)

may not have enough power to run a key.

Uses For the RISA Key Manager

Here are the two primary uses for this program.

Upgrading a Standalone Key for a New Version

For each major version of the program the key must be upgraded to the newer version. This can be done by click-

ing the radio button of the program you are updating, pressing the Upgrade button and inputting the RUS pass-

word. 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, then press Upgrade and the key will then be upgraded.

After this process you should then see the updated version next to that program and your key is then upgraded.

Note:

60 RISA Licensing

RISA Key Manager


65/85

RISA Key Manager

l Minor r eleases do not require an update to the key. For example, an update of RISA-3D from 10.0.0 to

10.0.1 will not require an update to the key.

l If you upgrade the key and you get a message stating Unable to update Sentinel key. The currently author-

ized program version exceeds the upgrade version, this means that the key is already up to date for the ver-

sion of the RUS password you entered.

Upgrading a Network Key for a New Program

A network key only has to be authorized for a program once. After the key is authorized, then upgrades do NOT

require the key to be updated. If you own a network version of RISA-3D and then purchase a network version of

RISAFloor, then you WILL need to update your key for RISAFloor. This is done by clicking the radio button of the

program you are updating, pressing the Upgrade button and inputting the RUS password. 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, then press Upgrade and the key will then be upgraded.

Note:

l If you upgrade the key and you get a message stating Unable to update Sentinel key. The currently author-

ized program version exceeds the upgrade version, t his means t hat the key is already been authorized for

that program.

Miscellaneous Uses

Here are some other uses that are much less common.

Copying the Locking Data from a Computer

The locking data is basically a code that is specific to your computer. If you ever need this locking data (we at

RISA may ask for it in rare instances), then you can press the "Copy Locking Data" button and it will paste this

information to your clipboard. You can then open up an e-mail and paste (CTRL-V) the locking data into an e-mail

Note:

l There is a New Style Codes checkbox. Whether you check this checkbox when copying locking data

depends on what vetsions of RISA programs you are working with. If you are using RISAFloor 6.0, RISA-3D

10, RISAFoundation 4.0, RISAConnection 2.0 and RISAFoot 4.0, then you will want to check the box. If you

are using older versions, or any other programs you will want to uncheck the box.

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

word to convert your key. To do this follow the Upgrade procedure above, except make sure to check the

"Change Key Type..." checkbox.

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. This can be done by:



66/85

l Clicking the radio button of the program you wish to install and press the Remove button.

l Enter the RUS Uninstall Password that has been e-mailed to you from RISA and press the Uninstall but-

ton.l You be asked if you wish to continue. Press t he Yes button.

l It will then tell you that the program has been uninstalle d.

l A final scre en will come up with a Product Return Code that MUST be sent to RISA to confirm that the

program has been uninstalled.

62 RISA Licensing

RISA Key Manager


67/85

Demonstration Mode

Demonstration Mode

RISA Products all come equipped with a Demonstration Mode which can be accessed when a license cannot be

retrieved. The Demonstration Mode has certain limitations, and is intended to function both as a reader of exist-

ing files and as showcase of product features for those users who do not own the product.

Launching in Demo ModeWhen a license cannot be found the option is presented to launch in Demonstration Mode. Once the program has

been launched in Demonstration Mode it cannot re-enter the regular Non-Demo Mode during the same session.

Example

If RISA-3D Standalone is launched without the Sentinel USB Key attached the user is given an option to launch in

Demo Mode. When in Demo Mode in RISA-3D no model with more than 40 Joints can be saved. If the user creates

a model with 50 Joints they cannot save it, even if the Sentinel USB Key is plugged in after the fact. That is

because the program cannot switch from Demo Mode back to Non-Demo Mode. The user will have to close the

model without saving, then launch the program with the key plugged in to enter Non-Demo Mode. The 50 Joint

model will be lost, and cannot be recovered.



68/85

Appendix A - Licensing Error Messages

Errors related to licensing are displayed in RISA dialog boxes. Each error has a code displayed in the header of

the dialog box, within brackets. 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.

What follows is a list of error messages, including steps that can be taken to resolve them.

Error [1]

Cause

There is an inherent problem with RISA's customized Sentinel RMS service.

Solution

Contact RISA Support

Error [2]

This error is effectively the same as Error 1

64 RISA Licensing


mailto:[email protected]:[email protected]


69/85


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, however that server cannot be found.

Solution

Confirm that there is a server with that name or IP address present on the network, and that there is no firewall

preventing the client machine from communicating with that server. If no such server exists then edit the

LS Query List registry entry or the LSFORCEHOST environment variable to specify a new license server, 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, however no licensing service (Sentinel RMS) was

found running on the license server.



70/85

Solution

Check the list of Services on the license server and confirm that Sentinel RMS is present and Started. If it is not

then load the sentinel service. Otherwise it is a firewall issue.

UDP port 5093 is blocked at the license server, the client machine, a router, or anywhere on the network. 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. Windows Firewall is commonly overlooked by IT administrators, but it is a common cul-prit.

Error [6]

Cause

The Sentinel RMS service on the license server is e ither unable to read the Sentinel Key, 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, open the RISA Key Manager and confirm that the key is being correctly read. If not then

resolve that issue. If the key is being correctly read then an out dated license file is currently loaded. Contact

RISA Support for a new license file and load that new license file.

Error [11]

This e rror is effectively the same as Error 1

Error [12]


66 RISA Licensing




71/85


Error [14]

Cause

Communication between the client machine and license server is present, but is too slow to establish a usable

connection.

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. If they are connected over a WAN or a VPN then try to increase

the speed of the connection.

Error [15]

Cause

Some licenses on the license server have been reserved by various clients on the network. The client machine ispart of a group of clients which has exhausted its supply of licenses.

Solution

Move the client machine in question to a group which has available licenses, or increase the number of licenses

reserved for the group to which the client machine is currently assigned.

Return some licenses to the license server by closing the application on other client machines within the same

group, or r eturning commuted licenses. Contact RISA Sales to purchase additional licenses.




72/85

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.

Solution

Confirm that the client machine is on the same subnet as 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.

Error [18]

Cause

The client machine was able to contact the Sentinel RMS service at the license server, however the service had

no license loaded for the particular program/version of RISA software which the client machine is attempting to

launch.

68 RISA Licensing



73/85


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. Contact RISA Support for a new license file and load that new license file.

Error [25]

Cause

The license server is running the wrong version of Sentinel RMS, possibly one that is not customized by RISA.

Solution

See the License Server Updater topic for information on migrating to the newest RISA-customized sentinel ser-

vice.

Error [37]

Cause

RISA has issued a trial license file with an expiration date, and that date has passed. The license file is no longer

valid as a result.




74/85

Solution

Contact RISA Support for a new license file.

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. The process where this may happen:

a. WRCommute.exe is run on the remote client computer and the code is saved to a file or the string is

copied.

b. WCommute.exe is run on the local client computer.

c. The program for the license that is to be checked out is selected, the "Check out authorizations for remote

machine" checkbox is checked, and the number of days is selected.

d. The string or file to copy string from is entered, and OK is pressed. This is when this error is t hrown.

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. You may wish to right-click and "Run as Administrator" on the com-

muting executables. Also, make sure that you have a license available for commuting.

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

Cause

This message can be caused by loading a bad license file on the license server.

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.

Err or [150]

This error is effectively the same as Error 6.

Error [0xC8001002]


70 RISA Licensing


mailto:[email protected]:[email protected]:[email protected]:[email protected]


75/85


Error [0xC8001006]

Cause

All of the available licenses on the license server have been checked out. No additional licenses may be checked

out.

Solution

Return some licenses to the license server by closing the application on other client machines, or returning com-

muted licenses. Contact RISA Sales to purchase additional licenses.

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).




76/85

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, and that it is connected (either

through a cable or wireless connection) to a network.

Error [0xC800100D]

Cause

RISA has issued a license file with an expiration date, and that date has passed. The license file is no longer valid

as a result.

Solution

Contact RISA Support for a new license file.

72 RISA Licensing


mailto:[email protected]


77/85

Appendix B - 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. These can be grouped into the following main categories:

Firewall Issues or Error Code 3:

Failed to resolve the server host. This means that the WLMAdmin utility was not able to communicate with the

server listed in the list of Defined Servers. This can occur for a couple of reasons:

l The name or IP address of the server was not entered properly.

l There is a network issue which is preventing communication with this computer.

l The service has not been loaded or is not running. See the Sentinel Services topic for more information.

Solution:

Frequently, the cause of this error is a firewall on the client, server, or network. The solution to this problem is

to set up a port exception in the firewall. How to accomplish this is dependent on the type of firewall. Below is

the Windows XP dialog for setting the port exception (Control Panel - Network and Internet Connections - Win-

dows Firewall).

Note:

l The port that needs to be open is 5093 and the communication protocol is UDP.

Alternate Solution:

The Sentinel RMS service on the license management computer has been stopped: To re-start the service, go to

the list of servcies (Control Panel – Administrative Tools – Services) on the license mangement server, right

click the Sentinel RMS License Manager.

Note:

l If the license management service shuts down almost immediatel y after start-up, this may be caused by a

network installations instructions

Documents