Msexchangetransport Error 5016
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums microsoft exchange could not discover any route to connector exchange 2013 Answered by: MSExchangeTransport 5016 Previous Versions of Exchange > msexchangetransport 5015 Exchange Server 2010 Question 0 Sign in to vote Does anyone know why i'm
The Active Directory Topology Service Could Not Discover Any Route To Connector Exchange 2010
receiving this event Log Name: Application Source: MSExchangeTransport Date: 2/4/2012 3:07:30 PM Event ID: 5016 Task Category: Routing Level: Error Keywords: Classic User: N/A
Exchange 2013 Could Not Discover Any Route To Connector
Computer: Exchange-Cas02.vms.ad.varian.com Description: The Active Directory topology service could not discover any route to connector CN=Internet Mail Connector,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=domain,DC=com in the routing tables with the timestamp 2/4/2012 11:07:30 PM. This connector will not be used. Edited by hclshafeek Monday, February 13, 2012 event id 5016 exchange 2007 7:24 AM Monday, February 13, 2012 7:21 AM Reply | Quote Answers 0 Sign in to vote There you GO.. http://blogs.technet.com/b/canitpro/archive/2007/01/04/your-solutions-fix-exchange-2007-smtp-connectors-with-adsiedit.aspx Cheers,Gulab Prasad, MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007 MCITP: Lync Server 2010 | MCITP: Windows Server 2008 My Blog | Z-Hire Employee Provisioning App
Proposed as answer by Jackzhou_5Microsoft employee, Moderator Tuesday, February 14, 2012 2:22 AM Marked as answer by Jackzhou_5Microsoft employee, Moderator Monday, February 20, 2012 2:22 AM Monday, February 13, 2012 7:25 AM Reply | Quote All replies 0 Sign in to vote There you GO.. http://blogs.technet.com/b/canitpro/archive/2007/01/04/your-solutions-fix-exchange-2007-smtp-connectors-with-adsiedit.aspx Cheers,Gulab Prasad, MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007 MCITP: Lync Server 2010 | MCITP: Windows Server 2008 My Blog | Z-Hire Employee Provisioning App Proposed as answer by Jackzhou_5Microsoft employee, Moderator Tuesday, February 14, 2012 2:22 AM Marked as answer by Jackzhou_5Microsoftof 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 February 27, 2013, in How-to, by Cubert aka (Cube Dweller)
Microsoft Exchange Could Not Discover Any Route To Connector Cn=windows Sbs Company Web Connector
We were getting the following error after a migration to Exchange 2010 from 2003 which indicated that event id 5016 dfsr Exchange was still looking for the old server. Event: Microsoft Exchange cannot find a route to the source transport server or home adsi edit MTA server The problem is during the migration the old server didn't get pulled from Active Directory correctly so there were still settings that caused Exchange to believe that there was another MTA available. To https://social.technet.microsoft.com/Forums/exchange/en-US/40c6377c-95d8-43a4-9958-fb837efa461a/msexchangetransport-5016?forum=exchange2010 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 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 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/ & 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. Systems Engineers HQ! Thanks for dropping by! Feel free to join the discussion by leaving comments, and stay updated by subscribing to the RSS feed. "Twitter messages not available." —Politicaliyinc LabTech Plugin Downloads ADMON Admin Group Monitor Plugin Agent Status Plugin Announce Maintenance Plugin AppassureD Backup Manager Plugin Apt-Get Package Manager for LabTech Chocolatey II Plugin Chocolatey Package Manager Plugi
Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service https://community.spiceworks.com/windows_event/show/2059-msexchangetransport-5016 ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 5016 (Error) Source: MSExchangeTransport How important is this event? (1 vote) 1 http://microsoft.public.exchange.admin.narkive.com/j7BdcaYL/exc2007-error-5016-and-5015 2 3 4 5 not important very important Description This Windows Event does not have a description yet. Add link Text to display: Where could not should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages The Active Directory could not discover topology service could not discover any route to connector CN=Windows SBS Company Web Connector FXBSSBS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=FLEXBIO,DC=local in the routing tables with the timestamp 12/7/2009 9:21:39 PM. This connector will not be used.
Dec 08, 2009 The Active Directory topology service could not discover any route to connector CN=Windows SBS Company Web Connector CCISBS,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=cci,DC=local in the routing tables with the timestamp 19/09/2011 4:50:52 PM. This connector will not be used. Sep 19, 2011 The Active Directory topology service could not discover any route to connector CN=Internet Mail SMTP Connector (SERVER2),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=blackall,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=blackall,DC=local in the routing tables with the timestamp 19/10/2012 12:07:50 AM. This connector will not be used. Oct 19, 2012 Comments Poblano Nov 30, 2014 Susan8645 Otherwhich 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=Config