Trouble Shoot Form: OpenLM Server Item 001(Unable to upgrade OpenLM server version)

 

Title Unable to upgrade OpenLM server version
Category Installation
Date Nov 03, 2011
Handled by Rachel, Oren
Relevant Links
Applies to license managers FLEXlm, FLEXera FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license model Floating licenses, Network licenses, Concurrent licenses, Node Locked
Symptoms “After upgrade, server configuration will not run”
Customer could not uninstall The OpenLM Server module, due to lacking permissions.
Observed during investigation Customer could not uninstall The OpenLM Server module.
OpenLM Server Service was not uninstalled.
Trouble shoot process Uninstall and reinstall the OpenLM Server Service manually.
Solution Found (Found/Pending/Known Issue)

Symptom

The customer complained that after upgrading the OpenLM server, the server configuration form would not open.

Observed during investigation

The customer could not uninstall the OpenLM server module. Although being set as an administrator with administrative privileges, he was denied the ability to uninstall the OpenLM server service.

Solution

1. Back up the Database.
2. Uninstall the OpenLM server service, using a CMD file:

  • Compile a CMD file (e.g.: myUninstallFile.cmd) from the following code.
  • Run the CMD file as an administrator: Either from a command line, or Right-click on its icon, and choose to run it as an administrator.

// Stop the OpenLM Server service
net stop “OpenLM Server”
// Uninstall the OpenLM Server Service
“C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe” /u “C:\Program Files\OpenLM\OpenLM Server\bin\OpenLM_Server.exe”
// Wait for the user to click any key
pause

3. Uninstall the OpenLM Server Using the Windows Control Panel.

Note: The OpenLM server service may be reinstalled using a CMD file in a similar manner to that of the uninstallment process:

  • Compile a CMD file (e.g.: myReinstallFile.cmd) from the following code.
  • Run the CMD file as an administrator: Either from a command line, or Right-click on its icon, and choose to run it as an administrator.

// Reinstall the OpenLM Server Service
“C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe” “C:\Program Files\OpenLM\OpenLM Server\bin\OpenLM_Server.exe”
// Wait for the user to click any key
pause

4. Restart the OpenLM server service.

5. Download and run the latest OpenLM server version (MSI file)

Trouble Shoot Form: OpenLM Server Item 002 (Connection to FlexLM license server failed)

Title Unable to connect to FlexLM license server
Category OpenLM Configuration Form
Date Nov 03, 2011
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXnet publisher
Applies to license model Floating licenses, Network licenses, Concurrent licenses, Node Locked
Symptoms No activity reported on EasyAdmin for a specific FlexLM license server
Observed during investigation A License server’s  ‘LED’ on the EasyAdmin “License Servers” window is red.
Clicking the “Check” button for one of the 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)

Symptom

The customer complained that there was no activity on the EasyAdmin web application regarding a specific license server.

Solution

1. Make sure the License server configuration is correct:

  • Open the LMtools utility on the “Server status” tab.
  • Click the “Perform status Enquiry”. Status text appears.
  • On the “License server status” line – extract the Server name and status (e.g.: olm_lm_acad and 27000)

2. Install the OpenLM Broker on each license server machine. Refer to the Application Note for reference.

Application Note 1000: OpenLM system structure overview

Application Note 1000: OpenLM system structure overview

Table of contents

OpenLM
OpenLM’s customer testimonials
The OpenLM solution
Components of the OpenLM system
Block Diagram
OpenLM Software Modules
OpenLM Server
OpenLM EasyAdmin
OpenLM Broker
OpenLM Alert
OpenLM Utilizer Agent
OpenLM Active Agent
OpenLM External Data Base (DB) Support
OpenLM Groups & Projects
OpenLM Role Based Security
OpenLM Option File Management
OpenLM Logs Uploader

OpenLM

OpenLM is a licensing management software company with an international install base. Companies that use OpenLM’s software range from global corporations and nation-wide companies to small offices. Our company’s commitment to innovation guarantees that our clients constantly receive updates with the most advanced technology.

OpenLM’s customer testimonials

Please review a partial list of OpenLM’s satisfied customers,

http://www.openlm.com/index.php/about-us-topmenu-3/customers

and their testimonials:

http://www.openlm.com/index.php/support/testimonials-topmenu-29

The OpenLM solution

