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: “Invalid (inconsistent) license key”
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
Feb 04, 2019
11:07 AM
I've recently run into a very strange problem, hoping for an easy solution....
I have a statically linked MFC application using FlexNet publisher. I have no problem making licenses and have never run into any issues. Once the parameters are correct, hostid, expiry date,etc, I can lmcrypt the file and it works as expected. However, recently I've encountered a machine that will not accept a properly configured license file. The application consistently receives the error "Invalid (inconsistent) license key”.
I'm looking for ideas on why I'd receive this error on what should otherwise be a valid license file.
Thanks.
I have a statically linked MFC application using FlexNet publisher. I have no problem making licenses and have never run into any issues. Once the parameters are correct, hostid, expiry date,etc, I can lmcrypt the file and it works as expected. However, recently I've encountered a machine that will not accept a properly configured license file. The application consistently receives the error "Invalid (inconsistent) license key”.
I'm looking for ideas on why I'd receive this error on what should otherwise be a valid license file.
Thanks.
(1) Solution
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 04, 2019
02:24 PM
KevinL33 wrote:
I've recently run into a very strange problem, hoping for an easy solution....
I have a statically linked MFC application using FlexNet publisher. I have no problem making licenses and have never run into any issues. Once the parameters are correct, hostid, expiry date,etc, I can lmcrypt the file and it works as expected. However, recently I've encountered a machine that will not accept a properly configured license file. The application consistently receives the error "Invalid (inconsistent) license key”.
I'm looking for ideas on why I'd receive this error on what should otherwise be a valid license file.
Thanks.
Problem solved! The issue was with a version mismatch between the compiled code in the application and the version of lmcrypt we were using. The application was an older version.
Thanks all to those that were thinking about this, I'll leave the thread for future reference.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 04, 2019
02:24 PM
KevinL33 wrote:
I've recently run into a very strange problem, hoping for an easy solution....
I have a statically linked MFC application using FlexNet publisher. I have no problem making licenses and have never run into any issues. Once the parameters are correct, hostid, expiry date,etc, I can lmcrypt the file and it works as expected. However, recently I've encountered a machine that will not accept a properly configured license file. The application consistently receives the error "Invalid (inconsistent) license key”.
I'm looking for ideas on why I'd receive this error on what should otherwise be a valid license file.
Thanks.
Problem solved! The issue was with a version mismatch between the compiled code in the application and the version of lmcrypt we were using. The application was an older version.
Thanks all to those that were thinking about this, I'll leave the thread for future reference.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 09, 2020
06:19 AM
FYI - a recently discovered cause and solution for “Invalid (inconsistent) license key” (error -8)
When using "demo" vendor keys, which in the year 2020 are automatically TRL enabled, do not use the encryption strength LM_STRENGTH_DEFAULT.
The solution is changing the encryption strength to 113BIT, 163BIT or 239BIT.
