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 Knowledge Base
- :
- Why can't older clients check-out licenses borrowed by newer clients?
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Why can't older clients check-out licenses borrowed by newer clients?
Why can't older clients check-out licenses borrowed by newer clients?
Summary
Why can't older clients check-out licenses borrowed by newer clients?Question
Did something change around FNP 11.14 that causes clients to not be able to use a borrowed license that was borrowed from a newer client? I?m running an 11.14.1.2 server (also reproduced with 11.14.0.1) and borrowed a license using and 11.14.0.1 client. Then when off the network I tried to use an 11.13.1.3 client (which used a checkout version lower than the one used to borrow), but the checkout failed. I can use an 11.14.0.1 client with a lower checkout version and use the borrowed key, so it seems like a version issue between 11.13 and 11.14. When building my vendor daemon I?m adding -bfixed to the lmnewgen call, so this is supposed to work.Answer
Your version of lmcrypt is actually quite old, so there is no version issue here. FNP 11.14.0 changed options available for borrow format of the data that is written in the registry (the key name now has the version number in it). Because of this, the old clients can't read this properly. If you remove the version from the name, the older clients work.Labels (10)
Labels:
-
FlexNet Publisher 2016 (11.14.0)
-
FlexNet Publisher 2016 R1 SP1 (11.14.0.1)
-
FlexNet Publisher 2016 R1 SP2 (11.14.0.2)
-
FlexNet Publisher 2016 R2 (11.14.1)
-
FlexNet Publisher 2016 R2 SP1 (11.14.1.1)
-
FlexNet Publisher 2016 R2 SP2 (11.14.1.2)
-
FlexNet Publisher 2016 R2 SP3 (11.14.1.3)
-
FlexNet Publisher 2017 R1
-
FlexNet Publisher 2018 R1 (11.15.1)
-
Question
0% helpful
(0/1)