Link to home
Start Free TrialLog in
Avatar of fgarufijr
fgarufijrFlag for United States of America

asked on

Exchange 2007 complaining about Removed E2k3 Server

Our orginization just did a migration from Exchange 2003 to Exchange 2007. After successfully moving all mailboxes over from the E2003 to E2007, and replicating all the public folders and moving them over, I decomissioned the E2003 server by using Add/Remove Programs to un-install it.

My Exchange 2007 server is now throwing Event ID's complaining that the Exchange 2003 server cannot be contacted.

Event ID 5006
Source: MSExchangeTransport
Category: Routing
Type: Warning
Cannot find route to Mailbox Server CN=SERVER0,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=org for store CN=Mailbox Store (SERVER0),CN=First Storage Group,CN=InformationStore,CN=SERVER0,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=org in routing tables with timestamp 7/11/2007 4:09:39 AM.  Recipients will not be routed to this store.


Event ID 5020
Source: MSExchange Transport
Category: Routing
Type : Warning

The topology doesn“ÇÖt contain a route to Exchange 2000 Server or Exchange Server 2003 server server0.domain.org in Routing Group CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=org in routing tables with the timestamp

It would seem that Exchange 2007 still thinks that Exchange 2003 is out there.. How can I clear this???

Also, I'm not sure if its related ( I have a feeling it is ), NONE of my POP3 users can send outgoing mail to any outside domain. Outlook is configured to use POP3, they are in the internal LAN, and specify the Exchange 2007 server as the SMTP server. They all get an immediate 550 Relaying error. I do have a send connector created in the Orginization Connector / Hub Transport. I know the first question will be "why if they are internal LAN users are they using POP3??"... Trust me, its not exactly how I want it, but its the way it is :)

Any help is GREATLY appreciated :)
ASKER CERTIFIED SOLUTION
Avatar of mass2612
mass2612
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of fgarufijr

ASKER

MASS - I did follow that "How To" article to a "t"... I just tried looking to see if maybe I missed a step with removing the RoutingGroupConnector in Exchange 2007, but I'm a bit confused by it. There is a link on how to remove the RoutingGroupConnector using the E2k7 Management Shell... I used the command Get-RoutingGroupConnector to see what connect is there, but nothing shows... It just gives me another command prompt directly after hitting enter. Am I missing something???

Consult - The server is still in the orginization, its just that Exchange 2003 has been uninstalled on it. That server also held websites on it, along with being a RADIUS server, so the entire server isn't removed from the orginization, just Exchange 2003 was uninstalled.

Do you still have the Exchange 2003 ESM tool installed somewhere? If so are you able to open it and see if the RGC's between the Ex2003 and Ex2007 servers are still showing. I'm not sure if this will work. You use to be able to open the Ex 5.5 tool after removing the last Ex 5.5 server but I haven't had the opportunity to remove Ex 2003 yet.
All right.You need to remove the exchange server object using adisiedit.msc
do the following:-
open adsiedit.msc and browse to the configuration container ->Exchagne organisation->administrativegroup->servers->locate the exchange 2003 server (with its name) and right click on the object to delete it.This only removes the object from the exchange container the server still remains as what ever services installed other than exchagne .
Consult:

I ran ADSIEdit.msc from the old 2003 Exchange Server. Here's what I've got

Configuration -> Configuration -> Services -> Microsoft Exchange -> <Domain Name> -> Administrative Groups ->

I then have two groups under that...

Exchange Administrative Group ( New Exchange 2007 )
First Administrative Group ( Old Exchange 2003 )

Do I want to delete the CN=<OLD 2003 Server Name> from the Frist Administrative Group???

MASS:

I tried to run Exchange System Manager from the old 2003 Exchange Server and it wont run anymore. It comes up with a 'problem with the snap-in". Is it possible to just install the System Manager again without installing anything else??
First Administrative Group ( Old Exchange 2003 )
THATS YOUR TARGET.but remember back-up active directory before doing any delete opertaion thats always safe.
1.Remove the old exchange 2003 server (currently do not delete first administative group).
2.It is possible to install exchange 2003 system manager on any (non exchange 2007) server.
Thanks.
Well, I resolved the issue...

Seems that Exchange 2003 wasn't completely removed through Add/Remove Programs. I was able to go into Add/Remove Programs and completely remove it this time. Exchange 2007 is no longer throwing Event ID's wondering where E2k3 is :)

I also figured out what was keeping our POP3 users from sending mail out through the Exchange 2007 servers. For some reason, the permissions on the Recieve Connector wasn't updating. I had to use ADSIEdit and manually add the permissions in order for it towork.

Thanks for all your help! :)