When exporting a message out of an Inbox using archive software or MFCMAPIx86, we get failures with the following errors:

On the Exchange Server Error ID 4999:

Watson report about to be sent for process id: 3312, with parameters: E12, c-RTL-AMD64, 15.00.1076.009, w3wp#MSExchangeServicesAppPool, unknown, M.E.S.W.M.<>c__DisplayClass3.<ReadMessage>b__1, System.NullReferenceException, da2f, unknown.

ErrorReportingEnabled: False

The MFCMAPI tool fails to export with the following error:

Error:

Code: MAPI_E_CALL_FAILED == 0x80004005

Function lpSource->CopyTo( 0, NULL, lpExcludedTags, lpProgress ? (ULONG_PTR)hWnd : NULL, lpProgress, lpGUIDLocal, lpDest, ulCopyFlags, &lpProblems)

File MAPIFunctions.cpp

Line 3014

Message Property values:

Property stream

Tag: 0x1000001E

Type: PT_STRING8

Property Name(s): PR_BODY, PR_BODY_A, ptagBody

Other Names: PR_BODY_W, PidTagBody

Err: 0x8004010F=MAPI_E_NOT_FOUND Property Name:  0x1000000A

Property stream

Tag: 0x10090102

Type: PT_BINARY

Property Name(s): PR_RTF_COMPRESSED, PidTagRtfCompressed, ptagRTFCompressed

DASL: http://schemas.microsoft.com/mapi/proptag/0x10090102

Value:  0x8007000E=MAPI_E_NOT_ENOUGH_MEMORY

Property stream

Tag: 0x1013001E

Type: PT_STRING8

Property Name(s): PR_BODY_HTML, PR_BODY_HTML_A, ptagBodyHtml

Other Names: PR_HTML, PR_BODY_HTML_W, PidTagHtml, PidTagBodyHtml, ptagHtml

DASL: http://schemas.microsoft.com/mapi/proptag/0x1013001E

Value:  0x8007000E=MAPI_E_NOT_ENOUGH_MEMORY

Things to note:

1. We have already checked permissions and the account has full access permissions.  We have tried two separate accounts.
2. We can export out other messages out of the same mailbox without any issue.
3. In many (possibly ALL) messages, even the messages that we are able to successfully export, we see the 0x8007000E=MAPI_E_NOT_ENOUGH_MEMORY value as well as Err: 0x8004010F=MAPI_E_NOT_FOUND.
4. We are running Outlook 2010 and MFCMAPI at 32bit.

Our archive provider will not provide support until we resolve this so any help is greatly appreciated!  Thank you!

• Edited by Deanbostedorjr Thursday, September 10, 2015 9:40 PM

As Winnie said above, you can use export/import method to accomplish this task in more easier way. Here is the tips to gather in-depth information : https://technet.microsoft.com/en-us/library/ee633455%28v=exchg.150%29.aspx

If you still unable to accomplish this task manually, you may also consider on this application available at (http://www.exchangemailboxtopst.org/) that could be an effective alternate solution in order to get this job done without having any interruption.

Hi,

Please confirm whether there is any other third-party mail related program installed in the machine which you are running MFCMAPIx86. If that is the case, please disable third-party program then run the MFCMAPIx86 to have a try.

Additionally, why not directly exporting messages by using Import and Export feature in Outlook instead of using MFCMAPIx86.

https://support.office.com/en-CA/Article/Export-Outlook-items-to-an-Outlook-Data-File-pst-14252b52-3075-4e9b-be4e-ff9ef1068f91

If there is any other event logs, please provide more error logs for further troubleshooting.

Regards,

I have tried exporting the message from the mailbox on machines with no 3rd party backup software and the errors are still produced in Exchange and during the MFCMAPI export.  I have tried using Outlook as well.

The export function in Outlook produces this error on the local machine where Outlook is installed (and no 3rd party software).

Event ID:  300

Microsoft Outlook could not make another copy of the item.  The original was either moved or deleted, or access was denied.

We've already ruled out permissions issues as we can move other mailbox items.  Also, this problem happens to multiple users and we cannot seem to identify a pattern as to why particular users or particular messages have this error. 

We must be able to export the messages using MAPI as our backup software (EMC SourceOne) uses MAPI to copy/export messages during archive. 

I'm using Outlook and MFCMAPI to troubleshoot a larger issue which is that messages will not export, not necessarily just to get the end result of the message moved from the mailbox.  Our shortcutting and archiving software (EMC SourceOne) uses MAPI to export messages and we've discovered that not only does SourceOne get the MAPI_E_CALL_FAILED == 0x80004005 error, but any MAPI tool that attempts to export the messages.  This seems to happen with many users and particular messages for those users.  We're having a hard time finding a pattern.