System Five Add-Ons & Integrations help simplify the way you do things.
Our catalog of services has topic-based, role-based, or technical plans that can help you maximize your software investment.
Copyright © 1984-present
Windward Software Systems Inc.
All Rights Reserved.
Privacy Policy
This is an old revision of the document!
The Remote POS Device Manager (Sometimes referred to as the Remote Message Relay or RMR for short) is required to connect local devices to System Five on Cloud.
The port number you use should ALWAYS be based on your System Five terminal number.
If you can't get the remote POS Device manager to communicate with System Five on Cloud. Review the Events tab for hints or error messages that may indicate what the issue is.
The POS Device Manager communicates using TCP ports in the 6001 - 600X range. If a software or hardware firewall is blocking those ports it will not be able to communicate with System Five on Cloud.
Use these steps to test that the ports (6001 - 600X) are open on the workstation and the remote desktop session.
Refer to the image below for example and response of a blocked port.
If you are getting an error when using the Remote POS Device Manager (RMR) on the host side with the words JsonArrayPool it means that the systemfive_saas.exe executable you are running does not have a corresponding systemfive_saas.exe.config
If running on the training data systemfive_training_saas.exe a systemfive_training_saas.exe.config must exist. This can be a copy of the other systemfive*.config files and renamed.
If running a second company, the executable could be named systemfive_[companyname]_saas.exe, so a systemfive_[companyname]_saas.config or training will be systemfive_[companyname]_training_saas.exe
If the following error is found in the RMR Remote POS Device Manager Events tab. “Remote Connection Closed: The server closed the connection with the following error: Connection closed with an error. “RelayTokenInvalidException: Connection Identifier token not valid”. The data/time of the connecting workstation differs from the System Five on Cloud servers by more than 5 minutes.
Sample Events tab details
12:29:13 PM MessageRelay: ----------------------------------------------------- 12:29:13 PM MessageRelay: Retrying in 15 seconds, retry attempt 41 12:29:28 PM RemoteRelayService: DLL Loaded 12:29:31 PM RemoteRelayService: Remote Connection Established 12:29:31 PM MessageRelay: Message Relay failed to connect: Remote Connection Closed: The server closed the connection with the following error: Connection closed with an error. RelayTokenInvalidException: Connection Identifier token not valid 12:29:31 PM MessageRelay: ----------------------------------------------------- 12:29:31 PM MessageRelay: Retrying in 15 seconds, retry attempt 42 12:29:46 PM RemoteRelayService: DLL Loaded 12:29:49 PM RemoteRelayService: Remote Connection Established 12:29:49 PM MessageRelay: Message Relay failed to connect: Remote Connection Closed: The server closed the connection with the following error: Connection closed with an error. RelayTokenInvalidException: Connection Identifier token not valid 12:29:49 PM MessageRelay: -----------------------------------------------------
The Remote POS Device Manager uses the date/time token from the servers in the System Five on Cloud data center. If the date/time of Windward System Five servers differs from the date/time of the connecting workstations by more than 5 minutes this error message is produced.
To resolve, have the customer update the date/time of the local workstation to be within 5 minutes of the System Five on Cloud server.
If the POS device manager does not connect. Check that your workstation is not named Guacamole (The same name given to Bastion sessions). The POS Device Manager will not connect through a Bastion session which is named Guacamole. Rename your connecting workstation to a different name than Guacamole will resolve this connection issue.
This error occurred when processing a gift card. The WindwardPOS.exe is out of date on the remote workstation. It should have a version (or date) greater or equal to the version on the server.
The POS Device Manager uses COM to communicate. If experiencing communication challenges such as opening the cash drawer, review this wiki.
If receiving an Exception EOleSysError on a new workstation installation. Follow this wiki.