This article contains information about a defect in FlexNet Publisher 11.19.2, 11.19.3, or 11.9.4 that may prevent vendor daemons from starting and serving license successfully. A fix will be available in FlexNet Publisher 11.19.4.1.
Note: This defect does not affect FlexNet Publisher 11.19.1 or earlier versions.
Symptoms
For integrations that upgraded to FlexNet Publisher 11.19.2, 11.19.3, or 11.19.4, the following errors may be observed when starting the vendor daemon:
Inconsistent authentication code
Feature <feature_name> is not enabled yet
Upon encountering these errors, the vendor daemon fails to start and cannot serve licenses.
Steps to Reproduce
Integrate with FlexNet Publisher to version 11.19.2, 11.19.3, or 11.19.4.
Start the FlexNet Publisher license server using a previously signed FlexNet Publisher license file or a newly signed license file.
Errors will appear in the lmgrd log file.
Workaround
There is no workaround for this issue.
Fix Version and Resolution
This issue will be addressed in FlexNet Publisher 11.19.4.1. Software producers will need to upgrade to FlexNet Publisher 11.19.4.1 or later.
If your FlexNet Publisher uses 11.19.1 or earlier and you are trying to integrate with FlexNet Publisher 11.19.2, 11.19.3 and 11.19.4, depending on your integration, you may observe the errors mentioned above. In this case, we recommend you pause your integration with 11.19.2, 11.19.3 or 11.19.4 and wait to integrate with 11.19.4.1 or later.
If your FlexNet Publisher was upgraded to FlexNet Publisher versions 11.19.2, 11.19.3 or 11.19.4, then please follow the steps mentioned below:
Integrate with FlexNet Publisher 11.19.4.1 or later.
Any license files crypted with 11.19.2, 11.19.3 or 11.19.4 must be re-crypted with 11.19.4.1 or later.
The vendor daemon must be started with the re-crypted license file.
