Hello Nlit, 

My guess is that your Web Screens is not currently configured to be run externally.. please review the installation guide (Chapter 5) Sage 300 2022 Installation and Administration Guide and see if you have added all your IIS Components and then if necessary please contact Customer Support to open a support ticket.

Regards,

David Crampton

Hi NLIT Sage in version 2023 this error specifically means the external name your using to reach the Sage server differs from the server name in your SSL certificate.  In version 2024 the error was changed to a proper message referring to a mismatched SSL certificate.

If you own a wildcard certificate for a company domain, just create a subdomain A record like sage300.<yourdomain>.<yourTLD> and apply the <yourdomain> wildard certificate to IIS on your Sage 300 server, opening up port 443 through to that server.  If 443 isn't available you can use any other port.  If you don't own a certificate remember you can use the inexpensive "Certify The Web" service to create and automatically install an SSL that exactly meets your subdomain, though you will need to forward or redirect Port 80 and to your server to allow it to generate the SSL.  If this is all an internal network then I recommend creating the subdomain and apply the relevant SSL certificate but use DNS forwarding rules in your environment to ensure your external name points to your internal server so that again the SSL server name matches the name used to hit the server.

I know this is all a bit annoying but its a huge improvement to the website by reducing the chance of Phising.

Finally if this server is 100% accessed internally and securely via VPN then for now remove the 443 binding and go back to port 80 allowing uses to access the site over http, but this is strictly against advice in the user guide.  The guide DCrampton is referring to is an excellent one.

For an example check out our demo Sage 300 site https://sage300demo.accsysconsulting.com.au/sage300 that just uses an A record as suggested above.

Let me know if you require further advice.

Cheers,

Tim

Thank you. We'll look into your suggestions. We realised that db server firewall blocked access to the sage databases. We made a rule to open the port and the UNDEFINED problem went away. 

NLIT-BCTeh that's unusual, when I block access to the databases I don't even get far enough to receive the Undefined error, I receive:

I'm glad its working though! Nice work.

Tim