A new Flexera Community experience is coming on November 25th. Click here for more information.
Symptom
When loading the Beacon Interface you might be presented with the following:
There are a few things that could be causing this
Issue 1:
The license file has not been imported into FNMS
Workaround:
First you will need to make sure you have a valid license. This can be obtained from within your Product and License Center Portal.
On your batch server, launch the Flexnet Manager Suite Activation Wizard (Start> Flexera Software> Flexnet Manager Suite Activation Wizard)
Press import License and import your license. that should resolve your beacon issue. It might be a good idea to restart the beacon engine service from within services manager
Issue 2:
Check your beaconengine.log for the following
2020-05-18 00:00:55,133 [Services.PolicyService|policy] [ERROR] Failed to download policy.
ManageSoft.Compliance.ComplianceException: Verification failed: No Signature was found in the document. ---> System.Security.Cryptography.CryptographicException: Error occurred during a cryptographic operation.
--- End of inner exception stack trace ---
at ManageSoft.Compliance.Security.Cryptography.DigitalSigner.VerifyXml(XmlDocument Doc, RSA Key)
at ManageSoft.Compliance.Security.Cryptography.DigitalSigner.VerifyXml(XmlDocument xmlDoc)
at Flexera.SaaS.Transport.Rules.PolicyClient.VerifyPolicySignature(MemoryStream ms)
at Flexera.SaaS.Transport.Rules.PolicyClient.DownloadPolicy(String currentVersion, String inventorySettingsRevision)
at Flexera.Beacon.Engine.Services.PolicyService.GetPolicyFromServer(Int32 currentRevisionNumber, String inventorySettingsRevision)
at Flexera.Beacon.Engine.Services.PolicyService.UpdatePolicy(IActivityLogger activityLogger)
2020-05-18 00:00:55,133 [llers.PolicyController|policy] [ERROR] There is a problem on the beacon. The beacon could not determine if an upgrade is required.
Work Around:
There is currently a bug located FNMS-64113
This is caused by a registry key that was mistakenly included in the installer
Open Registry Edit (regedit)
Navigate to
HLKM\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\
Remove the key certificatefile
Restart the beacon engine service
on May 22, 2020 05:16 AM - edited on Apr 16, 2021 10:51 PM by ChrisG