Unable to retrieve Free/Busy information for some Office 365 mailboxes. Event ID: 4002; Source: MSExchange Availability;

by Oleg

Problem:

If you running Hybrid Environment or just trying to share free/busy information between your on-premise Exchange Organization and Office 365 you may experience that free/busy information for some mailboxes which were recently moved to O365 is not available. Please note that problem does not affect free/busy from on-premise to O365, if you cannot get free/busy for on-premise mailboxes – it must be another issue.

In addition you may see error similar to following in Application Event Log of your Hybrid server:

Event 4002, MSExchange Availability
Process 4192: ProxyWebRequest FederatedCrossForest from S-0-0-00
-0000000000-0000000000-000000000-0000 to https://server_name.outl
ook.com/EWS/Exchange.asmx/WSSecurity failed. Caller SIDs: WSSecur
ity. The exception returned is Microsoft.Exchange.InfoWorker.Comm
on.Availability.ProxyWebRequestProcessingException: System.Web.Se
rvices.Protocols.SoapException: An internal server error occurred
. The operation failed.


E4002_1

Cause:

That issue is caused by Office 365 Autodiscover service which returns incorrect endpoint for calendar sharing for some mailboxes.

Solution:

In order to fix the issue you need to configure TargetSharingEpr property in Organization relationship in your on-premise organization. It will force connection directly to correct O365 endpoint without using Autodiscover.

Use following command:

 Set-OrganizationRelationship -Identity "On Premises to Exchange Online Organization Relationship" -TargetSharingEpr "https://outlook.office365.com/ews/Exchange.asmx"

“On Premises to Exchange Online Organization Relationship” is default name for on premise to O365 relationship. It could have different name if you not using Hybrid Configuration Wizard.

That will fix the issue and all O365 mailboxes free/busy information should be accessible from on-premise.

2 thoughts on “Unable to retrieve Free/Busy information for some Office 365 mailboxes. Event ID: 4002; Source: MSExchange Availability;”

  1. Hello, Thanks for the tips, it saved my day.
    Although I had bit diferent error :

    Process 9672: ProxyWebRequest FederatedCrossForest from S-X-X-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXXX to https://dbxprdXXX.outlook.com:443/EWS/username..domain.mail.onmicrosoft.com/Exchange.asmx/WSSecurity failed. Caller SIDs: WSSecurity. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: Proxy web request failed. —> System.Net.WebException: The request failed with HTTP status 400: Bad Request.

    And

    Process 11004: ProxyWebRequest FederatedCrossForest from S-X-X-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXXX to https://outlook.office365.com:443/EWS/username..domain.mail.onmicrosoft.com/Exchange.asmx/WSSecurity failed. Caller SIDs: WSSecurity. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: Proxy web request failed. —> System.Net.WebException: The request failed with HTTP status 404: Not Found.

    Using your command instantly solved random free/busy issue from onpremise to online.

Comments are closed.