Showing results for 
Show  only  | Search instead for 
Did you mean: 


This article discusses an error that may be experienced when the beacon cannot accept actions from the core server due to having a different beacon UID.


Recently restored the production environment DB on the development environment and now are seeing the following error during Discovery:

2017-03-09 14:08:54,761 [on.DiscoveryCalculator|Async] [ERROR] Failed to find this beacon, with an ID of '{3A1619F1-A9E6-4933-A6FB-F865B98C77A5}', in the current policy that includes valid filters
2017-03-09 14:08:54,761 [iscoveryActionExecuter|Async] [ERROR] An exception occurred when executing a discovery action
System.NullReferenceException: Object reference not set to an instance of an object.
at Flexera.Beacon.Engine.ActionExecution.DiscoveryCalculator.GetSubnetRanges(Rule rule, DynamicDeviceTargeting dynamicDevices)
at Flexera.Beacon.Engine.ActionExecution.DiscoveryCalculator.BuildSubnetRangeData()
at Flexera.Beacon.Engine.ActionExecution.DiscoveryCalculator..ctor(Policy policy, Rule rule, Boolean processSubnetFilter)
at Flexera.Beacon.Engine.ActionExecution.DiscoveryActionExecuter.Execute()


By re-installing the beacon, this then creates a new beacon UID that is now relevant and stops the error from occurring.
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Mar 03, 2018 03:39 AM
Updated by: