It appears EmailXtact code is checking what MAPI properties on the messages in exchange are reporting in attachment table and what EX has in its archive. If there is a mismatch that is where this message appears to be thrown. MessageID is already provided (485716A80DE17B7477945795 ) in the info you provided. Search for this MessageID, restore the message using EX Search plug-in to a PST file and then compare the attachment table between shortcutted message in mailbox and the one you restored, using MFCMAPI tool.
You will have to contact EMC support anyway to find a way out of it if you are running across large amount of such message. If it is only a few messages then when you will open message using outlook then shortcut should automatically restore to the exchange.
RKatwal
2 Intern
•
600 Posts
0
May 29th, 2012 00:00
Hi Mark,
It appears EmailXtact code is checking what MAPI properties on the messages in exchange are reporting in attachment table and what EX has in its archive. If there is a mismatch that is where this message appears to be thrown. MessageID is already provided (485716A80DE17B7477945795 ) in the info you provided. Search for this MessageID, restore the message using EX Search plug-in to a PST file and then compare the attachment table between shortcutted message in mailbox and the one you restored, using MFCMAPI tool.
You will have to contact EMC support anyway to find a way out of it if you are running across large amount of such message. If it is only a few messages then when you will open message using outlook then shortcut should automatically restore to the exchange.
Hope this helps.
Best regards,
Rajan