OpenLM’s Software provides a comprehensive management solution for license management software such as FLEXlm, FLEXnet, Sentinel RMS, Sentinel HASP, RLM, IBM LUM and LM-X. The software provides productivity tools for system administrators, managers and end users. OpenLM’s software supports the major trends in the field of license management, e.g.: license consolidation, Usage charge back (usage billing), usage trend analysis etc. The software provides a comprehensive solution that combines the best of breed software, superior support, implementation and consulting services, in order to ensure your success.

OpenLM is proudly ISO9001:2008 certified by the ANAB (the U.S. accreditation body for management systems), and an ESRI business partner.

OpenLM’s solution is tailored according to specific customer needs, optimizing the licensing system and increasing software productivity.

Components of the OpenLM system

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 and the OpenLM Utilizer Agent modules are incorporated in the basic software package, but their installation is not mandatory; The Open LM system can function without the use of these two components.

The OpenLM software package also includes several optional modules / capabilities, which are commonly referred to as “OpenLM extensions”. These extensions provide additional functions such as:

  • OpenLM Active Agent (Active release of licenses)
  • External DB support
  • Groups and projects management
  • Role based security
  • Option file management
  • OpenLM Alerts
  • OpenLM Logs Uploader

The OpenLM Extensions are separately licensed:

  • Some of them are included within the OpenLM Server but require additional licensing
  • Others require the installation of an additional software module.

Block Diagram

Figure1 (below) shows a generalized block diagram of OpenLM’s license management solution:

OpenLM Software Modules

OpenLM Server

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. It is responsible for collecting information from various system components and storing it in an embedded relational DB. External databases like Oracle or Microsoft SQL Server are also supported.

The OpenLM Server is implemented as a Windows service and could be installed on any network machine. It enables monitoring and managing of multiple license servers, over LAN or WAN networks. Common OpenLM Server configurations may vary from one or more license managers nationwide to multiple license servers located worldwide, over different time zones.

OpenLM EasyAdmin

OpenLM EasyAdmin is the administrative interface of the OpenLM system. EasyAdmin’s control panel features a desktop interface that enables users to configure the OpenLM Server; OpenLM’s core component. Some of EasyAdmin’s main properties are listed below:

  • EasyAdmin Easily extracts statistical license usage information from all attached license servers.
  • EasyAdmin’s role-based security enables system administrators to grant varying degrees of access to different groups of users.
  • EasyAdmin can run on any standard web browser (e.g.: Mozilla FireFox, Microsoft Internet Explorer, Google Chrome) and be accessed from any machine in the organization.
  • EasyAdmin features a touch interface that is compatible with mobile operating systems like Android, IOS, Blackberry and Windows Mobile. The OpenLM EasyAdmin Mobile application is particularly useful for after-hours crisis management situations.
  • EasyAdmin’s streamlined user interface design promotes simple and effective use of its unique capabilities.

OpenLM Broker

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

The Broker’s main task is to extract License Manager Servers’ debug log information and to push it to the OpenLM server. This action facilitates reading of license servers’ log files. Other capabilities provided by the broker are:

  • Controlling license servers remotely (e.g. start / stop the servers)
  • Managing FLEXLM option files.
  • Generating denial reports and
  • Support of complex configurations, e.g. license servers that work over WAN networks.

The Broker is an independent java based software module that can run on any license server operating system: UNIX, Linux or Windows.

OpenLM Alert

The OpenLM Alert is a dedicated alerting service for the OpenLM system. This module alerts system administrators when predefined conditions are met. Alert service users can set complex alert conditions on multiple license servers. For example, if the combined usage of a certain feature on servers A and B is above a certain threshold, an email message will be sent, alerting those concerned to the situation. The Alert service also supports adjustable timing for alert checking and message sending. Alert destinations are also configurable; Alerts could be sent to the EasyAdmin interface, over emails, as SMS text messages, or directed to a system event log.

OpenLM Utilizer Agent

The OpenLM Utilitzer Agent is the end user tool of the OpenLM system. It provides OpenLM users with the following capabilities:

  • Query license availability.
  • Check which users are holding required licenses.
  • View a user’s full set of details as they appear on the LDAP, and communicate with users regarding license availability.
  • Receive license availability notifications as soon as requested licenses become available.
  • Report the session’s active project (mainly for billing purposes).

OpenLM Active Agent

The Active Agent incorporates all the characteristics of the Utilizer Agent. On top of that, it supports an extension that enables system administrators to shut down open application either manually, or by defining a timeout policy. In this manner, system administrators can save, close, or suspend idle applications, in order to make more efficient use of licenses. The Active Agent features a user-friendly interface that enables users to quickly reopen closed applications, or resume suspended ones.

OpenLM External Data Base (DB) Support

