Forum Discussion
EWS with oAuth "An internal server error occurred. The operation failed."
The error message is extremely unhelpful and why is it needed is a mystery, but al least it's solved.
- MaloAug 26, 2022Copper Contributor
We have similar problem these days. Getting back the same error which tell nothing.
However, we already use the header "X-AnchorMailbox". Strange is that the error is not permanent but occurs occasionally (these days quite often). Retry after few minutes usually passes.
- chad512Aug 26, 2022Copper Contributor
We also already use `X-AnchorMailbox` and still get the same errors.
- prestonsbutlerAug 26, 2022Copper Contributor
Also using the x-anchorMailbox, and still getting the same problem. It is erroring on the finditems call.
</Trace>
2022-08-26 09:29:45.399 [(T06) VSLLC:RestoreArchive:AsProcess08:Schedule(10):Exch] - [TraceFlags.EwsResponse]
<Trace Tag="EwsResponse" Tid="6" Time="2022-08-26 14:29:45Z" Version="15.00.0913.015">
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="15" MinorVersion="20" MajorBuildNumber="5588" MinorBuildNumber="3" Version="V2018_01_08" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" />
</s:Header>
<s:Body>
<m:FindItemResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<m:ResponseMessages>
<m:FindItemResponseMessage ResponseClass="Error">
<m:MessageText>The mailbox operation failed.</m:MessageText>
<m:ResponseCode>ErrorInternalServerError</m:ResponseCode>
<m:DescriptiveLinkKey>0</m:DescriptiveLinkKey>
</m:FindItemResponseMessage>
</m:ResponseMessages>
</m:FindItemResponse>
</s:Body>
</s:Envelope>
</Trace>