Autodesk network to subscription licenses, plan your way

Autodesk is determined to move all its customers from using the network licensing model to a subscription or named user model. It is important that a comprehensive cost/benefit analysis is done before deciding what action to take, even if top management is pressurizing for a resolution to the situation.

While the network model is generally better for most organizations, there is  no one-size-fits-all answer to the dilemma, some companies might even benefit from switching to the named user model.

What would be a good methodology to consider the switch? We could apply a two-stage process.

Stage One, Identify your Baseline.

  1. Know your current maintenance costs.
  2. Count the number of unique users that you currently have
  3. Multiply the subscription cost by the number of users to understand what your annual cost will be.

Compare the price per year. If the subscription cost is higher than the current perpetual cost, refuse to upgrade. The difference you see now is the MINIMAL amount of money you can save!

If the subscription cost is equal to or lower than the current perpetual cost, move to the next stage that is checking if you currently utilize your license correctly and that you have not been missing out on potential savings.

Based on our experience, depending on the efforts one is willing to invest it is possible to get 100% more usage from the existing license pool, sometimes more. This would mean that you could decrease your licensing costs by 50% or more. In order to achieve this, you will need to have a software tool that will help you to optimize your license usage. The better the software you employ, the higher savings you will achieve.

Stage Two: Identify Where You can Optimize Usage
There are two main areas that require attention:-

  • your license server configuration
  • how both dedicated and network licenses are being utilized

License servers – the more license servers you have, the less optimized your configuration. License server consolidation is one of the most efficient ways to improve access to license pools. In the case of multi-nationals, it is not always possible to consolidate all the servers into a single centralized pool, because the licensing agreements were entered into with regional subsidiaries or partners of Autodesk and they are treated as separate entities. Even so, there will be at least a few consolidations possible, which has additional benefits in that the number of license servers is reduced and the complexity of managing the licenses is reduced as well.

Current License Utilization – Dedicated Licenses

A comprehensive audit of which licenses are being used and by whom is the next step. In the previous step we paid attention to the concurrent license pools. There is a good possibility that there are quite a few dedicated licenses on site. Sometimes granting a user a dedicated license makes sense, where that user spends most of their time using AutoCAD or Revit, for example. What often happens is that a dedicated or named user license was obtained for a short-term need, like a special project, and the user no longer uses it to the extent that a dedicated license is necessary. Going forward, such users can access licenses from the concurrent pool. As you are still evaluating whether subscription licenses will work for you, you should leave these licenses as is for now, bearing in mind the cost savings of dispensing with them.

Current License Utilization – Network Licenses

Once the license pools have been reconfigured, it is time to check what the actual utilization looks like. Data must be gathered on:-

  • Who is consuming the license?
  • On which workstation is it being used?
  • Where there are several software versions, which license is being used?
  • What time of day is the license being used, which aids in understanding usage peaks and troughs?
  • How long is the license session between access and release of the license?

If you are relying on Autodesk’s license manager software, you may find that this information is not readily available to you. This is where a dedicated license management software tool becomes useful. When you want to take the next step and start optimizing usage, the tool will quickly become worth its weight in gold.

However, just by using the basic information you have gathered, you will have identified areas for further investigation, such as:-

  • Should a user have access and why are they using the software? Maybe they just need a viewer to see a drawing, they are not actually drafting or designing
  • Why is the server underutilized?
  • Why are you getting denials when the server is not being heavily utilized?
  • Are users who book out a license for the whole day actually using the tool all day, or is it idle most of the time?
  • Are there users who do not release the software when they are finished, they keep it booked out overnight.

Autodesk’s license manager will definitely not give you all this information. You need a tool like OpenLM’s License Parser to understand what is really happening. Below is an example of reporting on license utilization from one of OpenLM’s customers.

AutoCAD license utilization

 

AutoCAD license utilization at an OpenLM customer

This chart shows how the licenses are utilized realtime. You can see from this graph that, although 70 licenses have been purchased, this could be reduced to 30 licenses without any significant change in quality of service.

First Conclusions

By this stage, you will already have a clearer view on whether subscription licenses are cost-effective for your organization. You might already find that the costs outweigh the benefits. This is even before you have started on your license optimization. You might even have identified that the pros and cons are pretty evenly balanced at this stage. It is premature to decide at this stage. We recommend that you implement some changes that will optimize utilization of your license pool(s) further. Once you have done this, you will get a clear view of your Autodesk license future.

Some Changes that will Reduce License Waste

The changes described below require targeted reporting to implement them. You will not be able to extract this data from your Autodesk license manager. The cost savings that you will achieve will more than pay for good license management software that is written to satisfy the customer’s needs rather than the vendor’s requirements.

