Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, May 24, 2019 5:28 PM
Hi,
I have Hybrid setup between Exchange 2016 and Office 365, in the event viewer appears this error with ID: 4002 Availability Service.
Any idea of what could cause this error?
Process 7228: ProxyWebRequest FederatedCrossForest from S-1-5-21-1632022391-3521142072-901748847-10479 to https://outlook.office365.com/EWS/Exchange.asmx failed. Caller SIDs: OAuth. 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.
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.EndGetUserPhoto(IAsyncResult asyncResult)
at Microsoft.Exchange.InfoWorker.Common.UserPhotos.UserPhotoApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService 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: SVR-EX-MB LID: 43532. 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.
All replies (5)
Monday, May 27, 2019 6:33 AM
Apart from the Event ID 4002, did the users encounter any issue?
I have heard that such event ID might be generated if hybrid free/busy lookups fail in Exchange 2016 CU8.
So first please ensure that your Exchange servers are up-to-date (CU12).
If so, confirm if all the on-premises/online users got the issue, if issue just occurs for some of them, compare the mailbox attributes of the problematic ones with the working ones, check if the target address are correct for the on-premises mail users.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Wednesday, May 29, 2019 9:54 AM
Just checking in to see if above information was helpful. Please let us know if you would like further assistance.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Monday, June 3, 2019 5:01 PM
Hi.
Thanks for the information Manu, in my Exchange server 2016 I have the CU4.
It is necessary to update to the CU12, with this update will stop receiving the error messages?
Is there any note or reference to this?
Tuesday, June 4, 2019 9:57 AM
Hi.
Thanks for the information Manu, in my Exchange server 2016 I have the CU4.
It is necessary to update to the CU12, with this update will stop receiving the error messages?
Is there any note or reference to this?
It is necessary to install the latest update, even if we don't encounter any issue.
Besides, did you confirm the following as I said?
======================
If so, confirm if all the on-premises/online users got the issue, if issue just occurs for some of them, compare the mailbox attributes of the problematic ones with the working ones, check if the target address are correct for the on-premises mail users.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Tuesday, June 18, 2019 12:34 AM
Hi.
I already have several weeks with this error and I have no report of any user who has problems with the operation of their mailboxes.
Isn't there a service that verifies the connection to Office 365?, how can I verify the service or perform any connection tests to this url?: https://outlook.office365.com/EWS/Exchange.asmx.