Problems with Public Folder Replication


Topic Last Modified: 2005-07-21

If there is a problem with folder replication (especially replication of the hierarchy), use Exchange System Manager to check whether folders have replicated. Do not rely on the view provided by Outlook to determine whether folders have replicated. The problem might relate to permissions, not replication.

To help identify replication issues, configure diagnostic logging.

For detailed steps about how to identify public folder replication issues with diagnostics logging, see How to Identify Public Folder Replication Issues with Diagnostics Logging.

If replication messages are not being sent or received, check that normal e-mail routing between the servers works.

For more information about troubleshooting public folder replication issues, see Microsoft Knowledge Base article 842273, "How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003."

This problem could have one of the following causes, each of which has its own solutions:

  • Public folder stores do not have e-mail addresses:

    • Check that the Recipient Update Service has stamped the mail attributes onto the public folder store's directory objects correctly.

    • In mixed Exchange Server 2003 and Exchange Server 5.5 organizations, check that Exchange Server 5.5 can access the directory entries for the Exchange Server 2003 public folder stores, and that Exchange Server 2003 can access the directory entries for the Exchange Server 5.5 public folder stores.

  • There is no route for mail to follow:

    • Check that normal mail traffic can flow between the servers.

    • If the replication message goes over an Exchange Server 5.5 Internet Mail Connector (IMC), check that the ResolveP2 registry key is set to 1. This registry key is located at:


      Check also that the Exchange Server 5.5 Public Information Store object exists in the Active Directory Configuration container and has a valid X.400 proxy address. (You can use ADSI Edit or the LDP utility to check attribute values.)

  • Transport links are restricted to disallow system messages:

    • Check that there is a route for system messages between the servers. Winroute.exe indicates whether there are restrictions on the links.

The backfill can take a long time when a new server is installed and the initial status request gets lost or goes to a server that also has no knowledge of the hierarchy. To remedy this, make a change to the hierarchy on another server and check that it replicates through correctly. The server should backfill within 24 to 48 hours.

If a server does not appear to be backfilling, check whether new folders that have been added to other servers replicate as part of hierarchy replication to the backfilling public folder store. If they do replicate correctly to the backfilling public folder store, the server determines that it is not synchronized and writes an entry into the backfill array. Backfilling could take two or three days to complete.