This extension facilitates saving license usage information on an external Data Base such as an Oracle or MS SQL Server. By default, OpenLM uses an embedded DB. External DB support is recommended for management of large licensing systems.

OpenLM Groups & Projects

This extension enables collecting license usage information from Groups of users or projects. This capability is predominantly used by companies that charge back usage time to cost centers. The Groups & Projects extension synchronizes users’ data with its LDAP Data Base (Active Directory), keeping the data collection process fully automatic.

OpenLM Role Based Security

The OpenLM Server supports a role-based security feature that enables the implementation of customized access to OpenLM tools by setting access roles. This feature facilitates the implementation of OpenLM tools for diverse groups; e.g.: help desk, system administrators, managers and developers. The role based security system secures nearly all parts of the system entities, such as listed servers, fields and action buttons.

OpenLM Option File Management

The OpenLM Option File Management extension employs LDAP (Active Directory), to enable system administrators to manage Option Files easily from the EasyAdmin web based interface. This gives the system administrators easy control over the access of user groups and individuals to licenses.

OpenLM Logs Uploader

The OpenLM Logs Uploader extension enables loading of historical FLEXlm debug log files. This extension is essential for investigating historical license usage. Logs Uploader is also necessary for checking license usage in files received from customer sites, typically in order to charge per use.

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

General:

FLEXLM ( FlexNet publisher ) option files grant license administrators close control over various operating parameters within the constraints of the license model. Licensed features can be dedicated, denied or reserved to users or groups of users, according to the option file’s setting.

Employing FlexLM option files, the license administrator can:

1. For concurrent (floating) licenses:

  • Allow the use of features

  • Deny the use of features

  • Reserve licenses

 

Concurrent licenses can be held either in license files or in fulfillment records within trusted storage.

2. For all license types:

  • Restrict the number of licenses available

  • Control the amount of information logged about license usage

  • Enable a report log file

  • Control the automatic rereading of licenses

 

FLEXlm Option files are implemented as text files, located on the license server. Although  this method fits the licensing requirements well, the process of creating and maintaining option files is error-prone and difficult to maintain.

The OpenLM solution incorporates synchronization of License administration tools with the organization’s LDAP (Active Directory), keeping the FLEXlm option file up-to-date as users leave or join the organization, or move between groups.

 

Creating an Option File

1. The Option file should be placed under the same directory as the vendor daemon file, in order to enable FlexLM to read it automatically. Locating the Option file in a different folder is possible, but this requires FlexLM to be configured to search for it in that location.

2. The recommended name for the Option file is vendor.opt, where vendor is the vendor daemon name. Note that the name should not contain white spaces ( e.g.: Arcgis vendor: arcgis.opt,  Adsflex vendor: adsflex.opt ) “Vendor name.opt” is illegal.

FLEXlm option file editing

When configuring the option file using OpenLM, the configuration data is presented to the OpenLM Server, and forward by it to the OpenLM Broker, located on the license server machine. The OpenLM Broker updates the option file.

OPENLM SERVER CONFIGURATION

Check the “Enable OpenLM option file management” box

 

It is necessary to install the OpenLM Broker on the license server machine in order to edit the option file using the OpenLM EasyAdmin web application.

OPENLM BROKER INSTALLATION

  • Information about the OpenLM Broker and its installation process is available in Application Note #1004.

  • The latest OpenLM Broker version  is available for download for version 1.8. If you need a previous version please contact Support@openlm.com.

OPENLM BROKER CONFIGURATION

The next step after creating an option file on the license server machine, is to configure the OpenLM Broker to work with it.

 

1. Open the “OpenLM Broker configuration tool” installed on the license server machine

(“Start” → “Programs” → “OpenLM” → “Broker” → “Broker Configuration Tool”). The Broker Configuration Tool window appears.

 

2. On the Broker Configuration Tool window, Click the (+) button near the License server name in the configuration window.

 

 

3. Click the (+) button near “Vendors” (1).

 

4. Click the “Edit” button.

 

5. Check the “Watch Option File” box (2)

 

6. Type in the path to the Option file previously created. (3)

 

7. Restart the OpenLM Broker.

Editing Option Files

OPTION FILE TARGETS: USERS, USER GROUPS, HOSTS, HOST GROUPS AND IPS

Option Files apply license permission limitations to certain target categories; namely Users, User groups, Hosts, Host groups and IPs. Setting up and introducing these targets is beyond the scope of this article, but a short explanation on each of these target categories is attached at the end:

In order to edit option files, select a specific option file, and then apply changes to it.

OPTION FILE SELECTION

