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.Was this helpful?
Related Articles
When Snow Inventory reaches the license limit, snowpacks are moved to Error folder and data is missing in Snow License Man… 99Number of Views FlexNet Publisher Best Practices in Terms of Performance 10Number of Views Checking for the Existence of Borrowed Licenses 6Number of Views Query Borrow Period From License Server 36Number of Views Providing a License File that Allows Checkouts from Both Old and New Clients 10Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago