Question : public folders do not replicate in exchange 2003. rpc errors in event log

Hi Guys,

we have an existing windows 2000 domain, nothing compicated. We had a single exchange 2000 server with latest service packs which was upgraded long time ago from 5.5, using the swing method.

just installed a new windows server 2003, and connected to the existing domain. Then run all the domain and forest preparation tools for installing exchange 2003. Installed exchange 2003 and sp1, and all looked ok. Moved all the mailboxes to this server, no problems. The final outcome is to actually remove the old exchange 2000 so that it is re-set to run other things.

Now, the problem began when i went to replicate the public folders from the 2000 to the 2003 exchange server. All looked ok in the configuration, accepting the replication set by me and all. Then i went to the new 2003 server, and there was nothing there. Not even replicas showing.

Deleted some of the replications and reset... nothing.
Did the replicas manually and still nothing comes in. All folders show empty in the 2003 server. What is even more weird, is that in the details it shows that the two replicas are in synch! but checked the public folder storage file and it is only some 5-6megs, when it should me around a few gigs.

Checked the event logs, and i get a couple of errors which repeat all the time:
- source mxexchangeMTA,  warning, event id 9318, INTERFACE category
An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 29, Windows 2000/MTA error code: 9297. Comms error 9297, Bind error 9297, Remote Server Name ISNEXCH [MAIN BASE 1 500 %10] (14)


- source mxexchangeMTA,  warning, event id 9297, SECURITY category
Calling client thread does not have permission to use MTA RPCs. Windows 2000 error code: 0X80070005. Client user account: NT AUTHORITY\ANONYMOUS LOGON. [BASE IL INCOMING RPC 25 237] (14)

these messages come on both servers. The isnexch is the old and the isnexch01 is the new.

I can see lots of messages leaving the old server, and going into the new. But on the new server they remain in a queue named PUBLIC FOLDER STORE (ISNEXCH01) which is an x400 folder and scheduled but does not process the messages. The next processing always shows to be forwarding by 3 hours every time you click on it.

There is also a queue named ISNEXCH01 on the old server, which has a number of messages which never get delivered.

I upgraded onsite the old exchange to exchange 2003  just in case it would help. Then installed also the sp1. Nothing. still same old thing

I checked the RPC with the rpc checkup tools, and also double and tripple checked the DNS settings and the FQDN of the servers and dns servers. Didnt find anything!  Even checked the virtual smtp server and didnt find anything wrong.

Any ideas? Could it be remaining from the 5.5 swing upgrade? or cound it have to do something with the anonymous login of the windows server 2000 / 2003?
it must have to do something with access rights, btu where do i change them?

would really appreciate your help!
Thanks people
Angelos

Answer : public folders do not replicate in exchange 2003. rpc errors in event log

Sending the hierarchy will not replicate the content as well. You need to set that by folder. At least you can set the replication at the top level and then propagate it down which makes setting it much easier.

Exchange 2003 also introduced a mechanism to send the content now which will force the content to go across. It floods the network but does work.
When I do a migration to new hardware I usually allow at least three weekends to do the work - once the new server has been built. This allows enough time to get everything moved without any data loss.

RPC errors usually mean that the servers cannot communicate with each other or a domain controller. There are tests on the Exchange server CD checklist that you can run to see where the problem is.

Simon.