Workspaces 404 / 403 Error

Hello,

We are having an issue with one of our customers regarding the homepage and workspaces for Sage 200, they are currently on version 10.00.0030 (Due to a lot of bespoke they have, they are due to upgrade around March next year). When you first log on or try to access workspaces, we're getting Server Error "404 - File or directory not found". This started suddenly about a week ago. I've confirmed this is not bespoke related and Sage had agreed with that when I spoke with them.

  • This happens for all databases on their server (including new databases).
  • If we take the data off site, it works as expected.
  • They have TLS 1.0 and 1.1 still enabled.
  • The password for the services/secured users are valid and re-entered into IIS.
  • Tried an IIS reset and restarted the server.
  • Happening for all users, on all servers, they use TS Environments.
  • There's no errors appearing on event viewer to suggest what the problem is.
  • Have gone through the Sage 200 install guide to make sure nothings been changed, this looks to be all correct.
  • Disabled Firewall and issue was still occurring.

From a logging point of view, the Sage200SelfService.log looks Ok! it's repeating the checks and showing:

Sage.IdentityModel.Claims.Sage200.ClaimsAuthorizationManager ClaimsAuthorizationManager.CheckAccess OK: Res=servername:10444/.../ , Act=GET }  

In the Sage200SecuredServices.log and Sage200Services.log, the only error that appears is:

2021-10-13 09:28:42,870 ERROR Sage.IO.SignedXMLReader LoadXML, Error:Unable to connect to the remote server
2021-10-13 09:28:42,870 ERROR Sage.IO.SignedXMLReader VerifyDigitalSignature, Error:Root element is missing.

However, we can access the server, SQL and everything else is running as expected. The issue happens where Sage is hosted too.

If we try to access the self service URL( https://servername:10444/Sage200SelfService/ ), we receive "403 - Forbidden: Access is denied" error page.

I understand this is all pointing to environmental aspects but is there any suggestions we can share with their IT on what to check? Their IT Team have confirmed they have not changed anything, they've checked all user profile permissions, access to the shares/inetpub folders, all ports are set on their firewall. Has anyone else had similar issues?

Many thanks,

Jamie