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.
Updated instructions for use with Message Relay
- Do not run System Five as Administrator. The clientname environment variable is not present.
On the Remote Computer: (Computer that connects to the network Via RDP / Terminal Services)
- Create a shortcut for the POS Device manager on the desktop. The POS Device manager is in:
- in C:\system5\bin\WindwardPOS.exe
- Right-click on the POS Device Manager icon you created on the desktop, and click on “Run as administrator” on the pop-up menu.
- The POS Device Manager will be running down on the taskbar. It is the little blue square with the gold palm tree on it. If you don’t see it there, click on the ^ on the taskbar and you will see it in the pop-up.
- Click on the icon in the taskbar to open the POS Device manager.
- Now click on the right arrow at the top of the POS Device Manager screen till you see the Remote Desktop button and click on it.
- Uncheck the checkbox next to Enable Remote Desktop Devices if it is currently checked. If it is checked you will not be able to change any settings on this screen.
- Set the Connection Mode to Connect – Server has fixed external IP
- Set your Server IP in the Server field.
- Set the port number to 6000, plus the System Five Terminal number they will be using. Terminal 1 will use port 6001, Terminal 2 will use 6002, terminal 11 would be 6011, etc.
- Set the Password to windwardremotepos . The Password needs to be at least 15 characters and can be the same for all terminals.
- Once you have made these changes, put a checkmark in the checkbox next to Enable Remote Desktop Devices.
- You will need to close the POS Device manager and then double click the icon on the desktop to restart it.
On the Server (RDP Session)
- Open System Five and on the login screen, select the correct terminal for the tablet or workstation you are setting up.
- For station 1 select terminal 1 from the terminal dropdown.
- Log in.
- From the navigator window, click on Setup Tools, then Setup Wizard.
- In the Setup Wizard, scroll down on the left-hand window till you see Point of Sale Devices
- Click on Device Options
- Click to select the radial button next to Remote - Server Listens for Client
- In the Port field, set the port number to 6000 plus the System Five Terminal number you are logged into. Terminal 1 will use port 6001, Terminal 2 will use 6002, terminal 11 would be 6011, etc.
- Set the Password to windwardremotepos . The Password needs to be the same one you used on the POS Device Manager and has to be at least 15 characters. Again, it can be the same for all terminals.
- Leave the Client IP field blank.
- Click on the button that says Restart TCP/IP Socket.
- Restart System Five and log in on the correct terminal for the workstation or tablet you are working on.
- Now go back to the desktop on the workstation or tablet and open the POS Device manager. If it is currently open, close it and open it again.
- Check the Remote Desktop button and you should see a green light if everything is working.
- If it is red, then a setting is wrong, or System Five is not open in the remote session on the server.
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.
- To open the POS Device Manager, click the POS Device Manager icon in your lower right hand Windows tray. Navigate
- Using the right arrow button in the top tab control, click through the tabs starting with General
- You may need to click several times until you see the Events tab.
- Click the “Events” tab to view connection information.
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.
- Open a Command Prompt by clicking on the start menu and typing “Command Prompt”.
- Type Ping with the remote session's IP address (example: ping 192.168.0.47)
- If you can ping the IP address successfully, try with the port number behind it (example 192.168.0.47:6001).
- If this doesn't give you the same response, the port may not be open in the firewall or router.
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
Remote Connection Closed
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.
Workstation Name is not Guacamole
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.
Local COM Communication Issues
The POS Device Manager uses COM to communicate.
If receiving an “Exception eOleSysError in module WindowardPOS.exe at xxxxxxxx. Error accessing the OLE registry.” message as seen below. Follow the instructions in this article to resolve.
The first time you log in to a freshly installed Windward System5 on a Windows 10 computer, you will get the error above. This means that 1 of the software components (WindwardPOS.exe) is not properly registered in Windows.
WindwardPOS Device Manager is a small application that comes with the software that handles some of the POS devices like (Pole / Customer Display, Cash Drawer, etc). So this is an important application for front tills or cash registers. It may not be needed for back-office computers but we should really fix the error and it's easy.
Method 1: Use the ARGUMENT "/regserver"
- Right-click on the System5 shortcut on the desktop
- Select PROPERTIES
- On the TARGET: field, go to the very end of it, create 1 space then /regserver
- Click on APPLY button, then OK
- Now run System5 as an administrator and login
System5 should not load or open, if it does then this did not work. What it does is simply register System5 in the windows registry. Then you can take out “/regserver” from the shortcut and run System5 normally.
Method 2: Toggle WindwardPOS.exe application to run as an administrator for all users
- Right-click on the System5 shortcut on the desktop
- Select “Open file location”. This will take you straight to the directory of System5 installation files
- Locate “WindwardPOS.exe, right-click on it and select PROPERTIES
- Switch to COMPATIBILITY tab
- Click “Change setting for all users” button at the very bottom
- You will then get a 2nd window where you can enable “Run this program as an administrator”
- Click APPLY, OK & OK to close all window and log in to System5
NOTE: You will get another error pop here but that's OK, we are expecting that. Just click on the “YES” button and logout of System5.
- Now go back to the System5 installation directory
- Right-click on WindwardPOS.exe
- Change setting for all users button
- Uncheck “Run this program as an administrator
- Click APPLY, OK & OK to close all window
- Log back into System5 and the error should be fix