Tag Archives: Floating Licenses

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

Posted on by

Trouble Shoot Form: Item 02.001

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

Symptoms

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

Observed during investigation

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

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

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

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

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

Trouble shoot process

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

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

We suggest acting according to one of these options:

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

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

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

Posted on by

 

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

Symptoms

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

Trouble shoot process

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

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

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

Posted on by

Trouble Shoot Form: Item 02.002

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

Symptoms

Customer reported failure to import the SQL database to FB.

Trouble shoot process

 

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

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

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

Posted on by

Trouble Shoot form: Item 01.004

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

Description

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

Troubleshoot

1. One option is:

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

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


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

Posted on by

Trouble Shoot form: Item 01.002

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

General

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

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

Symptom

The Command lines are blank

Troubleshooting

 

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

 

Status:

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

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

 

Data inquiry:

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

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

 

Start:

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

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

 

Stop:

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

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

 

Reread:

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

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

 

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

 

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

Troubleshoot Form: Broker Item 001 (Broker Service Not Starting)

Posted on by

Title Broker Service not starting.
Category Broker
Date Oct 05, 2011
Handled by Efrat, Rachel.
Relevant Links (link to mantis item, docs, customer correspondance etc.)
Symptoms Broker service failed to start,
No broker log file was written
Applies to license managers FLEXlm, FLEXera FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license mode Floating licenses, Network licenses, Concurrent licenses
Observed during investigation Error when attempting to run the broker service via command line.
Trouble shoot process 1. Run the Broker as a Java application (Not a service) from a command line, to establish whether the problem is in the application or just with running the service:
- Succeeded.
2. Check the registry for the required key.
- Failed.
3. Import the key.
Solution Fo

Symptom

Observed

Run net start “OpenLM Broker” on the command line.
The following error was observed

In this case

-NO log file is created, since the service does not run the application.

-NOR errors in the EventViewer

Trouble shooting:

  1. Try running the Broker from the command line.

This is running the Broker as a Java application, not as a service.

java -jar “C:\Program Files\OpenLM\OpenLM Broker\OpenLMBroker.jar”

start “C:\Program Files\OpenLM\OpenLM Broker\broker.xml”

 

In this case, this procedure succeeded. This means there is a problem only with the service and not the application.

  1. Check the Registry:

a. Open the registry editor : type regedit in the start command line.

b. Navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OpenLM Broker

c. check that you have a Parameters key, with an Application name.

The value of this name should be:

“C:/Program Files/Java/jdk1.6.0_25/bin/java.exe” -Xrs -jar “C:\Program Files\OpenLM\OpenLM Broker/OpenLMBroker.jar” start “C:\Program Files\OpenLM\OpenLM Broker/broker.xml”

  1. If this key does not exist, save the following marked text in a .reg file, and import it under key OpenLM Broker:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OpenLM Broker\Parameters]
“Application”=”\”C:/Program Files/Java/jdk1.6.0_25/bin/java.exe\” -Xrs -jar \”C:\\Program Files\\OpenLM\\OpenLM Broker/OpenLMBroker.jar\”  start \”C:\\Program Files\\OpenLM\\OpenLM Broker/broker.xml\”"

OpenLM Version 1.7 Screenshots

Posted on by

EasyAdmin

The EasyAdmin user interface is accessible from any standard internet browser, e.g.:
Mozilla FireFox, Microsoft Internet Explorer, Opera, Apple Safari & Google Chrome.

EasyAdmin Control Panel

The control panel allows users to get system status information in a single glance:

  • License server status.
  • OpenLM Broker status on each license server.
  • General statistics on license on daily and weekly license usage.
  • One-glance status of critical feature over multiple license servers.
  • Alerts system messages.

The control panel features a Windows-like interface that allows easy access and management of Windows on a standard browser interface.

OpenLM EasyAdmin – Licenses window

Start → Management → Licenses

The licenses window lists available licenses, and facilitates management of the organizational assets. A sophisticated sliding filter enables users to filter long lists easily.

OpenLM EasyAdmin supports advanced features like FLEXlm packages (As used by Autodesk that produce Autocad).
License Packages appear as boxed items.

Licenses with an upcoming expiration date are marked with a different color.

OpenLM EasyAdmin – License Servers window

