Exchange Server TechCenter > Exchange Server Forums > Deploy > Ex2007 Beta2 Transport Service will not start.
Ask a questionAsk a question
 

Proposed AnswerEx2007 Beta2 Transport Service will not start.

  • Friday, September 01, 2006 12:03 AMDel Pomerinke Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Install hung when trying to start MS Exchange Transport service.  And now I continually get 2080 Topology discovery Information event and then Red Error event 2114.  Source: MSExchangeADAccess

    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1940)

    Topology Discovery failed, error 0x800040a02

    (DSC_E_NO_SUITABLE_CDC)

     

     

All Replies

  • Wednesday, October 04, 2006 3:08 AMManjubn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Did you try to start MSexchangeADtopology service manually and try to install .

     

  • Friday, December 08, 2006 3:28 AMjader3rd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    I had a similar problem. There was no child domain, but there as a second domain controller. I didn't specify the domain controller during setup and thought that might have been the issue. Check to see if the server is part of the Exchange Servers and Exchange Install Domain Servers. If it is not, add it. After I added the server I rebooted the machine the MSExchangeADTopology had no more issues.
    • Proposed As Answer byjader3rd Wednesday, March 11, 2009 11:22 PM
    •  
  • Sunday, November 25, 2007 8:48 AMbbuhac Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    If you have disabled IPv6 on your network adepter then that is the reason. Just enable ipv6 on NIC and restart server. You can check for example on

    http://www.mcpblog.net/Lists/Posts/Post.aspx?ID=36

  • Monday, January 28, 2008 4:57 PMglg1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Adding my Exchange Server to the two groups fixed my problem.  I had removed it from the AD then added it again.  Thanks for the advice.

  • Tuesday, February 03, 2009 8:54 PMsheiep Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    "If you have disabled IPv6 on your network adepter then that is the reason. Just enable ipv6 on NIC and restart server. You can check for example on http://www.mcpblog.net/Lists/Posts/Post.aspx?ID=36"



    Thank you, I could not figure out why the transport service would not start and this was my issue.