1. Open the OpenLM EasyAdmin web application.

2. Click Start → Opt. File Admin. The “Option File” dialog window appears.

3. Select the specific Option file to be edited (e.g.: Autocad Option File) and click “Set”.

 

GLOBAL SETTINGS OF THE VENDOR DAEMON

On the EasyAdmin web application click Start →  Option Files → Policy.

The “Policy of Option File” window appears.

This window comprises of several text boxes:

GROUPCASEINSENSITIVE (OFF / ON)

ON: User names and host names specified with the Options File GROUP and HOST_GROUP keywords respectively, are treated as case insensitive.

OFF (Default): User names and host names are treated as case sensitive.

NOLOG { IN | OUT | DENIED | QUEUED }

Suppresses logging of the selected type of event in the debug log file.  License administrators may use this option to reduce the size of the debug log file, however it can reduce the usefulness of the debug log when debugging license server problems.

  • IN / OUT: Turns off logging of license check-ins and check-outs respectively.

  • DENIED: Turns off logging of license check-out denials.

  • QUEUED: Turns off logging of queued license requests.

REPORTLOG

Specifies the report log file for this vendor daemon. It is recommended to precede the report_log_path with a ‘+’ character to append logging entries; otherwise the file is overwritten each time the daemon is started.

TIMEOUTALL

Specify the idle timeout for all features, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

DEBUGLOG

Writes debug log information for this vendor daemon to the specified file.

Note that this affects output from only the vendor daemon associated with this options file. The debug log output of lmadmin or lmgrd and any other vendor daemons in the same license file is not captured in this file.

Click the ‘Save’ button in order to save the edited configuration.

FEATURE SETTINGS

On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘Features’.

The “Features of Option File” window opens, according to the option file selected before. This window enables the configuration of each feature separately, applying changes either globally or to specific Users, User groups, Hosts, Host groups and IPs.

1. Select a feature. The ‘Permission’ column is filled

2. Select a user (shown in the screenshot below):

2a. Select the Users tab

2b. Click the ‘Add’ icon. The “Users search” window appears.

2c. Mark users from the “Users search” window, and click the ‘Select’ icon. The selected users are added

3. Select a specific permission, and set its value as explained here:

BORROW_LOWWATER:

Sets the minimal number of BORROW licenses that cannot be borrowed, i.e: the minimal number of licenses that need to remain as Network licenses. For example, if FEATURE has a count of 10, borrowing is enabled in the application, and BORROW_LOWWATER = 7 then only 3 licenses may be borrowed. This option is used for licenses held in license files.

LINGER:

A lingering license stays checked out for a specified period of time beyond its checkin or FlexEnabled application exit, whichever comes first. This configuration enables users to extend the linger time for a feature beyond its check in.

Note:

  • The software publisher sets a minimum linger value. If a value smaller than the minimum is configured, the minimum value is used.

  • The linger time may be configured by the software publisher in the FlexEnabled application. When this is the case, the longer linger time is applied.

MAX_BORROW_HOURS:

Change the maximum borrow period for a specific feature. The new configured period value must be less than that in the license file. This option is used for licenses held in license files.

MAX_OVERDRAFT:

The overdraft policy allows a software publisher to specify a number of additional licenses which users are allowed to use, in addition to the licenses they have purchased. This allows your users to not be denied service when in a “temporary overdraft” state. The MAX_OVERDRAFT parameter Limits the overdraft usage to less than the amount specified in the license file.

TIMEOUT:

Specify the idle timeout for a feature, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

SETTING PERMISSIONS ON SPECIFIC FEATURES

Some Option permissions may be applied according to the following categories: Users, Groups, Hosts, Host Groups and IPs as shown below.

These configurations include

  • Reserved: Reserve licenses for a User / User group / Host / Host group of users/hosts.

  • Included: Allow a user to use a feature.

  • Excluded: Deny a user access to a feature.

  • Borrow Included: Allow a user to borrow licenses.

  • Borrow Excluded: Deny a user the ability to borrow licenses.

  • Max: Limit usage for a particular feature/group—prioritizes usage among users.

ALLOW OR DENY THE ENTIRE VENDOR’S FEATURE SET

It is possible to Allow or Deny a category of users (user\group\host\host group\IP) the entire set of features that a specific vendor daemon serves. In order to do that:

  1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → “All Features”.  The “All Features …” window appears.

1. Add a Category of users (User \ Group \ Host \ Host Groups \ IP)

2. Check the “Include All” or “Exclude All” radio button;

  • Include All: Allow a user to use all features served by this vendor daemon.

  • Exclude All: Deny a user access to all features served by this vendor daemon.

