This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Re: How is a borrowed license stored?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 17, 2009
10:37 AM
How is a borrowed license stored?
How does a client know that it has a borrowed license? Is there something being set in the registry? Or is it being stored in some other fashion?
I would like to know because I would like to remove whatever is there as lm_borrow_return does not seem to work properly with 11.6.1. It returns the borrowed license, but does not update the client accordingly. The client thinks it has a node-locked license.
This is bad because our application cannot support returning borrowed licenses from its GUI interface. A user could borrow a license on a client...return it...and then that client would have a license for a maximum of 2 weeks. This could be repeated indefinitely.
We've ripped out borrow returns from our application. Instead, the user has to use lmborrow.exe or lmtools. This is really inconvenient.
I would like to know because I would like to remove whatever is there as lm_borrow_return does not seem to work properly with 11.6.1. It returns the borrowed license, but does not update the client accordingly. The client thinks it has a node-locked license.
This is bad because our application cannot support returning borrowed licenses from its GUI interface. A user could borrow a license on a client...return it...and then that client would have a license for a maximum of 2 weeks. This could be repeated indefinitely.
We've ripped out borrow returns from our application. Instead, the user has to use lmborrow.exe or lmtools. This is really inconvenient.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 19, 2009
08:43 AM
The borrow data for the client is in the registry. Look in HKEY_CURRENT_USER\Software\FLEXlm License Manager\Borrow.
We've found two cases where the returns did not update the client data. The first was if the feature name has a '-' in it. The second was if when doing the return you used a different case from when you did the borrow. The checkout is actually case insensitive but apparently the borrow and return are case sensitive.
We've found two cases where the returns did not update the client data. The first was if the feature name has a '-' in it. The second was if when doing the return you used a different case from when you did the borrow. The checkout is actually case insensitive but apparently the borrow and return are case sensitive.