Sage 300 Web screens - You do not have a license to use this product. Ask your system administrator for help.

Hi

I have a client who is running Sage 2018 Pu 2 windows server 2019

I have installed the web screens, and run the portal.

As soon as I access the web screens I get this.  I can confirm the web licence is activated.

I am wondering if the fact that sharedata is mapped to \\server123\accpac$  , would this be causing the issue?

I read that 

  1. Sage 300 cannot be installed with a UNC path or mapped drive for the Program directory or shared data directory when using web screens. Check the registry path. Reinstall using a local path for the programs folder. Note: If a UNC path or mapped drive was used, the Sage.CNA.WindowsService will not have installed. If the shared data path using a UNC path, the error HRESULT E_FAIL will appear when loading the web screens login page. Edit the path in the registry to use a local drive.

Any thoughts

Thanks

  • 0

    Experiencing the same issue

  • 0 in reply to Demetech

    Hi, I work with Stacey and we fixed this issue in our scenario. Here's what I did, as ultimately its a permissions issue.

    In IIS I changed the Sage300 app to run as ApplicationPoolIdentity. (IIS / App Pools / Sage300 App Pool / Right Click - advanced settings / Identity)

    The same was done for the Sage 300 OAuth Pool.

    Then for both the Sage300 and Sage300WebApi web sites, I changed the Anonymous Auth to Application Pool Identity.

    We can now use the IIS App Pool identity for NTFS folder permissions, giving the identity user rights to read/modify the Sage300 folders.

    I assigned those App Pool identity permissions over the Sage300 directories. In this example we split the Sage300 Programs and SharedData. The identity was given Read & Execute over Programs, and Modify over Shared Data.

    To add the IIS app pool identity permissions, you need to type: IIS AppPool\<<app pool name>>, then press Check Names. Our example was IIS AppPool\Sage 300 Pool.

    This was repeated for the Sage 300 OAuth Pool.

    Because our Sage300 install had shared data as a UNC path, I had to add both app pool identities 'Change' permissions to the SharedData folder under Advanced Sharing:

    Once this was done, I recycled both IIS app pools. The web screens worked as expected.