Monthly Archives: November 2012

Trouble Shoot Form: Database Item 001 (Connection to SQL Server Database failed)

Posted on by

Trouble Shoot Form: Item 02.001

Title Connection to SQL Server DB failed.
Category Data Base
Date Sep 26, 2011
Handled by Rachel.
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet Publisher, IBM LUM, HASP, RLM, Sentinel RMS, DSLS, LM-X
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer reported failure to connect to a new SQL Server through EasyAdmin. Succeeded in connecting it via the Configuration form “Check” button. Customer succeeded in connecting to old FB Server through EasyAdmin.
Observed during investigation Log contained fatal error:
Login failed for user ‘DPI\ORANTESTSPATIAL$’
Trouble shoot process Credentials issue
Solution Found (Options: Found/Pending/Known Issue)

Symptoms

Customer reported a failure in connecting to an SQL Server.
The “Check” button worked OK in the “OpenLM Database Configuration” dialog box, but EasyAdmin couldn’t connect to the SQL Server. See customer’s image below.

Observed during investigation

1. The customer defined the OpenLM Server (in the “OpenLM Database Configuration” dialog box) to work with SQL server using “Windows Authentication”. This means that logging to the SQLServer was done using windows credentials.

2. The customer clicked “Check” on the “OpenLM Database Configuration” dialog box, and it worked OK because the process worked fine with these windows credentials.

3. Then he started the “OpenLM Server”. It didn’t work because it had other credentials.
The customer sent a log containing these lines:

FATAL 2011-09-26 12:11:14,276 [thread 11]  SessionProducer CreateFactory – Can’t map nhibernate domains
System.Data.SqlClient.SqlException (0×80131904): Login failed for user ‘DPI\ORANTESTSPATIAL$’.

This means that a user named DPI (on server ORANTESTSPATIAL) could not login to the SQL Server, hence the system halts (FATAL error means that the application could not recover).

Trouble shoot process

  1. The “Database credentials” dialog box may be configured wrong, e.g.: check the “Embedded” check box in the window for Databases that are located on local drives.
  1. OpenLM Service credentials: In the “Windows Services” window, Select the “OpenLM Server” item. The “OpenLM Server Properties” dialog window opens. Select the “Log On” tab.

Here you can see under what credentials the service runs. By default we install it with “Local System Account” but some users change it.

We suggest acting according to one of these options:

1. Change the OpenLM Service credentials to that of a user who has both administrative permissions and a permission to login to the SQL server.

2. Another option is not to use the “Windows Authentication” (but “SQL Server Authentication”).

Trouble Shoot Form: Agent Item 002 (All license usage information on the Agent is blocked)

Posted on by

 

Title License usage reporting information on the Agent is blocked
Category Permissions and Roles.
Date Jul 6, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Following the creation of an admin account in the OpenLM Server Configuration, all license usage information on the Agent is blocked
Observed during investigation
Trouble shoot process 1. Create a role.
2. Assign all the necessary resources, that will allow viewing details, to the new role.
3. Add users as members of this role.
Solution Found (Found/Pending/Known Issue)

Symptoms

The customer complained: “Every time I go to add an admin account in the OpenLM Server Configuration it blocks all license usage information on the Agent?  I’d like to password protect the EasyAdmin web application but still allow users to see the license usage through the agent. Is there a way to do this?”

Observed during investigation

An admin account on the OpenLM Server Configuration window was created. This can be done by unchecking, and then rechecking the “Enable permissions” highlighted checkbox. A small dialog box subsequently appears, requiring a name & password for the new user (e.g.: User name: admin, Password: admin).

Troubleshooting

When you enable permissions, users need to be assigned with a set of permissions that will allow them to view license servers’ details

1. Create a role: Login to EasyAdmin with the “admin” account. follow the steps described in the “Creating a new role” section of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