Introduce Chargebacks

If you do not charge licensing costs back to the respective business units that use the licenses, even your best managers are pretty relaxed about usage. Start charging back to cost centers and see how things change. The license costs will affect the bottom line for most managers, and they will start monitoring usage and cutting down on unnecessary use. You will be able to make this easier for them by providing reporting on idle licenses within their cost centre, which is part of the next change.

Actively Manage Idle Licenses

If you have not been able to manage idle licenses before, you will find that most users are very lax about checking a license back when they are not using it. You need reporting that will alert you to idle licenses. You can either “harvest” these licenses manually, or automate harvesting to occur after a certain elapsed number of idle minutes. Below are several reports available in OpenLM on idle licensing, from selected customer sites.

 idle licenses

List of idle licenses and elapsed time

It is easy to see from the display above which licenses need to be reclaimed. You also have the option to close the application or just remove the license. It may occur that you have a peak period and licenses are in short supply. You may decide to close the licenses for a low priority group to free them for another group who have top priority. However, this is not necessary in this case; here are 10 licenses you can harvest right away:-

 

license idle for over an hour

Licenses that have been idle for over an hour

You can even interrogate usage on a per license basis. Here is an example below.

interrogate license usage
The effect of harvesting is that your actual licensing utilization will drop quite dramatically. You will now be getting a far more accurate picture of your Autodesk license requirements. By now you should have discovered that you have more network licenses than you need for the actual current usage, like our customers who had 70 licenses but only needed 30. You might even have discovered “shelf” licenses, licenses that are completely unused, but you are still renewing the license and maintenance agreements for them. You will also have identified serial offenders who “hog” licenses and can apply some change management.

You are now ready to make an evaluation of whether you should move to Autodesk subscription licenses or not.

Will Subscription Licenses Work for Us? Some Assumptions

  1. There is huge industry pushback on the move to subscription licenses. We are not alone.
  2. The different features and products that are available in the subscription do not affect the decision-making process, we are deciding at vendor level.
  3. We would like to keep the same service level we have now.
  4. This was a preliminary exercise. We can optimize even further.
  5. There might be a case for a few subscription licenses (e.g. full-time draughtsmen)

With the data we have collected from our investigation, we can make an informed and objective decision on whether adopting subscription licenses and retiring concurrent licenses will work for us or not.

 network licenses compared to subscription

Graphical analysis of network licenses compared to subscription

  • In the graph above, the blue line is the named license requirement, where each user needs a subscription. This is a one-to-one relationship and creates a 45% angle.
  • The red line is the best case for concurrent license utilization. Some customers have even achieved a ratio of 1:5 licenses/users, but the average is probably 1:1.5
  • The orange line is a more realistic adjusted network license utilization.
  • Both the red and orange lines will be unique to your organization.
  • The saving exists in the area between the blue and the orange lines and is represented by the green arrow.

What are Autodesk offering?

The subscription option is not cheap- the solution is a package with multiple products, which you may not need and is almost €4000 per user. Even the discounted cost per user for 5 years is almost €15 000.

Subscription multi user – This is a subscription option where the user does not log in using his login credentials (user name and password), but logs in via the network and the license manager authenticates him,which is more flexible than the named user alternative.

Keeping your network licenses – Autodesk is increasing your maintenance costs over the next few years, which will erode the value of your concurrent pool – if you decide to continue paying maintenance costs. The original license purchase is a sunk cost and does not affect the calculation.

Market Forecast

Another factor that is vital in your considerations is your projections on your organization’s growth over the next few years.

Optimistic Scenario

The company will continue to perform well, new projects will come in regularly and we will need more licenses to support our growth. We have the following options:-
Subscription – we will need to buy subscription per user. – no other options
Network – squeeze more usage out of the existing license server (possible!!) OR buy some additional subscriptions.

Pessimistic Scenario

Economy is depressed -the company has lost projects, needs to scale back and needs less licenses –
Subscription – In the first three years, giving up any license will cause a loss of the discount benefit on subscriptions. After the first three years, giving up subscriptions has no effect.
Network – can reduce the usability and keep for better times and consider stopping maintenance in the short-term.

Other Considerations

You need some additional modules that are included in the latest industry package or the “one” Autodesk, but not in your current agreement. In this case consider buying a few subscriptions, without changing tour network pool.

What Most Customers have Told us

We stayed with our network agreement and purchased few subscriptions by swapping a few concurrent licenses to take advantage of the discount. We now have the benefit of having a hybrid license environment. We allocated the named licenses to a handful of power users and let the majority of users rely on the network licenses – we still have the benefit of the concurrent pool which costs less because of the licenses we converted to subscription licenses.

