License files and license server debug log parser

[orengabay]

We have launched a new and free service that allows users to parse FLEXlm license files and license server debug log files as produced by the Autodesk license manager (FLEXlm).

OpenLM Online License log parser

The service is provided by OpenLM for free and the site does not show any advertisement.

We are looking forward to receiving your feedback on the new service and to learn how we can improve it.

Thank you,

Oren Gabay

OpenLM

[orengabay]

Hi Duncan, 

Thank you, sorry for the delayed response.

At the current version all license parser can parse several formats, license server log or license files. The formats are:

- FLEXera publisher license files 
- FLEXlm license file
- OpenLM License file
- FLEXera publisher (FLEXlm) debug log file
- RLM (Reprise License Manager) log file
- OpenText (formerly Spicer) log file

The service tries to traslate cryptic license files to "English" that everyone can understand. We are trying to convert license log files to useful information: tables, charts and reports. We are also trying to deprecate occurrences of the same events to a single line and clear information.

Next version (1.6) will add few additional formats and this is what we plan to concentrate on in the near future. We may also try to improve the response layout and provide a better PDF report. 

We are yet sure about the future of this service. It all started as a service to our customers to parse the license files that we provide and evolve to what you currently see. We are actually getting interesting feedback and suggestions from users and will take that into account.

I hope that you will find our service useful, we are looking forward to getting more feedback.

Sincerely,

Oren 

[orengabay]

The new version of all license parser adds support to the following license servers: RLM license manager (Reprise license manager), Sentinel RMS license manager from SafeNet and the LM-X license manager.

The support for the Flexera FLEXnet publisher (FLEXlm) was extended to support the license output format as produced by the LMUTIL lmstat command line interface.

[orengabay]

We continue the development of all license parser and happy to announce version 1.7!

What is new in the OpenLM All License Parser Version 1.7?

The system now only offers HTTPS connection in order to better protect data privacy.

Added support to the DSLS license file and DSLS license server log (Dassault Systèmes).

Grouping error messages to create a clearer and shorter report:

This way error messages that shows many times on the debug log will show only once in all license parser report. Clicking on the time range will show the details messages.

The service is available at: www.alllicenseparser.com

[orengabay]

What is new in the OpenLM All License Parser Version 1.8?

– 0002564: Write the type of the file on the top of the report

– 0002698: Sentiel RMS license file support added

– 0002699: Sentiel RMS usage log support added

– 0002619: LM-X log file support added

– 0002562: improve FLEXlm LMUTIL format reading

– 0002677: when parsing a license file avoid the horizontal scroller

OpenLM All License Parser currently supports eight different license managers and we are working to support more. License Parser team is looking forward to receiving your requests to support additional formats.

Thank you for your feedback.

[orengabay]

OpenLM is proud to announce version 1.9 of  AllLicenseParser.com. This release of the parser focuses on our users feedback as well as many infrastructure improvements.

The main feature of version 1.9 is the ability to sign-up to the service. Signing up allows us to remove the limitation of 10,000 rows to log files.

We continue to support additional formats. This version add support to SlickEdit license log format.SlickEdit is a cross-platform, multi-language editor for programmers that supports concurrent licenses.

We also support the Sentiel Super Pro license manager license manager from safenet and improved the support for the LM-X log file format.

We would like to thank AllLicenseParser users for using the service and for spreading the word. We are looking forward to receiving your feedback and requests for additional functionality.

This is the full list of modifications:

- 0002835: [General] LM-X log file summary and other info.

- 0002715: [General] Authentication and user registration.

- 0002845: [General] Ignore garbage when parsing XML files.

- 0002826: [General] Parse SlickEdit stats output.

- 0002834: [General] LM-X log parser failed to recognize file data.

- 0002827: [General] Parser failed on a SlickEdit license log file.

- 0002332: [General] additional information to report summary.

- 0002790: [General] Invalid line: [flexlm_operations, 6504, 1, 0, 0].

- 0002773: [General] Autodesk FlexLM log conflicted with lmutil license info pattern.

- 0002807: [General] Error in the feature grabber.

- 0002700: [General] SLM - Sentinel SuperPro log.

- 0002749: [General] DSLS issues.

- 0002746: [General] OutOfMemoryError: PermGen space.

The service is available at: www.alllicenseparser.com

[dn]

Dear Orengabay,

First of all, thank you for this wonderful parser! It worked like a charm with our debug log file. 

I do have a few questions though. The way that the FlexLM describes its logging functionality is a bit unclear - other than the debug log is there a different type of log that you can set up, one that will provide even more detailed or acurate information? This leads to my second, more 'personal' to OpenLM question.

Is there enough information in the log file, or is the information provided structure in such a way as to provide you with the ability to extract the licence load per given time segment and maybe represent it in a graphical form of some way. The information we are after boils down to this:

• how often do we max out our licence pool;
• for how long do are working on maximum capacity.

You can see where this questions are coming from. Also, if there is a way for external contribution of any kind, please let me know. I have actually started doing the same sort of parser myself and midway through I stumbeled on OpenLM when reading on related information. 

Thank you for your nobel effort, I think the result is beautiful and handy!

Oh, and one more thing that you might want to check for - when you (your office) is running both 2014 and 2015 and even 2013 packages at the same time, the manager will first spit out the unbrella product code (85787BDSPRM_F) - Autodesk Building Design Suite Premium Package and then the actual service (86238BDSPRM_2015_0F) - Autodesk Building Design Suite Premium 2015. As it is right now, the parser will count them as two separate licences being used. I think, the lines containig 85787BDSPRM_F should be ommited for the purposes of licence usage analysis. Hope that makes sense.

