Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the "New-MailboxImportRequest" cmdlet
Article ID: 2710975 - View products that this article applies to.
Consider the following scenario:
This issue occurs because the Microsoft Exchange Mailbox Replication service cannot find a correct code page for the conversion of PT_STRING8 MAPI properties.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2785908/ )Description of Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2
To work around this issue, import the ANSI .pst file by using Microsoft Outlook or convert the ANSI .pst file to a Unicode file before you run the New-MailboxImportRequest cmdlet.
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 ANSI format and the Unicode format, go to the following Microsoft website:
General information about ANSI, DBCS, and UnicodeFor more information about MAPI string properties, go to the following Microsoft website:
General information about MAPI string propertiesFor more information about how to import a mailbox by running the New-MailboxImportRequest cmdlet, go to the following Microsoft website:
Understanding mailbox import and export requestsFor more information about the New-MailboxImportRequest cmdlet, go to the following Microsoft website:
General information about the New-MailboxImportRequest cmdletFor more information about the PR_DISPLAY_NAME property, go to the following Microsoft website:
PidTagDisplayName Canonical property
Article ID: 2710975 - Last Review: December 14, 2012 - Revision: 4.0