Even with a clear view of your actual current usage, this is not an easy decision to make, which is why most customers have hedged their bets by opting for a hybrid model.

Please follow and like us:

Finding a pot of gold in your software license portfolio

A substantial part of the budget of any company is taken up by IT, especially in engineering, healthcare and scientific organizations. For this reason, most CFOs scrutinize any capex or opex emanating from the IT division. One of the recurring costs that is laid out there in black and white will be for software licensing. The CFO will be unhappy about this ever-increasing cost, but regards it as an important part of compliance; after all, he does not want to be subject to a software audit that finds the company has compromised their license agreement and are now subject to a punitive fine. The number of licenses purchased and how efficiently they are used is rightly regarded as the CIO’s responsibility.

The CIO’s Challenge

The CIO, in turn, does his best to optimize license usage, by buying concurrent user licenses where possible and then monitoring that these licenses are used as efficiently as possible. However, if he is relying on the license management software provided by the vendor, the visibility of what is really happening is limited; the software is provided to help the vendor monitor usage, rather than the customer. Some organizations  that have never paid much attention to engineering and scientific software licensing costs, especially where licenses are acquired for every project and those costs are passed on to the customer. In these organizations, the licenses are often not under the control of IT, but are looked after by the relevant engineering department or project.

This does not mean that there are not IT shops who actively monitor and report on their concurrent licenses, but good license management results in demonstrable cost savings, and the CIO will obviously not downplay his success in cost reduction. There will also be readily available reports, which the CFO should take the time to understand.

Are The Cost of Engineering Licenses Often Overlooked?

The CFO is aware of licensing costs. After all the company usually has ERP, accounting and human capital software with which he is closely involved, as well as general office software, such as Microsoft Office, and will probably have several cloud-based applications like SalesForce. For these software products he has a close involvement in the licensing and renewals, but they tend to be on a per-seat or per user basis. This might be why so many CFOs leave money on the table when it comes to engineering software. The CFO will question the acquisition of new hardware, such as a high-spec laptop for the engineering department, but accept that new licenses need to be loaded on to the laptop. The fact that these licenses can cost far more than the laptop is often missed.

What a CFO can do to Mitigate these Costs

Tracking licensing costs for scientific and engineering software is a very labor-intensive task, especially if done manually. A diplomatic first step to get the information required, would be to request a new set of reports that show the number of licenses purchased, in use and the level of their utilization. There will probably be some resistance from the CIO, mainly because these values are very difficult if not impossible to determine using the vendor-supplied software. Any arguments can be countered by conceding that a reasonable budget will be allocated for getting the right software to do the job, but that this must be done as soon as possible. By showing empathy and understanding of the problem, there is no implication that the CIO has neglected to look after his licenses. It might even be the case that he has no control over these licenses, because the engineers buy and manage them directly.

Where this is the case, there may need to be some additional work to bring the license back under IT’s management. Whatever the situation, the reporting will be an eye-opener.

Finding the Money

There are three main sources of unnecessary spending or “waste” on licenses:-

  • unused licenses, or “shelfware”.
  • single-user or named user licenses that are only used occasionally
  • a concurrent or network license pool with poor utilization.

Shelfware. Unused licenses are commonly found where a set of new licenses was procured for a new project, and the project is now completed or the phase of the project where they were needed has passed. What tends to happen with these licenses is that license renewals are entered into without checking that they are needed. These licenses can immediately be dispensed with, you have enough licenses without them.

Single-User Licenses. It is often valid to purchase a single-user license for a resource who uses the software daily and for most of the day. However, there needs to be real justification for retaining them, rather than assigning the user to the concurrent user pool and freeing up the license, to be exchanged for a concurrent license or terminated. Single-user licenses are cheaper, but not if they are not used extensively.

Concurrent Licenses. Concurrent licenses cost more but can be used much more efficiently because users draw them from a pool and (hopefully) return them to the pool when they are finished (good license management software can manage that too by “harvesting” idle licenses). Ensuring that concurrent licenses are used to the maximum is not an overnight job, but the CIO should be able to demonstrate gradual improvement month-by-month once he has the right software to see what is really going on. We have several case studies where customers have used OpenLM to optimize concurrent license usage.

This may seem like an exercise that will result in small savings, but if you take the cost of these licenses into account, some companies have realized over a $1,000,000 by reducing their license overhead. It depends which software you use, but when you consider the price of Catia, Solidworks, Revit or AutoCad, it would be foolish not to get rid of licenses you don’t really need.

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

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

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


Please follow and like us:

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

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