Question : mail flow error's without any mail flow problem

After moving my hardware to virtual I am getting these 5015 & 5016 errors, however mail is flowing both ways. Can you experts guide me to correct the issue.

Log Name:      Application
Source:        MSExchangeTransport
Date:          7/6/2010 3:11:46 AM
Event ID:      5015
Task Category: Routing
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CMS-SBS2008.CMS.local
Description:
Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=Microsoft MTA\0ADEL:ae6e937a-c169-431a-b453-487f59410d39,CN=Deleted Objects,CN=Configuration,DC=CMS,DC=local for connector CN=Windows SBS Company Web Connector SBS2008,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CMS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CMS,DC=local in routing tables with timestamp 7/6/2010 10:11:46 AM. Microsoft Exchange is ignoring the source transport server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="49156">5015</EventID>
    <Level>2</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-07-06T10:11:46.000Z" />
    <EventRecordID>669788</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CMS-SBS2008.CMS.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>CN=Microsoft MTA\0ADEL:ae6e937a-c169-431a-b453-487f59410d39,CN=Deleted Objects,CN=Configuration,DC=CMS,DC=local</Data>
    <Data>CN=Windows SBS Company Web Connector SBS2008,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CMS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CMS,DC=local</Data>
    <Data>7/6/2010 10:11:46 AM</Data>
  </EventData>
</Event>


and then the 5016:

Log Name:      Application
Source:        MSExchangeTransport
Date:          7/6/2010 3:11:46 AM
Event ID:      5016
Task Category: Routing
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CMS-SBS2008.CMS.local
Description:
The Active Directory topology service could not discover any route to connector CN=Windows SBS Company Web Connector SBS2008,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CMS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CMS,DC=local in the routing tables with the timestamp 7/6/2010 10:11:46 AM. This connector will not be used.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="49156">5016</EventID>
    <Level>2</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-07-06T10:11:46.000Z" />
    <EventRecordID>669789</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CMS-SBS2008.CMS.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>CN=Windows SBS Company Web Connector SBS2008,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CMS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CMS,DC=local</Data>
    <Data>7/6/2010 10:11:46 AM</Data>
  </EventData>
</Event>


Thanks

Mark

Answer : mail flow error's without any mail flow problem

Do you still have ESM 2003 that you can connect to verify/fix?  If you  upgraded from 2003, most likely the connector is now orphaned and can be  safely deleted if your Exchange is standalone (most likely since it is a  SBS server) and not part of a larger Exchange infrastructure.  If you  needed again, you can use  Fix My Network wizard (FNCW) to recreate it.

Lastly, I believe in "don't fix what it is working"  - if the errors are just nuisances and not affecting Exchange operations, I would ignore them if I were you