Loading

FlexNet Manager Suite On-Premises

Skip Feed
  1. rinke.beimin asked a question.

    What is the recommended best practice for upgrading FlexNet Manager Suite On-Premises from version 2024 R2 to version 2025 R2 while simultaneously migrating from Windows Server 2019 to Windows Server 2025?

    Subject: Best Practice for Upgrading and Migrating FlexNet Manager Suite On-Premises

     

    Hello,

     

    We currently have FlexNet Manager Suite On-Premises version 2024 R2 running on Windows Server 2019. We are planning to both upgrade to version 2025 R2 and migrate the application to a new server running Windows Server 2025.

     

    We would like to confirm the recommended best practice for this scenario.

     

    Our understanding is that the safest approach would be to:

     

    1. Install version 2024 R2 on Windows Server 2025.

    2. Connect the existing database.

    3. Verify that the application is functioning correctly.

    4. Perform the upgrade from version 2024 R2 to version 2025 R2.

     

    However, we would like to know whether the following approach is also supported and recommended:

     

    1. Install version 2025 R2 directly on Windows Server 2025.

    2. Connect the existing database from the version 2024 R2 environment.

    3. Complete the upgrade as part of the first connection/startup.

     

    Is this approach supported, or is it necessary to first install the existing version before upgrading? If installing version 2025 R2 directly is supported, are there any prerequisites or additional considerations we should be aware of?

     

    Thank you in advance for your guidance.

    Expand Post

  2. Having an issue with our DEV instance attempting to connect to Db fnmscompliance when initiating webUI.

     Having an issue with our DEV instance attempting to connect to Db fnmscompliance when initiating webUI. The fnmscompliance Db doesn't exist on EITHER PRD or DEV DataBase Servers. PRD works fine. Why would DEV look for that Db to open the webUI? Where can I change it to be like PRD and/or would a copy of the PRD Db to DEV correct the issue?

     

    Server Error in '/Suite' Application. Cannot open database "fnmscompliance" requested by the login. The login failed

    Expand Post

    1 of 2
    • Thanks, Chris. Please see below. This is what I'm seeing on the Db Servers for each instance. The top one is PRD, the bottom is DEV. PRD works fine but I don't see an "fnmscompliance" Db whereas, the DEV instance will not open the GUI indicating it cannot find the "fnmscompliance" Db. Both Db Servers look the same with exception of the AppPortal and ContentStore Dbs. Am I missing it? Do you think a copy of PRD Db to DEV environment would correct the issue?

      image

      Expand Post

  3. Having an issue with our DEV instance attempting to connect to Db fnmscompliance when initiating webUI.

    Having an issue with our DEV instance attempting to connect to Db fnmscompliance when initiating webUI. The fnmscompliance Db doesn't exist on EITHER PRD or DEV DataBase Servers. PRD works fine. Why would DEV look for that Db to open the webUI? Where can I change it to be like PRD and/or would a copy of the PRD Db to DEV correct the issue?

     

    Server Error in '/Suite' Application. Cannot open database "fnmscompliance" requested by the login. The login failed.

    Expand Post

  4. When will the FNMS 2026 R1 release become available for download for all customers and Flexera partner companies?

    Working with our Flexera customers, we know that the FNMS 2026 R1 (on-prem) release is available for download since mid of last week. However, we still don see the downloads in the 'Product & LIcense Center'. FNMS 2026 R1 Release notes are available since July 1st, too.

    When will this release become available for download for Flexera partners and all customers?


    • ChrisG (Flexera Software)

      The FlexNet Manager Suite 2026 R1 release is now available to everybody who is entitled to it based on a current subscription or maintenance agreement.

       

      The release may not be available automatically to some Flexera partners. If you are a Flexera partner and would like to request access to the release then you may need to reach out to your Flexera Partner Manager or Flexera Support to arrange that.

      Expand Post

    • JohnSorensenDK (Flexera Software)

      @Simoney69​ 

      Personally, I wouldn't expect Trellix' newer core (or other) licensing models to automatically grant entitlement rights to deploy older node-based products unless Trellix's product use rights, grant letter, SKU migration guide, or ordering documentation explicitly state backward-use (downgrade) rights. If you have confirmed that you have such backward coverage included license entitlement wise you will likely to have manually apply this to the license objects.

       

      If you require further guidance from the forum members you may want to include more details about what you have tested.

       

      Thanks,

      John Sorensen

      Expand Post

  5. Database Upgrade Scripts complains about missing object 'PopulateInitialDataForDM_MT'

    Hi Champs,

     

    I just wanted to check if anyone while upgrading from 2024 R2 to 2025 R2 has faced issues like below:

     

    Preparing to run step 'Migration from 23.1 to 23.2'.

    Required minimum database compatibility level: SQL Server 2008 (100)

    Found database compatibility level: SQL Server 2019 (150)

    Required version: 23.1

    Found version: 23.1

    Executing step

    Checking that all database objects are owned by dbo...Validated

    Running 'common-mig-procs.sql'.

    Running 'dw-migr2320-migprep.sql'.

    Starting migration in phase "prep" at step 1

    Migration phase "prep" complete.

    Running 'dw-migr2320-DataWarehouseSchema.sql'.

    Changed database context to 'master'.

    Changed database context to 'DEV_FNMPDataWarehouse'.

    The module 'PopulateInitialDataForTenant' depends on the missing object 'PopulateInitialDataForDM_MT'. The module will still be created; however, it cannot run successfully until the object exists.

    The module 'PopulateInitialDataForTenant' depends on the missing object 'PopulateInitialDataForFNMP_MT'. The module will still be created; however, it cannot run successfully until the object exists.

    Creating procedure to return the contents of the license file associated with a particular tenant

    Creating procedure to set the contents of the license file associated with a particular internal tenant ID

    Creating procedure to set the contents of the license file associated with a particular internal tenant UID

    Changed database context to 'DEV_FNMPDataWarehouse'.

    Changed database context to 'DEV_FNMPDataWarehouse'.

    Changed database context to 'DEV_FNMPDataWarehouse'.

    Changed database context to 'DEV_FNMPDataWarehouse'.

    Changed database context to 'DEV_FNMPDataWarehouse'.

    Changed database context to 'DEV_FNMPDataWarehouse'.

    Checking identity information: current identity value '1000'.

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    Checking identity information: current identity value '1000'.

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    Checking identity information: current identity value '1000'.

     

     

    If I proceed with upgrade, will it cause any issue. Similar logs are being shows IM and DWH.

     

    Thanks,

    FL

     

     

    Expand Post

    • JohnSorensenDK (Flexera Software)

      @fawad_laiq​ 

      I can see that you raised the same question with Flexera Support and received confirmation that these messages were expected. If your experiences make sense to share with the broader community, then please do.

       

      Thanks,

      John Sorensen

      Expand Post

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
26 Followers
8.26K Posts
1.31K Articles
19 members are discussing this topic.
Loading
FlexNet Manager Suite On-Premises | Flexera