3.Click ‘Save’.

SAVING THE OPTION FILE ON THE LICENSE SERVER

Saving the changes made to the Option file back to the License Server is done as follows:

1. On the EasyAdmin web application window click “Start” → “Opt. File Admin.”

2. Select the specific Option File, and click “Set”.

3. Select “Save back to server”.

The Option file update mechanism

  • The OpenLM Server writes this request to a table on OpenLM db and waits.

  • Every 10-15 seconds the OpenLM Server checks that table for any new messages for sending to the OpenLM Broker.

  • If such messages are available, the OpenLM Server sends the option file back to the broker.

  • The OpenLM Broker receives the new option file. It creates a copy of the old option file and replaces it with the new one.

  • After that, the broker issues a re-read command to the license manager. If the re-read was successful, the process is complete.

This procedure refers to user permissions. The same permissions are applicable to Groups( a groups of users ), Hosts, Host Groups (defines a group of hosts) and IPs.

 

Appendix A: Users and Groups

There are two methods of introducing new users and user groups to the OpenLM system. One is through the EasyAdmin web application, and the other is by synchronizing with a company’s Active directory. Both these methods are elaborated below.

SYNCHRONIZING USERS AND USER GROUPS WITH AN ACTIVE DIRECTORY (AD)

The best way to add users and groups is to synchronize them with the AD. OpenLM supports such synchronization:

1. Open “OpenLM Server Configuration” (Start →  Programs → OpenLM →  OpenLM server configuration )

2. Select the “Active Directory” tab.

3. Enter The following information in order to connect to the AD and synchronize users:

3a. Domain name: The Active Directory domain name is the full Domain Name System (DNS) name of the domain.

3b. Active directory user name and password, in the respective fields.

4. From the LDAP Server drop-down menu select “ActiveDirectory”.

5. Check the “Synchronize users” checkbox.

Another method for adding users and groups makes use of the EasyAdmin “Users & Permissions” menu:

INTRODUCING A NEW USER

On The EasyAdmin window, Click Start → Users&permissions → Users. The User details window appears.

Insert the required data, Check the ‘Enabled’ box,  and click the ‘Save’ button.

INTRODUCING A NEW USER GROUP

  • In The EasyAdmin web application, Click “Start” → “Users & Permissions” → “Groups”. The Groups window appears.

  • Click the green “Add Group” icon in order to create a new group. Enter the new group name (e.g.: my_new_group), and click “OK”.

 

  • On the “Groups” window, select the newly created group (e.g.: my_new_group), and click the “Members” icon to add new members to the group. The “Users in my_new_group” window appears.

  • Click the green ‘Add’ button. The “Users search” window appears. Mark and select users from the “Users search” window to add to my_new_group.

Appendix B: Adding an IP

What is an IP?

An Internet Protocol (IP) address is a numerical label assigned to each device (e.g., computer, printer) participating in a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: Host or Network interface identification and location addressing.

Controlling the license usage of a specific computer is made possible by the “IPs” tab on the “Features of Option File” window. It is also possible to control the license usage of an IP range of computers. For example, typing in the IP:  123.123.123.* causes the feature configurations done in the “Features of Option File” window to be implemented on all user IPs in the range of 123.123.123.0 through 123.123.123.255.


Adding a specific IP:

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip address you want to add.

Add a range of IPs

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip range you want to add (as explained above).

 

Appendix C: Adding a Host Group

About Host Groups

Custom groups of virtual machine hosts may also be created, for grouping of hosts and their virtual machines in meaningful ways. For example, you may create a host group for every branch office in your organization. You can also use host groups to set aside resources on hosts in the host group for the use of the host operating system.

1. On the EasyAdmin web application window click “Start” →  “Option Files” → “Host Groups”. The “Host Groups” window appears.

2. Click the green ‘+’ sign, and add a group (e.g.: my_host_group1).

3. Select the newly added group, and click the “Members” icon. The “Memebers of my_host_group1” window opens (see image).

4. Select the computers that are required for grouping, and click the green “Select” button. The new Host group is ready for use.

Revision

Revision 1.3 (Revised)

Authors: Mira, Orik, Chen

May 20, 2013.

Upgrade guide of OpenLM Version 1.6 to Version 1.7

To take advantage of the significant changes made to the database structure and other important aspects in OpenLM version 1.7, we recommend performing a preliminary upgrade test before actually upgrading the production environment.

