Msexchangetransport Error 5015
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ microsoft exchange could not discover any route to connector exchange 2013 Search related threads Remove From My Forums Answered
The Active Directory Topology Service Could Not Discover Any Route To Connector Exchange 2010
by: EXCH 2010: Event ID's 5015 & 5016 Previous Versions of Exchange > msexchangetransport 5016 exchange 2013 Exchange Previous Versions - Setup, Deployment, Updates, and Migration Question 0 Sign in to vote HI, Let me start by saying
Event Id 5016 Exchange 2007
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 the old server, event id 5016 dfsr 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 February 27, 2013, in How-to,
Adsi Edit
by Cubert aka (Cube Dweller) We were getting the 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 Directory correctly so there were still settings that caused Exchange https://social.technet.microsoft.com/Forums/en-US/9c1d5467-8a12-4033-b5f7-adda382e53ca/exch-2010-event-ids-5015-5016?forum=exchangesvrdeploylegacy 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 this:Like Loading... Tagged with: 2010 Windows Exchange • Exchange 2010 • Microsoft • MS Exchange 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/ 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. 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." &mdash
Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to http://www.eventid.net/display-eventid-5015-source-MSExchangeTransport-eventno-10196-phase-1.htm www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and https://www.experts-exchange.com/questions/27346887/Deleting-an-Exchange-Connector-to-solve-Event-ID-5016.html workstation via the Splunk Universal Forwarder. read more... Event ID: 5015 Source: MSExchangeTransport Source: MSExchangeTransport Type: Error Description:Microsoft Exchange cannot find a route to the source transport server or home MTA server
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Deleting an Exchange Connector to solve Event ID 5016 Want to Advertise Here? Solved Deleting an Exchange Connector to solve Event ID 5016 Posted on 2011-09-28 Exchange 1 Verified Solution 9 Comments 5,823 Views Last Modified: 2012-05-12 I've been getting an error for a long time in Exchange that I've just been ignoring - now I'm tired of it. Event Type: Error Event Source: MSExchangeTransport Event Category: Routing Event ID: 5016 Date: 9/28/2011 Time: 3:06:46 PM User: N/A Computer: OURMAILSERVER Description: The Active Directory topology service could not discover any route to connector CN=AvExchangeIVC_MAIL,CN=Connections,CN=MYDOMAIN,CN=Routing Groups,CN=BLAHBLAH,CN=Administrative Groups,CN=Our Site Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ourcomany,DC=com in the routing tables with the timestamp 9/28/2011 7:06:46 PM. This connector will not be used. Regular mail is going out fine and I haven't noticed any real problems. Using ADSIEDIT and drilling down to Services,,then Connections, I can see the connector in question. I just see it and our Fax gateway. Can I safely delete that connector without causing any problems with email? 0 Question by:tolenmay Facebook Twitter LinkedIn Google Best Solution bytolenmay Since it didn't seem that Exchange was using that connector (it referenced a server that did not exist), I went into ADSIEDIT and deleted it. So far, so goo. No recurring errors anymore. Go to Solution 9 Comments LVL 12 Overall: Level 12 Exchange 10 Message Expert Comment by:Deepu Chowdary2011-09-28 Here the culprit was connector. Check connector setting once and make sure thay are optimal. Also check how many connectors are there. 0 LVL 12 Overall: Level 12 Exchange 10