We have two servers - these host both the HTML5 client (via Access Anywhere) and a simple Remote Desktop client for PlantSCADA 2023. Access Anywhere was working well - but then we added the two servers to a Remote Desktop Collection / Broker to provide a better level of redundancy / load balancing.
This breaks Access Anywhere - as it will (~50% of the time) redirect a new connection to the 'other' server, which fails. I'm not clear on what is happening in the background, but I assume Access Anywhere is simply an RDP session wrapped in HTML5. So when the RDP session is established, the Remote Desktop Services attempts to distribute the load to the 'other' server. The Access Anywhere logs confirm this:
23/10/25 11:10:08.787 | 23424 | [SESSION] Session #9 will be redirected to OTHERSERVER
23/10/25 11:10:08.789 | 23424 | [SESSION:4] Session #9 : DoTerminateSession called by the terminal server
| Reason:
23/10/25 11:10:10.294 | 29072 | [SESSION] Session #9 terminated by TERMINAL SERVER. Elapsed time: 00:02.079 Active sessions: 2 (top=3)
Any ideas if this is something that I can fix, or does the product itself need to be improved?