Start → Management → License Servers

OpenLM version 1.7 supports Flexera FLEXlm/FLEXnet, IBM LUM, Sentinel SafeNet HASP, Sentinel SafeNet RMS, Reprise RLM, and DSLS license managers.

The license servers window gives an overview of the monitored license servers:

 

  • ‘LED’ indications show stable (green) or faulty (red) connection between the OpenLM Server and the license server (round) or OpenLM Broker component (rectangle).

  • Basic information regarding the current license usage and license borrowing status for each license manager

  • Start / Stop and Reread action buttons for each license manager.

 

OpenLM EasyAdmin – Active Products Window

Start → Management →  Active Products

The Active Products window lists all currently active sessions by user name, workstation, product & Feature name, start time, etc.

License managers may sometimes label licenses as occupied, when in fact they are idle and wasting expensive resources. The Active products window serves as an interface for authorized system managers to trace idle sessions, and retrieve licenses from any user when necessary.

For more information on Manual and Automatic idle license harvesting, please refer to these Application notes:

Application Note 1020: Manually Removing Licenses Using the EasyAdmin web application
Application Note 1005: Configuring OpenLM to close idle Licenses

OpenLM EasyAdmin Workstations window

Start → Users & Permissions →  Workstations

The Workstations window provides all the information a system administrator needs in order to manage workstations that are accessing licenses.
This information includes:

  • Hostname
  • IP Address
  • Last logged in user
  • Agent version (if applicable)
  • Online (Workstation is online or offline)
  • Idle time (User idle time)
  • Controlled (for supported systems)

OpenLM EasyAdmin – License Activity

Start → Reports → License Activity


The License Activity window is a very powerful tool that enables system administrators and managers to produce sophisticated reports, and track license activity of individual users. It lists all finished session according to User names, Groups name, Host name, IP, Project name, Feature name , usage time, etc.

OpenLM EasyAdmin – Released Licenses window

Start → Reports → Released Licenses

OpenLM is able to save and close idle sessions of certain applications we refer to as extension – supported applications (ESRI Desktop ArcGIS, Autodesk products and Matlab) The Released Licenses window reports all such license release (checked in) instances.

OpenLM EasyAdmin - Denials window

Start → Reports → Denials

OpenLM accumulates reports of license request denials.
It thus provides comprehensive exact information, which is required for establishing a correct license purchasing policy.

OpenLM EasyAdmin – License Usage

Start → Reports → License Usage

The license usage report is an account of peak feature usage per time resolution (minutes / hours / days / weeks). It allows system administrators to compare the actual license usage to the number of available licenses. A smart Filter enables users to build customized lists of licenses and get the accumulated usage on these licenses.

OpenLM EasyAdmin – Groups and Projects Usage

OpenLM enables organization to organize users according to groups and projects, and obtain the total usage time these groups very easily.
This could be done either manually, or by synchronizing the OpenLM database with the organization’s Active directory.
This functionality is often applied in order to implement a license usage charge-back billing policy.

Project Report

Start → Users & Permissions →  Projects Usage

Project reporting enables project-oriented companies to get license usage time according to the active project, as reported by the end user.

Group Report

Start → Users & Permissions →  Group Usage

Group reporting allows managers and system administrators to obtain license usage data according to groups.

 

General Statistics window

Start → Management → General Statistics

 

The general statistics screen gives usage information across the whole organization. This is a general parameter providing statistics over all license servers and licenses. It can only be used as a general measure of efficiency. Monitoring this value from day to day can help system administrators to recognize trends or problems.

Recent hour statistics:

  • The number of unique users of software licenses monitored by OpenLM over the previous (ended) hour.

  • The efficiency figure gives the total usage time in hours as a portion of the total potential work hours of software licenses that have been purchased by the organization.

Daily Statistics:

The daily statistics “Total Users” and “Efficiency” figures are an average of the hourly statistics within the current workday.

 

EasyAdmin Settings

Start → User Settings

The configured preferences in the “User settings” window effect the format of information as it is presented to the User.

Start → Administration

The configuration screens allow users to set their preferences.

Start → Administration → Working Hours

Working hours’ selection effects the statistical information which is calculated and presented to all system users.

 

Products / Packages window

