Microsoft KB Archive/260330

= XADM: Public Folder Hierarchy and Content Is Not Being Replicated Across Routing Groups =

Article ID: 260330

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q260330



SYMPTOMS
Newly created folders and content of old public folders may not be correctly replicating across the routing group although the replication time period may have passed. The Event Log shows no errors.



CAUSE
Replication messages may be sent out; however, they are not being received by the destination servers.



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 &quot;Max.&quot;
 * 2) Enable Message Tracking on Sending1.
 * 3) On another server (Receiving1), increase the logging level of the Replication Incoming item to &quot;Max.&quot;
 * 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  @ .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, &quot;Failed to connect to remote server.&quot;
 * 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):

An outgoing replication message was issued.

Type: 0x2

Message ID: 1-2A4EE

Database &quot;First Storage Group\PubStore&quot;

CN min: 1-2A4E9, CN max: 1-2A4EC

RFIs: 1

1: 1-246FA,1-1,28

IPM_SUBTREE\Boris's Folder

IDCN Deleted:

{0)

Keywords: kbprb KB260330

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.