Public Folders Not Replicating on Exchange 2003


First, let me say that I know lots of folks have already made posts about Public Folder Replication Issues, and I've read lots of them.  Although many were informative, I have followed their recommendations and are still having issues.

We have an Old Exchange Server (W2K3X) running Windows Server 2003 Standard R2 SP2, and a New Exchange Server (W2K3M) running Windows Server 2003 Enterprise R2 SP2.  Both Servers are Running Exchange 2003 SP2...the build numbers are identical.  Neither server is a DC.

The Old Exchange server supports tasks other than Exchange, and is overloaded.  Our goal is to move the Exchange Function to the New Exchange Server.  We started by following the instructions in KB822931.  Unfortunately Public Folder replication is one of the first tasks followed by the OAB replication.

All versions of the OAB have been setup for replication.

Although we have been mostly sucessful moving a few test mailboxes to the New Exchange Server, those users do get the Send and Receive Error when pressing Send/Receive.  If they don't press it works fine.  It is our understanding this error is directly related to the OAB not replicating to the New Exchange Server.

We have not made any configuration changes in almost a day, and replication has not occured.  Even using "Send Changes" with 999 for the number of days does not work.

Our preference is to transition gradually over a period of time, rather than transition everyone at once.  I've put up a number of screen shots to show our configuration.  I'd appreciate specific help, rather than reference to other articles, since I've probably read them already.  I'd be happy to take screen shots of other configuration screens.

Thank you in advance for your help!


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Stacy SpearPresident/Principal ConsultantCommented:
Did you set replication for the root address book folder as well (I believe this can be set)? All the listed address books must be set to replicate as well. Has the RUS given the new public folder store an email address? This can be done by using ADSIEdit, going to the configuration container and drilling down into Services, Exchange, and going down to the server. Pull up the properties on the public folder store to see if it has an email address. If not, trouble RUS.

If all this is done, you need to track down the replication messages to see where they are stopping. You can do this by first turning logging in Exchange to maximum for all replication entries and  NDRs. Then you should start getting detailed events in the application log. These should be set on both servers BTW.

Once you verify that the old server is indeed creating outgoing messages, then track them using the message tracking tool in exchadmin.
djhunt01Author Commented:
Hi!  Thank you for your guidance!

I apologize for the delay in getting back to you.  We had an outside consultant who claimed to have expertise in Exchange remote in, and after three hours gave up.  We then decided to completely reinstall Server 2003 Enterprise and Exchange Server 2003 on the New Server because we were informed that it might be an issue that the first time we tried to replicate the Exchange Service Packs between the two servers were not identical.  We also change the name of the New Exchange Server to W2K3MB.

I've attached screen shots showing the differences in the Public Folders between the two servers, and the message history showing that the old server did successfully send out a replication message to the new one.

Any ideas on next steps?  We are about to call Microsoft, but I'm keeping my fingers crossed that we can solve this problem with help from this forum.

Thank you!

Stacy SpearPresident/Principal ConsultantCommented:
The message history shows successful sending, did you click on w2k3mb to see if it actually sent it to the public folder store?

Did you use ADSIEdit to look at the new server as I posted above?

In the attached image, everything highlighted in yellow needs to be set up for replication on the old server. I prefer immediate because folks gripe if they don't have the latest.

The Schedule Free busy is iffy. I prefer to have one across the organization, but some folks like to have replicas of it. With one, everyone has the same data.

You ever worked with GoldMine? Knew of a DJ Hunt that helped me out a lot with it in 2005-2006.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
djhunt01Author Commented:
Hi!  Thank you for your help!

I ended up spending 6.5 hours on the phone with Microsoft Tech Support.  Fortunately you help me rule out a number of issues.

There were half a dozen layers to the onion of problems we had to peel through, but the two biggest were that the old exchange server was a member of some exchange admin groups as well as domain admin groups and the domain admin groups denied some permissions.  Also the SMTP filter was causing messages not to go through.

Thank you again for your help!


P.S.  Sorry, but I'm not the DJHunt you worked with on GoldMine.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.