Versions / Builds AffectedGFI MailEssentials 2014 R2
Problem SummaryAfter upgrade, EmailSecurity updates failing on GFI MailEssentials 2014 R2
TT / JIRAID2349
How to IdentifyThe following points identify the issue:
1. The AutoUpdate log file shows an error similar to the below:
"error ","AutoUpdate","error: ReadConfig() exception: System.Runtime.Remoting.RemotingException: Requested Service not found
;Server stack trace:
; at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
;Exception rethrown at :
; at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
; at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
; at MEC.ConfigurationServices.ConfigurationService.Read(String strRuleID)
; at MEC.AutoUpdate.AuDriver.ReadConfig(Hashtable parm)"
"error ","AutoUpdate","error: Failed to read config"
2. The RemotingHelper log file shows:
"error ","RemotingHelper","Error during GetHashTablePollComponentsStatus: No connection could be made because the target machine actively refused it 127.0.0.1:8015"
3. Netstat does not show all GFI MailEssentials ports on listening
Workaround / Fix DetailsMake sure that the 3 GFI MailEssentials ports set in Switchboard are reflected in the MEC.AutoUpdate.AuSvc.exe.config file.
Also, as a more general approach, searching the whole installation folder (including .xml and .config files) for the old ports used in the previous version of MailEssentials (8013, 8021) and checking the registry, can help to discover files which were not correctly updated by the upgrade process in order to prevent further issues.
Required ActionsAttach article and troubleshoot as above.