Showing posts with label license reporting. Show all posts
Showing posts with label license reporting. Show all posts

Friday, April 11, 2014

JTB FlexReport 8.0 adds Reprise License Manager monitoring

This new version of JTB FlexReport license report solution adds some new functionality to help with your license tracking and solves some other issues:

  • Added support for monitoring of Reprise License Manager (RLM) usage. For RLM monitoring rlmutil.exe is used and is available for download here: http://www.reprisesoftware.com/enduser_kits/end-user-download.php You might need to run the installer and take note of installation folder to find it. Import of RLM license server report log is also available.
  • Added support for monitoring of Venturis (TRICAD) license usage.
  • Added support for monitoring of Ranorex license usage.
  • JTB FlexReport Config has got a large UI update.
  • Email PNG reports automatically added to chart client.
  • More settings available before a report is created on the Report Settings tab in the chart client. These are also use by the auto report functionality.
  • More preset values for date ranges added in the chart client.
  • Time frame is being used for Histogram charts now.
  • <All> and <Unassigned> added to all list boxes in chart client where applicable to make it easier to make selections.
  • Filtering added for lists in the chart client. Example: filter all features containing the text Auto.
  • Improvements and bug fixes for the auto report functions.
  • and much more added and fixed that can be found in the revision history.

Here are the downloads and general upgrade tips.

Previous release: JTB FlexReport 7.4.3

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

About JTB FlexReport: JTB FlexReport from JTB World is a report tool (HTML, chart and list reports) for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS/Sentinel Protection Server/SafeNet Sentinel, LM-X, Solidworks SNL License Manager, T-Systems license manager product LICMAN, Vertex Systems, MathLM (Wolfram Mathematica license manager), RLM (Reprise License Manager), Ranorex, Venturis, Primavera from Oracle or 12D software licensing. With Process Monitor any Windows application like Acrobat, Visio, Bentley MicroStation, single licensed AutoCAD or AutoCAD LT can be reported usage of.

Monday, September 23, 2013

Cascading of AutoCAD 2014 with Product Design Suite 2014

If you use Autodesk Network License Manager and have licenses for both the point product AutoCAD 2014 and Product Design Suite 2014 on the license server but on the user’s machines only Product Design Suite 2014 installed, launching AutoCAD 2014 will take a Product Design Suite 2014 license. Why is that? AutoCAD 2014 shortcut is a vanilla AutoCAD profile of AutoCAD Mechanical 2014. So if if you want to have your users use the cheaper AutoCAD 2014 license instead you will have to also install the point product AutoCAD 2014.

  • Point Product AutoCAD 2014 = This is AutoCAD 2014 only!
  • AutoCAD 2014 in the Product Design Suite 2014 = AutoCAD Mechanical 2014 with Vanilla Profile.
  • AutoCAD Mechanical 2014 = One of the products in the Product Design Suite 2014.

Via Up and Ready

If you want to monitor license or application usage consider JTB FlexReport.

Wednesday, September 18, 2013

FlexNet license manager 11.12

The updated FlexNet (FLEXlm) version (based on Flexera Software’s FlexNet Publisher 2013 R2) has been released and is now available as a public download as well as the updated License Administration Guide.

Here are the news in Version 11.12 as far as I could find. There might be some bug fixes too that not are documented.

License Server Diagnostics in the Debug Log

Enhanced license server diagnostics will now be emitted in the license server debug log. Additional diagnostics are prefixed by “(@lmgrd-SLOG@)” for the lmgrd and “(@<vendor>-SLOG@)” for the Vendor Daemon, facilitating easy grep-like extraction from the debug-log. The Vendor Daemon would emit the additional diagnostics when run with lmgrd or lmadmin. These diagnostics are intended to assist publishers and Flexera diagnose license server issues.
These diagnostics include:

For lmgrd:
Start timestamp, Version, ProcessID, Network Info (IPv4/IPv6 interface, listening port), command-line options, list of license files, whether the license server is running as a windows service.

For Vendor Daemon:
Start timestamp, Version, ProcessID, Network info (IPv4/IPv6 interface, listening port, select timeout of vendor daemon), Vendor daemon name, Options file used, Trusted storage accessed (yes/no), Host name, Virtual/physical environment, (limited) hypervisor info if virtual, Lmbind used (yes/no), #Restarts of vendor daemon since lmgrd startup, #Rereads since vendor daemon (re)start, Last reread time, Reread initiation type (automatic versus lmreread).

Every 4 hours (and at vendor daemon shutdown) the following performance data are logged:
Details of the 10 peak client transactions (including client hostname, user, transaction time, concurrent clients at time of transaction, memory usage (Windows only)), Peak concurrent clients served, High watermark memory usage (Windows only), Transaction time for last 10 transactions.

Some examples from a log:

18:46:56 (lmgrd) Server's System Date and Time: Tue Sep 17 2013 18:46:56 W. Europe Daylight Time
18:46:56 (lmgrd) SLOG: Summary LOG statistics is enabled.

18:46:56 (lmgrd) (@lmgrd-SLOG@) ===============================================
18:46:56 (lmgrd) (@lmgrd-SLOG@) === LMGRD ===
18:46:56 (lmgrd) (@lmgrd-SLOG@) Start-Date: Tue Sep 17 2013 18:46:56 W. Europe Daylight Time
18:46:56 (lmgrd) (@lmgrd-SLOG@) PID: 6868
18:46:56 (lmgrd) (@lmgrd-SLOG@) LMGRD Version: v11.12.0.0 build 136775 x64_n6 ( build 136775 (ipv6))
18:46:56 (lmgrd) (@lmgrd-SLOG@)
18:46:56 (lmgrd) (@lmgrd-SLOG@) === Network Info ===
18:46:56 (lmgrd) (@lmgrd-SLOG@) Socket interface: IPV6
18:46:56 (lmgrd) (@lmgrd-SLOG@) Listening port: 27000
18:46:56 (lmgrd) (@lmgrd-SLOG@)
18:46:56 (lmgrd) (@lmgrd-SLOG@) === Startup Info ===
18:46:56 (lmgrd) (@lmgrd-SLOG@) Is LS run as a service: Yes
18:46:56 (lmgrd) (@lmgrd-SLOG@) Server Configuration: Single Server
18:46:56 (lmgrd) (@lmgrd-SLOG@) Command-line options used at LS startup: -c C:\Program Files\Autodesk\Autodesk Network License Manager\Autodesk2014.lic -l C:\Program Files\Autodesk\Autodesk Network License Manager\autodesk.log -z -s
18:46:56 (lmgrd) (@lmgrd-SLOG@) License file(s) used:  C:\Program Files\Autodesk\Autodesk Network License Manager\Autodesk2014.lic
18:46:56 (lmgrd) (@lmgrd-SLOG@) ===============================================

lmgrd.exe, lmutil.exe and lmtools.exe are all version 11.12 now. It might take some time before vendors start supporting this new version.

Previous FlexNet 11.11.1 described.

JTB World’s JTB FlexReport license monitoring tool has been tested with and supports this new version.

Tuesday, August 20, 2013

JTB FlexReport 7.4.3

This new version of JTB FlexReport license report solution adds some new functionality to help with your license tracking and solves some other issues:

  • Added support for Sentinel Protection Server logs. Available on the SLM tab in JTB FlexReport Config>Properties.
  • JTB FlexReport Detailed Reports added option to include or not include duplicates (for example with Process Monitor data when a user runs two or more sessions of a program at the same time you might want to not included duplicates). Also available as separate download. Direct link here.
  • Issues with the reports using these combinations are fixed: Feature Group-Server–Host Group and Features-Server Group-Host Group.
  • Discrepancy report bug fixed where some of the data ended up in wrong column.
  • Added a workaround for a rare bug in lmutil.exe that could cause incorrect usage. This is used when taking FlexNet usage snapshots.
  • Fixed a problem with Wildcard processing.
  • Fixed an error with Sentinel parsing: "Error in ProcessSentinel inner".
  • Fixed SLM parser to handle logs where the first rows in the log include LM_SERVER as user name, something that can happen if the log is started while there are users having licenses checked out. This could result in reports showing too much usage. If you have this problem you either need to filter out the SLM features in the tables tblUserDetailedLog and tblUserDetailedLogPrev and delete them or if you have MS Access as database, JTB FlexReport Database Administration.exe can be used, select the SLM features, specify a date range that is a bit larger than the existing data and then delete them. Alternatively start with a new database.

Here are the downloads and general upgrade tips.

Previous release: JTB FlexReport 7.4.2

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

About JTB FlexReport: JTB FlexReport from JTB World is a report tool for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS/Sentinel Protection Server/SafeNet Sentinel, LM-X, Solidworks SNL License Manager, T-Systems license manager product LICMAN, Vertex Systems, MathLM (Wolfram Mathematica license manager), Primavera from Oracle or 12D software licensing. With Process Monitor any Windows application like Acrobat, Visio, Bentley MicroStation, single licensed AutoCAD or AutoCAD LT can be reported usage of.

Chart report on how many hours users have been using a feature.

Wednesday, June 26, 2013

JTB FlexReport 7.4.2

This new version of JTB FlexReport license report solution solves the following issues:

  • Fixed an issue with the Get Feature Descriptions in JTB FlexReport Config where it just did not work to get the descriptions.
  • Fixed a bug in the Access database table tblAppName that causes feature and description to be padded with up to 255 spaces causing among other things issues with some of the reports. Running JTB FlexReport as normal after upgrading to 7.4.2 on a problematic database will automatically fix the issue.

Note that it is only JTB FlexReport Core that is updated to 7.4.2. Uninstall existing JTB FlexReport Core and install the new one. Here are the downloads and upgrade tips.

If you use SQL Server there is no need to upgrade between 7.4.1 and 7.4.2.

Previous release: JTB FlexReport 7.4.1

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

Monday, June 10, 2013

JTB FlexReport 7.4.1

JTB FlexReport license and application usage monitoring tool has got some bugs squashed in version 7.4.1. No new features are added. You may see it as a service pack 1 for version 7.4. See the revision history for what’s been fixed. Here are the downloads and upgrade tips.

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

Friday, May 31, 2013

Autodesk Robot Structural Analysis Professional 2014 network license

RSA 2013 to RSA 2014 Pro network license issue

