This behavior is consistent with a corrupted installation of GFI MailEssentials, caused by a blocked installer. ,11:30:27,692,1,"#000042AC","#00000046 ","warning","CentralizationConfiguration","Warning: TestConfigurationConnection.FAILED: System.Exception: Server is not set as a master System.InvalidOperationException: You can't enroll on a non-controller master at (CentralizationHost host, String loggedInUser) : You can't enroll on a non-controller master (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: \GFI\MailEssentials\Attendant\DebugLogs\CentralizationConfiguration.log ,11:20:30,829,1,"#000042AC","#0000003B","error ","CentralizationConfiguration","Error: SetCentralizationSettings - `1 Additionally, you see the following error in the log: With tracing enabled, you may see multiple engines failing. Testing the connection in the Multi-Server Setup interface on the Master and the Slave servers show no failures. Additionally, on the Master server, in the Multi-Install Network list, you may see multiple instances of localhost (127.0.0.1). 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |