Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

This issue occurs after you import a .pst file that contains public folders from Microsoft Exchange Server 2003 to Microsoft Exchange Server 2010. The event log resembles the following:

Log Name: Application
Source: MSExchangeIS Public Store
Date: Date & Time
Event ID: 3091
Task Category: Replication Errors
Level: Warning
Keywords: Classic
User: N/A
Computer: Computer
Description: Error 0x8004010f occurred while processing an incoming replication message.

Cause

This issue occurs because the .pst file that contains the public folders has the PR_EXTENDED_ACL_DATA property. However, the property cannot be recognized and processed by Exchange Server 2010. Therefore, the public folder replication fails.

Resolution

To resolve this issue, install the following update:

Update Rollup 9 for Exchange Server 2010 Service Pack 3

Workaround

To work around this issue, before you import each .pst file to Exchange Server 2010, open the .pst file, and remove the PR_EXTENDED_ACL_DATA property by using the Microsoft Exchange Server MAPI Editor (MFCMAPI) utility.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about the publish folder replication, see Understanding Public Folder Replication in Exchange Server 2010.

For more information about the MFCMAPI utility, see Microsoft Exchange Server MAPI Editor.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×