Phone Lines icon GFI Support Home

Articles in this section

See more

Multi-server setting on slave gets disabled after some time

Author: Andrei Bogdan Apostol Updated

Overview

After updating to the latest version of GFI MailEssentials in a multi-server environment, after enabling the multi-server setting on the slave to connect to the master, the setting gets disabled after a while. Additionally, on the Master server, in the Multi-Install Network list, you may see multiple instances of localhost (127.0.0.1). Testing the connection in the Multi-Server Setup interface on the Master and the Slave servers show no failures.

Solution

With tracing enabled, you may see multiple engines failing. Additionally, you see the following error in the log:

<GFI MailEssentials installation path>\GFI\MailEssentials\Attendant\DebugLogs\CentralizationConfiguration.log

2020-09-06,11:20:30,829,1,"#000042AC","#0000003B","error  ","CentralizationConfiguration","Error: SetCentralizationSettings - System.ServiceModel.FaultException`1
[System.ServiceModel.ExceptionDetail]: You can't enroll on a non-controller master (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:;
System.InvalidOperationException: You can't enroll on a non-controller master;  at MailEssentialsClientService.MasterClass.MultiNodeService.Enroll(CentralizationHost host, String loggedInUser)

2020-09-06,11:30:27,692,1,"#000042AC","#00000046","warning","CentralizationConfiguration","Warning: TestConfigurationConnection...FAILED: System.Exception: Server is not set as a master
;  at MEC.Configuration.RemotingHelper.TestConfigurationConnection()"

This behavior is consistent with a corrupted installation of GFI MailEssentials, caused by a blocked installer. The solution is to reinstall the application on all the affected servers.

Download the same version of GFI MailEssentials as the one currently running in your environment. Links to all the versions are available in the Download Links for All Versions of GFI MailEssentials article.

Note

Before completing the process below, it is recommended to back up the configuration settings. Upgrading usually keeps the existing configuration in place. However, it is always good practice to have a backup of your MailEssentials configuration.

  1. Go to Control Panel.

  2. Locate MailEssentials and select Uninstall.

  3. After completing the uninstall process, locate the previously downloaded installer.

  4. Verify that the file is not blocked.

  5. Right-click on the installer and select Run as Administrator.

  6. Verify that the installer is pointed to the same install location as the previous installation and that the previous settings should be used.
    Once you have confirmed that the settings are the same, it is safe to delete the backup previously taken.

    Note

    If any of the settings are missing, refer to the Restoring a Manual Backup of MailEssentials article for information on how to restore the settings.

Testing

Reinstalling MailEssentials in your environment with the installer unblocked will allow the application to operate optimally. If the issue still persists, please generate the troubleshooting logs as follows:

  1. Make sure that you have tracing enabled.
  2. Wait for at least 30 minutes to gather enough information and for the issue to be reproduced.
  3. Run the troubleshooter:
    1. Start > Programs > GFI MailEssentials > Troubleshooter
    2. Follow the Log Generation Wizard for collecting the required and pertinent information.
    3. Select New Case when completing the log generation to attach the logs to a new case that will be automatically created, or open a support ticket manually and attach the logs to that ticket, so that the Support team can investigate the problem.

Related articles