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

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.

Please follow and like us:

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

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


Please follow and like us:

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

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
Please follow and like us:

Application Note 1003_a: OpenLM Groups License Activity Report tool

The OpenLM Groups License Activity Report tool provides the 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, the current OpenLM version (1.8.1.17) 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 these Application notes:

Application Note 2029_a: LDAP (Active Directory) Synchronization. Basic guide v1.8

Application Note 2029_b: LDAP (Active Directory) Synchronization. Comprehensive guide v1.8

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

Please follow and like us:

Application Note 1032: Monitoring FlexLM license denials

General:

OpenLM monitors and optimizes the usage of various license managers (e.g.: FlexLM / Flexnet publisher, Sentinel RMS Reprise RLM, MathLM, DSLS, Sentinel HASP, LM-X, IBM-LUM etc).

As part of FlexLM license monitoring, OpenLM also produces license denial reports, i.e.: an account of instances where the vendor daemon has declined an application’s license request. License denial is a key parameter in license maintenance and in the planning of additional license procurement.

The Denials report window

License denial information is clearly presented in the OpenLM EasyAdmin web interface, in the Reports → Denials window. It includes the details of the denial event (Denied user, Denied workstation, Time, License Server, Denied Feature, and vendor) as well as the cause for denial (e.g.: limit of available licenses reached or User on Option file exclude list)

Set up OpenLM to monitor license denials

In order to produce denial reports for monitored licenses, please:
1. Set up the OpenLM Server to monitor the License server. In this case, the host is vmw_win2008_64, its type is FlexLM, the Server port is 27000, and the time zone is Central:

2. Install the OpenLM Broker on the License server machine:
Application Note 1004: OpenLM Broker quick start guide
Make sure that the License server name is exactly (case sensitive) the same as configured in the OpenLM server configuration tool (e.g.: vmw_win2008_64). The OpenLM server in this example resides in 102.101.100.135. The Broker communication port is (by default) 7016.

3. Set the OpenLM Broker to read the Denials’ information from the Monitored application’s debug log file: Type in the filename and click the ‘Enabled’ check box in the image below. Click ‘Apply’ and “Restart Broker” to finalize the configuration.

4. Make sure the Broker indication in the EasyAdmin “License Servers” window turns green. Note the green rectangle adjacent Server name vmw_win2008_64 in the image below. If it isn’t so – wait a while and refresh the “License servers” window. If it is still red – recheck your configuration, and check for alerts in the Easy Admin → Start → Management → Alerts window.

License number surpassed: Case study

In case the number of licenses has been surpassed – the vendor daemon would deny the license request, and a license denial notification will be produced. In the case of AutoCad: this is Network license error -96.

The debug log file shows this too as a string
Licensed number of users already reached. (-4,342)
Note the last denial report at 4:12:22 (Central time US):

It would also be apparent on the EasyAdmin Denial reports window at 11:12:22, according to the difference in time zones between the location of the OpenLM Server (Europe) and the AutoCad License server (Central time, US).

This same information can be presented as a column or pie chart, according to Users, Servers, Vendors, Features or time of occurrence.

Troubleshoot: Denials do not appear in the Flexnet debug log

Denial reports may not appear in the FlexLM debug log if the application’s option file contains a NOLOG line, with a DENIED flag. If this is the case, edit the option file to exclude this flag, and restart the license server. See this document for more information.

Document Revision Table

Version Author Date Changes
0.1 – Preliminary Orik Oct 25, 2012 Preliminary
1.0 Orik Dec 17, 2012 Added troubleshoot

 

Please follow and like us:

Troubleshoot Form: OpenLM Server Item 003 (Unable to connect to FLEXlm license server error: -96,7:11004 “Comm. error”)

Title Unable to connect to FLEXlm license server
Category OpenLM Configuration Form
Date Oct 24, 2012
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXera FLEXnet,
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms No activity reported on EasyAdmin for a specific FlexLM license server
Observed during investigation Clicking the “Check” button for one of the FlexLM license servers on the OpenLM Configuration Form resulted in an error
Trouble shoot process Check License server connectivity configuration.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the FLEXlm license server”. Attempting to connect to the license server resulted in the following message box appearing on his screen:

lmgrd is not running: License server machine is down or not responding. (-96,7:11004 “Comm. error”)

Troubleshoot process

1. Make sure the license manager machine is up and that you could check out licenses from it.

2. Make sure that the hostname , Port number, License Manager type and timezone are configured correctly in the OpenLM server configuration tool. Also, please review this Troubleshoot guide.

3. Check the connectivity between the OpenLM server machine and the license server (using ping or telnet).

4.  Make sure that any security components (Firewall) are not blocking communication on both ends. The OpenLM server uses ports 7012, 7014, 7016, 7017 and 7019. The OpenLM server’s communication with the License server relies on port 7014.

Make sure that the port is open:

 

  • Try disabling the firewall temporarily.
  • Enter “Control Panel”→“System and Security”→“Windows Firewall”→ Advanced settings”.
  • If the port isn’t defined under the “‘Inbound Rules” open the port by adding a New Rule using the “New Rule” button located on the lower right side of the screen as depicted below:

