ravikumar.ladhawala asked a question.
Hello Team,
We are using Flexera One and recently upgraded our FlexNet Beacon from version 22.4 to 25.1.0. Following the upgrade, the Beacon UI is not opening successfully and displays the following error message:
"Beacon service not found."
"The application could not start because it could not connect to the FlexNet Inventory Beacon Engine service. Please check that the service is running."
However, when we check Windows Services, we can see that the FlexNet Inventory Beacon Engine service is present and running successfully, which makes this behavior somewhat confusing.
As part of our troubleshooting, we reviewed the prerequisites for Beacon version 25.1.0, which indicate that .NET Framework 4.8 is required.
We verified the installed .NET Framework version using the following PowerShell command:
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full').Version
The output shows 4.8, suggesting that .NET Framework 4.8 is installed on the server.
However, when checking Add or Remove Programs, we can only see .NET Framework 4.6, and there is no visible entry for .NET Framework 4.8. To further validate this, we attempted a manual installation of .NET Framework 4.8, but the installation failed with the following error:
"Installation did not succeed. .NET Framework 4.8 has not been installed because: Cannot find object or property."
For reference, I have attached the following:
- Beacon UI error message
- Beacon Engine log screenshot
- .NET Framework installation error screenshot
Has anyone encountered a similar issue after upgrading from Beacon 22.4 to 25.1.0? Any guidance, recommendations, or troubleshooting suggestions would be greatly appreciated.
Thank you in advance for your assistance.
Regards,
Ravi Ladhawala
Hi Chris,
Thank you for your response. We connected with the Support team, and they initially recommended uninstalling and reinstalling the current Beacon version. We followed this approach; however, the same error reappeared after the reinstallation. At that point, I strongly suspected that the .NET Framework 4.8 installation might be corrupted, especially since the .NET 4.8 entry was not visible in Add/Remove Programs, although the 4.8 update was listed in Windows Update and only able to see .NET Framework 4.6 entry in Add or Remove Programs.
The following day, we had a Meeting with a senior support engineer who recommended performing a complete uninstallation of FlexNet Beacon. During earlier uninstall attempts, we encountered two pop-up messages, which we had ignored. One was related to a running .exe file, and the other indicated that an MSI package could not be found.
Based on the engineer's recommendation, we stopped all Flexera services, terminated related processes from task manager, disabled scheduled tasks, and stopped the IIS websites. This resolved the first pop-up issue. We then proceeded with the uninstallation, and Beacon 25.1.0 was successfully removed. However, we noticed that Beacon 19.0.1 was still listed in Control Panel.
It appeared that the original Beacon 19.0.1 installation had not been fully removed during the upgrade process from 19.0.1 to 22.4 Beacon version. Attempts to uninstall version 19.0.1 failed because the required MSI package was missing. After several unsuccessful attempts, we finally removed the legacy Beacon installation using the MSIZap utility.
Once the older version was removed, we backed up the required configuration files, deleted the remaining Flexera folders from C:\ProgramData and Program Files (x86), and cleaned up the associated registry entries. After completing the cleanup, we installed FlexNet Beacon 25.1.0 again, and the installation completed successfully. The Beacon application then functioned as expected without any further issues.
Regards,
Ravi Ladhawala