2. Assign resources to the new role: After you save the new role, the “Resources” tab will become enabled. Navigate to that tab. Note that it is assigned with one default resource. Now you need to add all resources that have this name pattern “server_servername” e.g. server_srv1 (where srv1 is the name of the server that you will grant access to). In order to do so, Follow the description in section “Adding resources to a role” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

3. Assign the new role to the “admin” user: In order to do so, Follow the description in section “Assigning roles to a user or group of users” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

 

Trouble Shoot Form: Database Item 003 (Following data migration from SQL to FB, EasyAdmin doesn’t show any logging)

Posted on by

 

Title Following data migration from SQL to FB, EasyAdmin doesn’t show any logging
Category Database
Date Sep 25, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer complained that EasyAdmin does not show any stats.
Observed during investigation
Trouble shoot process
Solution Found (Found/Pending/Known Issue)

Symptoms

A customer complains that: “I have successfully connected the new database, BUT nothings seems to be logging. I have no stats showing on the EasyAdmin screen.”

Trouble shoot process

1. Make sure the license servers list is defined at the “OpenLM Server Configuration Form”
2. All settings of OpenLM are saved in the database. When you migrate to a different database (e.g.: from SQL to FB), you need to re-enter the license servers list.

  1. Switch to Firebird.
  2. Open “OpenLM Configuration Form”, navigate to “Advanced” panel, click “Export…” button and save the settings to a file.
  3. Close “OpenLM Configuration Form”.
  4. Switch to SQLServer.
  5. Open “OpenLM Configuration Form” again and you will see that servers list is empty.
  6. Navigate to “Advanced” panel, click “Import…” and import the file you saved earlier.
  7. Click “Apply” and restart OpenLM server.
  8. Check EasyAdmin.

Trouble Shoot Form: Database Item 002 (Data migration from SQL to FB)

Posted on by

Trouble Shoot Form: Item 02.002

Title Data migration troubles, from SQL to FB.
Category Database
Date Sep 25, 2011
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Symptoms Customer reported failure to import the SQL database to FB At first.
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process
Solution Found (Found/Pending/Known Issue)

Symptoms

Customer reported failure to import the SQL database to FB.

Trouble shoot process

 

  1. Make sure the “Data Migration” tool version is compliant to the OpenLM version.
  2. A special version of the data migration tool is required for 64 bit computers.
  3. Migration of a database over to a new database that is not empty may result in failure to migrate certain tables. This is indicated by the following message: 

If this is the case, create a clean database again, and run the OpenLM_SQLServer.SQL” script to build the tables and try to migrate again.

Trouble Shoot Form: Broker Item 005 (can not open the broker configuration tool)

Posted on by
Title Can not open the Broker configuration tool.
Category Broker
Date Oct15, 2012
Handled by -
Relevant Links -
Symptoms
Applies to license managers FLEXlm, FLEXnet publisher, IBM LUM, LM-X
Applies to license mode Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process See below
Solution

 

Description

The Broker configuration tool will not open.

Troubleshoot

1. Make sure  Java 1.6 or higher is installed on the computer.
2. Make sure a 32bit/64bit compatible Java version is installed.
3. Try running the configuration tool from a command line:

  • Open a command prompt as an administrator
  • Navigate to the Broker directory: C:\Program Files\OpenLM\OpenLM Broker
  • Run the Broker configuration tool from a command line: Java -jar BrokerConfigurator.jar broker.xml

