Avatar of AmbientIT
AmbientITFlag for United States of America asked on

Errors related to routing groups after Exchange 2003 (SBS) to Exchange 2007 (SBS) migration

I have finished a SBS 2003 to SBS 2007 migration and have a few errors in the event logs and an couple of items in the Microsoft Exchange Best Practice Analyzer that I would like to clean up.

Near the end of the migration I ran in to an issue uninstalling Exchange 2003 off the old server. (it would produce an error three or four minutes in to the process) Where I am at now is that the old server has been demoted and turned off for over a week and everything appears to be working correctly, but the following items come up in the BPA and Event logs

MS Exchange BPA items
1. Cannot connect to port 25 of the routing group master
Server LCRF1 is a routing group master but a connection to port 25 cannot be established...

2. Cannot connect to port 691 of the routing group master
Server LCRF1 is a routing group master but a connection to port 691 cannot be established...

3. Exchange Server cannot be contacted
Exchange server LCRF1 is down or unreachable

Event Log errors
Log Name:      Application
Source:        MSExchangeTransport
Event ID:      5006
Task Category: Routing
Level:         Warning
Computer:      SBS.LuvaasCobb.local
Description:
A route to Mailbox server CN=LCRF1,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=LUVAASCOBB,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LuvaasCobb,DC=local could not be found for store CN=Mailbox Store (LCRF1),CN=First Storage Group,CN=InformationStore,CN=LCRF1,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=LUVAASCOBB,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LuvaasCobb,DC=local in routing tables with timestamp 11/8/2010 7:11:50 PM. Recipients will not be routed to this store.


Log Name:      Application
Source:        MSExchangeTransport
Event ID:      5020
Task Category: Routing
Level:         Warning
Computer:      SBS.LuvaasCobb.local
Description:
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server lcrf1.LuvaasCobb.local in Routing Group CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative Groups,CN=LUVAASCOBB,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=LuvaasCobb,DC=local in routing tables with the timestamp 11/8/2010 7:11:50 PM.

My assumption is that this is because there is still information in AD/Exchange regarding the Routing group and the old server.

What I have tried
From the EMS I have used the commands to get-RoutingGroupConnector and get-RoutingGroupConnector | fl so that I could determine what the names were so that I could remove them with the Remove-RoutingGroupConnector command. When I use the Get-RoutingGroupConnector commands no information is displayed, but rather am sitting at the command prompt waiting for a new command to be entered.

Do I need to remove information from Active directory using ADSIEdit using the information found here?
https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26369456.html
and
https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23153319.html

Misc Information
Old server (SBS2003) name: lcrf1
New server (SBS2007) name: sbs

I do not have access to ESM for Exchange 2003. I have tried to install it on a workstation so that I could remove the routing group, but while we have the original OEM SBS media we cannot find the CD Key anywhere so I have not been able to get it installed.
SBSExchangeWindows Server 2008Microsoft Server OSActive Directory

Avatar of undefined
Last Comment
AmbientIT

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
AshwinRaj111

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
AmbientIT

There were no routing groups listed in AD using ADSIEdit, but the old server information was, removing the old server information took care of the issue.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy