Solution to fix these Exhange errors?

Overview: We have an Exchange 2007SP3 server with all updates. We have a 2003 level domain\forest. We have a BSD\Linux box named "mail.domain.com" that forwards email to the Exchange server. We have cleaned up an old 2003 and 2007 Exchange server from AD and are now left with an Exchange 2000 server that is still in AD. It is named the same as the BSD box... When I look in AD, it appears to show there are no roles installed on the 2000 "mail.domian.com" server, but we get these messages in Exchange 2007 error logs which tend to say it is a Routing Group Master.


Question #3
What do you think should be done to solve these errors? We want to upgrade to Exchange 2013 in the near future.

Error List:
Event Type:      Warning
Event Source:      MSExchangeTransport
Event Category:      Routing
Event ID:      5020
Date:            10/14/2013
Time:            4:49:33 AM
User:            N/A
Computer:      Exchange2007
Description:
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server mail.domain.com in Routing Group CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com in routing tables with the timestamp 10/14/2013 8:49:33 AM.



Event Type:      Warning
Event Source:      MSExchangeTransport
Event Category:      Routing
Event ID:      5006
Date:            10/14/2013
Time:            4:49:33 AM
User:            N/A
Computer:      Exchange2007
Description:
A route to Mailbox server CN=MAIL,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com could not be found for store CN=Public Folder Store (MAIL),CN=First Storage Group,CN=InformationStore,CN=MAIL,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com in routing tables with timestamp 10/14/2013 8:49:33 AM. Recipients will not be routed to this store.



Event Type:      Warning
Event Source:      MSExchangeTransport
Event Category:      Routing
Event ID:      5006
Date:            10/14/2013
Time:            4:49:33 AM
User:            N/A
Computer:      Exchange2007
Description:
A route to Mailbox server CN=MAIL,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com could not be found for store CN=Mailbox Store (MAIL),CN=First Storage Group,CN=InformationStore,CN=MAIL,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com in routing tables with timestamp 10/14/2013 8:49:33 AM. Recipients will not be routed to this store.

Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      Routing
Event ID:      5015
Date:            10/14/2013
Time:            4:49:33 AM
User:            N/A
Computer:      Exchange2007
Description:
Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=MAIL,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com for connector CN=FAXmaker:i386 (MAIL),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com in routing tables with timestamp 10/14/2013 8:49:33 AM. Microsoft Exchange is ignoring the source transport server.

Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      Routing
Event ID:      5016
Date:            10/14/2013
Time:            4:49:33 AM
User:            N/A
Computer:      Exchange2007
Description:
The Active Directory topology service could not discover any route to connector CN=FAXmaker:i386 (MAIL),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com in the routing tables with the timestamp 10/14/2013 8:49:33 AM. This connector will not be used.
LVL 1
johnj_01201Asked:
Who is Participating?
 
johnj_01201Connect With a Mentor Author Commented:
Two of the errors pertaining to FAXMAKER:I386 have been solved by following this article:
http://support.microsoft.com/kb/322123
0
 
Manpreet SIngh KhatraConnect With a Mentor Solutions Architect, Project LeadCommented:
Simple Delete the RoutingGroupConnector if you think it shouldnt exist

Get-RoutingGroupConnector
Get-RoutingGroupConnector "ConnectorName" | Remove-RoutingGroupConnector

- Rancy
0
 
johnj_01201Author Commented:
I've tried that, no results are returned, as if there are none.
0
 
johnj_01201Author Commented:
I was able to get rid of 2 of the errors on my own and the other 3 gone from another Rancy answer, that was not provided here, but worked.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.