Some items do not recall properly, error during move archive operations, or report errors when being checked by EVSVR. Items affected by this will return a MAPI error 0x8004010f.
0x8004010f = MAPI_E_NOT_FOUND
The following can be seen in a Dtrace of StorageOnlineOpns or EVSVR during the FixBody function:
CMessageExtractor::ExtractMAPIMessage _com_error exception. hr=<0x8004010f>
Investigation thus far has shown this to have two causes:
A. Affected items have a greater than default number of recipients where the local version of Outlook cannot view.
B. Current investigation has also shown that this can be caused by corruption related to the messages in question (e.g. a corrupt embedded attachment).
Increase the AttachmentMax and/or the RecipientMax registry values to a value above the default (2048)
See the following Microsoft articles per the current version of Outlook on the Enterprise Vault server.
Description of the Outlook 2003 post-Service Pack 3 hotfix package: January 23, 2008
You cannot open an .msg e-mail message file in Outlook 2003 after you install Office 2003 Service Pack 3
You cannot open an .msg e-mail message file in Outlook 2007 if the file contains many attachments or many recipients
Note: The Post Outlook 2003 SP3 Hotfix is Required (948073) is required in order to leverage the new registry values (948074)
Note: This fix is not intended to automatically increase the RecipientMax value as this is an MS registry key
This issue has been addressed as part of the following release:
Enterprise Vault 9.0.3 - Release Details
Enterprise Vault 10.0.1 - Release Details