XADM: Public Folder Hierarchy and Content Is Not Being Replicated Across Routing Groups (260330)

MORE INFORMATION

Replication messages informing other servers in other routing groups may be sent, however, they are not properly arriving at the destination site. To test this, do the following:

1. On one server (Sending1), increase the logging level of the Replication Outgoing and Replication NDRs items to "Max."
2. Enable Message Tracking on Sending1.
3. On another server (Receiving1), increase the logging level of the Replication Incoming item to "Max."
4. On Sending1, create a new public folder.
5. Allow normal replication to take place (as defined by the Public Folder Replication schedule).
6. On Sending1, check the application event log for Event IDs in the range of 3011-3020.
7. After the replication message is sent, check the receiving server for a corresponding Event ID in the range of 3021-3030.
8. If the receiving server does not contain the specific Event ID and no notice of replication messages generates a non-delivery report (NDR), on Sending1, navigate to the Message Tracking Center in Exchange System Manager, and track messages sent from Pub-IS@domain_name.com.
9. If the last hop is the Categorizer, check the current status of the Routing Group Connector.
10. Display the queues; the queue for the Routing Group Connector between two servers is in a retry state.
11. Display the properties of the queue; the status reads, "Failed to connect to remote server."
12. Attempt to force connection.
13. If forcing the connection does not work, make sure that you can telnet to port 25 on the remote server and ping the remote server. The issue is most likely caused by an unstable connection between the two routing group servers.

The following is an example of a 3018 Event (outgoing replication message):