Autodesk customers already owning Autodesk® Robot™ Structural Analysis 2013 will be automatically upgraded to Autodesk® Robot™ Structural Analysis Professional 2014.
For the network installations under subscription, as usual once upgraded, you will need to get a new license file. The new license file will be valid for the current and prior 3 version of the product but, this concerns the Professional versions only.
In fact, if you previously had an Autodesk® Robot™ Structural Analysis 2013 network license, you will not be able to get a license from the new file.
You have to request a combined file that integrates both the 2014 Professional and the 2013 (http://www.autodesk.com/licensesupport).
Note: combining the files that you own won’t work as they have different issue dates.

If you upgraded from Autodesk® Robot™ Structural Analysis 2013 Professional version everything is fine with the new license file.

Via Up and Ready’s post.

For more about Autodesk Network License Manager (FlexNet) and usage reporting using JTB FlexReport.

Tuesday, May 14, 2013

JTB FlexReport 7.4 released

Software usage and monitoring product JTB FlexReport has been updated to version 7.4.

Downloads here. See also the Upgrade tips. Customers with maintenance have access to this release at no extra cost.

Main news are:

  • Added feature description download button to JTB FlexReport Config>Features. Descriptions are taken from this FlexNet features code page that has been updated with Autodesk’s 2014 products.
  • Edit functionality for auto report settings.

But there are much more, see the revision history for more details on this release.

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

About JTB FlexReport: JTB FlexReport from JTB World is a report and monitoring tool for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS, LM-X, Solidworks SNL License Manager, T-Systems license manager product LICMAN, Vertex Systems, MathLM (Mathematica), Primavera from Oracle or 12D software licensing. With Process Monitor any Windows application like Acrobat, Visio, Bentley MicroStation, single licensed AutoCAD or AutoCAD LT can be reported usage of.

See also: Autodesk Network License Manager downloads and Software Vendor Audits are Increasing as well as the guide to the Network License Manager for FlexNet/FLEXlm in general and Autodesk licensing in particular as well as our freeware JTB FlexReport LT.

Tuesday, March 26, 2013

Autodesk Network License Manager downloads for 2014 product line

Autodesk IPv4 Network License Manager for Windows is found here and Autodesk IPv6 Network License Manager for Windows is found here. Supported operating systems are:
Microsoft Windows Server 2008 and 2008 R2 32-bit and 64-bit
Microsoft Windows Server 2012 32-bit and 64-bit
Windows 7 32-bit and 64-bit
Windows 8 32-bit and 64-bit

FlexNet version and version of all .exe files is 11.11.

Autodesk IPv6 Network License Manager for Windows supports mixed IPv4/IPv6 and IPv6-only environments. It does not support network license checkouts in an IPv4-only environment.

If you have multiple servers you can install on one of them and then grab lmtools.exe, lmutil.exe, lmgrd.exe, and adskflex.exe and copy to the others, just stop and start the FlexNet services in between.

Upgrade your license servers if you plan to support Autodesk’s 2014 products.

JTB FlexReport fully supports Autodesk Network License Manager and usage monitoring of all products licensed with FlexNet including version FlexNet 11.11.

For the FlexNet (FLEXlm) executables there is a newer version available FlexNet 11.11.1.

Tuesday, November 27, 2012

Autodesk University 2012 #AU2012

Autodesk University 2012 is at Mandalay Bay in Las Vegas, November 27-29, 2012. If you could not attend at the location there is AU Virtual so you can watch classes on demand. Live Streaming of Keynote Address and Innovation Forums will start today at 8 a.m. PST.

My class Autodesk® Network License Manager from last year is still available online if you want to learn about this topic. Also available on YouTube and on the Autodesk Network License Manager page.

Friday, October 26, 2012

JTB FlexReport 7.3 Released

The license usage report solution JTB FlexReport has been updated to version 7.3.

Downloads here. See also the Upgrade tips. Customers with maintenance have access to this release at no extra cost.

See the revision history for more details on this release.

Windows 8 and Windows Server 2012 are the new supported operating systems.

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

About JTB FlexReport: JTB FlexReport from JTB World is a report and monitoring tool for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS, LM-X, Solidworks SNL License Manager, T-Systems license manager product LICMAN, Vertex Systems, MathLM (Mathematica), Primavera from Oracle or 12D software licensing. With Process Monitor any Windows application like Acrobat, Visio, Bentley MicroStation, single licensed AutoCAD or AutoCAD LT can be reported usage of.

See also: Autodesk Network License Manager for 2013 products and Software Vendor Audits are Increasing as well as the guide to Autodesk Network License Manager (FlexNet).

Wednesday, October 10, 2012

All about FlexNet License Borrowing

Some FlexNet/FLEXlm enabled products support license borrowing. Some of the below apply only to Autodesk products but most applies to other FlexEnabled applications too.

What is License Borrowing?

License Borrowing allows users to borrow a product license from the network license server to use the product for a specified time even if the computer is not connected to the network. When a license is borrowed, one license less is available for other users. The license is automatically returned to the license server at the end of the day on the return date set when the license was borrowed. The user can return a license early but that must be done when connected to the network license server and be done from the same user and computer that initially borrowed the license. A borrowed license cannot be returned earlier from the license server. The maximum borrowing period can be different from software to software but can be limited by editing the options file.

Most network licensed Autodesk products allow you to use the software while temporarily disconnected from your company's network, such as when you are on business trip or working at a remote location. Unless 6 months are needed set as low limit as possible to avoid licenses from being orphaned, something that can happen if a laptop is stolen during a trip.

Because network licenses are more expensive than single licenses make sure users don’t borrow licenses just to be sure they have a license all the time. Make sure users return the borrowed license as soon as they don’t need it any more. JTB FlexReport has reports that helps to identify users that are borrowing licenses while still connected to the network.

Autodesk product licenses do not support the Borrowing tab in LMTOOLS. This tab exists to support other products that use FlexNet.

You can upgrade FlexNet even if licenses are borrowed. It is possible to release licenses early to the updated FlexNet server.

How to can I Borrow a License?

In AutoCAD it is found in the Tools menu > License Borrowing > Borrow License but for some other products it is hidden in Help>About>Product Information dialog box and then you can select License borrow.

BORROWLICENSE command is another option that can be used in for example AutoCAD.

For non-Autodesk products to initiate borrowing, the end user of the FlexEnabled application sets the borrow period by running lmborrow from the command line or through lmtools on the FlexEnabled client machine. It is also possible to set the LM_BORROW environment variable directly.

When does the Borrowed License Expire?

If you don't remember when a license expires, you can check the date by placing your cursor over the Borrowing icon in your Autodesk product's status tray (does not work in all products) or by clicking Help > About and consulting the Product License Information dialog box. When the borrowing period expires, the borrowed license is automatically returned to the license server at the end of the day on the return date you set when you borrow the license. When your computer is reconnected to the network, you can run your Autodesk product from the network or borrow a license again. See also below under “How to Find out what Users are Borrowing a License?”.

For non-Autodesk products end users can issue the following commands to display the status of licenses (vendor, feature name, and expiration date) currently borrowed by their FlexEnabled application. From the FlexEnabled client machine, enter the following command: lmborrow -status

How can a License be Returned Early?

Borrowed licenses can only be returned early from within the application that they were borrowed and when connected to the network license server. Borrowed licenses cannot be returned early from LMTOOLS for Autodesk licenses.

Access to the command varies by product, and includes one or more of the following options:
■ Click Tools menu ➤ License Borrowing ➤ Return License Early.
■ Click Help menu ➤ About ➤ Product Information or Product License Information. In the Product License Information dialog box, click Return License, and then click Yes.
■ In the status tray, right-click the License Borrowing icon. Click Return License Early.

RETURNLICENSE command is another option that can be used in for example AutoCAD.

For non-Autodesk products end users of the FlexEnabled application return a borrowed license early this way:
1. Reconnect the FlexEnabled client to the network.
2. From the FlexEnabled client machine, issue the following command:
lmborrow -return [-fqdn][-c license_file_list] [-d display] feature

argument -fqdn: Directs lmborrow to access the borrowing system using its fully qualified host name.Use this option if the license was borrowed based on the fully qualified host name,rather than the relative distinguished name. Use lmstat to determine the format of the host name used when the license was borrowed.

argument -c license_file_list: Use the specified license files. In some configurations, the license file needs to be specified in order to return the license file early.

argument -d display: Used to specify the display from which the borrow was initiated. Required if your current display is different than what was used to initiate the borrow.
On Windows, it is the system name or, in the case of a terminal server environment, the
terminal server client name. On UNIX, it is in the form /dev/ttyxx or the X-Display name.

argument feature: The name of the borrowed feature to be returned early. Use lmborrow -status to get a list of borrowed feature names.

End users can clear the LM_BORROW setting to stop licenses from being borrowed until borrowing is initiated again. For example, users might run lmborrow -clear after they have borrowed licenses for features that are used offline if—before disconnecting from the network—they want to run an application that checks out additional features, served by that vendor name, that are not meant to be borrowed. Clearing LM_BORROW does not change the status for already borrowed licenses. End users can remove expired borrowed licenses from their FlexEnabled client machine using lmborrow -purge.

How is Borrowing Defined in the License File?

In the license file below the INCREMENT line there can be a BORROW parameter. If it says BORROW=4320, the maximum period that licenses can be borrowed is 4320 hours (180 days), unless otherwise noted. The default borrow period is 168 hours, or one
week.License borrowing is disabled when this parameter is absent in the license file. Example:
INCREMENT 57600ACD_2009_0F adskflex 1.000 permanent 5 \
    VENDOR_STRING=commercial:permanent BORROW=4320 SUPERSEDE \

How to Find out what Users are Borrowing a License?

LMTOOLS>Server Status or the LMSTAT argument of LMUTIL can be used to perform a status enquiry that will show if a license is borrowed. Linger is a value that indicates the original borrow period in seconds. To convert value to days, divide the linger value by 86400.

Row showing a borrowed license:
    jtb PC-HP PC-HP (v1.0) (PC-HP/27000 101), start Sat 11/5 12:36 (linger: 40980)

Normally it can be calculated when the borrowed license expires by using the start date (checked out date and time) and the linger value but if the license server or service is restarted the start date will change and thus give an incorrect expire date.

JTB FlexReport and the freeware JTB FlexReport LT comes with a HTML report that will show the information like this:
License server status: 27000@server1
AutoCAD 2013: 21 licenses  16 in use.
user6@c1547 Checked out license at 2012-04-26 21:24 Hours used: 36:01 * (Borrowed until 2012-10-27 06:25)

Configure License Borrowing with the Options File

AutoCAD 2004 and AutoCAD 2005 maximum borrowing period is 720 hours (30 days).

AutoCAD 2006 up to AutoCAD 2012 maximum borrowing period is 4320 hours (180 days).

The absolute maximum borrowing period is determined by the BORROW=statement in the license file increment for the product. This cannot be amended.

If the license file has a package increment use both Product and Package feature codes.

Limiting borrowing

You can specify a number of specific licenses that cannot be borrowed.

BORROW_LOWWATER [productfeature] [count]

The following example blocks license borrowing for 5 AutoCAD 2012 licenses:
BORROW_LOWWATER 85730ACD_2012_0F 5

Limit borrow period

You can specify the maximum duration of time that a specific license can be borrowed for in hours. This value cannot be above the maximum borrow period specified by Autodesk in the product license file. Note! Licenses are borrowed in increments of 24 hours only. Any number that is more than a 24-hour increment is not used. For example, the number 365 would be rounded down to 360 hours, or 15 days.

MAX_BORROW_HOURS [productfeature] [hours]

The following example limits license borrowing of AutoCAD 2012 licenses to 3 days:
MAX_BORROW_HOURS 85730ACD_2012_0F 72

Excluding license borrowing

You can block the ability to borrow specific licenses for a user, computer, group of users or computers, IP address, IP address range or by LM_PROJECT variable association (computer names and user names are case sensitive). Any users, hosts or IP addresses not explicitly excluded will continue to have the ability to borrow licenses.

EXCLUDE_BORROW [productfeature] [type] [name]

The following examples block borrowing of AutoCAD 2012 licenses for a variety of types:
EXCLUDE_BORROW 85730ACD_2012_0F USER smithj
EXCLUDE_BORROW 85730ACD_2012_0F HOST computer1
EXCLUDE_BORROW 85730ACD_2012_0F GROUP EngineeringGroup
EXCLUDE_BORROW 85730ACD_2012_0F HOST_GROUP DraftingDept
EXCLUDE_BORROW 85730ACD_2012_0F INTERNET 192.168.0.100
EXCLUDE_BORROW 85730ACD_2012_0F INTERNET 192.168.0.*
EXCLUDE_BORROW 85730ACD_2012_0F PROJECT CivilProject

Including license borrowing

You can provide the ability to borrow specific licenses for a user, computer, group of users or computers, IP address, IP address range or by LM_PROJECT variable association (computer names and user names are case sensitive).

Note: Any users, hosts or IP addresses not explicitly included will not have the ability to borrow the specified licenses. If you want to block license borrowing for only a few users, you should consider using the EXCLUDE_BORROW syntax above.

INCLUDE_BORROW [productfeature] [type] [name]

The following examples allow borrowing of AutoCAD 2012 licenses for the specified type only:
INCLUDE_BORROW 85730ACD_2012_0F USER smithj
INCLUDE_BORROW 85730ACD_2012_0F HOST computer1
INCLUDE_BORROW 85730ACD_2012_0F GROUP EngineeringGroup
INCLUDE_BORROW 85730ACD_2012_0F HOST_GROUP DraftingDept
INCLUDE_BORROW 85730ACD_2012_0F INTERNET 192.168.0.100
INCLUDE_BORROW 85730ACD_2012_0F INTERNET 192.168.0.*
INCLUDE_BORROW 85730ACD_2012_0F PROJECT CivilProject

What Autodesk says about Interaction with Other License-Borrowing Tools

Using the license-borrowing feature in your Autodesk product is the recommended way to borrow a license. Some third-party borrowing tools may also be available to you, but these tools are not supported or compatible with the license-borrowing feature in your Autodesk product. Other third-party or legacy license-borrowing tools that may be available to you are the Autodesk License-Borrowing utility (shipped with Autodesk products) and the borrowing feature in LMTOOLS utility, a component of the Autodesk Network License Manager on Windows servers. If another license-borrowing tool is active when you attempt to use the license borrowing feature, you should proceed as follows to borrow a license for your Autodesk product:
■ If you run the Autodesk License-Borrowing utility that shipped with your Autodesk product and then turn on the borrowing flag for the Adskflex option or the All option, a license can be borrowed when you start your Autodesk product. However, you cannot return a license until you exit and then restart your Autodesk product.
■ On a Windows server, if borrowing is set in the LMTOOLS utility for all products, you can either use the other tool to borrow licenses for your Autodesk product, or stop the borrowing process in LMTOOLS utility, and then use the license-borrowing feature in your Autodesk product.
■ If borrowing is set in LMTOOLS utility for non-Autodesk products only, you must stop the borrowing process in LMTOOLS utility. You can then use the license-borrowing feature to borrow licenses for your Autodesk product. If you do not stop the borrowing process in LMTOOLS utility, the license borrowing feature will not function.

lmborrow

For non-Autodesk products the lmborrow utility supports the borrowing of those licenses that contain the BORROW attribute. This utility runs on the FlexEnabled client machine that borrows the licenses. The FlexEnabled application end users can use the utility to do the following:
• Initiate borrowing by setting the borrow period
• Clear the borrow period
• Purge expired licenses
• Determine borrow status
• Return a borrowed license early

Problems with network licensing borrowing

You are looking for information about license borrowing or you are experiencing problems with network license borrowing.

Common problems with network license borrowing for AutoCAD-based software are listed below. Try applying these solutions first, and then review further instructions if the problem persists.

  • Unable to run the product after borrowing a license

    You borrowed a license for your Autodesk product. However, when you tried to start the program, you received an error indicating that the license manager could not be found.

    Borrowed network licenses are locked to the workstation machine in a number of ways.

    A borrowed license is stored in the local user profile and is only available to the exact same user that originally borrowed it. Make that your login credentials match those used at the time the license was borrowed. Pay careful attention to the username and login domain to ensure that you are logging in as the same user.

    Note: If the user profile is removed or significantly altered while a license is borrowed, you may lose access to the license for the duration of the borrow period.

    A borrowed license is locked to the network card that was active when the license was borrowed. For example, if a removable (PCMCIA, USB etc) network adapter is used to borrow the license, this device must be present when you run the Autodesk application with that license.

    Note: Some network adapters are disabled by default as part of the power management profile. You should refer to the documentation for your machine and network card for additional information about disabling this feature.

  • Error 1.5.-124 when attempting to return a borrowed license

    When you tried to return a borrowed license from a client workstation, the following error message was displayed:

    License Return Error - Your license cannot be returned. For more information, contact your system administrator. Note: you can still use your borrowed license until (midnight): <Date>. Error: [1.5.-124]

    This error usually indicates that the client and/or license manager have changed in some way since the license was originally borrowed. There is no way to force the early return of a borrowed license. However, the following procedures will often resolve the error.

    Method 1 - Wait out the borrow period

    Depending on how long your license is borrowed and how urgently you need to return it to the network pool, it may be easiest to simply wait out the remainder of the borrow period when the license will be automatically returned. Network administrators might consider implementing an Options file to restrict the maximum borrow period or limit who can borrow licenses so the impact of future borrowing problems can be reduced. Refer to the following solution for details about configuring an Options file. Controlling network license access using an options file.

    Method 2 - Reborrow the license and then return it

    Erase the knowledge of the borrowed license from the client machine, borrow it again, and then try to return it using the procedure below. Note: This procedure resets all borrowed licenses for this user/computer.

    On the client computer, log in as the user who borrowed the license.
    On the Start menu (Windows), click Run (Windows 2000/XP) or Start>Search (Windows Vista).
    Enter regedit, and then click OK.
    In the Registry Editor, navigate to the following registry key:
    HKEY_CURRENT_USER\Software\FLEXlm License Manager\Borrow
    In the Registry Editor, on the File menu, click Export to create a back up of this key.
    Delete this registry key.
    Close the Registry Editor.
    Borrow the license again for the product(s) and version(s) that you could not return.
    Return the license(s) for each product.

  • Forcing the return of a borrowed license

    You borrowed a license and you now want to return it to the server. You were unable to return the license from the client machine. Possible reasons can include:

    Errors when trying to return a borrowed license early
    Deletion or corruption of the user's profile who borrowed the license
    Hard drive failure which renders the operating system inaccessable

    There is no way to force the return of a borrowed license from the FlexLM license manager. Once the borrow period expires the license will be automatically returned to the license server pool.

    Notes: It is strongly recommended that network administrators limit network license borrowing to those users who specifically need to take licenses on the road. It is strongly recommended that administrators set the maximum borrow period to an amount of time that corresponds with how long these users will be away from the license manager. These settings are controlled using an options file. For more information about configuring an options file see the following solution: Controlling network license access using an options file.
    Do not use the Borrowing tab in LMTOOLS with Autodesk product licenses. Doing so can cause additional borrowed licenses to become orphaned from the license manager.

  • Using the Borrowing tab in LMTOOLS
    The Borrowing tab in LMTOOLS is not used with Autodesk products. Using this tab may cause unexpected results (including the potential for lost licenses). The Borrowing tab exists in LMTOOLS to support other vendor's products. While some users have been successful using the Borrow tab in LMTOOLS with Autodesk products, it is not tested or supported and has caused issues for users in the past.
    Borrowed licenses cannot be returned early from LMTOOLS.

If these solutions do not resolve the installation error, the additional tests listed below will help you determine the cause of the problem:

  • If you are experiencing problems returning a license from a client machine, you should make sure that the client machine is still pointing to the correct license manager by setting the ADSKFLEX_LICENSE_FILE environment variable.
  • As a network administrator, consider restricting the maximum borrowing period and/or limiting who in your organization can borrow licenses. These tasks can be performed by implementing an options file on your license manager.

If you worked through the standard troubleshooting steps and were not able to resolve the issue, follow this link for additional technical assistance.

Please collect the following information from your system before requesting technical assistance:

  • Screenshots of any error messages encountered
  • License file currently in use at each license manager
  • Options file in use at each license manager (if applicable)
  • Debug log file in use at each license manager
  • Copy and paste from LMTOOLS > Server Status tab > Perform Status Enquiry

Borrow Errors produced by FlexEnabled applications:
-67 No licenses available to borrow.
-68 License BORROW support not enabled.
-102 A FLEXid borrow error occurred.
-104 Cannot borrow that long.
-117 BORROW failed.
-118 BORROW period expired.
-120 Cannot lmdown the server when licenses are borrowed.
-122 Unable to delete local borrow info.
-123 Returning a borrowed license early is not supported. Contact the publisher for further details.
-124 Error returning borrowed license.
-128 Error, borrowed license doesn't match any known server license.

lmremove

If license lingering is set and lmremove is used to reclaim the license, lmremove starts, but does not override, the license’s linger time.

Suites

Borrowing of Autodesk Suite product licenses: Because of how cascading works, one machine will end up taking multiple different features when the suite is borrowed.

I don’t want to get the License Borrowed dialog box

Do you use a borrowed license and want to prevent the "License Borrowed" message from showing up every single time i start your AutoCAD? If so, look at Close License Borrowed Dialog boxes automatically freeware.

License Borrowed

More

For more information about Autodesk Network License Manager.

JTB World’s JTB FlexReport will show borrowed usage and information in several different reports for both current and historic borrowed licenses.

Thursday, October 4, 2012

JTB FlexReport 7.2 Released

JTB World’s license report solution JTB FlexReport has been updated to version 7.2 and includes mainly some bug fixes as well as a few new features.

Downloads here. See also the Upgrade tips. Customers with maintenance have access to this release at no extra cost.

See the revision history for more details on this release.

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

About JTB FlexReport: JTB FlexReport is a report and monitoring tool for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS, LM-X, Solidworks SNL License Manager, T-Systems license manager product LICMAN, Vertex Systems, MathLM (Mathematica), Primavera from Oracle or 12D software licensing. With Process Monitor any Windows application like Acrobat, Visio, Bentley MicroStation, single licensed AutoCAD or AutoCAD LT can be reported usage of.

See also: JTB FlexReport 7.1 introduces MathLM monitoring, Autodesk Network License Manager for 2013 products and Software Vendor Audits are Increasing as well as the guide to Autodesk Network License Manager (FlexNet).

Friday, September 7, 2012

FlexNet 11.11 downloads available

The updated FlexNet (FLEXlm) version (based on Flexera Software’s FlexNet Publisher Licensing Toolkit 11.11.0) was released in August 2012 and is available as a public download as well as the updated License Administration Guide.

Here are the news in Version 11.11.0
• Support for XenServer in virtualized environments
• New hostid keyword VM_UUID to support binding to a virtual machine on VMware, Microsoft Hyper-V, and XenServer platforms

No words about if there are any bug fixes but if you experienced unknown problems with the license manager it can be worth trying if updating will help.

lmgrd.exe, lmutil.exe and lmtools.exe are all 11.11 now.

Previous FlexNet Version 11.10.1 described.

JTB FlexReport license monitoring tool has been tested with and supports this new version. See also JTB FlexReport 7.1 introduces MathLM monitoring

Monday, August 27, 2012

JTB FlexReport 7.1 introduces MathLM monitoring

JTB World’s license report product JTB FlexReport is updated to version 7.1 and there are some news, performance improvements and a lot of fixes included so it is strongly recommended to upgrade. MathLM license usage reporting is now supported. MathLM (Mathematica license manager) administers licenses for organizations running multiple instances of Wolfram Mathematica with a network license.

Downloads here. See also the Upgrade tips. Customers with maintenance have access to this release at no extra cost.

See the revision history for more details on this release.

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

About JTB FlexReport: JTB FlexReport is a report and monitoring tool for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS, LM-X, Solidworks SNL License Manager, T-Systems license manager product LICMAN, Vertex Systems, MathLM (Mathematica), Primavera from Oracle or 12D software licensing. With Process Monitor any Windows application like Acrobat, Visio, Bentley MicroStation, single licensed AutoCAD or AutoCAD LT can be reported usage of.

See also: JTB FlexReport 7.0 Introduces Automatic Chart Creation, Autodesk Network License Manager for 2013 products and Software Vendor Audits are Increasing as well as the guide to Autodesk Network License Manager (FlexNet).

Tuesday, June 26, 2012

Autodesk's license models are complex and confusing

Gartner’s report, Software Vendor Auditing Trends: What to Watch for and How to Respond (May 23, 2012) contains this snippet about Autodesk network licenses:

Autodesk: “…Autodesk's license models are complex and confusing, particularly the way in which subscription entitlements and prior version rights work… Autodesk products are notoriously difficult to audit and many clients find that their incumbent tools are unable provide the necessary information to demonstrate compliance with negotiated license terms and conditions…” – ref

Cascade Licensing for Autodesk Products explained shows some of this complexity.

Cascading Sequences for Autodesk 2013 Products let you know in what order cascade licensing checks for available licenses in Autodesk 2013 products and here are the Autodesk FlexNet Feature Codes with descriptions that are useful to understand Package licenses and prior version support as well as Prior version support and license usage of Autodesk Suite products.

Many have found JTB World’s JTB FlexReport useful to monitor and audit their Autodesk license usage. There are many different reports that can be generated in chart or list form. There is still room for improvements though. JTB FlexReport supports email notifications when licenses are denied but when cascading is used there will often be denials when the license cascade from one feature to another. Another problem with the cascading is that there is no way from the license server logs to see what actual Autodesk product was started by the user, hopefully Autodesk can do something about this in the future. If it is of interest to know that information we have JTB Process Monitor that will be able to tell if it was AutoCAD or Revit or whatever product being used and how much.

Wednesday, May 16, 2012

Ports for network licenses based on FlexNet

This post should cover all you need to know about FlexNet/FLEXlm ports being used by vendors like Autodesk.

Port 2080 is used for by the vendor daemon, for example adskflex.exe
Port 27000-27009 is used for the lmgrd.exe

The first lines in an FlexNet license file look like this.

SERVER LABSERVER 03D054C0149B
  USE_SERVER 
  VENDOR adskflex port=2080

LABSERVER is the host name of the server where the Network License Manager resides.

03D054C0149B is the Ethernet address/Host ID of the server where the Network License Manager resides.

adskflex is the name of the server-side vendor daemon. In this case Autodesk’s.

2080 is in this example the network port number reserved and assigned for use only by Autodesk products running the Autodesk vendor daemon. Normally there is no need to change this port.

The port lmgrd.exe uses can optionally be changed.

SERVER LABSERVER 03D054C0149B port=27000
USE_SERVER
VENDOR adskflex port=2080

It’s good practice to specify the port for the vendor daemon in the license file. Specifying a port for each vendor if multiple vendors exists on the license server will help to avoid conflicts if the license server is restarted. To keep the port fixed helps if you want to report on it using lmutil.exe or the license report solution JTB FlexReport.

If you have a firewall between the license server(s) and the client computers, you need to open some TCP/IP ports on the server for license-related communication. Open port 2080 for adskflex, and open ports 27000 through 27009 for lmgrd. If these port addresses are restricted by a router or firewall software, users on the remote side of the router will not have access to licenses controlled by the Network License Manager. The Autodesk Network License Manager needs unrestricted access to the two TCP ports used. Ping Firewall rule called "File and Printer Sharing (Echo Request - ICMPv4-In)" might need to be enabled.

When you set up clients to find network licenses it is good practice to include the port otherwise all ports between 27000 and 27009 will be tested until the license server is found and if you have many license servers this can take some time.

Bad example: ADSKFLEX_LICENSE_FILE=@server1; @server2

Good example: ADSKFLEX_LICENSE_FILE=27000@server1;27000@server2

FlexNet debug log can be used to find out what the License Manager and vendor daemon ports being used are.

According to Autodesk’s TS67745: “Note: Specifying a port outside of the 27000-27009 range should be avoided unless the vendor specifies that a particular port outside of the range should be used instead.”

But on the other hand “Do not use the default 27000 TCP port.” according to Potential Security Vulnerability in FlexNet license manager and according to FlexNet Version 11.10.1 download available “Note! For security purposes, best practice is not to use a default port for the license server. Instead, specify a port number outside of the range 27000 through 27009.”

More about Autodesk Network License Manager can be found here and if you want a solution to report on the license usage JTB FlexReport will help.

Monday, May 14, 2012

FlexNet License Server Manager lmgrd.exe Security Vulnerability

FlexNet License Server Manager version 11.9.1 and others earlier have a bug in lmgrd that can cause a stack overflow.

“The server is affected by a classical stack buffer-overflow in the
function that copies the data received after the header in a buffer
smaller than the needeed bytes. … lmadmin is not affected.” Ref. lmgrd advisory that was made public 13 May 2012 by Luigi Auriemma but found already back in 26 Oct 2010.

Recommendation is to make sure to use the latest lmgrd.exe that comes with FlexNet Version 11.10.1 or at least a version newer than 11.9.1.

Related post: Potential Security Vulnerability in FlexNet license manager

To monitor and report on usage of FlexNet based applications use JTB FlexReport.

Wednesday, May 2, 2012

FlexNet Version 11.10.1 download available

The updated FlexNet (FLEXlm) version (based on Flexera Software’s FlexNet Publisher Licensing Toolkit 11.10.1) was released in February 2012 but first now available for public download as well as the updated License Administration Guide.

Here are the news in 11.10.1:

• Full support for Mac OS X 10.7.x
The following features were introduced for trusted-storage-based licensing:
• Support for prepped trusted storage
• Hybrid license information displayed on lmadmin dashboard
• New options keyword (DAEMON_SELECT_TIMEOUT) to support for activations against license servers in bandwidth-restricted environments
• New function flxActTransactionGetResponseXML used to retrieve response XML from online activations

lmgrd.exe version is 11.10.1 and lmutil.exe version is 11.10.1 while lmtools.exe is still version 11.10.

I found this addition in the documentation. “Note • For security purposes, best practice is not to use a default port for the license server. Instead, specify a port number outside of the range 27000 through 27009.” Anyone know why? (Other than what is mentioned in this post Potential Security Vulnerability in FlexNet license manager, but should this not be fixed?)

I tested to use the new lmgrd.exe version with my Autodesk network licenses but when starting the service I get this error below and no log file created. Eventually I found that I had used the 32-bit version of lmgrd.exe while it was the 64-bit version that should have been used.

Flexible License Manager status on Fri 5/4/2012 13:08

[Detecting lmgrd processes...]
License server status: 27000@SERVER
    License file(s) on SERVER: C:\Program Files\Autodesk\Autodesk Network License Manager\Autodesk.lic:

lmgrd is not running: Cannot connect to license server system.
The license server manager (lmgrd) has not been started yet,
the wrong port@host or license file is being used, or the
port or hostname in the license file has been changed.
Server name:   192.168.1.1
License path:  27000@SERVER
FLEXnet Licensing error:-15,10.  System Error: 10061 "WinSock: Connection refused"
For further information, refer to the FLEXnet Licensing documentation,
available at "www.flexerasoftware.com".

JTB FlexReport license monitoring tool has been tested with and support this new version.

Related links:

Autodesk Network License Manager

Instructions on how to Update FlexNet from a Previous Version.

Software Vendor Audits are Increasing

Autodesk Network License Manager for 2013 products

JTB FlexReport 7.0 Introduces Automatic Chart Creation

Monday, April 16, 2012

JTB FlexReport 7.0 Introduces Automatic Chart Creation

JTB FlexReport 7.0 comes with the functionality to schedule creation of license usage charts. One usage of this functionality is to create an intranet web page that always shows the usage from the last 7 days for the main features (products) on your license server. Support for Vertex Systems licensed products is also added.

Downloads here. See also the Upgrade tips. Customers with maintenance have access to this release at no extra cost.

See the revision history for more details on this release.

Here is from the documentation of the chart client.

Auto Reports tab
With this functionality you can have reports automatically created as PNG image files at specified recurrence pattern.
This requires that the JTB FlexReport Auto Chart Service is running.
To set up a report first manually create the report you like to use.


Specify the recurrence pattern if the report should be created on an hourly, daily or monthly basis.
Hourly settings allow a report to be created multiple times per hour.

 
Daily settings allow a report to be created at specified days and time.


Monthly settings allow a report to be created on a monthly basis.


The Settings panel explained.
File Save Path is a path located where the Auto Chart Service is running. You can run this client on any computer but the report file will be created locally on the server. Use Validate Path to ensure it is correct.
If the report should overwrite itself each time use a fixed file name checkbox.
Enter a file name that is the basis for the report file. If fixed file name is not used the file name will have a suffix with the date and time. For example AutoCADperDay (2012-02-13 08.52.12).png where AutoCADperDay is the file name.
Specify also the size for the image.
When ready press Save Settings.


The report will show up on the Report List panel and can also be deleted from there.

JTB FlexReport is a report tool for applications using the FlexNet / FLEXlm (flexlm license manager), IBM LUM (IBM License Use Management), SPLM (Intergraph SmartPlant License Manager), SLM/Sentinel LM/Sentinel RMS, LM-X, Solidworks SNL License Manager, Licman, Primavera from Oracle, Vertex or 12D software licensing as well as any Windows application like Acrobat, Visio, single licensed AutoCAD or AutoCAD LT.

Contact us to get a time limited license file for free. You can try it in your environment with your real data for a few weeks with full functionality.
Full support is provided during trial period.

See also: Autodesk Network License Manager for 2013 products and Software Vendor Audits are Increasing


Some of the latest blog posts

Subscribe to RSS headline updates from:
Powered by FeedBurner