• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 806
  • Last Modified:

Free Busy Stop Working

I'm running Exchange 2010 sp2 update 5 on three servers, 2008r2 sp1, and after three years of working great now freebusy has just stop working on two of my three servers, and it only affects users who's database resides on those two servers.  The two exchange servers where freebusy is not working I'll call A & B, the third server which is working fine I'll call server C.
 
Users who's database reside on server A can only see freebusy infomation of other users who's database resides on server A, the same is also true of Users on server B, they can only see freebusy information of other Users who's database resides on server B, however users who's database resides on server C can get freebusy information from all users on all servers.
 
Has anyone ran into this lately? Maybe a microsoft update bug?
 
Results from Autodiscover test:
 
Test-OutlookWebServices -ClientAccessServer "Server Name" -Identity:useraccount@###.com -TargetAddress "useraccount@###.com" | ft * -AutoSize –Wrap
 
When querying Availability for the recipient e-mail address "#######", the following error code and message were received: ErrorProxyRequestProcessingFailed:System.Web.Services.Protocols.SoapException: The server cannot service this request right now. Try again later.

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(). The request information is
 
ProxyWebRequest type = CrossSite, url = https://#######.#####.com/ews/exchange.asmx
0
Puke Foo
Asked:
Puke Foo
  • 2
  • 2
2 Solutions
 
AmitIT ArchitectCommented:
Server restart normally fixes this issue. Try server reboot and check again.
0
 
Puke FooAuthor Commented:
I did reboot one of the servers which resolved the issue, and I'm rebooting the other tonight, however having this happen out of the blue is irritating.  I tried restarting IIS, nothing, then I tried restarting Microsoft Exchange Active Directory Topology, nothing.  Very frustrating
0
 
AmitIT ArchitectCommented:
I faced similar issue long back and i opened case with MS for this issue. According to them, if user on Server A try to Fetch free/busy information for Sever B user and if it not fetched during a timeframe, server A marks Server B as bad server and caches it. After reboot only cache clears automatically.

So, you should check, if there are any network issue or high CPU utilization on servers during production hours.

Secondly, I suggest you to upgrade to Sp3 with RU1.

Note: There is disclaimer bug with RU1, so in case you are using disclaimer, you might face issue after updating to RU1, for fixing it, you can disable the rule and then call MS and get the interim update for free.

You can follow my article for upgrading to SP3, though i wrote it for SP2, however steps are same for Sp3 too.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_10389-Steps-for-Upgrading-Exchange-2010-SP1-to-SP2-with-RU3.html

Hope this helps
0
 
Puke FooAuthor Commented:
Thanks to both of you, I appreciate the help
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now