The level of this preliminary check varies depending on the customer’s needs. If 24/7 service level is needed, then a full check that includes an installation of a test system and a full upgrading and testing of the test system is recommended. A short DB upgrade test may sufficiently satisfy less comprehensive customer requirements. OpenLM customers are welcome to contact our support team and consult with them about any upgrade issues.

The changes to the upgrade process relevant to the installation included in this version are:

  • DB structure change
  • Agent software, featuring an improved performance and streamlined interface. As OpenLM Agents prior to version 1.6 are not compatible with the new server version, this upgrade is a must. Agent versions 1.6 and above are compatible with the new version, so a graduate upgrade is recommended to enjoy the full capabilities of the new version.
  • FDB has replaced GDB as the standard extension for the Firebird DB file.
  • OpenLM now supports the use of a virtual license server, which can be a group of Triad servers (with FLEXlm). This will change your existing license server configuration.
  • OpenLM Broker is significantly upgraded to support the advanced new functions of OpenLM version 1.7. We highly recommend to also upgrade OpenLM Broker, but this can be done separately after upgrading the server. The current installation of Broker 1.7 will not be able to preserver your current broker settings (link).
  • The server and agent software requires .NET Framework 4.0.

Two different procedures are outlined in this document. One is for installations that use the embedded Firebird database and the other is for installations that use external database (Oracle, MS SQL Server or Firebird Server – requires additional licensing). These two procedures are further divided into a full and a preliminary check procedure.

Short preliminary check procedure for embedded database configuration

First stage: Backup your database file!

Stop “OpenLM Server” Windows Service, navigate to the location of your OpenLM Server database file, typically “C:\Program Files\OpenLM\OpenLM Server\db\OPENLM_DB.GDB,” and backup the database file.
Note that backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file risks your data.

Second stage: Test the database upgrade process (optional)

Choose a test workstation  (XP, Vista, Windows 7 or server OS) and take the following steps:

  • Install OpenLM Server version 1.7 on the test machine.
  • Stop “OpenLM Server” windows service (on the workstation).
  • Copy of your production database and paste it to C:\Program Files\OpenLM\OpenLM Server\db\OPENLM_DB.GDB to the test workstation. Rename it to OPENLM_DB.FDB and delete the DB provided with the software. Run Start→OpenLM→Server→Upgrade Database from Earlier Versions.
  • Upgrade your database and make sure that no errors are reported.

Now you can upgrade your production system.

Short preliminary check procedure for external databases

First stage: Backup your database!

Note that the backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file risks your data.

Second stage: Upgrade your database

  • Download the appropriate database upgrade script from OpenLM Downloads area.
  • Stop OpenLM Server service and then Run the appropriate upgrade script in order to upgrade the database.
  • Make sure that no error messages are reported.

Now you can upgrade your production system.

Full Upgrade procedure with preliminary check for embedded database configuration

First stage: Backup your database file!

Stop “OpenLM Server” Windows Service, navigate to the location of your OpenLM Server database file, typically “C:\Program Files\OpenLM\OpenLM Server\db\OPENLM_DB.GDB” and backup the database file.

Note that the backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file risks your data.

Second stage: Test the database upgrade process (optional)

Choose a test workstation (Not your current OpenLM Server) and take the following steps:

  • Install OpenLM Server version 1.6. (the exact version you currently use) on a workstation (XP, Vista or Windows 7).
  • Stop “OpenLM Server” windows service (on the test workstation).
  • Replace the database with a copy of your production database C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB.
  • Start “OpenLM Server” windows service.
  • Upgrade the system by installing OpenLM Server 1.7 on-top of this installation and follow the instructions.

Test the new installation.

Third stage: Make sure your database backup is in a safe place and upgrade your production system.

This upgrade is simple – install the new 1.7 package on your production server. It will update both the software and  your database. OpenLM service will not be available during the upgrade process.

Fourth stage: Update OpenLM Agents.

OpenLM Utilizer Agent versions that prior to version 1.6 are not compatible with OpenLM Server 1.7. You must upgrade OpenLM Agent software on all workstations.

Agent versions 1.6 and above are compatible with the new version, so a graduate upgrade is recommended to enjoy the full capabilities of the new version (like the Active Agent new features).

OpenLM Utilizer users can download and install OpenLM Utilizer Agent on every workstation using floating licenses.

OpenLM for ESRI ArcGIS and OpenLM for Autodesk users can download and install OpenLM Active Agent.

OpenLM supports various distribution methods including start up scripts and network management systems like CA Unicenter and Microsoft SMS. Check this blog post for more information about OpenLM Agent silent install.

