Solved

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

Posted on 2010-11-08
4
1,913 Views
Last Modified: 2012-05-10
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?
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26369456.html
and
http://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.
0
Comment
Question by:AmbientIT
4 Comments
 
LVL 13

Accepted Solution

by:
AshwinRaj111 earned 500 total points
ID: 34098679
Since you cant get the ESM installed and the Get-RoutingGroupConnector is not displaying any result, your best bet would be to use the ADSIEDIT and remove the Routing Group Connector.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23153319.html

You can follow the same link that you have mentioned earlier and remove it.
0
 
LVL 2

Author Closing Comment

by:AmbientIT
ID: 34140110
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.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This video discusses moving either the default database or any database to a new volume.

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

26 Experts available now in Live!

Get 1:1 Help Now