Jim,

        We have a similar environment and experienced a similar problem
with public folder replication.  We ( in consultation with PSS ) ended
up doing the following to try and narrow down where the problem was ... 

        Turn up diag logging to MAX for every 'Replication' setting and
also 'Non-Delivery Reports' ( this was done for the first test on the
Ex5.5 server in the site and the E2K bridgehead in the same site.  The
second test was done on the two bridgeheads in different sites ).  We
then created a new folder to force a hierarchy replication.  We then
checked for Event 3018 ( outbound replication message ) and Event 3028 (
inbound replication message ) to ensure that was working correctly.  We
then posted content to the folder to force content replication and
looked for Event 3020 ( outbound content replication ) and Event 3030 (
inbound content replication ) to ensure that was working OK.  Some other
Events to look for are 3014 / 3024 ( outbound / inbound backfill request
), 3019 / 3029 ( outbound / inbound backfill response ) and 3017 / 3027
( outbound / inbound status replication messages ).

        If this test is OK, there may be a problem with the system not
recognizing the content is out of date - you may need to trigger a
status request.  This is apparently more common when E2K is the
receiving server - due to changes in public folder behaviour between
Ex5.5 and E2K.  Check out KB articles 321082 and 813629 about forcing
E2K to send Status Request Messages.

Regards,

Paul.


-----Original Message-----
From: Becker, Jim [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, 23 December 2003 7:06 AM
To: Exchange Discussions
Subject: Public Folder replication problem


We are experiencing a mysterious problem with E2K public/system folder
replication.

We've got a multi-site org with Ex5.5 & E2K in each site as we're
mid-transition.  All servers are fully SPed and patched.

In one particular site we have several folders that are replicated to
servers in the other sites.  Unless a replica of these local public or
system (Free/Busy) folders exists on the local Ex 5.5 server,
replication of these folders does not "happen" to the other sites.  All
other sites send and receive public folder content just fine.  The site
in question also receives other site PF content just fine.

We have evidence of SMTP messages being sent between the pub store
objects (<serverX>[EMAIL PROTECTED] and <serverY>[EMAIL PROTECTED]) every 15
minutes that are trackable under System Manager | Tools.  I presumed
these emails consisted of pub folder content replication since the
messages are to and from the public stores and the timing matched the
replication interval for the Always schedule.  Is that true?  If so,
what might cause a remote site not to update their local replica of my
folders?

I've searched Technet, found precious few articles about ways
replication can be broken, but none of them apply.  There is nothing in
the event logs anywhere indicating a problem.  SMTP traffic is moving
smoothly amongst the sites otherwise.

Any suggestions as to what Diagnostics Logging might aid in determining
a problem?  Helpful Q articles?  Any other ideas?


Thanks,

Jim Becker

Manager of LAN Services
State University of New York
System Administration
[EMAIL PROTECTED]


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]



_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: 
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to