Summary
When attempting to build the FLEXlm SDK the following error message appears: FLEXlm Error -44: Invalid FLEXlm key data supplied. How can this resolved so that the SDK can be built successfully?
Synopsis
When attempting to build the SDK the following error message appears: FLEXlm Error -44: Invalid FLEXlm key data supplied. How can this resolved so that the SDK can be built successfully?
Discussion
There are several factors that could cause this error to occur. These factors have been listed and a brief description of each has been provided below:
For Evaluation Keys
The primary reason for the FLEXlm Error -44 to occur would be that the demo keys have expired. If that is the case you will need to contact your sales representative for new demo keys. Also make sure you have not changed the vendor name from 'demo'.
For Production Keys
If you attempting to build your Production SDK with the production vendor keys generated for you by Flexera and encounter this error, you will need to check the following items:
- Compare the vendor keys provided to you by Flexera Software with the vendor keys installed in lm_code.h. Any additional characters or missing characters will cause the build process to fail.
- Check to make sure that the vendor daemon name is correct in the lm_code.h file. Note, the vendor daemon name is case sensitive and deviation from the case will cause the build to fail.
- Make sure the platform you are attempting to build the FLEXlm SDK on is one of your supported platforms. Vendor keys are generated to work with specific platforms that your company has purchased support on. If you do not have support for a particular platform, the keys will not be enabled for that platform. Also note that 32-bit is considered a different platform than 64-bit. Check to see the version of your vendor keys and the SDK you are attempting to build on. Vendor keys can not be used across major versions (i.e. v9.x keys will not work on v10.x SDK, and v10.x keys will not work on v11.x SDK). New vendor keys will need to be requested if you wish to upgrade.
NOTE: All information about your specific vendor keys can be found on the License Certificate used to send the keys to you.
Related Articles
Authorization Error in Data Access API When Using Base64-Encoded Credentials in Swagger UI 12Number of Views Oracle Licenses Consumption Details and Optimizations report may fail with error in webui.log: "String or binary data woul… 4Number of Views Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a service 3Number of Views Invalid (inconsistent) License Key. (-8,523) Error When Checking Out From ASR Trial License Generated From FlexNet Operati… 5Number of Views How to Write Custom Messages in the DEBUG log using lc_log? 472Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
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. | |
Case id: 00001065
Activity: Status change: 2 hours ago