Fifth Stage: Install OpenLM Broker on any FLEXlm server managed by OpenLM.

If OpenLM Broker is not already installed, download OpenLM Broker and install it on each license server. OpenLM Broker highly enhances the capabilities of OpenLM Software.

We also recommend upgrading existing OpenLM Broker installations by installing OpenLM Broker 1.7 over the existing version of the software. Since now the upgrade program will not preserve your existing settings,  please backup the settings by taking screenshots or by backing up the broker configuration file named: broker.xml. The file is located in the broker installation folder. On Windows it typically located in C:\Program Files\OpenLM\OpenLM Broker (Link) .

On a Windows workstation the broker typically recognizes most of the settings automatically.

Full Upgrade procedure with preliminary check for sites that use an external database

This procedure is relevant to users who configured an external database with OpenLM Server. OpenLM Server supports Oracle, Ms SQL Server or Firebird server.

First stage: Backup your database!

Note that backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file risks your data.

Second stage: Upgrade your database

Download the appropriate database upgrade script from OpenLM Downloads menu.
Stop OpenLM Server service and then run the script in order to upgrade the database.

Third stage: upgrade your production system.

To Upgrade your production system, install the new package 1.7 on your production server. It will update the software while preserving all your settings. OpenLM service will not be available during the upgrade process.

Test the system!

Fourth stage: Update OpenLM Agents.

OpenLM Utilizer Agent versions prior to version 1.6 are not compatible with OpenLM Server 1.7. You must upgrade OpenLM Agent software on all workstations.

Agent versions 1.6 and above are compatible with the new version, so a graduate upgrade is recommended to enjoy the full capabilities of the new version (like the Active Agent new features).

OpenLM Utilizer users are able to download and install OpenLM Utilizer on every workstation using floating licenses.

OpenLM for ESRI ArcGIS and OpenLM for Autodesk users are able to download and install OpenLM Active Agent.

OpenLM supports various distribution methods including start up scripts and network management systems like CA Unicenter, Microsoft SMS and others. Check this blog post for more information about OpenLM Agent silent install.

Fifth Stage: Install OpenLM Broker on any FLEXlm server you may have.

If OpenLM Broker is not already installed then download OpenLM Broker and install it on each license server. OpenLM Broker highly enhances the capabilities of OpenLM Software.

We also recommend to upgrade existing OpenLM Broker installations.
Please report problems to OpenLM Team!
Email: support@openlm.com
OpenLM contact form.

Problem/Error with AutoCAD network license management: “A valid license could not be obtained by the network license manager”

Details:

You can face above problem frequently on AutoCAD 2007 based products when you are working in an organization where:

  • Concurrent licensing scheme is implemented through server/client networking mode.
  • Network bandwidth is low.
  • Network latency is high or connected through VPN.

All of the products based on AutoCAD 2007 contain licensing enhancements which tend to increase network latency and bandwidth utilization of the network. Therefore, you can face this problem while trying to claim the license of the program from the License Manager Server. Earlier versions of AutoCAD products i.e. older than 2007 release were not observing this problem. In this problem, first you are presented with a FLEXlm license finder dialogue box during license obtaining process followed by a message stating:

“A valid license could not be obtained by the network license manager.

Error [1.5. -15]”

In some other products you can receive a bit different message as given below:

“A valid license could not be obtained by the network license manager.

Error [1.5. -18]”

Reasons for Error:

A network throughput or data rate of the link is the main reason for this error especially in case of heavy applications like AutoCAD 2007. Reasons can be summarized as below:

  • Low Bandwidth of the connection i.e. Dial-up connection or low speed ISDN/DSL connection.
  • High Network Latency i.e. VPN
  • Response waiting time of the application/program

One or more of the above reasons can be the root cause of this problem. This problem has recommended solutions which given below.

Solutions:

  • Recommended solution for this problem is either increase in the bandwidth of the connection or decrease in the network latency or enhancement in both parameters.
  • By modification of the response waiting time counter/value which is used as the last resort for the solution of this problem. This is a stepwise procedure to modify the response waiting time counter. Here is the stepwise procedure for the same:
  1. Right click My Computer and choose properties.
  2. On system property dialogue box choose advanced tab.
  3. Click on the environment Variables
  4. On environment variable dialogue box choose system variables field and hit the new button
  5. A new system variable dialogue box with two fields appears; put “FLEXLM_TIMEOUT” in variable name and put 1000000 in variable value field.
  6. Click OK on all three dialogue boxes to close them
  7. Launch the AutoCAD application

 

 

 

 

 

 

 

 

