Discussion Locked

exchange server 5.5

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Recently I purchased a new server with the intents of transferring my existing Exchange Server on to my new server. I tried to do this by installing exchange on the new server as a second server replicate the directories. Once that was done I was going to copy over the *.edb files and run the isinteg -patch and hoping that would work. Unfortunately it did not so I went about a different way by installing exchange as a new site with the same container names and then giving the new server the same name as the last one then copying over all the necessary files. It worked but now I am getting an error in the event id as 9318 - an rpc communications error - unable to bind over RPC locality table. I think all I have to do is delete the other site I have on this server(when i first tried to install the new server, I did the directory replication). Help! I don't know exactly where to go from here.

8 replies

by curacao_dejavu

Hi,

the error message is more detailed than you have described. pls put the complete error message.
I think you are right though.
In the meantime you can do a search on 9318 (9 results) and look up the results if it applies to the situation.regards,

Leopold

by paul

The exact error is:
An RPC Communications error occurred. Unable to bind over RPC Locality Table(LTAB)index 69, NT/MTA error code: 1722 Bind error 0. Remote Server MACHINENAME MAIN BASE 1 500 %10(14)

by robert schommer

I am going to assume you are replacing the old server with the new.

if you want to do this in an unsupported manner you can follow: http://support.microsoft.com/support/kb/articles/Q199/9/54.ASP?LN=EN-US&SD=gn&FR=0&qry=replace%20first%20server%20in%20site&rnk=10&src=DHCS_MSPSS_gn_SRCH&SPR=ECH

A better method may be to do as I did recently.

Bring the new server up in the same site, move the users mailboxes using the "move mailbox" feature. make sure you do not have circular logging enabled as that will reduce you fallback options during the mass moves. You must also pay particular attention to the available space for your transaction logs. This produces a huge amount of logs and those need to be retained in case of migration failure and rollback.

There are also several roles the first server up in a site performs such as maintaining the "Free/Busy Folder" for calendaring funtionality. This requires that you move those roles. There are serveral other roles that must be transferred to the new server also.

I would suggest searching the KB for additional issues. Q155216 is a good one.

by curacao_dejavu

ok,

If you sure that you don't need the other site anymore you can stop the transfer and delete the bindings.

verify what's going on with MS KB Article ID: Q303156

Leopold

This discussion is closed to new replies.