Error signing into Web Screens

I am getting the following error on logging in to Web Screens on a new installation:

A problem occurred when signing in to web screens. Try signing in to the Sage 300 Desktop and activate data for all company databases that use the same system database before signing in to web screens.

The Sage 300 Desktop is working fine.

How do I fix this error?

Thanks
&
Regards,
Ubaidullah Nubar.

Parents
  • 0

    Have you logged into ALL companies that belong that are attached to the SYSTEM database via the desktop? In the Database Setup Screen, have you accessed the "Portal" button and set that up?

  • 0 in reply to John Thomas

    Yes. Logged into all companies. Portal database is also setup.

    I also tried creating a new company and activated only General Ledger in it but am still getting the same error when logging in to it also.

    Another symptom that might indicate what the problem is: the Sage logo above the sign-in area isn't displaying either.

  • 0 in reply to unubar

    And, in the SITE folder of your Sage 300 installation do you see the dbconfig.xml file? This is created when the logic behind the Portal button is run. Sounds like you might need to contact customer support and be able to send them your trace.log file that is found in your ..\online\web\Logs folder that might assist when diagnosis of the situation.

  • 0 in reply to John Thomas

    Yes, the dbconfig.xml file exists. It has the connection info for the PORTAL database.

    The trace.log file contains an error message:

    Error HRESULT E_FAIL has been returned from a call to a COM component.

  • 0 in reply to John Thomas

    The problem with sage support is when we log on a support query, they will still refer me to this discussion whereby one has already done that before we log in the support query with them.

    Most of the times this is very frustrating bearing in mind we are in consulting business, and we need to close incidents fast for us to earn. I wish in addition to sage city & KBs references there was a way they could manage to look into the individual problem

Reply
  • 0 in reply to John Thomas

    The problem with sage support is when we log on a support query, they will still refer me to this discussion whereby one has already done that before we log in the support query with them.

    Most of the times this is very frustrating bearing in mind we are in consulting business, and we need to close incidents fast for us to earn. I wish in addition to sage city & KBs references there was a way they could manage to look into the individual problem

Children
No Data