If this solution (#3) worked, permissions’ issue needs to be addressed. Please address your system administrator.

Trouble Shoot Form: Broker Item 004 (Broker installation stuck after installing JRE1.6.)

Posted on by

Trouble Shoot form: Item 01.004

Title Broker installation stuck after installing JRE1.6.
Category Broker
Date Apr17, 2012
Handled by -
Relevant Links -
Symptoms
Applies to license managers FLEXlm, FLEXera FLEXnet publisher , IBM LUM, LM-X
Applies to license mode Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process Erase directory in “InstallJammer Registry”
Solution

Description

According to a client: “I’m trying to install the OpenLM Broker.  When I first tried to install it, I didn’t have Java v1.6 installed, so the installation failed.  I then went and downloaded and installed JRE 1.6.  Now, when I go to install Open LM Broker, I get this error message.”

Troubleshoot

1. One option is:

Navigate to “C:\Program Files\InstallJammer Registry” or
“C:\Program Files (x86)\InstallJammer Registry” and erase a directory that looks like
37BAF401-7176-4BCD-A5BB-70F5F9990F94

2. Another option for solving this, is by Installing the broker in command line, e.g.:
openlmbroker-windows-setup_1718.exe \notcheckprevver


Trouble Shoot Form: Broker Item 002 (Broker commands not showing)

Posted on by

Trouble Shoot form: Item 01.002

Title Broker commands not showing.
Category Broker
Date Oct 11, 2011
Handled by -
Relevant Links -
Symptoms
Applies to license managers FLEXlm, FLEXera FLEXnet publisher, IBM LUM, LM-X
Applies to license mode Floating licenses, Network licenses, Concurrent licenses
Observed during investigation
Trouble shoot process Troubleshooting
Solution

General

Upon start-up, the OpenLM Broker compiles lmutil commands that are installation specific. These commands would later be used for interfacing the license server, and sending information over to the OpenLM server. These commands are ‘Status’, ‘Data inquiry’, ‘Start’, ‘Stop’ and ‘Reread’. In the image below, The command set of two license servers are highlighted, and the ‘Status’ command respective to the ArcGIS License manager is shown.

The Broker has the capability of self extracting information regarding the License Server’s port, and the location of the License file and lmutil executables in order to compile the commands. At the time of writing this document, This capability is only available for Windows’ license servers (OpenLM Broker version 1.7xx).

Symptom

The Command lines are blank

Troubleshooting

 

  1. Unix servers: As mentioned above, auto compiling of lmutil commands is only available on Windows servers. Solution:
    1. Add a Windows License server and get the commands there.
    2. Modify the commands so that they comply with the Unix format.
    3. Following are the commands as they appear on my Windows Broker (as an example), followed by the respective Unix command templates:

 

Status:

Windows: “C:\PROGRA~2\ESRI\License\arcgis9x\lmutil” lmstat -c 27004@olm2008

Unix: <installationFolder>/lmutil lmstat -c <port>@licenseServerName

 

Data inquiry:

Windows: “C:\PROGRA~2\ESRI\License\arcgis9x\lmutil” lmstat -a -c 7004@olm2008 -i

Unix: <installationFolder>/lmutil lmstat -a -c <port>@licenseServerName -i

 

Start:

Windows: “C:\PROGRA~2\ESRI\License\arcgis9x\lmgrd” -z -c “C:\Program Files (x86)\ESRI\License\arcgis9x\Viewer9.lic”

Unix: <installationFolder>/lmgrd -z -c <license file>

 

Stop:

Windows: “C:\PROGRA~2\ESRI\License\arcgis9x\lmutil” lmdown -q -c  ”C:\Program Files (x86)\ESRI\License\arcgis9x\Viewer9.lic”

Unix: <installationFolder>/lmdown -q -c <license file>

 

Reread:

Windows: “C:\PROGRA~2\ESRI\License\arcgis9x\lmutil” lmreread -c  ”C:\Program Files (x86)\ESRI\License\arcgis9x\Viewer9.lic” -all

Unix: <installationFolder>/lmreread -c <license file> -all

 

  1. The automatic detection capability is only applied when a license manager is installed on the same machine as the OpenLM Broker. If no such installation is noted in the registry, no Broker commands would be automatically compiled.

 

  1. In the OpenLM Broker’s installation folder, under the ‘tools’ directory (i.e.: C:\Program Files\OpenLM\OpenLM Broker\tools) there is a default lmutil executable file. This file is referred to when no other lmutil executable file is set. Note its existence in order to avoid problems arising from multiple code reference.
  1. View the Broker.xml file under the Broker’s installation folder ( i.e.: C:\Program Files\OpenLM\OpenLM Broker) in order to extract information regarding the Broker’s whereabouts. See the following code cut-out as a reference to the required Broker’s behavior

ESRI ArcGIS 10.1 SP1 version published

Posted on by

General

ESRI has recently published the ArcGIS 10.1 SP 1 patch version.
This release contains a list of bug fixes and enhanced performance.

Relevant to OpenLM users:

One fix is related to the desktop’s license borrowing capability:
NIM060359: High Latency/Low Bandwidth connections including VPNs may prevent license borrowing.

OpenLM compatibility

OpenLM has already installed and tested the patch with OpenLM Server and Agent version 1.7. No compatibility issues were found.

Further information

If you have any questions regarding the upgrade of ESRI ArcGIS to the 10. SP1 version, please contact OpenLM: support@openlm.com

Application Note 1003_a: OpenLM Groups License Activity Report tool

Posted on by

General:

The OpenLM Groups License Activity Report tool provides this ability to present an historical account of groups’ license usage sessions.

More details:

OpenLM provides an easy interface for monitoring software license usage. It does so for a constantly expanding variety of concurrent license manager types, e.g. FlexLM / Flexnet, Sentinel RMS Reprise RLM, MathLM, DSLS, Sentinel HASP, LM-X, IBM-LUM etc.

OpenLM is capable of reporting usage according to Users, User groups, Hosts, Host groups, Organizational Units and Projects. OpenLM’s web application – EasyAdmin – presents users’ accumulated data in a variety of real-time windows (e.g. “Active Products” and “Feature Usage Status” windows), and historical usage tables (e.g. “License usage” and “License activity” windows). See the OpenLM screenshots document for more information.

At the time of writing this revision (0.1), the current OpenLM version (1.7.3.4) is not yet capable of presenting an historical account of groups’ license usage sessions (i.e. the groups’ equivalent of single users’ “License activity” window).

The OpenLM Groups License Activity Report tool provides this ability.

OpenLM License Activity

The EasyAdmin “License activity” window provides an account for all ended sessions on license managers that are monitored by OpenLM. This window contains columns for the user name, Feature name and Session start & end times. (Some items on the image below have been deleted for privacy considerations)
The users who populate this list are members of groups in the OpenLM database. These groups may be introduced either manually, or by means of LDAP (Active Directory) synchronization.
Please refer to this Application note
Application Note 1029: LDAP (Active Directory) Synchronization
And this video
Synchronize Active Directory, and add users manually
for more information on OpenLM Groups.

In the image above, the ‘Engineering’ group has been selected for the time period from 22/10/2012 until now. In order to provide information for the Groups reporting tool, the information needs to be exported to a CSV file, using the green arrow icon (marked by a red rectangle).

OpenLM Groups reporting tool

Once the License Activity information was exported to CSV, the OpenLM Groups reporting tool may be employed:

  • Open the OpenLM Groups reporting tool.
  • Type in the exported file path.
  • Select the Date time format (in the example above it is dd/MM/yyyy)
  • Click the Start button.

After the tool is run, a CSV format file should be created and its directory presented on the desktop. This file’s default name is OpenLMGroups.csv, and it contains an historical account of OpenLM groups’ license usage

The default location for the output CSV, as well as for Log files is

For post Vista Windows’ version:
C:\Users\<username>\AppData\Roaming\OpenLM\OpenLMGroupsReport_Log.txt
C:\Users\<username>\AppData\Roaming\OpenLM\OpenLMGroups.csv

For pre Vista Windows’ version: this would be at:
C:\Documents and Settings\<username>\Application Data\OpenLM

Revision 0.1, Nov18 2012.