Best regards,

Deyan 

[orengabay]

Hi Deyan, 

Thanks for your feedback, please check my response inline

---

dn wrote:

Dear Orengabay,

First of all, thank you for this wonderful parser! It worked like a charm with our debug log file. 

I do have a few questions though. The way that the FlexLM describes its logging functionality is a bit unclear - other than the debug log is there a different type of log that you can set up, one that will provide even more detailed or acurate information?

Yes, FLEXlm also writes another log file called report log. This file is binary encrypted. It contains more detailed information, for example, IP address for each session and projects as reported by users. We can't parse this file. In our software, OpenLM, we apply an alternative methods to provide IP and project information.

This leads to my second, more 'personal' to OpenLM question.

Is there enough information in the log file, or is the information provided structure in such a way as to provide you with the ability to extract the licence load per given time segment and maybe represent it in a graphical form of some way. The information we are after boils down to this:

• how often do we max out our licence pool;
• for how long do are working on maximum capacity.

Yes, the information exists and we are looking into providing additional information in future releases.

You can see where this questions are coming from. Also, if there is a way for external contribution of any kind, please let me know. I have actually started doing the same sort of parser myself and midway through I stumbeled on OpenLM when reading on related information. 

Thank you for your nobel effort, I think the result is beautiful and handy!

Thank you!

Oh, and one more thing that you might want to check for - when you (your office) is running both 2014 and 2015 and even 2013 packages at the same time, the manager will first spit out the unbrella product code (85787BDSPRM_F) - Autodesk Building Design Suite Premium Package and then the actual service (86238BDSPRM_2015_0F) - Autodesk Building Design Suite Premium 2015. As it is right now, the parser will count them as two separate licences being used. I think, the lines containig 85787BDSPRM_F should be ommited for the purposes of licence usage analysis. Hope that makes sense.

In OpenLM software the user can easily filter to see the package or the individutal features. The parser interface/report is designed to be more simple so we report everything. I think that in some cases it make sense to look on the package usage and in others you need to check the individual feature. We will look into this in future versions.

Thank you for taking the time to check the software and to send feedback, we appreciate it.

Oren 

Best regards,

Deyan 

---

[dn]

Thank you for your reply!

Once again, thank you for your work.

[PHILLIPC]

serial number xxx-xxxxxxxx` old number up datedto 382-xxxxxxxx

old subscriptiom number `1-acl3pou

subscription number 110000xxxxxx

subscription number 110000xxxxxx

Edited by
Discussion_Admin

[jessica.t]

Hello all!

For anyone who requires direct licensing assistance, please contact the Activation and Registration team through our Contact Us page. Please be sure to select a sub-topic at the bottom of the page so that the contact options become visible.

Thanks!

[orengabay]

Benchmarks are a new and existing feature of OpenLM Online license parser. This functionality allows users to compare their license usage performance with the average performance of other users that have also used OpenLM Online parser.

The statistics is collected anonymously per vendor so provides a realistic benchmark to compare to. This is important since the usage pattern may be very different between industries. For example, CAD sessions are usually long compared to EDA software that can execute a scenario in few minutes.

Currently we have implemented 4 measures:

Average Session Duration.

Denials Per hour.

%usage: Usage rate relative the number of licenses.

Daily Session per user.

We collect the statistical data from files uploaded to OpenLM and store the stats, not the original information that is deleted after processing. The more files will be processed, the more accurate and valuable benchmark statistics we will be able to provide.

[orengabay]

We already announced the benchmark functionality that allows users of Autodeak software to compare their license utilization to other companies. We have learnd a lot from the initial version and now after a redesign, we did it better. Please try it!

Initially you will get charts that looks like this:

As you can see the system is showing the the benchmark for one of the features in the file, in this case, for Design Suite Standard. Since this is the first sample that the system has, the benchmark is equal to the actual score of the first sample. After processing more files, the system will show more significant results allong with the number of samples and the standard diviation. 

We are looking forward to get your feedback on this new functionality.

[orengabay]

Information starts to built up in the benchmark database, following an example based on 20 samples. Help us collect more information and we will share it with you

[orengabay]

We are very happy to announce version 1.13 of OpenLM License Parser. www.alllicenseparser.com

The main new functionality in this new version is:

- Better FlexLM Debug Log date handling.

- SeisWare CSV log file format supported

- LS-DYNA LSTC log and license file formats supported.

- Closed sessions are in a grid

- Added registration capability

- Fix for false detection of a tab separated data such as lmutil file format

Registration to the system now allows user to upload very big debug log file, removing the limitation of 10,000 rows. It also allows users to compare their performance to a benchmark data that we collect.

An example of benchmark data for the MATLAB feature from Matworks:

The image shows date that is based on about 21 samples. We invite users to upload their files so more statistical information will be collected. Note that your original files are automatically deleted after processing, only accumulated statistical information is preserved.

[orengabay]

A new version 1.14 has been released. Many small bug fixes and modifications to existing reports. 

We are looking forward to receive some feedback. 

[orengabay]

It's been a while since the last update and now we are out with a new system and a lot of new functionality.

This new version is milestone version with total redesign of the interface and reports. Now you can parse huge files after registering to the service. We keep your privicy and delete the uploaded files automatically.

What’s new in OpenLM Parser Version 1.15?

New layout and support for mobile devices.
Sign-in on main page from inside the report.
Move Vendors to the summary area.
Each chart is to be displayed on its own page.
SeisWare csv file not parsing.

Please try it our www.alllicenseparser.com and send us some feedback. 

Scrrenshot: