OpenLM Maintenance Release Version: OpenLM Server 2.0.0.33

OpenLM Server version 2.0.0.33

OpenLM Server version 2.0.0.33 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend all users of previous OpenLM Server 2.0 versions to upgrade to this latest version.

Note that this version does not update the database, only software. If your current version is 2.0.0.28 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.33 (October 29th, 2014)

Fixed Issues:

  • 2407: Feature Usage Status showing wrong results for ArcGIS products

Prerequisites

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.33:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.27 or lower in order to upgrade to version 2.0.0.33, please contact OpenLM support at support@openlm.com

OpenLM Maintenance Release Version: OpenLM Server 2.0.0.32

OpenLM Server version 2.0.0.32

OpenLM Server version 2.0.0.32 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend that all users of previous OpenLM Server 2.0 versions would upgrade to this latest version.

Note that this version does not update the database, only software. If your current version is 2.0.0.26 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.32 (August 19, 2014)

Fixed Issues:

Issue #2402: [OpenLM Server] Apply algorithm for continued session only to vendor policy = one

Issue #2403: [OpenLM Server] Data completion – do not return used log action to pool

Issue #2386: [OpenLM Alerts] Alerts – Feature Expiration Data: When more than one Feature is selected only the first is shown in Alert

Issue #2385: [OpenLM Server] Can’t parse Broker port messages

Issue #2369: [EasyAdmin] Products / packages: search only refers to features.

Issue #2375: [EasyAdmin] Products / Packages window: Can’t copy + paste a parent package name.

Issue #2338: [OpenLM Server] Codemeter: Same Feature shows up only once in “Licenses”

Issue #2361: [EasyAdmin] Can’t see projects if start date is not within the filter view period.

Issue #2377: [EasyAdmin] License Usage – “Clear All” in features filter doesn’t clear the chart line colors

Issue #2397: [EasyAdmin] License Usage Archive Report: Totals not summed up correctly

Prerequisites

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.32:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.7, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the C:\Program Files (x86)\OpenLM\OpenLM Server\License   folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.26 or lower please contact OpenLM support at

support@openlm.com for assistance in the upgrade process.

 

OpenLM License Parser Release Version 1.2

OpenLM License Parser Version 1.2

Version 1.2 is the third release of OpenLM License Parser, a service provided by OpenLM to the public of license managers.

The service is available at: www.alllicenseparser.com

What’s new in OpenLM Parser Version 1.2

  1. Added license usage charts:
    1. Session Length Distribution By Duration
    2. Top 10 Used Features in Minutes
    3. Top 10 Consumed Features by Number of Sessions
    4. Top 10 Users by Number of Sessions
    5. Top 10 Denied Features
    6. Top 10 Denied Users

Single user checking out licenses on different workstations

License management systems have methods of applying license consumption policies to their license pools. This policy determines the number of licenses that are effectively checked out for every usage scenario; For example, a user invoking the same application twice on the same workstation could either consume a single license or multiple licenses from the license pool.

Example 1: Flexera Flexnet Publisher (FlexLM)

In FlexLM this policy is set by the DUP_GROUP attribute in the FlexLM license file. The optional DUP_GROUP flags are:

Site, None, U (user), H (Host), D (Display), V (Vendor).  Any combination of UHDV is allowed, and the DUP_MASK is the logical OR of this combination. For example, DUP_GROUP=UHD means that a user on the same host and display will not consume additional licenses when invoking multiple instances of a feature.

Example 2: Reprise RLM

In Reprise RLM this policy is set by the ‘share’ attribute in the license file. A license can be shared between processes with the same username (U), hostname (H), or ISV-defined data (I), or any combination of the above. In addition, the maximum number of shared licenses can also be specified in the ‘share’ attribute; For example: share=U:3 means that a user would be able to open up to three instances of the licensed application on any host machine, consuming a single license.

Controlling the consumption policy

From our experience, Software publishers (‘vendors’)  rarely consider invoking multiple sessions on different workstations as consuming a single license. Consequently, users may inadvertently check out multiple licenses over different host machines and render the organization’s license utilization non-optimal. Having multiple license management systems, each with its own (sometimes unintelligible) method of setting the consumption policy may further worsen this condition.

OpenLM’s Solution

OpenLM provides an intuitive method of dealing with this problem: Each vendor may be attributed a “Vendor policy”. This attribute determines whether a single or multiple licenses are checked out per user. In addition, the OpenLM alerts system provides a built-in alert for notifying system administrators when a user is trespassing the license consumption policy, and consuming two licenses of the same feature in parallel.

 

Flexnet Publisher (FlexLM) Debug logs for single vendors

Closing in on specific vendor daemons

When controlling several license vendors on a single server, it is a bit difficult to zoom in on a debug messages that originate from a single vendor. Debug logs’ contents may be split and redirected to separate files, making it easier to concentrate on a specific vendor daemon’s  activity. This can be done in one by one of three methods:

DEBUGLOG

Setting the DEBUGLOG line in the options file for each vendor daemon.

Syntax:

DEBUGLOG [+] debug_log_path

This line specifies a location for the debug log output from the vendor daemon associated with the specific options file. Preceding the debug_log_path with a ‘+’ sign would append the logging information rather than overriding the file each time the License server is restarted

lmswitch

Invoking the lmutil command with the lmswitch on the vendor daemon.

Syntax:

lmutil lmswitch vendor_name debug_log

This will set debug_log as the designated file for the vendor_name daemon.

lmadmin

In the case of lmadmin – this can be done on the Vendor Daemon Configuration screen.

OpenLM

OpenLM makes use of the information in the debug log to accumulate and refine the license usage and license denial statistical data.

Flexera Flexnet Publisher (FlexLM) version 11.12 SLOG: Summary Log statistics

What’s new in FlexLM 11.12 debug logs

The FlexLM license manager produces Debug log files, which hold status information and error messages that are useful for debugging its activity. In version 11.12 Flexera added a few changes to the Debug logs; namely a set of global information entries that relate to the lmgrd daemon and to specific vendor daemons. These are referred to as SLOG: Summary Log statistics.

SLOG for lmgrd

SLOG entries for the lmgrd daemon are prefixed by (@lmgrd-SLOG@).

These include:

  • Start timestamp
  • Version
  • ProcessID
  • Network Info (IPv4/IPv6 interface, License manager port)
  • Command-line options
  • list of license files
  • Is the license server running as a Windows’ service.

Example from an actual debug log file:

 

7:47:03 (lmgrd) SLOG: Summary LOG statistics is enabled.

7:47:04 (lmgrd) (@lmgrd-SLOG@) ===============================================

7:47:04 (lmgrd) (@lmgrd-SLOG@) === LMGRD ===

7:47:04 (lmgrd) (@lmgrd-SLOG@) Start-Date: Mon Oct 06 2014 07:47:04 Central Daylight Time

7:47:04 (lmgrd) (@lmgrd-SLOG@) PID: 4756

7:47:04 (lmgrd) (@lmgrd-SLOG@) LMGRD Version: v11.12.0.0 build 136775 x64_n6 ( build 136775 (ipv6))

7:47:04 (lmgrd) (@lmgrd-SLOG@)

7:47:04 (lmgrd) (@lmgrd-SLOG@) === Network Info ===

7:47:04 (lmgrd) (@lmgrd-SLOG@) Socket interface: IPV6

7:47:04 (lmgrd) (@lmgrd-SLOG@) Listening port: 27000

7:47:04 (lmgrd) (@lmgrd-SLOG@)

7:47:04 (lmgrd) (@lmgrd-SLOG@) === Startup Info ===

7:47:04 (lmgrd) (@lmgrd-SLOG@) Is LS run as a service: Yes

7:47:04 (lmgrd) (@lmgrd-SLOG@) Server Configuration: Single Server

7:47:04 (lmgrd) (@lmgrd-SLOG@) Command-line options used at LS startup: -c D:\License\2015License.lic -l D:\License\debug -z -s

7:47:04 (lmgrd) (@lmgrd-SLOG@) License file(s) used:  D:\License\2015License.lic

7:47:04 (lmgrd) (@lmgrd-SLOG@) ===============================================

 

