Exchange Server Forums

Public Folders Not Replicating

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Public Folders >> Public Folders Not Replicating

Page: [1]

Message

<< Older Topic Newer Topic >>

Public Folders Not Replicating - 27.Oct.2006 11:21:23 AM

mikehunt31

Posts: 17
Joined: 18.Apr.2006
Status: offline

I have 2 exchange 2k ent servers each located in its own routing group.

emails successfully traverse the routing group connector and all outgoing emails are successfully delivered.

I have setup several public folders on server1 and configured all the replication options.

I have discovered that these folders are not replicating. After some hours on the web searching for solutions i discovered that the RUS enterprise service was set to never run. changed this setting to be always on, but still no replication.

After reading article http://www.msexchange.org/articles/Public-Folder-Replication-Troubleshooting.html i discovered that the email stamps for the first storage group within active directory (see article for more details) were missing.

I have added the smtp email stamp according to the article to the stores, but cannot get the complete format for the x400 address.

Is the x400 address stamp required?????

is the format of the smtp address stamp correct - server1-IS@domain.com There are no clues to this problem in the event logs as no errors are being generated.

is there anybody out there that can help me resolve this issue ???

Any help is gratefully received.

many thanks in advance.

< Message edited by mikehunt31 -- 27.Oct.2006 11:26:18 AM >

Post #: 1

Featured Links*

RE: Public Folders Not Replicating - 27.Oct.2006 11:30:28 AM

jchong

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline

Are there PF replication message being queued? They would be coming to and fro in the fromat of server1-IS@domain.com.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to mikehunt31)

Post #: 2