EWS api BusinessAddressInternal is too large and requires streaming.

Joyce Beck 31 Reputation points
2022-04-27T03:56:19.987+00:00

Hi,
I've attempted to use GetItem ews operation with IncludeMimeContent set as true. However, in the response I've got the following error:
<m:GetItemResponseMessage ResponseClass="Error">
  <m:MessageText>An internal server error occurred. The operation failed.</m:MessageText>
  <m:ResponseCode>ErrorInternalServerError</m:ResponseCode>
  <m:DescriptiveLinkKey>0</m:DescriptiveLinkKey>
  <m:MessageXml>
    <t:Value Name="InnerErrorMessageText">The object data is corrupted. The value of property [{00062004-0000-0000-c000-000000000046}:0x801b] BusinessAddressInternal is too large and requires streaming.</t:Value>
    <t:Value Name="InnerErrorResponseCode">ErrorPropertyTooBig</t:Value>
    <t:Value Name="InnerErrorDescriptiveLinkKey">0</t:Value>
  </m:MessageXml>
  <m:Items/>
</m:GetItemResponseMessage>
I'm wondering if there is any way to download the contact correctly. (eg. the business address field contains more than 100k bytes)
Thank you.
Best regards,
Joyce Beck

Exchange Server Development
Exchange Server Development
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Development: The process of researching, productizing, and refining new or existing technologies.
528 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Glen Scales 4,431 Reputation points
    2022-04-28T00:54:51.767+00:00

    That sounds like a bug or at least a limitation of that backend mime conversion, for a contact it would be trying to convert the Exchange Store Item to a vcard, it sounds like in your instance this might be an edge case base on what you have amount of text stored in that property. So your options would be log it as a formal support issue/bug with MSSupport and if you need to workaround the problem in the meantime select all the relevant contact properties yourself using GetItem and build the vcard. The Vcard format isn't that complex so while its a pain to do its probably the only fast resolution you will have to that problem unless you can fix the underlying property issue.

    0 comments No comments