SLOG for vendor daemons

Debug logs may be split and redirected according to Vendor daemons. This facilitates zooming in on vendor specific data. Vendor daemon specific SLOG entries are prefixed by (@<vendor>-SLOG@). These include:

  • Start timestamp
  • Version
  • ProcessID
  • Network info (IPv4/IPv6 interface, listening port, select timeout of vendor daemon)
  • Vendor daemon name
  • Options file used
  • Trusted storage accessed (yes/no)
  • Host name
  • Virtual/physical environment
  • (limited) Hypervisor info if virtual
  • Lmbind used (yes/no)
  • Number of restarts of the Vendor daemon since lmgrd startup
  • Number of rereads since vendor daemon was started (or restarted)
  • Last reread time
  • Reread initiation type (automatic versus lmreread).

Every 4 hours (and at vendor daemon shutdown) the following performance data entries are also logged:

  • Details of the 10 peak client transactions (including client hostname, user, transaction time, concurrent clients at time of transaction, memory usage (Windows only))
  • Peak concurrent clients served
  • High watermark memory usage (for Windows only)
  • Transaction time for the last 10 transactions.

 

Example from an actual Autodesk debug log file:

 

7:47:21 (adskflex) SLOG: Statistics Log Frequency is 240 minute(s).

7:47:21 (adskflex) (@adskflex-SLOG@) ===============================================

7:47:21 (adskflex) (@adskflex-SLOG@) === Vendor Daemon ===

7:47:21 (adskflex) (@adskflex-SLOG@) Vendor daemon: adskflex

7:47:21 (adskflex) (@adskflex-SLOG@) Start-Date: Mon Oct 06 2014 07:47:21 Central Daylight Time

7:47:22 (adskflex) (@adskflex-SLOG@) PID: 3008

7:47:22 (adskflex) (@adskflex-SLOG@) VD Version: v11.12.0.0 build 136775 x64_n6 ( build 136775 (ipv6))

7:47:22 (adskflex) (@adskflex-SLOG@)

7:47:22 (adskflex) (@adskflex-SLOG@) === Startup/Restart Info ===

7:47:22 (adskflex) (@adskflex-SLOG@) Options file used: None

7:47:22 (adskflex) (@adskflex-SLOG@) Is vendor daemon a CVD: No

7:47:22 (adskflex) (@adskflex-SLOG@) Is TS accessed: No

7:47:22 (adskflex) (@adskflex-SLOG@) TS accessed for feature load: -NA-

7:47:22 (adskflex) (@adskflex-SLOG@) Number of VD restarts since LS startup: 0

7:47:22 (adskflex) (@adskflex-SLOG@)

7:47:22 (adskflex) (@adskflex-SLOG@) === Network Info ===

7:47:22 (adskflex) (@adskflex-SLOG@) Socket interface: IPV6

7:47:22 (adskflex) (@adskflex-SLOG@) Listening port: 2080

7:47:22 (adskflex) (@adskflex-SLOG@) Daemon select timeout (in seconds): 1

7:47:22 (adskflex) (@adskflex-SLOG@)

7:47:22 (adskflex) (@adskflex-SLOG@) === Host Info ===

7:47:22 (adskflex) (@adskflex-SLOG@) Host used in license file: 73YDBW1

7:47:22 (adskflex) (@adskflex-SLOG@) Running on <Physical/Virtual>:  Physical

7:47:22 (adskflex) (@adskflex-SLOG@) LMBIND needed: No

7:47:22 (adskflex) (@adskflex-SLOG@) LMBIND port: -NA-

7:47:22 (adskflex) (@adskflex-SLOG@) ===============================================

OpenLM

OpenLM makes use of the information in the debug log to accumulate and refine the license usage and license denial statistical data.

OpenLM Maintenance Release Version: OpenLM Server 2.0.0.31

OpenLM Server version 2.0.0.31

OpenLM Server version 2.0.0.31 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend all users of previous OpenLM Server 2.0 versions to upgrade to this latest version.

Note that this version does not update the database, only software. If your current version is 2.0.0.28 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.31 (October 20th, 2014)