Start → Administration → Products / Packages

The “Products/Packages” window enables users to define a meaningful product name to be displayed alongside a feature name.

It also facilitates the organization of licensed features in packages.

For more information on these capabilities, please refer to

Application Note 1022: Products and Packaged licenses in OpenLM

 

OpenLM Agent

The end user tool of OpenLM system improves license availability, empowers the user and provides advanced functionality.

OpenLM Agent functionality:

  1. Query  license manager status (and check who is using the license).
  2. Open documents that were closed by OpenLM (only supported for dedicated system like ESRI Desktop ArcGIS).
  3. Allows the user to set the active project (when projects are active).
  4. Gets the LM_PROJECT environment value and sends it to OpenLM Server.
  5. Provides license availability notifications.

OpenLM Agent is shown as an icon on the Windows system tray:

 The blue and white icon indicates connectivity to OpenLM Server.

 The grey icon indicates no connectivity to OpenLM Server.

 

OpenLM Agent - License Usage Information

The License Usage Information window is available to the end user.
The ability to query license availability from the end user workstation is a very important step towards improving license usability.
The license usage window displays the total number of used, borrowed, and available licenses.
Click on a row to get the complete list of active users who are currently drawing on that license.

 

OpenLM Agent – License usage information: “Who has my license ?”

This is what every FLEXlm user wants to know at any specific point in time. Now you can find that information quickly with a single click.

Whoever needs the use of that license at a particular time can now call the user who is occupying the license and request that it be released.

This feature on its own has proved to save a considerable amount of time for users and administrators, by facilitating faster access to licenses.

 

OpenLM Agent allows users to see who is currently running the floating license on their station, an important and useful feature for any system that incorporates floating licenses such as:

Autocad, Matlab, ESRI, AVEVA, Cadence, IntelliCAD, MathCAD, Pro-Engineer, Solidworks, and Synopsys.

It is also a powerful tool for systems with extensions, especially when there is a limited number of extensions to go around, and users tend to use them mostly for a short time span.

A click on the any of the users displays the users details as stored in OpenLM Users table.
These tables can be synchronized with an organization’s LDAP database: e.g.: Microsoft Active Directory.

OpenLM Agent – License available notification

When a user is denied a specific license, the OpenLM Server sends a notification to the user once the specific license becomes available again: 

OpenLM Agent – Project selection

OpenLM System also enables end users to choose the active projects:

OpenLM Agent Configuration Form

The OpenLM Agent Configuration form sets and tests the connection to an OpenLM server.
Note – this is the OpenLM server, NOT a license (e.g.: Flexera FLEXnet) server.

The Agent’s logging level may also be set here.
A “Silent Install” option is available for automatic distribution of the OpenLM Agent to all workstations in the network.

OpenLM Active Agent

The OpenLM Active agent boosts organizations’ license usage by actively retrieving idle licenses.
The Active Agent supports many different software products from various vendors, such as:

  • Autodesk software - Autocad, Revit, Electrical, Architecture, Mechanical, Map 3D, MEP, Navisworks etc.
  • ESRI -  ArcGIS  Desktop products: ArcView, ArcEditor, ArcInfo, Network Analyst, 3d Analyst, ArcGIS Data Interoperability, ArcGIS Data Reviewer, ArcGIS Spatial Analyst etc.
  • Matlab

The Extension provides additional functions, such as:

  1. Closing idle sessions when licenses are no longer in use.
  2. One-click reopening of closed projects.

When OpenLM saves and closes an idle session, it alerts the user with a notification message:

A single click on the bubble reopens the project exactly as it was before OpenLM closed it.
Also, right clicking the Active Agent icon, and selecting “Recently Closed Documents” displays all recently closed documents:

Click on one of the recently closed documents to reopen it.

OpenLM Server

The OpenLM Server is the hub component of the OpenLM Utilizer system.
It collects license usage information from various sources and stores it in a relational database.
The OpenLM Server is a Windows service that can manage and monitor multiple license servers, located in different time zones and running on different operating systems (UNIX, Linux, or Windows).

OpenLM Server Configuration Form – License Servers Tab

This tab enables system administrators to effectively configure and manage license servers via the OpenLM Server.

