Are you working here with FlexNet Manager Suite Cloud? This type of logging will typically appear when you have a FlexNet Manager Suite Cloud beacon that is a child of another beacon. There is nothing in the UI that will stop you from configuring beacons in this way, but it is best to avoid it as it doesn't work as you're seeing.
To avoid the error, configure all beacons to connect directly to FlexNet Manager Suite Cloud: do not have any beacon configured as a child of another beacon.
Another workaround to try is to delete the following registry entry on the child beacon:
HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\CertificateFile
This is the entry that effectively makes the beacon think that it is communicating with FlexNet Manager Suite Cloud directly, so removing the entry removes that assumption.
With that said, I've heard mixed reports about whether this is actually effective at working around the issue so it may not help. Please post here if you have any experience.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
oqueck
