Summary
The FlexNet Manager for Engineering Applications UI dashboard does not display the current feature usage data under the 'Most Active Features' section. The Activity tab also does not show concurrent feature usage details.Symptoms
The FlexNet Manager for Engineering Applications UI dashboard does not display the current feature usage data under the 'Most Active Features' section.
The Activity tab also does not show concurrent feature usage details.
The following error occurs in admin server flexnet.log:
2018-01-15 13:16:18,776 WARN [flexnet.agent] [pool-19-thread-1] Unexpected LicenseItem line: 247 35.0 1 cybercad permanent(no expiration date)
2018-01-15 13:16:18,776 DEBUG [flexnet.agent] [pool-19-thread-1] expiration string invalid: cybercad
java.text.ParseException: Unparseable date: "cybercad"
The Flexnet Publisher version(lmgrd.exe) that is being used is 11.14.1.2 or higher
Cause
FNP 11.14.1.2 uses a different format for the output of the lmstat command.
In versions of Flexnet Publisher until 11.14.1.1, the lmstat command result shows expiry as "1-jan-0" for features whose expiry is permanent. However from version 11.14.1.2 the lmstat command returns permanent(No Expiration Date) for the same. FlexNet Manager for Engineering Applications fails to parse the missing expiration date and hence fails to get any usage info from these license servers.
Resolution
Engineering has provided the attached hotfix for FlexNet Manager for Engineering Applications 2016 R2 SP1 and FlexNet Manager for Engineering Applications v15.5 to resolve this issue.
Please follow these steps to apply the hotfix.
1. Stop the flexnet admin server.
2. Extract the relevant hotfix version corresponding to the version of FNMEA you are using under custom hotfix folder in <FNMEAAdmin Install Path>/
For example - \FLEXnet\manager\admin\custom
Once extracted, the full directory should look like this: \FLEXnet\manager\admin\custom\webapps\flexnet\WEB-INF\classes\com\flexnet\manager\services\agent
3. From command prompt navigate to <FNMEAAdmin Install Path> and run "flexnet site make"
4. Start admin server.
Workaround
Alternatively downgrading to a version of Flexnet Publisher prior to v11.14.1.2 will resolve this issue as well.