5. The OpenLM Broker may bypass such communication issues. Install the OpenLM Broker on the license server machine. See this application note for more information: Application Note 1004: OpenLM Broker quick start guide

Please follow and like us:

Application Note 1033: Retrieving license usage information with the OpenLM logs uploader

General

OpenLM people have been addressed many times by customers who were asking for a way to produce license usage reports retroactively, i.e.: for the time period before the OpenLM software was installed on their system. This was usually side-dished with a considerable portion of panic, having to produce reports for a software auditing session, or before the year’s end.

OpenLM has come up with the Logs Uploader module for this purpose. This module guarantees that customers would be able to produce decent usage reports, given that the FlexLM debug log files have been kept throughout the time – period of interest.

How is it done?

The OpenLM logs uploader takes its information from the FlexLM license manager debug log file, and produces historical data in the OpenLM database. This information can later be displayed over EasyAdmin reporting windows, or extracted to CSV files to produce usage reports and statistics.

Where can I get it from ?

In order to get the OpenLM Logs Uploader tool, please contact support@openlm.com

Configuration

First – the OpenLM Server needs to be installed, and configured to monitor the FlexLM license manager of interest. For more information about that: please refer to this Application Note:
Application Note 1026: Basic OpenLM Server configuration for FlexLM

Note the FlexLM license manager which resides on the lm10 host, and port 27000.

Open the Logs uploader tool, and configure it as follows (see image below):

  • Type in the OpenLM server host name (e.g. localhost) and Server port (7014 by default)
  • Click the OK button. The rest of the configuration tool becomes active.
  • Select the target license server from the drop-down list. In this case that is 27000@lm10.
  • Keep the Timestamp value at its default 360 minutes value.
  • Select the debug log file to be imported, and click the Upload button.

The logs’ uploading process may take quite a long time, depending on the size of the debug log and the computer’s performance, so please be patient.

That’s it – this has imported the data from the debug log into the OpenLM database, and potentially saved some headache for a system administrator somewhere.

Version: 0.1 (Preliminary), October 17 2012.
Please follow and like us:

Get more out of your floating licenses

OpenLM is a complete floating license management solution designed to optimize the use of licensed software: more production for lower cost.
OpenLM is made to harvest idle licenses, and improve license utilization of any organization: big or small.

Who was the OpenLM Utilizer Designed For?

Unlike other license management systems that only offer administration and license monitoring statistics, the OpenLM Utilizer optimizes license usage in a unique manner that provides all personnel with useful license-related functions.

Organization managers:

  • Know what you have: Inventory.
  • Plan license maintenance and procurement of expensive licenses.
  • Charge projects or business units for software usage time.
  • Cut costs by dropping maintenance for licenses that are no longer in use.

Administrator view:

  • Real time license usage management
  • Alerts – Real time troubleshooting
  • Extract usage statistics information and patterns as reports or charts.
  • Roles and Permissions: Grant licenses according to specific Users’ permissions. Enforce concurrent License restriction.

End User View:

  • End users are not kept in the dark. They are informed about the status of denied licenses.
  • Receive a License availability notification when a license becomes vacant.
  • Who is using the license I need?
  • What is this person’s contact details?

Supported features

License managers:

  • OpenLM interfaces a wide variety of license managers, e.g.: FLEXlm / Flexnet, IBM LUM, Sentinel RMS, Sentinel HASP, RLM, DSLS and other leading license managers.
  • OpenLM supports Concurrent monitoring of multiple license servers on multiple time zones.
  • OpenLM supports management of Floating, Node-locked and Borrowed licenses.

Monitoring capabilities:

  • Easily review license inventory in real time.
  • Extract license activity reports, with configurable resolution.
  • Receive FLEXlm reports, statistics and charting (FLEXnet reports).
  • Receive Billing reports for any time period, per user or software (FLEXbill capabilities).

Infrastructure:

  • OpenLM may work over WAN and LAN networks.
  • OpenLM employs a web-based user interface that works with any supported browser.
  • A Mobile interface application enhances monitoring abilities for system administrators.
  • OpenLM may interface license managers that run on UNIX, Linux, or Windows’ Operating systems
  • OpenLM supports both external and embedded databases.

Proactive capabilities:

  • Release orphan licenses with a single mouse click.
  • Query users and licenses from any workstation.

Other features

  • A customizable alert system
  • An open, detailed API

OpenLM Architecture

OpenLM’s basic software package includes the core OpenLM Server module and its user interface; the OpenLM EasyAdmin module. In addition to these core components, the OpenLM Broker, OpenLM Alerts module and the OpenLM Utilizer Agent modules are also incorporated in the basic software package.

The OpenLM Server

is the core element of the OpenLM system. It integrates the functionality of all other peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. The OpenLM Server is implemented as a Windows service and could be installed on any network machine.

OpenLM EasyAdmin

An HTTP based application that can run on any machine in your network. EasyAdmin is the reporting and management interface of OpenLM. It facilitates extraction of lisence usage statistics, and usage repots, as well as the control and optimization of license usage.

OpenLM Agent

