Application Note 1032: Monitoring FlexLM license denials


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

OpenLM Maintenance Release Version


Version is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.


In order to upgrade to version
1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
2. Stop the OpenLM Server service
3. Make sure ALL windows are closed; especially the services window.
4. Install the new version on top of the existing one.

What’s new in version (and its close predecessors)?

OpenLM Server:

1. Fixed Reprise RLM license manager issue #515: No active users (v1.7.3.2).
2. Fixed Sentinel RMS token counting issue #511 (v1.7.3.1)
3. Fixed LM-X version parsing issue (v1.7.3.0)
4. Changed the registration link to the new from (v1.7.3.0).
5. Fixed HASP issues #495 & #496 (v1.7.3.0)
6. Changed license matching for Monitored Processes (v1.7.3.0)
7. Fix RLM date parsing.  (v1.7.2.9)
8. Add debug info for suspend/resume. (v1.7.2.9)

Please follow and like us:

IBM LUM i4blt command reference


Even though the IBM LUM license monitoring tool has decreased in popularity over the passed several years, it is still a widely spread tool for monitoring and tracking license usage of many CAD applications.

The OpenLM license monitoring tool extracts information from a variety of license managers, such as Flexnet / FlexLM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and – of course IBM LUM. OpenLM extracts comprehensive license reports and obtains license statistics for all these lisence managers.

In order to interface the IBM LUM license manager, OpenLM employs the i4blt command.
The i4blt command is very versatile; its usage depends on the attached i4blt flag options. The following document is a reference to some of these flags.


There are several syntax rules to be met:
1. Named strings containing spaces must be presented within single quotation marks.
2. Names are case sensitive
3. Listed values must be presented within double quotation marks, e.g.:
i4blt -lp -n my_server -v “‘Vend A’ ‘Vend B'”
4. Parameters that appear within options are position specific, e.g.: vendor information in the i4blt -E (Enrollment) option include vendor_name, vendor_id, and vendor_password.

Command reference

The following diagram is a reference to some of the main i4blt options. The Yellow rectangle is a complete reference to the primary i4blt command options. the turquoise rectangles contain elaboration for some of these primary options.

Usage examples:

The following are usage examples of the i4blt command. The examples are taken from real workstations, and include genuine usage information. They were cleared of any user identification markings.

i4blt -s -lc

In order to obtain current license usage information, OpenLM employs the i4blt -s -lc option.

i4blt -ln

The list display option with the ‘n’ flag lists the servers which are monitored by the IBM LUM.

i4blt -r1 -e

The r1 report type enables the extraction of  further information. This example shows license related event logging, in this case: license release.

Forward reading

I have found the following links helpful:
From the University of Alberta

A bit about HAL (High – Availability licensing) : i4blt -H.

Please follow and like us:

License manager ports: FlexLM(Flexnet), DSLS, IBM LUM, LM-X, Sentinel HASP, Sentinel RMS, Reprise RLM.


Licensed applications communicate with license management tools over predefined ports. system administrators need to know these port numbers, verify that these ports are open and communication via these ports is kept functional.

The OpenLM Utilizer tool interfaces various license managers in order to extract license statistics and usage reports. The license manager ports are different for each tool as elaborated below, and need to be configured correctly in the OpenLM modules.

How do I know the port I need is open for communication ?

The simplest method for verifying that a port is open for communication is by ‘Telnet’. The Telnet utility comes built in Windows XP, but needs to be installed on Windows 7. Open a command line prompt, and type in the following line: telnet <Hostname or IP> <Port number>. For example:
> telnet 27000 or > telnet My_Hostname 27000
If the cmd window remains blank, the port is open. Otherwise, an error string would appear.
In such a case, it is suggested to do the following:
1. Make a port exception in FireWall, or temporarily disable it altogether, to ascertain whether the Firewall is to blame.
2. Temporarily disable the Antivirus, to ascertain the same.
3. If a hostname was inserted in the command line, try typing in an IP instead.
4. Try a different port, or ‘ping’ the server:

Specific license management tools

Flexera FlexLM ports:

The OpenLM license monitoring tool provides unique abilities for monitoring and controlling Flex-enabled applications. The FlexLM ( Flexnet ) license manager communicates through ports 2080 and 27000 to 27009. In order to verify which ports are used, please read this short post.
The ports may also be altered, and set up statically by the system administrator.

Dassault Systemes DSLS ports:

DSLS employs three ports for License management:

  1. Administration port: default 4084. Connecting the License Administration Tool GUI to the Server.
  2. Licensing Port: default 4085. Used by clients to request licenses.
  3. Failover port: default 4086.Used for communication among cluster members.

IBM LUM ports:

LUM Network Client and Server communicate over UDP protocol on Network License Server port (by default 1515).

LM-X ports:

LM-X Network Clients and Servers communicate through port 6200 (default) over TCP.

Sentinel HASP ports:

The Sentinel HASP License Manager uses port 1947 to transfer data over TCP and UDP protocols.

Sentinel RMS ports:

  • The Sentinel RMS License Manager uses port 5093 to transfer data over UDP between Servers and clients.
  • Port 5099 is used for intercommunication between servers in a Server Redundancy constellation.

Reprise RLM port:

RLM uses port 5054. It was port 9000 prior to RLM version 6.

Please follow and like us:

OpenLM Version 1.8 Preview

The upcoming OpenLM release version 1.8 is a major milestone in the development process of the OpenLM license management system. This version has been in preparation since October 2011, when version 1.7 was released, and is expected to be officially released by the end of 2012.

Version 1.8 incorporates many bug fixes, performance improvements and new features that were required by our expanding circle of trusted customers. These changes have increased OpenLM’s robustness and made it less prone to errors.

Version 1.8 also integrates some architectural changes that have expanded OpenLM’s ability to further develop license usage control and monitoring. Here are some of the main highlights of this new version.

Database manipulation

Version 1.8 enhances the administrator’s capabilities to manipulate the OpenLM database:

  • Archive or delete old data,

  • Extract irrelevant users, delete unnecessary groups, or even

  • Use multiple OpenLM servers on a single Database. This is a prerequisite for providing support for cloud – computing license management environments.


Many changes have been made to the EasyAdmin administrative interface, making the presentation of usage reports more efficient, robust and better designed. Here are some of these enhancements:

  • Support of the Apple Safari Browser
  • License Expiration date filtering
  • License Manager Up-time logging
  • Improvements in License usage reporting (e.g: Flexnet / FlexLM reporting).
  • Improvements Feature usage reporting: accessible from every workstation.


Software packages are automatically recognized, and populated by the software product  which are members  of these packages.

User Group monitoring

The group monitoring tool would be integrated into OpenLM v1.8, and enhance OpenLM’s ability to provide clear group-related license statistics.

Support of new License management tools

The addition of license management tools to the expanding portfolio of OpenLM’s supported license managers is an on-going task. Version 1.8 already incorporates the support of FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta LM, Mathematica LM (MathLM), and Easycopy, and the list is constantly expanding.

Version 1.8 has seen the addition of Beta-LM, Mathematica LM (MathLM), and DSLS. In addition to that, support of some license management tools was enhanced, for example – the IBM_LUM license manager has been added expiration date and license denial indications.

Please follow and like us: