This looks more like an installation issue than the licensing.  You should review the IIS traffic to see what kinds of messages/transactions are occurring.

Hi Laurence,
If you launch it directly via the following URL in a Chrome browser window do you get any additional details on the error?  (it doesn’t look like a license issue to me, I suspect there may be something wrong with the actual installation):

http://localhost/AsteaMobileEdgeServices/Warehouse/

Launch the Developer Tools and then click on the Network tab and see if there are any error entries captured in there, thanks.
Reid

Do you mean Log Viewer Reid ? If yes, I couldn’t find anything related to this error.

Sure, We’ve done that, and here is the screenshot. 

Hi Reid, 

Any idea ? 

We (as a partner) have the exact same error on our DEMO environment. Potentially something is bad in the License key or configuration. How can we move forward  ?

Thank

Hi Laurence,
This will need to be researched further...I suspect it may be an issue with the installation executable.  I logged a support ticket for this in ServiceNow, thanks.
Reid

Hi Laurence,
As a workaround in the meantime try making the following change to your Program Files\Alliance Mobile Edge\AsteaMobileEdgeServices\appsettings.json file (make a backup of the current version beforehand), then scroll down to the bottom of the file and update the Identity Clients section RedirectUris and PostLogoutRedirectUris entries as follows...copy and paste the entire entries and then replace the section highlighted in yellow with the fully qualified domain name for your current environment:

        "RedirectUris": s
          "http://YourFQDNServerNameGoesHere/AsteaMobileEdgeServices/Warehouse/auth/callback/"
        ],
        "PostLogoutRedirectUris": u
          "http://YourFQDNServerNameGoesHere/AsteaMobileEdgeServices/Warehouse/"
        ],

Be sure to do an IISRESET on the server afterwards and then launch the application in a new Chrome tab, this solved the problem on my local environment.  Also test it through the Publisher link (it won’t work through localhost once you enter the FQDN entries).
Thanks,
Reid