Graph API Error Codes - Revision history

Cstelzmann: /* text does not support structured data */

2026-04-09T12:18:48Z

text does not support structured data

Ltalaschus at 09:46, 9 April 2026

2026-04-09T09:46:16Z

Ltalaschus: Created page with "== ErrorMimeContentConversionFailed == '''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs. '''Sol..."

2026-04-09T09:24:14Z

Created page with "== ErrorMimeContentConversionFailed == '''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs. '''Sol..."

New page

== ErrorMimeContentConversionFailed ==
'''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs.

'''Solution:''' This kind of Exchange internal server error is caused by an internal Exchange function that is not able to convert a message from Exchange's internal MAPI format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the Exchange server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.

Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8 by modifying the global property public.arcclient.skipMimeContentConversionFailed by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:

store-setprop --name="public.arcclient.skipMimeContentConversionFailed" --value="true"

'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the Exchange server.

[[de:Graph_API-Fehlermeldungen]]
[[en:Graph_API_Error_Codes]]

@@ Line 1: / Line 1: @@
 == text does not support structured data ==
-'''Problem:''' While archiving email from a Microsoft 365 server an Graph API error code ''text does not support structured data'' occurs.
+'''Problem:''' While archiving email from Microsoft 365 a Graph API error code ''text does not support structured data'' occurs.
 '''Solution:''' This kind of server error is caused by an internal Microsoft 365 function that is not able to convert a message from its internal format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the mail server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.

@@ Line 1: / Line 1: @@
-== ErrorMimeContentConversionFailed ==
+== text does not support structured data ==
-'''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs.
+'''Problem:''' While archiving email from a Microsoft 365 server an Graph API error code ''text does not support structured data'' occurs.
-'''Solution:''' This kind of Exchange internal server error is caused by an internal Exchange function that is not able to convert a message from Exchange's internal MAPI format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the Exchange server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.
+'''Solution:''' This kind of server error is caused by an internal Microsoft 365 function that is not able to convert a message from its internal format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the mail server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.
-Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8 by modifying the global property public.arcclient.skipMimeContentConversionFailed by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:
+Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed by modifying the global property ''public.arcclient.skipGraphContentConversionFailed'' by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:
-  store-setprop --name="public.arcclient.skipMimeContentConversionFailed" --value="true"
+  store-setprop --name="public.arcclient.skipGraphContentConversionFailed" --value="true"
-'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the Exchange server.
+'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the mail server.
 [[de:Graph_API-Fehlermeldungen]]
 [[en:Graph_API_Error_Codes]]