Hello Paul,
the way you are referring to is the most commonly used. The users usually find the GUI more practical. To change the settings you can move the Gateway HDB file to a GUI Client, update the settings and move the HDB file to the slave Gateway back. This is not elegant, but faster.


In order to achieve your purpose you should follow step by step this instruction:
If the Gateway machine does not have a graphical interface and/or is not accessible (e.g. it is in a different building), you should work on a normal client machine to create the Gateway database, which you will then copy to the Gateway machine when the configuration work is complete. Remove the existing database (named "HANSA.HDB") from the folder containing the Standard ERP client application, and then launch the application. Because there is now no database in the folder containing the application, a new database will be created.


You can file the extended guide on how to set a Gateway and a mail system up on the hansamanual.com site:
http://hansamanuals.com/main/mailnumber___60009/theconf___85/manuals/version___82/english/hwconvindex.htm?shortcode=HW0602SETTINGUP_External_Mail

Best Regard

Giuseppe L.
HansaWorld Team

The problem was that the server .exe name has an ending with "64". I have copied the slave executable to StandardERPServer64-Slave and it looks the main exe is trying to start the slave, but cannot. It's the same problem we have faced a few months ago (Slave exe thinks there is no RAM):


2018-04-30 08:52:27 Application shutdown properly...
2018-04-30 12:00:33 (-1) database cache may be max 80% of physical RAM (physical
RAM is: 0bytes, attempted to use: 100000bytes for DB cache)
2018-04-30 12:00:33 (-1) Exit


It may be related to our virtual server (Centos 7) configuration I guess, because the gateway runs on the Centos 7 on another virtual server.
Any more ideas?