Solved

Free Busy Stop Working

Posted on 2013-06-21
4
751 Views
Last Modified: 2013-06-21
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
Comment
Question by:Puke Foo
  • 2
  • 2
4 Comments
 
LVL 41

Assisted Solution

by:Amit
Amit earned 500 total points
ID: 39266909
Server restart normally fixes this issue. Try server reboot and check again.
0
 

Author Comment

by:Puke Foo
ID: 39266935
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
 
LVL 41

Accepted Solution

by:
Amit earned 500 total points
ID: 39266945
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
 

Author Closing Comment

by:Puke Foo
ID: 39266968
Thanks to both of you, I appreciate the help
0

Featured Post

Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

Join & Write a Comment

Suggested Solutions

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.

747 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now