Error 5015 Exchange 2007
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users microsoft exchange could not discover any route to connector exchange 2013 FAQ Search related threads Remove From My Forums event id 5016 exchange 2013 Answered by: EXCH 2010: Event ID's 5015 & 5016 Previous Versions of event id 5016 exchange 2007 Exchange > Exchange Previous Versions - Setup, Deployment, Updates, and Migration Question 0 Sign in to vote HI, Let me start
The Active Directory Topology Service Could Not Discover Any Route To Connector Exchange 2010
by saying I am still learning my way around Exchange 2010. We recently had a consultant help us migrateto Exchange 2010 from 2003. We are getting errors in the event viewer that I believe indicate that Exchange is still looking for event id 5016 dfsr the old server, which is now offline but available if needed. I'll paste the info from event viewer below. Log Name: Application Source: MSExchangeTransport Date: 2/14/2011 1:09:42 AM Event ID: 5015 Task Category: Routing Level: Error Keywords: Classic User: N/A Computer: Description: Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=Microsoft MTA\0ADEL:b5996ea8-7330-4b7e-9352-96ce502e22b9,CN=Deleted Objects,CN=Configuration,DC=XXX,DC=Local for connector CN=Internet,CN=Connections,CN=XXX,CN=Routing Groups,CN=XXX,CN=Administrative Groups,CN=XXX,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXX,DC=Local in routing tables with timestamp 2/14/2011 7:09:42 AM. Microsoft Exchange is ignoring the source transport server. Event Xml:
of mass destruction [Solved] Event ID's 5015 & 5016 Microsoft Exchange 2010 cannot find a route to the source transport server or home MTA server On exbpa February 27, 2013, in How-to, by Cubert aka (Cube Dweller) We were getting the
Adsi Edit
following error after a migration to Exchange 2010 from 2003 which indicated that Exchange was still looking for the old server. Event: Microsoft Exchange cannot find a route to the source transport server or home MTA server The problem is during the migration the old server didn't get pulled from Active https://social.technet.microsoft.com/Forums/en-US/9c1d5467-8a12-4033-b5f7-adda382e53ca/exch-2010-event-ids-5015-5016?forum=exchangesvrdeploylegacy Directory correctly so there were still settings that caused Exchange to believe that there was another MTA available. To resolve we opened up ADSI Edit on the AD server and navigated to the following container: [Configuration][CN=Configuration,DC=xxx,DC=local][CN=Services][CN=Microsoft Exchange][CN=MyDomainName][CN=Connections] Inside this container you may find entries that reference your old server. Just delete them and you should be good. Share this:FacebookLinkedInPrintEmailLike http://www.squidworks.net/2013/02/solved-event-ids-5015-5016-microsoft-exchange-2010-cannot-find-a-route-to-the-source-transport-server-or-home-mta-server/ this:Like Loading... Tagged with: 2010 Windows Exchange • Exchange 2010 • Microsoft • MS Exchange Server • Windows SBS Migration • windows server 2 Responses to "[Solved] Event ID's 5015 & 5016 Microsoft Exchange 2010 cannot find a route to the source transport server or home MTA server" Migration problems? | michael.kardela.net says: June 3, 2014 at 10:24 am […] the new SBS server will complain that it cannot connect to the old server. Please follow this or that guide to rectify the problem and associated with it errors 5015, 5016 in the even […] Evolution Microsoft Exchange Plugin - Remove Spyware, Malware and Viruses says: November 25, 2014 at 8:00 am […] [Solved] Event ID’s 5015 & 5016 Microsoft Exchange … – 1 Response » to “[Solved] Event ID’s 5015 & 5016 Microsoft Exchange 2010 cannot find a route to the source transport server or home MTA server”… […] Leave a Reply Click here to cancel reply. Name (required) Mail (will not be published) (required) Website CAPTCHA Code* Notify me of follow-up comments by email. Notify me of new posts by email
| My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out Event Logs http://forums.msexchange.org/Event_Logs_After_Last_03_Server_Removed/m_1800513517/tm.htm After Last 03 Server Removed Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [Microsoft Exchange 2007] >> Migration >> Event http://microsoft.public.exchange.admin.narkive.com/j7BdcaYL/exc2007-error-5016-and-5015 Logs After Last 03 Server Removed Page: [1] Login Message << Older Topic Newer Topic >> Event Logs After Last 03 Server Removed - 20.Jul.2009 2:20:24 PM ace1701 event id Posts: 279 Joined: 1.Dec.2000 From: Chicago Status: offline I have a "mirror" of my production network for testing (VMWare Rules!) After I removed the last 03 server I started receiving 3 events in 2007 that I'm a little concerned about. Event ID 3092 I deleted this "globalevents" via the ESM in 03 so that I could uninstall event id 5016 the server. Event ID 5015 & 5016 I uninstalled the 03 server. Why does 2007 still care about it? Any help would be appreciated. Log Name: Application Source: MSExchangeIS Public Store Event ID: 3092 Task Category: Replication Errors Level: Warning Error 1129 occurred while processing a replication event. Folder: (5-13) NON_IPM_SUBTREE\StoreEvents{A0C3CD89-134A-43BE-8D3C-5103EF71ABCE}\globalevents ************************************************************** Log Name: Application Source: MSExchangeTransport Date: 7/20/2009 9:33:06 AM Event ID: 5016 Task Category: Routing Level: Error Keywords: Classic The Active Directory topology service could not discover any route to connector CN=Internet Mail SMTP Connector (SERVERNAME),CN=Connections,CN=GRP2,CN=Routing Groups,CN=GRP2,CN=Administrative Groups,CN=Company Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Company,DC=com in the routing tables with the timestamp 7/20/2009 2:33:06 PM. This connector will not be used. ************************************************************** Log Name: Application Source: MSExchangeTransport Date: 7/20/2009 9:33:06 AM Event ID: 5015 Task Category: Routing Level: Error Keywords: Classic User: N/A Description: Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=Microsoft MTA\0ADEL:ca87de9c-948c-49cb-af3e-f44f5e1e985e,CN=Deleted Objects,CN=Configuration,DC=Company,DC=com for connector CN=Internet Mail SMTP Connector (SERVERNAME),CN=Connections,CN=GRP2,CN=Routing Groups,CN=GRP2,CN=Administrative Groups,CN=Company Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Company,DC=com in routing tables with timestamp 7/20/2009 2:33:06 PM. Microsoft Exchange is ignor
which I do not yet have a solution.Every few hours the following two errors are logged in the Eventlog:MSExchangeTransport Error 5016Microsoft Exchange cannot find a route to the source transport server orhome MTA server CN=MicrosoftMTA\0ADEL:042ac15a-4849-4802-8def-89b2a4331f74,CN=DeletedObjects,CN=Configuration,DC=cedp,DC=local for connector CN=FAXmaker:i386(CEDPEXC1),CN=Connections,.......undMSExchangeTransport Error 5015The Active Directory topology service could not discover any route toconnector CN=FAXmaker:i386 (CEDPEXC1),CN=Connections,CN=CEDP,CN=RoutingGroups,......Exchange and all services/connectors are running without problems otherwise.All info I've found so far in the net assumes that I'm trying to use a MTAwhich is not available and I should try to create/reactivate these MTAs.This is not the case in my situation. The MTAs in error are MTAs from theold EXC2K world and should not be used anymore.I could locate the deleted object in the AD deleted objects container.Here are my questions:1. should/could I simply delete these objects from the AD deleed objectscontainer?Or should I set the Tombstone Lifetime (temporarily) to a shorter interval(i.E. 2 days)?Could this have any negative impact to other operations (other than notbeeing able to restore/recreate deleted objects)?2. In Exc2K7 I cannot find any info/references pointing to this MTA.Since EXC is trying to do something with this MTA (otherwise it wouldn't logthe error messages)There must be some place in the configuration which references this MTA.Can someone shed some light on me so I could find this spot and try toeliminate it?Thanks in advanceRichard John Fullbright 2007-10-24 16:54:05 UTC PermalinkRaw Message Your faxmaker connector is gone, but looks like you are still trying to sendover it.. You should be using faxmaker 14 to install directly on Exchange2007, or use this work around on a seperate box if using 12.http://kbase.gfi.com/showarticle.asp?id=KBID003044Post by Richard ClementHello NG,after a successful migration from EXC2K to EXC2K7 I have one problem leftfor which I do not yet have a solution.MSExchangeTransport Error 5016Microsoft Exchange cannot find a route to the source transport server orhome MTA server CN=MicrosoftMTA\0ADEL:042ac15a-4849-4802-8def-89b2a4331f74,CN=DeletedObjects,CN=Configuration,DC=cedp,DC=local for connector CN=FAXmaker:i386(CEDPEXC1),CN=Connections,.......undMSExchangeTransport Error 5015The Active Directory topology service could not discover any route toconnector CN=FAXmaker:i386 (CEDPEXC1),CN=C