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

"Your system is not licensed to use this application."

Big_Kev
By Level 7 Champion
Level 7 Champion

Hello App Portal Experts

I have a migration scenario , taking a DB backup from the  existing 2019 production (On Premise data center) server, and  restoring the DB backup on a new Azrue VM.  The goal is then using 2022 R1 installer do the upgrade.

Strange enough is the installer has completed (upgrade) successfully. But while logging http://localhost/ESD,  any user including existing administrators whoever login, the website keep throwing  -- "Your system is not licensed to use this application."

There are some old thread `suggesting remove the License Collection & view setting, but as no one can login the UI to change the setting...is there any other option ? or SQL updates by how ?   What's the root cause of that is because the new Azure VM is not a Device collection with the SCCM it's connecting ? or ....simply a product defective behavior ?  

Any suggestion will be much appreciated. 

Best Regards

Kevin

 

(1) Solution
CharlesW
By Level 12 Flexeran
Level 12 Flexeran

With regards to the "your system is not licensed" dialog, you should be able to get around this by running the following query:

update WD_AppSettings set value = '' where keyname = 'LicenseCollectionID'

After running this query, be sure to perform an iisreset.

View solution in original post

(3) Replies
CharlesW
By Level 12 Flexeran
Level 12 Flexeran

With regards to the "your system is not licensed" dialog, you should be able to get around this by running the following query:

update WD_AppSettings set value = '' where keyname = 'LicenseCollectionID'

After running this query, be sure to perform an iisreset.

P.S. The root cause of the issue is that you put in bogus values for the SCCM deployment settings. As such, App Broker was not able to look up the collection membership of the licensed collection.

Hello @CharlesW 

Thank you very much...IISreset was what I missed, This fixed the problem.

Sweet

Cheers

Kev