We recently applied a role up patch to our Exchange environment and we've now lost the ability to unlock accounts with Netwrix ALE remote control. We are on Exchange 2010 SP3 roll up 11. According to the ALEService.log it sees Exchange and connects to it. It fails now with the the following response below:
ALEService.exe Warning: 0 : [TID: 18, Time: 2/4/2016 8:13:05 AM] REMOTE CONTROL: System.Net.WebException: The request failed with an empty response.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
at ESB2010.ExchangeServiceBinding.FindFolder(FindFolderType FindFolder1)
at ALService.RemoteControl.Listeners.ExchangeServerListener.GetMessages(RemoteControlSettings settings)
at ALService.RemoteControl.Listeners.DefaultMessageListener`1.OnDoWork(DoWorkEventArgs e)
ALEService.exe Information: 0 : [TID: 18, Time: 2/4/2016 8:13:05 AM] REMOTE CONTROL: Listener will be restarted after 00:01:00 minutes
I've verified that the service account has full control rights to the mailbox and ownership rights of it.
I finally got it working. Turns out that Netwrix ALE was not getting past my hardware load balancer for Exchange. I created a local host file on the server to points directly to an Exchange server rather than the load balancer. After that, ALE started working where I can remote unlock users again.