Flexera Community

Aug 29, 2024

Hello,Did some encounter errors with the beacon server after upgrade to 2024 R1? I have the following error:[8/29/2024 9:43:09 AM (G, 0)] {2424} Uploading file 'system on at 20240826T175539 (Full).ndi.gz' to 'https://ManageSoftRL/Inventories'[8/29/20...

May 22, 2019

Hi Community,I have the following issue.FNMS 2018 R3 on prem implementationAsset import from SNOW, via mid serversThe problem is that the quality of data in SNOW are very bad, I have a lot of assets with no serial number, the serial number is blank, ...

Sep 13, 2024

Nope

Sep 13, 2024

Hello,I had 2 days ago a call with Flexera support, and they linked the case with other one, and forwarded to engineering team. Our solution was to downgrade all the master beacons to the latest stable version that is in use.

Aug 29, 2024

One short update, I downgraded the master beacon server to version 21 (2023 R2) and seems to work now, it generate again errors but in the end he uploaded the pending inventories. So seems to be an issue related to the latest version 2024 R1

Aug 29, 2024

Hello, the beacon name was remove to not provide customer sensitive information. The beacon is correctly configure as it work and then stop with that error. I opened also a Flexera case on this topic.

Apr 09, 2021

Also Flexera has in the newer version the option to create targets and to assign it to a beacon. You can create targets on subnets if you want, and practically you will force the agent to send the data to the designated beacon.

Flexera Community

User Statistics

User Activity

Error after upgrade to 2024 R1

Asset link to inventory with no serial number

Re: Error after upgrade to 2024 R1

Re: Error after upgrade to 2024 R1

Re: Error after upgrade to 2024 R1

Re: Error after upgrade to 2024 R1

Re: Best practices for more than 1 Beacon