search

OfficeDev / ews-managed-api

Other
585 stars 321 forks source link

Fail to export message #213

Open joewutaiwan opened 6 years ago

joewutaiwan commented 6 years ago

Grap API and EWS-managed API have different response behavior in a message.

By using graph API

GET messages/m_id

I could successfully get message information

But when I using EWS-managed API to export mail:

http code 500

An internal server error occurred. The operation failed.,
Index was outside the bounds of the array.

headers

< Cache-Control: private
< Transfer-Encoding: chunked
< Content-Type: text/xml; charset=utf-8
< Server: Microsoft-IIS/10.0
< request-id: be514a6b-3052-461a-bf17-bf9773ac681f
< X-CalculatedFETarget: AM0PR0102CU001.internal.outlook.com
< X-BackEndHttpStatus: 200
< Set-Cookie: exchangecookie=031f6bb16fa74cdeaf1b60600ffa5140; expires=Wed, 13-Nov-2019 06:51:53 GMT; path=/; HttpOnly
< X-FEProxyInfo: AM0PR0102CA0011.EURPRD01.PROD.EXCHANGELABS.COM
< X-CalculatedBETarget: AM0PR04MB5218.eurprd04.prod.outlook.com
< X-BackEndHttpStatus: 200
< X-RUM-Validated: 1
< x-ms-appId: af08ce07-1df9-4a39-b6e6-092ac934eb21
< x-EwsHandler: GetItem
< X-AspNet-Version: 4.0.30319
< X-BeSku: WCS5
< X-DiagInfo: AM0PR04MB5218
< X-BEServer: AM0PR04MB5218
< X-FEServer: AM0PR0102CA0011
< X-Powered-By: ASP.NET
< X-FEServer: HK0PR01CA0012
< Date: Tue, 13 Nov 2018 06:52:03 GMT

It is seems a general error, how should handle this?

Or it is a bug to export message?

Thank you for help

pkropachev commented 6 years ago

Could you show your piece of code and raw SOAP requests? BTW, if you are using Graph, then you've made the right choice.