Loading
search-img

Flexera Beacon

Skip Feed

  1. ravikumar.ladhawala asked a question.

    September 7, 2026 at 11:38 AM
    FlexNet Beacon 25.1.0 Upgrade Issue – "Beacon Service Not start" / .NET Framework 4.8 Validation

    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:

    1. Beacon UI error message
    2. Beacon Engine log screenshot
    3. .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

    Expand Post
    Question with a best answer.

    Best Answer

    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

    Expand Post
    ravikumar.ladhawala by ravikumar.ladhawala
    • 2 answers
    • 33 views

    • ChrisG (Flexera Software)

      The errors seen in the logging seem to imply that the configuration settings for the beacon expected to be in the registry do not exist. Perhaps try:

      1. Uninstall the beacon software.
      2. Delete (or maybe just rename to keep a backup of current settings) the following registry key: HKLM\SOFTWARE\Wow6432Node\ManageSoft Corp
      3. Install the beacon software again.

       

      I don't see anything in what you've shared that suggests there is a problem with the .NET Framework installation.

      Expand Post

  2. ravikumar.ladhawala asked a question.

    September 1, 2026 at 5:08 AM
    Flexera Beacon Upgrade (19.x to 22.4) – ManageSoftDL and RL Application Error

    Hi Team,

     

    We are using Flexera One and recently upgraded our Flexera Beacon from version 19.x to 22.4. As part of our upgrade roadmap, we are planning to upgrade the Beacon further to the latest available version.

     

    However, after upgrading from version 19.x to 22.4, we encountered an issue while testing connectivity to the ManageSoftDL and ManageSoftRL virtual directories from the Beacon server. The test fails with the following error message:

    "Server Error in '/ManageSoftDL' Application. Could not load file or assembly 'Newtonsoft.Json, Version=6.0.0.0'"

     

    It is worth noting that the Parent Beacon connectivity test is successful, indicating that communication between the Beacon and its parent is working as expected. The issue appears to be specific to the ManageSoftDL/ManageSoftRL web applications.

     

    Please find the attached screenshot for reference.

     

    We would appreciate your guidance on the possible cause of this issue and the recommended steps to resolve it.

     

    Regards,

    Ravi Ladhawala

     

    Expand Post
    Question with a best answer.

    Best Answer

    Hi @mag00_75​ ,

     

    Thanks for your response.. Following discussions with the Flexera Support team, their investigation revealed that the Newtonsoft.Json version referenced in the Web.config file was not updated as part of the Beacon upgrade. The team provided the required configuration changes, which were subsequently applied. As a result, access to the ManageSoftDL and ManageSoftRL application URLs was successfully restored.

     

    Regards,

    Ravi Ladhawala

    Expand Post
    ravikumar.ladhawala by ravikumar.ladhawala
    • 2 answers
    • 67 views

    • mag00_75

      Hi

      I think support had a hotfix for that release, reach out to them with a ticket if you cant use a newer beacon version.

  3. Flexera One Blog — Miguel Borges (Flexera Software)

    Edited April 22, 2026 at 4:00 PM

    North America Organizations: Inventory Beacon Release 25.4.0 - Conversion of FlexNet Beacon to a 64-bit application - Action needed!

    The April 2026 update for North American organizations changes FlexNet Beacon from a 32-bit to a 64-bit application. Version 25.3.0 that included the 32-bit to 64-bit change was released to organizations in other regions but skipped in North America. For organizations with automatic upgrade of the Beacon turned on, Flexera One will bump the version to the latest available automatically – 25.4.0. Version 25.3.0 will however still be available for download from the Beacon Versions page in Flexera One.

    If your organization has automatic Beacon upgrades active, or if you want to manual upgrade your Beacons to the latest version, please first refer to our previous post about the version upgrade and the required steps to ensure that you don't have any breaking changes.

    Expand Post
    • 609 views

  4. Mitsuki asked a question.

    March 26, 2026 at 1:26 AM
    When the Inventory beacon is automatically updated, is the server running the beacon restarted?

    My client plans to select the mode "Always use the latest version (currently release-number)" to automate the beacon upgrade process.

    Does the server need to be restarted every time an upgrade is performed in this mode?

    • 2 answers
    • 107 views
    1 of 2

    • Mitsuki

      Hi atique,

       

      • After successful beacon update server does not restarts automatically nor it's required to restart.

      I got it.

      Thank you so much!

       

      Expand Post

  5. Flexera One Blog — Vijay Menon (Flexera Software)

    August 22, 2025 at 10:03 AM

    Flexera Beacon support for Self-Hosted/Embedded Web Server

     

    Overview

    We are pleased to announce the release of the Flexera Beacon version 24.2.0. This release introduces support for secure communication protocols for self-hosted/embedded servers, strengthening data security and enabling a smoother migration path for customers from Snow Extenders to the Flexera Beacon. Along with this enhanced functionality this release also addresses important bugs and technical debt items.

     

    What’s new?

    Previously, the Flexera beacon had very limited support for self-hosted or embedded web servers. This made it difficult for customers who want to have more flexibility in ensuring secure communication between the inventory agent and the beacons.

    The Flexera Beacon now fully supports key protocols and authentication methods - including Basic Authentication, HTTPS, and mTLS for self-hosted/embedded servers. These features add an extra layer of security in the Flexera Beacons, ensuring safer data transmission and reducing vulnerabilities for Flexera customers. This will also enable smoother migration of all existing Snow Atlas customers that currently rely on the embedded server functionality in Snow Extenders.

     

    Release Version: 24.2.0

    Release Date: AP/EU: 2025-08-20, NA: 2025-08-27

    Product Documentation: FNMS/ITAM, Flexera One

    Expand Post
    • 177 views
    Hameed Iqbal likes this.

  6. Flexera One Blog — Vijay Menon (Flexera Software)

    July 7, 2025 at 9:16 AM

    Unified Beacon Onboarding and Configuration

     

    We are excited to announce the unification of the beacon onboarding and configuration process for beacons across IT Visibility and IT Asset Management customers within the TI Platform. This is a significant milestone towards enhancing the user experience and reducing the time required to set up inventory collection. Going forward, customers can download a single unified beacon installer and follow a single standard process to configure it for collecting inventory.

     

    What is unified beacon onboarding and configuration?

    Previously, customers with both IT Asset Management and IT Visibility would have to download the configure their beacons in separate places. We have unified and simplified the beacon onboarding process as part of a multi-phase effort to combine and improve the functionality for inventory collection across capabilities.

     

    What has changed in the existing functionality?

    There is a ‘Common Beacons’ page under ‘Data Collection > Common Inventory Tasks’ which has a new ‘Create Beacon’ page which allows you to create and register both ITAM as well as ITV beacons. If you have both ITAM and ITV capabilities, you should chose the ITAM option from the dropdown. If you just have ITV, then you should chose the ITV option from the dropdown.

    New Create BeaconThe unification is currently limited to beacon onboarding but will be expanded in the near future to the end-to-end beacon management functionality.

     

    Important Notes:

    • ITAM and ITV customers will now be led to the same installers page for the beacon installer.
    • ITAM and ITV customers will use the same 'Create Beacon' workflow (in both online and offline beacon configuration scenarios)
    • The 'IT Visibility Inventory Tasks' menu group has been renamed to 'Common Inventory Tasks' to indicate that it has common tasks and will now be visible for ITAM-only customers as well
      • The following menu items under ‘Common Inventory Tasks’ will be common to ITAM and ITV customers: External Inventory Connections, Common Beacons, Beacon Versions, Installers.
      • The following menu items under ‘Common Inventory Tasks’ will be useful only for ITV customers for now: Inventory Targets, Inventory Groups, Tasks Lists, Agent Configurations
    • The 'IT Visibility Beacons' page has been renamed to 'Common Beacons' since it will contain both ITV and ITAM beacons
    • The 'Beacons' page under 'IT Assets inventory Tasks' will co-exist with the 'IT Visibility Beacons' page till we merge the beacons lists and properties in a subsequent phase of the project.
    • ITAM customers should continue using the existing 'Beacons' page to manage their ITAM beacons and properties (including ‘upgrade mode’ and ‘enable/disable’).
    • ITAM customers will be able to reconfigure (rotate password for) their beacon using the new beacon properties page.

     

    Release Date: July 07, 2025

    Product Documentation: https://docs.flexera.com/flexeraone/EN/WhatsNew/FeatureList/ITV-ITAM-July2025-beacon.htm

    Expand Post
    • 356 views

  7. Flexera One Blog — Vijay Menon (Flexera Software)

    June 8, 2025 at 2:13 AM

    Update to ‘Create Beacon’ workflow for IT Asset Management and Visibility 

    In the 23.3 version of the Flexera Beacon, we have removed the 'Download configuration' button in order to unify and simplify the configuration process for both ITAM and ITV beacons. The button highlighted in the screenshot below is not part of the UI and the workflow anymore.

    The new Beacon creation workflow involves copying the Beacon UID that is displayed in the beacon UI and pasting it in the ‘Create Beacon’ workflow for both ITAM and ITV. 

    For creating an ITAM beacon, use the existing interface to paste the beacon UID and create beacon configuration.

     

    For creating an ITV beacon, use the ‘Create Beacon’ button which brings up a popup. You can paste the beacon UID on the field provided in the popup and click ‘Proceed’.

    You will then be taken to the details page of the beacon where you can enter the rest of the details before completing the configuration of the beacon.

    A single unified beacon configuration page for both ITV and ITAM is being worked on and coming soon which will altogether eliminate the need to create the beacon for ITAM and ITV in separate pages.

     

     

    Expand Post
    • 227 views

  8. Flexera One Blog — Vijay Menon (Flexera Software)

    February 27, 2025 at 11:22 AM

    Flexera Beacon Configuration Workflow Known Issue and Upcoming Change for ITAM Cloud Customers

    In versions 23.1 and 23.2 of the Flexera Beacons, you will notice that the ‘Download Configuration’ button under ‘Download and Import Configuration file’ (screenshot below) does not redirect you to a Flexera URL properly. This is currently a known issue due to inter-release dependencies but has an easy workaround with an existing alternative method (described below with link to documentation).

    Beacon Download Config_EditWe will be addressing this issue in version 23.3 with a change to simplify the configuration workflow. The ‘Download Configuration’ button will be removed completely to avoid having two different methods of configuring and simplify the process. The streamlined single method to configure the beacon after the change will be as follows. Since it's an existing method, we advise customers to use the same workflow for 23.1 and 23.2 beacons till the 23.3 beacon becomes available at the end of March 2025 and the ‘Download Configuration’ button no longer exists.

    1. Use the ‘Configure a Beacon’ (ITAM) option in the Flexera One web UI on the beacons page
    2. On that page, enter the details to configure a beacon, including pasting the Beacon UID from the beacon server, which is now made visible with a copy button
    3. Complete the configuration process and download the configuration from that page
    4. Import that configuration file into the beacon server using the ‘Import Configuration’ button as shown in the screenshot above. 

    As mentioned earlier, this is an existing method which has been documented in the following page: Creating and Registering an IT Asset Management Inventory Beacon

    The 23.3 change to the beacon, the removal of the 'Download configuration' button, will be applicable to both ITAM and ITV going forward and will be in line with ongoing efforts to unify the beacon processes for both products.

    Expand Post
    • 382 views
    PaulReit likes this.

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
8 Posts
3 members are discussing this topic.

Related Topics

+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Flexera Beacon | Flexera