MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Free busy not visible with Federated Domains – Exchange 2010

After setting up federation for a new domain, free busy wasn’t visible older Federated domains.

While troubleshooting, we saw event id: 4002 as below:

Log Name:     Application

Source:        MSExchange Availability

Date:         5/14/2013 9:23:50 AM

Event ID:     4002

Task Category:     Availability Service

Level:        Error

Keywords:     Classic

User:         N/A

Computer:     Name of Computer

Description:

Process 3260: ProxyWebRequest CrossForest from S-1-5-21-823518204-1303643608-725345543-4514 to https://FEDERATED-DOMAIN/ews/exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. 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.EndGetMailTips(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.MailTips.MailTipsApplication.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 = CrossForest, url = https:// FEDERATED-DOMAIN /ews/exchange.asmx Mailbox list = <name of user in federated domain>SMTP:Federated domain email address, 51552735 SMTP:email address from our domain—> System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. 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.EndGetMailTips(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.MailTips.MailTipsApplication.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()

We then ran the command below to refresh metadata and Booooooom!! Issue was fixed in less than 5 minutes:

Get-FederationTrust | Set-FederationTrust –RefreshMetadata

This command needs to be run from powershell on the source and destination domains that has Federation setup. It ran for less than a minute for us and free busy was visible immediately.

This requires no reboot.

Ratish Nair

Microsoft MVP

Team @MSExchangeGuru

One Response to “Free busy not visible with Federated Domains – Exchange 2010”

  1. Jesse Houwing Says:

    We ran into this issue with a different cause, I want to share it here because when searching for the error message this post and a post on TechNet come up, but not the KB Articles that eventually helped us solve the issue.

    I detailed the steps and the KB articles in this answer on StackOverflow: http://stackoverflow.com/a/25672613/736079

Leave a Reply

ad

Categories

Archives