Version 1.7 supports the FLEXlm FLEXnet license manager and additional license servers like IBM LUM, Sentinel SafeNet HASP, Sentinel SafeNet RMS, Reprise RLM, and more.
The OpenLM server supports world-wide license server monitoring; It is important to specify the time zone of each server.
After introducing new license servers, it is recommended to click the “Check” button to verify that the OpenLM server is able to connect to the license server.

Free text display names are attached to each server for better identification.
Fail safe server (Triad configuration) may also be configured on this tab.

OpenLM Server Configuration Form – Advanced Tab

Advanced OpenLM Server settings include:

  • Option file management
  • Translate workstation names to IPs
  • Enable the OpenLM Role based permissions system
  • Logging level
  • miscellaneous.

OpenLM Server Configuration Form – Port settings Tab

The Openlm Server interfaces all other OpenLM peripheral modules via ports, which numbers are defined in this form.

 

OpenLM Server Configuration Form – Active Directory Tab

The OpenLM server can synchronize users and user groups with organizations’ LDAP Database (Microsoft Active Directory).
Group synchronization is complex; OpenLM provides multiple policies for such synchronizations.

OpenLM Server Configuration Form – Notifications Tab

The Notifications tab is extremely important!
These settings allow OpenLM to send error notifications, updates on new releases, and other important messages aimed at improving the license usage.

OpenLM Server Configuration Form – LM tools Tab

The LM tools tab holds the directories in which every license manager commands are located.

 

OpenLM Server Configuration Form – Projects Tab

The Projects tab configures miscellaneous properties OpenLM when working in projects; Logging project information, Minimal project usage time, etc.

 

OpenLM Server Configuration Form – Registration Tab

This tab serves to enter the OpenLM license key, for product registration.


Trouble Shoot Form: Agent Item 001 (Failed to close application via the “Close Application” button)

Posted on by

Title Failed to close application via the “Close Application” button on the “Active Products” window
Category Agent and extensions
Date Mar 01, 2012
Handled by Rachel
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXera FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms AutoCAD application was not closed after clicking the “Close Application” button on the “Active Products” window
Observed during investigation In the OpenLM Server log file: the server reports it “Could not find license id for product <product name>”.
Trouble shoot process 1. Create a role.
2. Assign all the necessary resources, that will allow viewing details, to the new role.
3. Add users as members of this role.
Solution Found (Found/Pending/Known Issue).

 

 

Symptoms

AutoCAD application was not closed after clicking the “Close Application” button on the “Active Products” window.

Some Background…

  • When required to shut down an application, EasyAdmin web application sends the “CloseApplication” request over to the OpenLM server.


  • The OpenLM server writes this Closure request to a table in the OpenLM database, and should receive a ‘Success’ response.


  • The Active Agent requests a periodic update in the “CycleInfo message”. It is informed it should shut down the application.


  • The OpenLM server then searches the look-up table in the database for a match between the required feature (Product) and a process name.


  • The problem is that process names tend to change. This causes the Agent not to recognize the process name, and the application fails to shut down.


Observed during investigation

Currently – there is no method of identifying this problem, other than inspecting the OpenLM Server logs. Please set the OpenLM Server logging level to ‘ALL’ , compress the entire log directory and send it to support@openlm.com.

Solution :

The solution to this issue is to update the OpenLM database, and fix the Look-up table so that the product would point to a correct process name.
This update is done through an XML file, which OpenLM needs to generate. This file should be run in the following way:

1. Get the XML file from OpenLM. Save it to a temporary directory.
2. On the OpenLM server configuration tool, select the ‘Advanced’ tab, and click the “Update products feature table” button. The  ”Update products features” window opens.
3. Click the “Update from file” radio button, and type in the xml file with its full path.
4. Click the ‘Update’ button, ‘Apply’ and ‘restart server’.

See the following image for clarification.

Trouble Shoot Form: EasyAdmin Item 001 (Unable to connect to EasyAdmin)

Posted on by

Title Unable to connect to EasyAdmin
Category EasyAdmin web application
Date Oct 11, 2011
Handled by -
Relevant Links
Applies to license managers FLEXlm, FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer could not connect to EasyAdmin.
Observed during investigation
Trouble shoot process Check web server service running,
Check OpenLM server service running.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the EasyAdmin”. Attempting to open the EasyAdmin web application resulted in the following message box appearing on his screen:

