Bei der Outlook Free Busy Abfrage zwischen Exchange 2010 SP3 CU19 in Domäne A zu Exchange 2016 CU8 in Domäne B gab es folgende Fehler:
Auf dem Exchange 2010:
Quelle: MSExchange Availability
Ereignis-ID: 4002
Prozess ‘4932’: Fehler bei ‘ProxyWebRequest CrossForest from S-1-5-21-3386154569-1807573594-3971606385-1119 to https://owa-q.bema-con.de/EWS/Exchange.asmx’. Anrufer-SIDs: NetworkCredentials. Die zurückgegebene Ausnahme ist ‘Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Web.Services.Protocols.SoapException: Interner Serverfehler. Fehler bei diesem Vorgang.
bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
bei System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling(). The request information is ProxyWebRequest type = CrossForest, url = https://owa-q.bema-con.de/EWS/Exchange.asmx
Mailbox list = <test mig>SMTP:test.mig@migbema-con.de, Parameters: windowStart = 26.02.2018 00:00:00, windowEnd = 09.04.2018 00:00:00, MergedFBInterval = 30, RequestedView = MergedOnly
. —> System.Web.Services.Protocols.SoapException: Interner Serverfehler. Fehler bei diesem Vorgang.
bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
bei System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
— Ende der internen Ausnahmestapelüberwachung —
. Name of the server where exception originated: OLD-EX01′. Stellen Sie sicher, dass der Active Directory-Standort/die Active Directory-Gesamtstruktur mit dem Benutzerpostfach mindestens einen lokalen Exchange 2010-Server aufweist, der den Verfügbarkeitsdienst ausführt. Aktivieren Sie die Protokollierung für den Verfügbarkeitsdienst, und prüfen Sie die grundlegende Netzwerkkonnektivität.
In der Outlook Protokollierung war folgender Fehler in dem Free Busy Log sichtbar:
2018/03/19 13:27:27.245: Getting ASURL
2018/03/19 13:27:27.245: URL returned from cached autodiscover: https://owa-old.bema-con.de/EWS/Exchange.asmx
2018/03/19 13:27:27.245: Request to URL: https://owa-old.bema-con.de/EWS/Exchange.asmx
2018/03/19 13:27:27.245: Request action: http://schemas.microsoft.com/exchange/services/2006/messages/GetUserAvailability
2018/03/19 13:27:27.245: Request XML: <?xml version=”1.0″?>
<q:Envelope xmlns:q=”http://schemas.xmlsoap.org/soap/envelope/”><q:Header><wsa:MessageID xmlns:wsa=”http://www.w3.org/2005/08/addressing/”>urn:uuid:146BDD7C-11EA-4B3E-BD47-555CDF88A5A3</wsa:MessageID></q:Header><q:Body xmlns:wsa=”http://www.w3.org/2005/08/addressing/”><ex12m:GetUserAvailabilityRequest xmlns:ex12m=”http://schemas.microsoft.com/exchange/services/2006/messages” xmlns:ex12t=”http://schemas.microsoft.com/exchange/services/2006/types”><ex12t:TimeZone><ex12t:Bias>-60</ex12t:Bias><ex12t:StandardTime><ex12t:Bias>0</ex12t:Bias><ex12t:Time>03:00:00</ex12t:Time><ex12t:DayOrder>5</ex12t:DayOrder><ex12t:Month>10</ex12t:Month><ex12t:DayOfWeek>Sunday</ex12t:DayOfWeek></ex12t:StandardTime><ex12t:DaylightTime><ex12t:Bias>-60</ex12t:Bias><ex12t:Time>02:00:00</ex12t:Time><ex12t:DayOrder>5</ex12t:DayOrder><ex12t:Month>3</ex12t:Month><ex12t:DayOfWeek>Sunday</ex12t:DayOfWeek></ex12t:DaylightTime></ex12t:TimeZone><ex12m:MailboxDataArray><ex12t:MailboxData><ex12t:Email><ex12t:Address>test.mig@migbema-con.de</ex12t:Address><ex12t:RoutingType>SMTP</ex12t:RoutingType></ex12t:Email><ex12t:AttendeeType>Required</ex12t:AttendeeType></ex12t:MailboxData></ex12m:MailboxDataArray><ex12t:FreeBusyViewOptions><ex12t:TimeWindow><ex12t:StartTime>2018-03-03T14:00:00</ex12t:StartTime><ex12t:EndTime>2018-04-02T14:00:00</ex12t:EndTime></ex12t:TimeWindow><ex12t:MergedFreeBusyIntervalInMinutes>30</ex12t:MergedFreeBusyIntervalInMinutes><ex12t:RequestedView>Detailed</ex12t:RequestedView></ex12t:FreeBusyViewOptions></ex12m:GetUserAvailabilityRequest></q:Body></q:Envelope>
2018/03/19 13:27:27.245: Sending request
2018/03/19 13:27:27.401: Request sent
2018/03/19 13:27:27.401: Response error code: 00000000
2018/03/19 13:27:27.401: HTTP status code: 200
2018/03/19 13:27:27.401: XML response:<?xml version=”1.0″ encoding=”utf-8″?><s:Envelope xmlns:s=”http://schemas.xmlsoap.org/soap/envelope/”><s:Header><h:ServerVersionInfo MajorVersion=”14″ MinorVersion=”3″ MajorBuildNumber=”382″ MinorBuildNumber=”0″ xmlns:h=”http://schemas.microsoft.com/exchange/services/2006/types” xmlns=”http://schemas.microsoft.com/exchange/services/2006/types” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”/></s:Header><s:Body xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”><GetUserAvailabilityResponse xmlns=”http://schemas.microsoft.com/exchange/services/2006/messages”><FreeBusyResponseArray><FreeBusyResponse><ResponseMessage ResponseClass=”Error”><MessageText>System.Web.Services.Protocols.SoapException: Interner Serverfehler. Fehler bei diesem Vorgang.
bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
bei System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
bei Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling(). The request information is ProxyWebRequest type = CrossForest, url = https://owa-q.bema-con.de/EWS/Exchange.asmx
Mailbox list = <test mig>SMTP:test.mig@migbema-con.de, Parameters: windowStart = 03.03.2018 14:00:00, windowEnd = 02.04.2018 14:00:00, MergedFBInterval = 30, RequestedView = Detailed
., inner exception: Interner Serverfehler. Fehler bei diesem Vorgang.</MessageText><ResponseCode>ErrorProxyRequestProcessingFailed</ResponseCode><DescriptiveLinkKey>0</DescriptiveLinkKey><MessageXml><ExceptionType xmlns=”http://schemas.microsoft.com/exchange/services/2006/errors”>Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException</ExceptionType><ExceptionCode xmlns=”http://schemas.microsoft.com/exchange/services/2006/errors”>5016</ExceptionCode><ExceptionServerName xmlns=”http://schemas.microsoft.com/exchange/services/2006/errors”>OLD-EX01</ExceptionServerName></MessageXml></ResponseMessage><FreeBusyView><FreeBusyViewType xmlns=”http://schemas.microsoft.com/exchange/services/2006/types”>None</FreeBusyViewType></FreeBusyView></FreeBusyResponse></FreeBusyResponseArray></GetUserAvailabilityResponse></s:Body></s:Envelope>
2018/03/19 13:27:27.401: XML response processed successfully
Dies ist scheinbar ein Bug in Exchange 2016 CU8. Nach der Installation von Exchange 2016 CU7 funktioniert die Cross Forest Free Busy Abfrage ohne Probleme.