Sage 300 v2023 external web screen error Undefined after entering login

SUGGESTED

After upgrading to Sage 300 from v2022.4 to v2023.1, we get an Undefined error after entering the login screen from external web screen. his issue is only with external access outside the network. Internal web screens are fine. I have reviewed KB 77607 (Setting up Sage Web Screens) and KB 117661 (Error: Undefined), but these have not helped to resolve problem. Any thoughts?

  • 0

    I have the same problem. Were you able to solve the problem?

  • SUGGESTED

    I discovered this error began occurring with version 2023 of the Web Screens.  It would appear to be the result of improved security on Sage's part.  The cause of the error for me was accessing the login screen from a different URL than that published in the underlying SSL certificate.  In version 2024, this error was improved further with an actual message being returned instead of "Undefined".  In version 2024, the error reads as: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel."



    In version 2023, I could immediately work around the "undefined" error by accessing the site over port 80 http externally (this was via a secure VPN) until the problem with the external subdomain and SSL mismatch was rectified.  The cause may not be the same for you but if you're using an internally signed SSL and users are accessing the site using a different IP or hostname externally, it may be the cause.  You could try switching back to port 80 http briefly to test if the error goes away externally (perhaps do this after hours with production databases offline for security).

    Cheers

  • 0 in reply to NLIT Sage

    I have the same issue with 2024 version. Seems no answer yet. 

  • 0 in reply to BULAIRE

    The best solution is to add a forwarder into DNS on your domain controller that matches the name of an available SSL certificate.  Install the SSL certificate onto your Sage 300 web server and bind it to the secure port i.e. https 443 you're using to publish Sage 300.  Then ensure all your users on the network access Sage 300 via the DNS forwarder i.e. sage.yourcompany.com.  They will no longer experience the undefined or other errors.  If you already have access to your site setup correctly via a proper SSL certificate, and are still experiencing an 'undefined' or similar error, please post a screenshot of it for us to investigate.  You can access our sample site at https://sage300demo.accsysconsulting.com.au:4433/Sage300 user ADMIN password <DM me> if that helps you get configuration ideas for yours.  Its on an old server with only two vCPU's so it take a while to spin up when you first access it.