In a similar case, the customer got a different notification:

 Troubleshoot process

This kind of issues is related to services that have stopped and are not currently active. The 1st thing to try is restarting the respective process.

1. Navigate to the windows services: Click Start → Control Panel → System and Security → Administrative Tools → Services. The “Services” window appears.

2. In the first case (“Couldn’t connect to host” message box), it may be an issue of the OpenLM Server service.

2a. Select that OpenLM Server service in the “Services” window.

2b. Right click the OpenLM Server service, and set it to restart – see image below.

2c. Restart the EasyAdmin web application.

3. If the 2nd type message box (“Please Check your Internet connection”) appeared, it may be an issue of the web server service. Restart your web server service (e.g.: LightTPD).

Other steps for troubleshooting:

If restarting the services does not work – here are some other things you may try:

  • Run the EasyAdmin application from the same computer as the OpenLM Server.

  • Make sure that any security components (Firewall) are not blocking communication to the EasyAdmin web application.

  • Temporarily stop the OpenLM Server and OpenLM Broker services. Open the task manager’s processes window. Make sure the computer is not held-up by any other process.

  • Still in the task manager’s processes window, look for the LightTpd process. If there are multiple processes with that name – kill them, and restart the LightTpd service on the services window.

  • Make sure the default HTTP listener port (7019) is kept open. Try a different port (e.g. 7020) on the lighttpd-inc.conf configuration file(C:\Program Files\OpenLM\OpenLM Server\WebServer) . Then restart LightTPD service.

  • Try connecting the proxy to the test page; Select the test page from the ‘Start’ menu (see below). Click the ‘Check’ button. An indication similar to that of the 2nd image below should appear.

  • Try a different web browser.

  • Try erasing the Proxy server logs. These are found in the following positions:

Win 7: C:\ProgramData\OpenLM

XP, Win 2003: C:\Documents and Settings\All Users\Application\OpenLM

Trouble Shoot Form: Broker Item 003 (LUM licenses don’t show up in EasyAdmin)

Posted on by

 

Title LUM licenses don’t show up in EasyAdmin
Category Broker
Date Nov 11, 2011
Handled by
Relevant Links http://bug.openlm.com/view.php?id=225
Applies to license managers LUM
Applies to license model Floating licenses, Network licenses, Concurrent licenses, Node Locked
Symptoms LUM licenses don’t show up in EasyAdmin.
Observed during dubug 1. The Broker was not sending any information to the OpenLM Server
2. The Broker “test connectivity” button clicked: Broker saw the OpenLM Server OK.
Trouble shoot process 1. Upgraded Broker version.
2. Changed the I4BLT.EXE path from the OpenLM folder to one supplied by the application vendor.
Solution Found (Found/Pending/Known Issue)

Symptom

LUM licenses don’t show up in EasyAdmin.

Solution

1. Upgrade the OpenLM Broker on the license server machine. Refer to the Application Note for reference.
2. As part of the OpenLM package, the latest version of the I4BLT.EXE file is supplied. This file may not be inter-operable (version too new) with the licensed application version. If this is the case, please follow these steps:

Changing a single port’s configuration

  1. Open the OpenLM Broker configuration tool.
  2. Select the relevant License server.
  3. Check the “Update to the following path” radio button
  4. Click the “Edit” button. The text box becomes active.
  5. In the “Path” text box, type in the path of the I4BLT.EXE file in the LUM folder, originally supplied by the application vendor.

This configuration change may also be achieved by individually typing the I4BLT.EXE file path in each Broker command text box.

Changing all ports’ configurations

  1. Open the OpenLM Broker configuration tool.
  2. Click the “Advanced Settings” wrench icon. The Advanced settings window opens.
  1. Click the “Edit” button. The text boxes become active.
  2. In the “I4BLT Path” text box, type in the path of the I4BLT.EXE file in the LUM folder, originally supplied by the application vendor.
  1. Select a specific port’s “Commands” list item. The “Commands” window opens.
  1. Check the “Update according to advanced settings” radio button, and click the “Update” button. The I4BLT path of the specific port is changed.
  2. Repeat steps 5 & 6 for all ports.