OpenLM Maintenance Release Version 1.8.1.29

OpenLM Server version 1.8.1.29

OpenLM Server version 1.8.1.29 is a maintenance release to version 1.8. It contains some bug fixes to problems found in previous versions and enhancements. We  recommend that users of previous 1.8 versions to whom these problems may be relevant upgrade their system to this version.

Upgrading the OpenLM Server

In order to upgrade to version 1.8.1.29:

1. Stop the OpenLM Server service

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

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

4. Install the new version on top of the existing one.

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

What’s new in OpenLM Server 1.8.1.29 (Feb 06, 2014) and its close predecessors

1. Issue #1564: [OpenLM Server] HASP unlimited – show total licenses.

2. Issue #1562: [OpenLM Server] License overuse report.

3. Issue #1565: “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full”

OpenLM Server 1.8.1.28 (Jan 29, 2014)

4. Issue #1531: [OpenLM Server] OpenLM Server configuration form will not start.

5. Issue #1502: [OpenLM Alerts] Alert does not work for feature usage threshold > 0.

OpenLM Broker complementary version 1.8.2.2

This Broker version is complementary to the 1.8.1.29 OpenLM Server version.

6. Issue #1563: [Config Tool] hide “HASP” option in Broker configuration tool.

7. Issue #1521: [Config Tool] Broker manual configuration of multiple license files (“separate by colon”) does not work.

OpenLM Agent version 1.8.1.9

8.  Issue #1401: Matlab extension installed, but not activated.

Please follow and like us:

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

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 (0x80131904): 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”).

Please follow and like us:

Trouble Shoot Form: Agent Item 002 (All license usage information on the Agent is blocked)

 

Title License usage reporting information on the Agent is blocked
Category Permissions and Roles.
Date Jul 6, 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 Following the creation of an admin account in the OpenLM Server Configuration, all license usage information on the Agent is blocked
Observed during investigation
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

The customer complained: “Every time I go to add an admin account in the OpenLM Server Configuration it blocks all license usage information on the Agent?  I’d like to password protect the EasyAdmin web application but still allow users to see the license usage through the agent. Is there a way to do this?”

Observed during investigation

An admin account on the OpenLM Server Configuration window was created. This can be done by unchecking, and then rechecking the “Enable permissions” highlighted checkbox. A small dialog box subsequently appears, requiring a name & password for the new user (e.g.: User name: admin, Password: admin).

Troubleshooting

When you enable permissions, users need to be assigned with a set of permissions that will allow them to view license servers’ details

1. Create a role: Login to EasyAdmin with the “admin” account. follow the steps described in the “Creating a new role” section of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

2. Assign resources to the new role: After you save the new role, the “Resources” tab will become enabled. Navigate to that tab. Note that it is assigned with one default resource. Now you need to add all resources that have this name pattern “server_servername” e.g. server_srv1 (where srv1 is the name of the server that you will grant access to). In order to do so, Follow the description in section “Adding resources to a role” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

3. Assign the new role to the “admin” user: In order to do so, Follow the description in section “Assigning roles to a user or group of users” of “OpenLM Roles and Permission Groups based security – Application Note 1006”.

 

Please follow and like us:

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

 

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

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

Trouble Shoot Form: Item 02.002

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

Symptoms

Customer reported failure to import the SQL database to FB.

Trouble shoot process

 

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

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

Please follow and like us:

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

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\””

Please follow and like us:

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

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.

Please follow and like us:

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

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

Please follow and like us:

OpenLM Maintenance Release Version 1.7.1.8

Version 1.7.1.8

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

Upgrading

In order to upgrade to version 1.7.1.8:

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


What’s new in version 1.7.1.8 ?

OpenLM Server:

  1. Changes made to the Readme text, apparent during  the OpenLM Server installation.
  2. EasyAdmin: Fixed User Details for user names with special characters.
  3. Mobile: The OpenLM EasyAdmin Mobile application has been added to the installation files. The Mobile application enables system administrators to keep track of the license management systems, while being out of office.
  4. Working days computing error was fixed.
  5. EasyAdmin: Color selection problem on report charts was fixed.
  6. HASP: Errors in reading certain formats of the HASP license output files were fixed.
Please follow and like us:

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)

Please follow and like us: