EWS Error Codes
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'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.
ErrorItemNotFound
Problem: While archiving email from a Microsoft Exchange server or Office 365 the following error occurs:
Microsoft Exchange Server was unable to complete the task. Details: The specified object was not found in the store. EWS Error Code: ErrorItemNotFound.
This error may occur under different circumstances.
1: It mostly occurs when the Outbox folder is being archived. MailStore first retrieves a list of message IDs of a folder, then it fetches the message headers belonging to these IDs. Since a message is usually only in the Outbox folder for a very short period of time, the message is already gone, when the headers should be fetched.
Solution: Exclude the Outbox folder from being archived. The messages are archived from the Sent Items folder.
2: You are using a load balancer in front of your Exchange servers. Due to the replication mechanism, the mailbox databases on the Exchange servers are not always identical. MailStore tries to fetch messages headers of IDs which have been received from another server, which are not present on the currently queried server.
Solution: Configure the archiving profile to connect directly to one of the Exchange servers instead of connecting to the load balancer, or make sure the load balancer is not switching between servers during a session.
Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 10 by modifying the global property public.arcclient.skipEwsErrorItemNotFound by executing the following command in MailStore's Management Shell:
store-setprop --name="public.arcclient.skipEwsErrorItemNotFound" --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.
ErrorVirusDetected
Problem: While archive email from a Microsoft Exchange Server an EWS error with error code ErrorVirusDetected occurs.
Solution: An Exchange integrated antivirus software prevents the delivery of the requested message to MailStore. Therefore, the email could not be archived successfully. Due to false-positives of antivirus programs, it is advised to manually review the corresponding message before deleting it from the mailbox.
Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8.1 by modifying the global property public.arcclient.skipVirusDetected by executing the following command in MailStore's Management Shell:
store-setprop --name="public.arcclient.skipVirusDetected" --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.
