The hierarchy of a new public folder database on an Exchange Server 2010 SP1 server is not replicated

You create a new public folder database on a Microsoft Exchange Server 2010 Service Pack 1 (SP1) server. However, the hierarchy is not replicated from other public stores to this new database. Additionally, the following events are logged in the Application log:

Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Description:
Unexpected replication thread error 80070057 on database "First Storage Group\Public Folder Store (<Server_Name>)".

EcReplFolderMessagesUnpack
EcReplMessageUnpack
FReplRcvAgent <xxx>

0f = ecNotFound-MAPI_E_NOT_FOUND

Event Type: Warning
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3089
Description:
Error 80070057< occurred while processing an incoming replication message on Public Folder Store "First Storage Group\Public Folder Store (<Server_Name>)".

Note The events are logged every time when the server tries to backfill the hierarchy.

This issue occurs because ReplidMap in the public folder database contains a zero GUID.

To resolve this issue, install the following update rollup: After you apply this update on all the computers that have public folder databases, follow these steps:

1. Unmount all public folder databases in the organization.
2. Run the following command on all the computers that have public folder databases in the organization:
   
   isinteg -s <server> -test replidguid -fix
3. Mount all public folder databases.

Notes

• The command must be run simultaneously on all the computers that have public folder databases in the organization.
• Do not follow these steps if there are any public folder servers that are not running Update Rollup 4 for Exchange Server 2010 SP1, such as Exchange Server 2003, Exchange Server 2007, or earlier versions of Exchange Server 2010.
• If you try to run the command on only a subset of computers that have public folder databases in the organization, public folder replication issues occur. Additionally, the issues cannot be resolved.

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