Fixed Issues:

  • 2355: License Activity not showing content / not doing Group By
  • 2364: License is always a package when reading license file
  • 2217:On the actual day of expiration, OpenLM already regards the license expired, instead of waiting to the end of the day
  • 2345: “GetOpenLMLicenseOverview failed” message on EasyAdmin
  • 2301: Corrections/Additions to Configuration tool – LM Tools
  • 2314: SPLM not reported correctly : SPP feature == SPPD
  • 2362: Single project not attributed usage
  • 2366: License activity “group by” tab stuck

Prerequisites

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.31:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.27 or lower in order to upgrade to version 2.0.0.31, please contact OpenLM support at support@openlm.com

What is new in license parser version 1.1

OpenLM License Parser Release Version 1.1

Version 1.1 is the second release of OpenLM License Parser, a service provided by OpenLM to the public of license managers.

The service is available at: www.licenseusageparser.com

What’s new in OpenLM Parser Version 1.1

  1. Added support for the new SLOG section that is supported by Flexera Publisher version 11.12. To our best knowledge, the only vendor that supports this functionality is Autodesk.
  2. Reporting of Options that are defined for the license manager. See this post for a short explanation about FLEXlm options files.
  3. Report license server diagnostics.
  4. Better error handling and reporting to the user.
  5. Updated site layout and added a “What is OpenLM License Parser Video?”
  6. Better drag & drop interface for files

OpenLM Maintenance Release Version: OpenLM Server 2.0.0.30

OpenLM Server version 2.0.0.30

OpenLM Server version 2.0.0.30 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend all users of previous OpenLM Server 2.0 versions to upgrade to this latest version.

Note that this version does not update the database, only software. If your current version is 2.0.0.28 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.30 (October 6th, 2014)

Fixed Issues:

  • 2309: Agent_Query_Role is missing when Roles_Based_Security is not licensed
  • 2282: LM-X over-usage reported. – incorrect parsing of output file
  • 2296: AbstractBatcher Error – Could not execute SQL command
  • 2299: “Filter management” window issues
  • 2303: System Message with OpenLM Server 2.0.0.29

Other:

The option  “Consider only working hours” was temporarily removed from License Activity filter panel, because it doesn’t work properly. After fixing this option will be available in the next major version of OpenLM Server.

Prerequisites

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.30:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.27 or lower in order to upgrade to version 2.0.0.30, please contact OpenLM support at support@openlm.com

OpenLM Maintenance Release Version: OpenLM Server 2.0.0.29

OpenLM Server version 2.0.0.29

OpenLM Server version 2.0.0.29 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend all users of previous OpenLM Server 2.0 versions to upgrade to this latest version.

 

Note that this version does not update the database, only software. If your current version is 2.0.0.18 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.29 (October 1, 2014)

Fixed Issues:

 

  • 0002295: [EasyAdmin] License Servers: sorting by percentage of actual usage does not work correctly – resolved.
  • 0002293: [EasyAdmin] Feature Usage Status: sort by percentage does not work – resolved.
  • 0002297: [OpenLM Server] Avoid remote output when Broker sends information – resolved.
  • 0002292: [OpenLM Server] OpenLM_Server_Logger.txt says “Evaluation Version” though it is fully licensed – resolved.
  • 0002259: [OpenLM Server] SPLM not working with French locale – resolved.
  • 0002285: [OpenLM Server] DSLS output coming from Broker wasn’t parsed – resolved.
  • 0002281: [OpenLM Server] RMS unlimited number of licenses can not be recognized – resolved.
  • 0002279: [EasyAdmin] Feature usage status – export does not work – resolved.
  • 0002277: [OpenLM Server] Can’t clean the SPLM exe in the openlm server configuration form – resolved.

 

Prerequisites

1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.

2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.29:

1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.

2. Stop the OpenLM Server service

3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)

4. Make sure ALL windows are closed; especially the services window.

5. For OpenLM versions 1.7, Install the new version on top of the existing one.

6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the

C:\Program Files (x86)\OpenLM\OpenLM Server\License   folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.17 or lower in order to upgrade to version 2.0.0.29, please contact OpenLM support at

support@openlm.com