Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Public folder replication

Status
Not open for further replies.

henrik1980

IS-IT--Management
May 31, 2007
7
GB
I've just installed a new exchange server onto my domain.

I'm now trying to follow MS KB article 822931 which describes how to move the public folders and mail accounts to a new mail server.

The problem is I've stumbled at the first hurdle as my public folders will not replicate between the 2 servers. In the replication tab on ESM the current server is showing as 'in sync' while the new server shows as 'local modified'.

The only thing I can think of is that the current server cannot find the new server during the replication, however both can ping one another.

The current server is on it's last legs therefore I need to get everything moved over.


All help is appreciated!
 
Have you tried moving the replicas to the new server? Or perhaps the public folder migration tool?

Are you able to move mailboxes between the 2 servers?

Mike Fegan
tweakmybox.com

Get a free iPod at tweakmybox.com!
 
I've just looked in the event viewer on the current server and the following event ID occurs daily:

EVENT ID 929

Failed in reading Connector's DS Info Process Id: 1820 Process location: C:\WINDOWS\system32\inetsrv\inetinfo.exe ConnectorDN: CN=Internet Mail SMTP Connector (EMAIL),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=My company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=co,DC=uk Hr:80040920 Attribute:[]

I've ran some searches on this and it suggests that it's an old exchange 5.5 installation that's causing the problem. However even though it was the previous network admin that installed the server I do know that the company never used 5.5.

 
Interesting. My gut tells me to create a new routing group, and move both servers into the new group...

Mike Fegan
tweakmybox.com

Get a free iPod at tweakmybox.com!
 
It sounds like the old problem with backfill attempts prior to hierarchy replication. If this is the case, then you'll see all the replication messages queued for local delivery. This happens because the new server is added as the first entry of the PR_Replicas attribute.

The solution is to create a new routing group, then move the new server only to this routing group until the hierarchy replicates.



 
Yes xmsre, all the replications are queued.

Where can I see that the new server is added as the first entry of the PR_Replicas attribute?

So just create the routing group, move my original server in to it and then the replication should work?

Thanks!
 
Move the new server to the new routing group until hierarchy replication completes, then you can move it back.

It's really sort of funny how old problems appear in new releases. If you set the wayback machine to 2002, when I was a ROSS engineer before Exchange 2000 SP4, I created the routing group work around. Eventially a hotfix was created to cause the routing engine to ignore a new PF for a configurable number of days. It's actually msExchOwningPFTreeBL; I was going from memory and gave you the wrong attribute. The problem is documented for 2000 in KB 328870.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top