An optional component that can be installed on any machine on the network. The Agent enables end users to query license availability and find who is using the license they need at any point in time.

OpenLM Alerts

is a dedicated alerting service for the OpenLM system. This module alerts system administrators when predefined conditions are met.

OpenLM Broker

is an optional server component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server, and is required in order to provide advanced licensing information and sophisticated abilities.

OpenLM Screenshots

Watch the OpenLM EasyAdmin screenshots on the OpenLM site.

Want to evaluate the software ?

You can get the most updated version of OpenLM Utilizer from our OpenLM downloads area. After filling in your name and email – you’d be directed to the Downloads section. The Installation process is easy and straightforward, but if you still need any assistance – Please send an email to support@openlm.com, and we’ll be glad to help.

Please follow and like us:

Application Note 1030_a: OpenLM license usage monitoring according to projects – v1.7.

General

OpenLM is able to record information about the usage of various licenses and allocate them to different company projects. This ability facilitates license allocation according to organizational projects, and can also serve as a mean to effectively charge-back license usage expenses and manage project billing.

This ability complements OpenLM’s license monitoring capabilities; integrating license usage optimization with Active directory synchronization, Project assignment, and monitoring a variety of  license managers such as FlexLM (Flexnet), Sentinel HASP, Sentinel RMS, RLM, DSLS, IBM LUM and LM-X.

Scope

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. This Application Note describes the feature as implemented in the 1.7 version.

Project usage reporting

The Project usage reporting is available on the EasyAdmin web interface. Click OpenLM Start → Resports → Project usage in order to see the report. Set the filtering options on the left-hand side of the screen, and click the ‘Apply’ button in order to run the usage query.
It is also possible to view the report in a chart format, or extract the information to a CSV file (green arrow icon at the bottom) and manipulate it on a spreadsheet software.

However, before having any information to report – it is necessary to set up the projects. Please follow the section below in order to do so.

Projects Settings

The OpenLM Server configuration tool’s ‘Projects’ tab defines the policy of the Project usage monitoring capability. Please note that Projects’ information logging requires the installation of the OpenLM Agent (Either Active Agent or Utilizer Agent) on the end-users’ workstations.

Log Projects Information

Check the Log projects information checkbox to start recording license usage information according to projects’ allocation.

Minimal Usage Duration for Project

This setting defines the shortest duration for logging purposes. Shorter periods would be merged together to form significant usage periods. For example, if the minimal duration is set to 5 minutes, and a user has opened the application for only 3 minutes, this usage period will not be accumulated to the current session, but rather merged with the following session.

Active Project window

These settings define what end-users see on their workstations if they work on more than one project for their organization. If users are only allocated to one project, OpenLM will log their license usage without the need to take any action when the software is started. If the users work on more than one project, then a dialog box will appear on their screen prompting them to select the current project. The timing and duration for the appearance of this dialog box is configured here:

  • Display at license retrieval: The default option is to prompt the worker to select the project when retrieving a license. This is a very useful way to ensure accurate logging of the project information, therefore the recommended setting is to leave the checkbox turned on.

  • Display periodically every: Users may start to work on one project, and then switch to a different one, without changing the Active Project setting. If this checkbox is ticked, the dialog box will pop up in a predefined time interval, according to the number of minutes set by the user.

Hide projects option from menu

Deny users the ability to determine the name of the project on which they’re working.

Support Environment Variable

The LM_PROJECT env. variable support is a backward-compatibility option, that supports this variable for registering projects. The variable is defined separately for each workstation, so there is no option of overriding its value between users.

The environment variable option is disabled by default. It is recommended to use the OpenLM supplied solution, unless backward support of the environment variable option is required.

The “Add unknown project” option presents an administrative filter for project names that are unknown to the OpenLM server:

  • Checked: The unknown project will be set and added to the list of projects.

  • Unchecked (default): The unknown project will not be set.

Project creation

In order to create a new project, open the EasyAdmin web application.

  • Click the EasyAdmin ‘Start’ Button, and navigate to “Users & Permissions” → “Projects”. The “Project List” dialog box appears.

  • Click the “Add project” icon, and type in a name for the new project, e.g. “Proj1”.

  • Click the “Members” icon. the “Users in Proj1” appears.

  • Click the green ‘Add’ icon to assign users to this new Proj1.

Selecting the active project

When logging of project information is enabled (see above), work hours need to be assigned to a specific project. When there is only one project – that project will automatically be assigned all the working hours. When there are more than one project – it is up to end users to report on what project they are currently working.

1. One option for the end user to set the Active project is to right-click the Agent icon, and select the “Set Active Project” option.

2. Another option for setting the Active project is by a pop-up window. The appearance of this pop-up is configurable by options in the OpenLM server configuration tool’s ‘Projects’ tab, elaborated above.

Please follow and like us:

FLEXlm FLEXnet 2013 feature codes for Autodesk products

Feature Code => Product Name translation table can be found in Autodesk site: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=18708301&linkID=9240617

OpenLM updates this information regularly. If update is needed open the OpenLM Server configuration form->Advanced tab and update the translation table from our website with a single click.

Please follow and like us: