none
Event ID 2142, 2077, 2069 MSExchangeADTopology Exchange 2013 RRS feed

  • Question

  • Hello,

    I have just inherited a slightly abused new server as part of my job and it looks like the previous admin was using a live single domain as a test bed.

    From what I have been able to determine this windows 2008R2 server started life as a single name domain (no FQDN) that had exchange 2013 running on it (sin I know).  A domain rename was performed and from what I can tell it did change the domain name to a FQDN environment.  (it went for COMPANY to COMPANY.COM)

    I have been able to clean up most of the other ghosts in the machine except when it comes to exchange.  I get event ID 2142(error), 2077 (info), and 2069 (info) repeatedly it cycles every 2 minutes:

    Log Name:      Application
    Source:        MSExchangeADTopology
    Date:          4/18/2013 11:42:39 AM
    Event ID:      2142
    Task Category: Topology
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER2013.COMPANY
    Description:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=13460) Forest COMPANY.com. Topology discovery failed, error details
    No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name..
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeADTopology" />
        <EventID Qualifiers="49156">2142</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-04-18T16:42:39.000000000Z" />
        <EventRecordID>4918254</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVER2013.COMPANY</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
        <Data>13460</Data>
        <Data>COMPANY.com</Data>
        <Data>No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name.</Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchangeADTopology
    Date:          4/18/2013 11:42:39 AM
    Event ID:      2077
    Task Category: Topology
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER2013.COMPANY
    Description:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=13460) Forest COMPANY.com. Exchange Active Directory Provider could not find any suitable domain controller servers in either the local site 'Default-First-Site-Name' or the following sites:
    .
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeADTopology" />
        <EventID Qualifiers="16388">2077</EventID>
        <Level>4</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-04-18T16:42:39.000000000Z" />
        <EventRecordID>4938976</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVER2013.COMPANY</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
        <Data>13460</Data>
        <Data>COMPANY.com</Data>
        <Data>Default-First-Site-Name</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        MSExchangeADTopology
    Date:          4/18/2013 11:42:39 AM
    Event ID:      2069
    Task Category: Topology
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER2013.COMPANY
    Description:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=13460) Forest COMPANY.com. Exchange Active Directory Provider couldn't find any suitable Global Catalog servers in either the local site 'Default-First-Site-Name' or the following sites:

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeADTopology" />
        <EventID Qualifiers="16388">2069</EventID>
        <Level>4</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-04-18T16:42:39.000000000Z" />
        <EventRecordID>4938977</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVER2013.COMPANY</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
        <Data>13460</Data>
        <Data>COMPANY.com</Data>
        <Data>Default-First-Site-Name</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    It looks to me that exchange is still looking for the old domain name.  Does anyone know how to point it to the correct domain name?

    Exchange is currently down and I am unable to log into EAC, OWA or Exchange Management Powershell.  I am also unable to un-install exchange as it is reporting active mailboxes and I can't delete them because I am unable to log in.

    My overall goal is to remove exchange from this server and put it on a separate server but until I can get exchange working to a point where I can remove the mailboxes, I am stuck.

    Any and all help appreciated.

    Hummedan


    • Edited by Hummedan Thursday, April 18, 2013 8:59 PM
    Thursday, April 18, 2013 4:58 PM

All replies

  • This is the same issue as with exchange 2010, you must in AD create a subnet in accordance with exchange..

    http://www.techieshelp.com/process-msexchangeadtopologyservice-exe-pid1756-topology-discovery-failed-error-0x8007077f/

    Friday, April 19, 2013 4:24 PM
  • Thank you for your advise on correcting my issue.  I created the subnet and assigned it to the Default-First-Site-Name as there weren't any subnets listed.

    Upon reboot I checked the event log and I am still receiving the event log entries as above; however, I am now receiving a few new errors along with them and they are repeating (4027 error and 3176 action).  Here are the additional errors:

    Log Name:      Application
    Source:        MSExchange ADAccess
    Date:          4/22/2013 9:52:48 AM
    Event ID:      4027
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER2013.COMPANY
    Description:
    Process msexchangerepl.exe (PID=8016). WCF request (Get Servers for COMPANY.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
     An error occurred during forest discovery (COMPANY.com). ----> No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name.
       at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
       at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
       at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
       at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
       at System.Threading.Tasks.Task.Execute()
    -----------
       at Microsoft.Exchange.Directory.TopologyService.Common.Extensions.WrapAndRethrowException(Exception exception, LocalizedString errorMessage)
       at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
       at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndGetServersForRole(IAsyncResult result)
       at Microsoft.Exchange.Directory.TopologyService.TopologyService.<>c__DisplayClassa.<EndGetServersForRole>b__9()
       at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)

    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          4/22/2013 9:52:48 AM
    Event ID:      3176
    Task Category: Action
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER2013.COMPANY
    Description:
    The Microsoft Exchange Replication service attempted to start the Active Manager RPC server but failed because an error occurred when attempting to read the Exchange Servers universal security group SID from Active Directory. Error:
    The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details An error occurred during forest discovery (COMPANY.com)..

    Log Name:      Application
    Source:        MSExchange ADAccess
    Date:          4/22/2013 9:52:48 AM
    Event ID:      4027
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER2013.COMPANY
    Description:
    Process MSExchangeSubmission.exe (PID=10708). WCF request (Get Servers for COMPANY.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
     An error occurred during forest discovery (COMPANY.com). ----> No Suitable Directory Servers Found in Forest COMPANY.com Site Default-First-Site-Name.
       at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
       at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
       at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
       at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
       at System.Threading.Tasks.Task.Execute()
    -----------
       at Microsoft.Exchange.Directory.TopologyService.Common.Extensions.WrapAndRethrowException(Exception exception, LocalizedString errorMessage)
       at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
       at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndGetServersForRole(IAsyncResult result)
       at Microsoft.Exchange.Directory.TopologyService.TopologyService.<>c__DisplayClassa.<EndGetServersForRole>b__9()
       at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)


    • Edited by Hummedan Monday, April 22, 2013 3:13 PM
    Monday, April 22, 2013 3:11 PM
  • Hi everyone!

    I have the same issue and found a solution:

    You'll need to edit the Default Domain Controllers Policy in Group Policy.

    1. Computer Configuration
    2. Windows Settings
    3. Security Settings
    4. User Rights Assignment
    5. Mange auditing and security log

    Add "Exchange Servers" or "Exchange Enterprise Servers" to that policy.

    gpupdate /force on the domain controller and restart the Exchange Services

    Solution by http://bloke.org/windows/exchange-2003-2007-2010-topology-discovery-failed-error-0x80040a02-dsc_e_no_suitable_cdc/#comment-3982


    • Edited by Russian Wings Thursday, October 17, 2013 7:31 AM
    • Proposed as answer by Russian Wings Thursday, October 17, 2013 7:31 AM
    Thursday, October 17, 2013 7:30 AM
  • This fixed my issue.

    dcdiag /s:[Domain]

    After doing so, it told me the cmdlet to "Repadmin /options DC -Disable_inbound_repl"

    Article used. http://technet.microsoft.com/en-us/library/cc730868.aspx

    Thursday, October 23, 2014 9:26 PM
  • If nothing else works try this!

    In exchange 2013 there is now a setting that requires you to have at least 50% of your domain controllers global catalog servers.  Without 50% of your DC's being GC's you will get event id 2069, 2060, and 2070 and exchange will fail to find other global catalogs or Domain Controlers in your organization.  Took me 80 hours to fix this problem.  Thought id share and save others some headaches.

    This can be fixed by editing the "Microsoft.Exchange.Directory.TopologyService.exe.config" file

    Look for this line:
    MinPercentageOfHealthyDC = "10"

    Also add this line:
    MinSuitableServer = "1"

    • Edited by Mr Someone Monday, January 12, 2015 10:07 PM
    • Proposed as answer by Abbas A Dirani Saturday, July 4, 2015 2:31 AM
    Monday, January 12, 2015 10:05 PM
  • Thank you Mr.Someoneyou help my life.

    i find many soultion to solve that but not help.

    thank you again. 

     

     
    Tuesday, January 13, 2015 6:32 AM
  • Worked for me on 2012R2 with Exchange 2013

    Thank you :)

    Wednesday, April 15, 2015 12:29 PM
  • Thank you so much for this! It worked with my 2013 exchange and 2012r2 server!
    Friday, May 15, 2015 9:57 PM
  • Thank you very much, that works!

    Friday, June 12, 2015 9:47 AM
  • you forgot to mention that the effected Exchange server must be rebooted prior retrying the setup, restarting the Active Directory Topology Service usually helps however some cases I found that the transport service would fail to start. only started normally and in working condition after a server reboot.

    Regards.

    Saturday, July 4, 2015 2:33 AM
  • Thanks a lot,

    worked for me, too.

    My situation (ExSrv 2013 sp1 on 2012 r2) was an old dc that was present during the installation of the new exchange server but was later on removed from the domain.

    Again, thx a lot, you saved my weekend!

    Sunday, August 23, 2015 3:36 PM
  • Thanks Mr Someone!

    This fixed it!

    Windows 2012 Server SP1 and Exchange 2013 SP1-CU9

    Friday, August 28, 2015 6:53 PM
  • Hi,

    Exchange Server DNSs are wrong, 

    Local dns entries are entered remote DC/GC so I changed to local DNS and reboot the server.

    Working fine.

    BR

    Monday, August 31, 2015 12:01 PM
  • Thanks Mr Someone

    Worked as well for me: Windows 2012 R2 / Exchange 2013 CU8

    Regards
    Peter

    Monday, October 12, 2015 7:12 AM
  • Worked for me as well, thanks alot for this! Old DC I removed that didn't apparently get fully removed and was throwing off the healthy check. 
    Saturday, December 12, 2015 2:17 AM
  • Mr. Someone , You guided in the right path , all of a sudden the problem came and I tried many solutions but the solution that worked was yours editing the config file .

    Microsoft.Exchange.Directory.TopologyService.exe.config" file

    And the location to the file is : C:\Program Files\Microsoft\Exchange Server\V15\Bin

    C: exchange installation directory

    following Microsoft Document also helps us

    support.microsoft.com/en-us/kb/3088777

    Thanks a lot bro


    • Edited by Imran24 Monday, December 28, 2015 6:55 AM
    Monday, December 28, 2015 6:54 AM
  • Thank you so much, it helped me a lot, with only MinSuitableServer it didnt work but change MinPercentageOfHealthyDC WORKED.

    Tuesday, October 18, 2016 5:57 PM
  • This worked for me 
    Tuesday, January 22, 2019 11:00 PM
  • If nothing else works try this!

    In exchange 2013 there is now a setting that requires you to have at least 50% of your domain controllers global catalog servers.  Without 50% of your DC's being GC's you will get event id 2069, 2060, and 2070 and exchange will fail to find other global catalogs or Domain Controlers in your organization.  Took me 80 hours to fix this problem.  Thought id share and save others some headaches.

    This can be fixed by editing the "Microsoft.Exchange.Directory.TopologyService.exe.config" file

    Look for this line:
    MinPercentageOfHealthyDC = "10"

    Also add this line:
    MinSuitableServer = "1"

    This was a life saver for me :) thanks for the help.
    Friday, January 10, 2020 9:19 AM