This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Knowledge Base
- :
- Failed to find this beacon, with an ID of
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Subscribe
- Article History
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Summary
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.Symptoms
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()
Resolution
By re-installing the beacon, this then creates a new beacon UID that is now relevant and stops the error from occurring.Mar 03, 2018 03:39 AM
Labels:
No ratings
