Exporting archived items to original mailbox does not always replace shortcut/stub

Article:TECH179431  |  Created: 2012-01-20  |  Updated: 2013-11-11  |  Article URL http://www.symantec.com/docs/TECH179431
Article Type
Technical Solution


Environment

Issue



When exporting an archive back to the original mailbox some or all of the archived data does not overwrite the shortcuts/stubs. 


Error



No error occurs. A Dtrace will show the following, note the entry missing for shortcut deleted when unsuccessful and no errors.

Successful Shortcut Deletion

640 11:45:59.734 [9368] (MigratorServer) <9412> EV:M
CSaveset2::get_ContentHandlingName (Exit). hr=False [0x1]
641 11:45:59.734 [9368] (MigratorServer) <9412> EV:M
FixMessageProps: bSetRestoredDate = 1
642 11:45:59.765 [9368] (MigratorServer) <9412> EV:M
RestoreSaveset: - Shortcut deleted : 1
643 11:45:59.765 [9368] (MigratorServer) <9412> EV:M
CArchiveRestorer::RestoreSaveset (Exit) |Success  [0] |
644 11:45:59.890 [9368] (MigratorServer) <9412> EV:M
RestoreSavesets: - Number of Savesets processed : 1

Unsuccessful Shortcut Deletion

640 11:58:42.234 [8956] (MigratorServer) <5944> EV:M
CSaveset2::get_ContentHandlingName (Exit). hr=False [0x1]
641 11:58:42.234 [8956] (MigratorServer) <5944> EV:M
FixMessageProps: bSetRestoredDate = 1
642 11:58:42.265 [8956] (MigratorServer) <5944> EV:M
CArchiveRestorer::RestoreSaveset (Exit) |Success  [0] |
643 11:58:42.453 [8956] (MigratorServer) <5944> EV:M
RestoreSavesets: - Number of Savesets processed : 1

 


Cause



If the mailbox archive is exported to the original mailbox more than once, the MAPI attribute Entry-ID is modified the second time the item is archived again and therefore is not recognized as requiring removing on the second export to original mailbox.


Solution



WORKAROUND: Delete shortcuts/stubs manually in MS Outlook.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article. Symantec Corporation is committed to product quality and satisfied customers.

There are currently no plans to address this issue by way of a hotfix or cumulative hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com


Supplemental Materials

SourceETrack
Value2659277


Article URL http://www.symantec.com/docs/TECH179431


Terms of use for this information are found in Legal Notices