[Incident]: Some users report they are unable to access the case portal. Please see this community notice for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Devices tab not listed after FNO On-premises upgrade

Devices tab not listed after FNO On-premises upgrade

Symptoms:

It is seen that after the upgrade of FNO On-premises, the devices tab is not being listed either in producer portal or in end user portal even though customer has valid licenses of FNE.

Diagnosis:

FNO On-premises gets its licenses from Revenera hosted instance endpoint which is being defined in FNO under system-->configure-->Licensing.

It's observed that while checking out the licenses from the Licensing endpoint, FNO throws following error in flexnet log.

 2022-03-09 22:15:00,670 [default task-18] ERROR (licensing) [ADMN] Failed to set up license source: System machine type does not match expected machine type. 

It can be seen in the  logs that,  the machine type information which is stored in FNO Trusted storage from the previous license checkout is different than the one on which it is trying to checkout licenses now. And because of this mismatch FNO is not able to checkout license. This may be happen if VM machine type changed from Physical to Virtual or vice versa.

Solution:

One can follow below steps to release the previous stored information of licenses in FNO and then refresh it with new licenses.

  1.  Stop the FNO server.
  2.  Take the backup of TS files usually located under "C:\Windows\System32\config\systemprofile\.fnoStorage\ADMN" . See screenshot below for reference
  3.  Remove the TS files from the location mentioned in step 2
  4. Start the FNO
  5. Now you can see in flexnet.log that licensing threads are successful and you will be able to see the Devices tab as well. 

     

    Sample Screenshot Showing TS files:

    FNO_TS_Files.png

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Mar 10, 2022 04:22 AM
Updated by:
Contributors