Hi Margaret,

What version and patch level are you on? It always helps to include this in forums. What are you doing when you receive this error?

We are on version 11, patch 11.

The user was going to a landing page when this happened.  Still sitting on the menu.

I have the same error on 12.0.21 on one node of a 5 syracuse cluster with haproxy on front. Only on the IE browser. Not able to connect from one of the nodes... This seams to me something related to the browser itself.  message is "message from webpage - no boundary "

solved in one minute!completely deleted the browser cache and the error just gone away... :-)

The issue has been reported in the past other browsers like Firefox or IE and has seemed to been occurring as a result of pop up blocking mechanisms on the browser as well as Oauth2 redirection. Ideally, you want to use Google Chrome moving forward. 

Hi, Even if we are using Google Chrome we are facing the same issue. X3 is on V12 and Patch 19

How did you solve it? It happens to me after a cut of the session. I killed the zombie session but still happens. How to delete the browser chache?? Thanx

Here's an article on clearing browser cache and cookies. 

https://support.google.com/accounts/answer/32050?

MC_SEI - What version of Syracuse are you on? Are you on the latest version?

Yes, The latest one, but suddenly the problem disappeared! Thanks

Context:

X3 v12p33

Using Syracuse cluster. 2 servers. Both can talk to each others at first port 8124 TCP. This was set: www.sagecity.com/.../is-syracuse-s-load-balancer-messing-with-your-external-load-balancer-learn-to-turn-it-off.

Load Balancer on front.

Case:

Already cleared cache.

From a common DNS name at load balancer, login to Sage X3.

On login, got a popup saying "No boundary"

Screen goes white.

Refresh will kick back to login screen.

Repeat to cause issue again.

Change browser and try again, same issue.

My browser:

When I manually access to the syracuse node directly through localhost, there is no issue.

Found this Sage KB: 107812

Restarting syracuse server daily is not a feasible solution.

That error goes away for me(V12) if I leave "Remember me on this device" unchecked. I use Chrome.

For AWS ALB, use duration-based stickiness: docs.aws.amazon.com/.../sticky-sessions.html

I cannot seem to access the KB article, is there a new link?  Also I believe we're having this same issue, did you ever find a way to resolve it?

I am using AWS and have an external load balancer in front of my syracuse cluster so the external load balancer must have sticky session: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/sticky-sessions.html

I am not sure on your case so no comment here.