A customer reported that a previously working Riva server started to report connection errors for every target user. Examination of the crmex-log file revealed:
2013-05-13 16:47:43,354 ERROR [CTP-kbu #0] [1RF3HKFS36DC] Unable to connect to remote Exchange server. Connection Failed.
Omni.Connection.Ews.x86553da961a3d285: Unable to connect to remote Exchange server.
Connection Failed. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: Request failed.
Unable to connect to the remote server ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.50.177.24:443
An investigation revealed that the Windows system hosting Riva could resolve the URL specified in the connection and it did match the IP address that was returned with a NSLOOKUP. The customer was able to use a web browser to log in to OWA as the Riva connection user from the Riva server.
Customer finally determined that the issue resulted from implementing an Exchange CAS Windows Network Load balancing solution that Riva cannot connect to.
In the Windows system hosting Riva, the customer added a HOSTS entry to resolve the URL to the IP address of one of the CAS servers.
Article ID: 945
Last updated: 30 May, 2019