If the problem persists, increase the variable value in multiples of 1000000 micro seconds and reach to the value which gives you satisfactory communication results.

ArcGIS Software Bug/Problem: “The ArcGIS Desktop Administrator does not connect to ArcGIS License Manager 9.3 while it is connected through VPN or network speeds are slow”

Details:

You must not panic when you see above mentioned issue during the process of ArcGIS license-claiming from ArcGIS License Manager 9.3. This is a software bug mostly observed in all level of ArcGIS software ver9.3; earlier releases of this software did not observe this problem but following mentioned all levels observed this issue.

  • ArcGISArcEditor 9.3
  • ArcGIS – ArcInfo 9.3
  • ArcGIS – ArcView 9.3 & 9.3.1
  • ArcInfo Workstation 9.3

All of the above software modules observe this problem while operating on following Windows Operating systems.

  • Windows 2000
  • Windows XP
  • Windows 2003 Server
  • Vista

This bug is identified by the ID ‘NIM037135’ and FlexNet licensing error ID “-15,570” which is shown in the error report/message returned against licensing request to the server. Following error message is returned with related details:



The name of the server and license path may vary as per network configuration. The error numbering scheme will be -15 and followed by 570 after comma; this is ArcGIS error reporting format.

Reasons for error:

This happens mostly in following two conditions when network/concurrent licensing scheme for ArcGIS is implemented.

  • The connection between server and license requesting machine is through VPN.
  • The connection is either Dial-up or a slow ISDN/DSL one.

Solution:

There is a stepwise process to resolve this issue of the software through modification of the environment variables in the Windows operating systems. The network or server client messages take certain time to process and reach at their destinations. Therefore, the waiting time of the program for communication response to reach is set a bit larger to resolve this issue on the windows OS. Stepwise procedure is given below:

  • Right click My Computer and choose properties.
  • On system property dialogue box choose advanced tab.
  • Click on the environment Variables
  • On environment variable dialogue box choose system variables field and hit the new button
  • A new system variable dialogue box with two fields appears; put “FLEXLM_TIMEOUT” in variable name and put 1000000 in variable value field
  • .Click OK on all three dialogue boxes to close them
  • Launch the ArcGIS 9.3 program

If the problem still persists then, repeat above mentioned procedure with an increase the variable value in the multiples of 1000000 micro seconds and reach to the value which gives you satisfactory communication results.

OpenLM Version 1.6.2.4 – Maintenance release

Version 1.6.2.4 is a maintenance release to version 1.6. It contains some bug fixes to problems found in previous versions. We  recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.2.4?

OpenLM Server:

  1. Configuration – problem configuring DNS resolve time & Workstations release time on AM/PM formatted times.
  2. Export IP column in “License Activity” report.
  3. Fix issue with reading licenses in MS SQL Server.
  4. Fix user details display when user contains special characters.
  5. Fix – when adding new user with only one group/project it now automatically becomes default.
  6. Option files – error reading long paths policy strings.

Note:
Please follow these steps when upgrading (Some of our customers experienced “error 1001” which is related to a problem with Windows):

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

OpenLM Version 1.6.1.4 – Maintenance release

Version 1.6.1.4 is a maintenance release to version 1.6. It contains minor bug fixes to problems found in previous versions. We  recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.1.4?

OpenLM Server:

  1. Hide Active Directory password also while editing in “Configuration Form”.
  2. Fix roles management functions for Oracle users..
  3. Fix License Activity TAB sometimes shows negative working hours when “Consider only working hours” is checked.
  4. Fix message box shadow in “Change Password” form in IE8 with compatibility view.

OpenLM Active Agent version 1.6.0.4 was also published. Please check a separate message regarding this.

OpenLM Version 1.6.1.2 – Maintenance release

Version 1.6.1.2 is a maintenance release to version 1.6. It contains bug fixes to problems found in previous versions. We recommend all users of version 1.6. to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.1.2?

OpenLM Server – Fixed problem with reading messages from OpenLM Broker.
OpenLM Server – Fixed a problem with RLM license server.
OpenLM Server – Fixed an issue with workstations listing in Workstations tab.
OpenLM Server – Fixed an issue related to many agents.
Easyadmin – Solved problem with dragging and dropping groups in Groups window..
Easyadmin – Solved a problem with Minutes-resolution charts.
Easyadmin – Fix an issue related to  message-box shadow in IE in compatibility mode.
EasyAdmin – Set default group automatically when a user is assigned to one group.
OpenLM Alerts – Fixed problem with listing user without groups.