The New-MailboxImportRequest cmdlet does not import all messages in a .pst file in the old American National Standards Institute (ANSI) format in a Microsoft Exchange Server 2010 environment. Additionally, when you run the Get-MailboxImportRequestStatistics -id <mailboxname\requestname> -includereport | fl > report.txt command to generate the import log, you receive the following error message in the log file:
Note This issue also occurs if you run the Exmerge.exe utility to create a .pst file, and then run the New-MailboxImportRequest cmdlet to import the .pst file into a mailbox.
A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox. <baditem errorType="MapiExceptionInvalidEntryId" errorCode="0x80040107" flags="0x00000000" id="ID">
To work around this issue, use one of the following methods:
- If you have a few .pst files to import, you can manually import email messages from the old .pst file into the new Unicode .pst file by using Outlook 2010. Then, run the New-MailboxImportRequest cmdlet to import email messages in the new Unicode .pst file into mailboxes that are located in the Exchange Server 2010 environment.
- Import messages in the .pst file by using a cross-forest mailbox move operation.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the New-MailboxImportRequest cmdlet, visit the following Microsoft TechNet website:
Article ID: 2513723 - Last Review: Jul 28, 2011 - Revision: 1