[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Exchange cross-site availability

Posted on 2014-12-05
1
Medium Priority
?
1,215 Views
Last Modified: 2014-12-12
Hello,

I have Exchange 2010 servers in two sites. Recently, users in Site A have been reporting that they can't see free/busy info for users in Site B. They get the hash lines with "The recipient's server could not be contacted" error. This doesn't happen every time and if you refresh the free/busy with ALT+K a few times, the free/busy will eventually populate. Users in Site B are having no trouble seeing free/busy for users in both sites.

Event ID 4002 appears on the CAS server in Site A, with the following text:

Process 3820: ProxyWebRequest CrossSite from S-1-5-21-4230717640-2408447126-919093004-1176 to https://SITEBCAS1.domain.local:443/ews/exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: The request failed with HTTP status 400: Bad Request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling():<No response>. The request information is ProxyWebRequest type = CrossSite, url = https://SITEBCAS1.domain.local:443/ews/exchange.asmx
Mailbox list = <Joe User>SMTP:Joe_User@domain.com, Parameters: windowStart = 11/26/2014 2:00:00 PM, windowEnd = 12/26/2014 2:00:00 PM, MergedFBInterval = 30, RequestedView = Detailed
. ---> System.Net.WebException: The request failed with HTTP status 400: Bad Request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
   --- End of inner exception stack trace ---
. Name of the server where exception originated: SITEACAS1. Make sure that the Active Directory site/forest that contain the user's mailbox has at least one local Exchange 2010 server running the Availability service. Turn up logging for the Availability service and test basic network connectivity.

There are two CAS servers at each site. I'm seeing event ID 4002 on both of Site A's CAS servers and the URL for both of SITE B's CAS servers appears in the error. So, I can't narrow this down to a single CAS server. I have tried rebooting the CAS servers and that didn't help. There have been no recent changes and this has previously been working fine.

Thanks,
JJ
0
Comment
Question by:Jamie McKillop
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 37

Accepted Solution

by:
Jamie McKillop earned 0 total points
ID: 40496593
We were able to figure this out. The cross-site proxy uses Kerberos authentication. We have WAN optimizers (Riverbed) that were interfering with the Kerberos authentication. Once we configured the WAN optimizers to not try to optimize the traffic between the CAS servers, the issue went away.

-JJ
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New style of hardware planning for Microsoft Exchange server.
The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question