locked
'MSExchangeTransport' failed to reach status 'Running' on this server.

    Question

  • I am installing Exchange 2007 SP1 on x64 Windows Server 2008 and I receive the following error.


    Hub Transport Role
    Failed

    Error:
    Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.

    When I look at the Microsoft Exchange Transport service is contiously tries to start but doesn't. the Microsoft Exchange Active Dictory Topology service started ok. How do I troubleshoot this?

     

     

    Monday, February 18, 2008 4:01 PM

All replies

  • I solved the problem by installing IPv6 protocol. I originaly turned it off because Exchange wanted a static IP address and I could not set it on the IPv6 because it kept telling me it was invalid. If anyone has information on this please let me know.

    • Proposed as answer by Funnybaai Sunday, December 27, 2009 3:32 PM
    Monday, February 18, 2008 4:47 PM
  •  

    For me the service was installed but the installer could would not start it.  I started the Trasnport service manually and then re-ran the install.  I was then able to add the mailbox and client access role.
    Wednesday, March 19, 2008 5:41 PM
  • I had the same problem, and it appears that the following warning during the installation has a relation,

     

    Setup cannot detect an SMTP or Send connector with an address space of '*'.

     

    and this fix

    http://support.microsoft.com/kb/556055

    solved the/both problem(s)

    Wednesday, March 19, 2008 9:19 PM
  • I'm still having this problem myself.  I do not have IPv6 enabled, I have tried the global * fix and I have also tried to manually start the Transport service but the installation still fails and Transport service still remains in the "Starting" state.  Any ideas on how to fix this nusance of an issue?
    • Proposed as answer by Funnybaai Sunday, December 27, 2009 3:31 PM
    Thursday, March 20, 2008 11:14 AM
  •  Scott N. Weber wrote:

    I solved the problem by installing IPv6 protocol. I originaly turned it off because Exchange wanted a static IP address and I could not set it on the IPv6 because it kept telling me it was invalid. If anyone has information on this please let me know.

     

    Worked also for me.!!! thanks Scott!

    • Proposed as answer by shahulhameed Saturday, November 13, 2010 9:04 AM
    Friday, March 28, 2008 9:20 AM
  • I had the identical problem.  The send connector did not work.  Just enabling IPv6 got me to a point where the service would start then stop, and finally assigning an address to the IPv6 got it to start and stay that way.
    Monday, April 14, 2008 11:53 PM
  • Thx mate, it really help. I guess everyone who just get started with Win2k8 will stop the IPV6. There would be lots of people have the same problem. Why ms didnt do a better job... 
    Tuesday, April 29, 2008 3:27 AM
  • Enabling the IPv6 protocol, restarting the server and then re-running the install did it for me ;o)

    Monday, May 12, 2008 12:43 PM
  • Scott,

     

    I just want to sincerely thank you for helping me to understand my problem.  I have spent literally 12 man hours on this issue.  I have another 12 to go, because now I have to do an Exchange Recovery.  Long story.

     

    In my case, my Windows 2008 DC became unresponsive when I demoted the last Windows 2003 domain controller in the domain.  After that, my Windows 2008 DC (the only DC left in the domain) would not start correctly.  In retrospect I think that the Windows 2008 went from being happy to talk either IP v4 or v6 to only wanting to talk IP v6.  Since I only had IP v4 installed services would not start - the most important of which being the DNS server service, so AD would not work either, so Exchange would not work.

     

    I am disgusted with Microsoft on this issue.  We have been happily working with IP v4 for ages.  So of course first time installers of Win2K8 will unselect IP v6.  When you unselect IP v6 there is no warning indicating that certain services will fail to start or that certain applications (like Exchange 2007) will fail to install.

     

    At the very least it would have saved my *** if Event ID 4013 had have made some mention that one possible cause of DNS not being able to replicate is not having IP v6 bound to the NIC.

     

    Boo for Microsoft.  Yay for Scott.

    Sunday, May 25, 2008 4:25 AM
  •  

    "So of course first time installers of Win2K8 will unselect IP v6"

     

    As well they should.  Good security practice dictates that services which are not needed are either switched off or removed.  Considering the fact that there's VERY few of us who would actually need IPv6, I would expect it would be disabled for almost all systems by default if competent system administrators are involved.

     

    Considering I have no requirement for IPv6, I had it switched off - it was one of the very first things I did directly after installing Server 2008.  And so I've had this problem for a while now (longer than necessary to be fair, I should have searched for the error message sooner rather than rebuilding the server three times...).

     

    I've just enabled IPv6, and am rebooting.  I'll report back on success...

    Sunday, May 25, 2008 12:03 PM
  •  Robert Hudson wrote:

    I've just enabled IPv6, and am rebooting.  I'll report back on success...

     

    And the report is good.

     

    All I did was enable IPv6 again on the NIC in use on the server, and everything installed properly.

     

    Why this isn't documented in the pre-reqs on Technet (http://technet.microsoft.com/en-us/library/bb124558(EXCHG.80).aspx for instance), or checked by the installation program (which is happy to report that there's no Sender configured, even though Exchange isn't even installed yet!) is beyond me.  Hopefully this thread will become more and more prominent in the community and will save more people from grief...

    Sunday, May 25, 2008 9:37 PM
  • I stumbled on this error in the Eventlog around the times of my installation:

    Automatic certificate enrollment for local system failed to enroll for one Domain Controller certificate (0×80070005).  Access is denied.

     

    This led me to the following solution:

    "add domain controllers to CERTSVC_DCOM_ACCESS group"

     

    I had already implemented IPv6 on both NICs and static IPs for all protocols, and removed a hyper-v virtual adapter.  This final tweak did the trick. I was finally able to get through the Exchange 2007 installation.  I hope this helps somebody, somewhere.  This is my first posting to a forum...the first time I had something to contribute.  Smile   let me know if this helped you: groovyyuvie@gmail.com


     

     

     

    Tuesday, June 17, 2008 4:53 PM
  •  

    Hi I'm getting the same problem that the MSExchangeTransport' wont start but none of the above fixes seem to work for me. This is the error from the event log.

     


     

    Log Name:      Application
    Source:        MSExchangeTransport
    Date:          17/07/2008 16:03:17
    Event ID:      7001
    Task Category: Components
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      CWEXCH.cwprint.local
    Description:
    The service will be stopped. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'SmtpOutConnectionHandler' failed. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Microsoft Exchange couldn't read the configuration from the Active Directory directory service. ---> Microsoft.Exchange.Data.Directory.SystemConfiguration.ErrorExchangeGroupNotFoundException: The Exchange group with GUID "6c01d2a7-f083-4503-8132-789eeb127b84" was not found. This group was automatically created during Exchange Setup, but has been subsequently removed. ---> Microsoft.Exchange.Data.Directory.ADTransientException: Could not find any available Global Catalog in forest cwprint.local.
       at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
       at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType)
       at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
       at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)
       at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
       at Microsoft.Exchange.Data.Directory.ADSession.FindByWellKnownGuid[TResult](Guid wellKnownGuid, String containerDN)
       at Microsoft.Exchange.Data.Directory.ADSession.ResolveWellKnownGuid[TResult](Guid wellKnownGuid, String containerDN)
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector.PermissionGroupPermissions.<>c__DisplayClass1.<GetSidForExchangeKnownGuid>b__0()
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector.PermissionGroupPermissions.GetSidForExchangeKnownGuid(ADRecipientSession session, Guid knownGuid, String containerDN)
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.SmtpSendConnectorConfig.GetDefaultPermission()
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.SmtpSendConnectorConfig.GetDefaultSDForEnterpriseRelayConnector()
       at Microsoft.Exchange.Protocols.Smtp.SmtpOutConnectionHandler.Load()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Protocols.Smtp.SmtpOutConnectionHandler.Load()
       at Microsoft.Exchange.Transport.SequentialTransportComponent.<>c__DisplayClass2.<Load>b__0()
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
       at Microsoft.Exchange.Transport.Components.Activate()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeTransport" />
        <EventID Qualifiers="16388">7001</EventID>
        <Level>4</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-07-17T15:03:17.000Z" />
        <EventRecordID>350</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CWEXCH.cwprint.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'SmtpOutConnectionHandler' failed. ---&gt; Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Microsoft Exchange couldn't read the configuration from the Active Directory directory service. ---&gt; Microsoft.Exchange.Data.Directory.SystemConfiguration.ErrorExchangeGroupNotFoundException: The Exchange group with GUID "6c01d2a7-f083-4503-8132-789eeb127b84" was not found. This group was automatically created during Exchange Setup, but has been subsequently removed. ---&gt; Microsoft.Exchange.Data.Directory.ADTransientException: Could not find any available Global Catalog in forest cwprint.local.
       at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
       at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType)
       at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId&amp; rootId)
       at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId&amp; rootId)
       at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
       at Microsoft.Exchange.Data.Directory.ADSession.FindByWellKnownGuid[TResult](Guid wellKnownGuid, String containerDN)
       at Microsoft.Exchange.Data.Directory.ADSession.ResolveWellKnownGuid[TResult](Guid wellKnownGuid, String containerDN)
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector.PermissionGroupPermissions.&lt;&gt;c__DisplayClass1.&lt;GetSidForExchangeKnownGuid&gt;b__0()
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector.PermissionGroupPermissions.GetSidForExchangeKnownGuid(ADRecipientSession session, Guid knownGuid, String containerDN)
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.SmtpSendConnectorConfig.GetDefaultPermission()
       at Microsoft.Exchange.Data.Directory.SystemConfiguration.SmtpSendConnectorConfig.GetDefaultSDForEnterpriseRelayConnector()
       at Microsoft.Exchange.Protocols.Smtp.SmtpOutConnectionHandler.Load()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Protocols.Smtp.SmtpOutConnectionHandler.Load()
       at Microsoft.Exchange.Transport.SequentialTransportComponent.&lt;&gt;c__DisplayClass2.&lt;Load&gt;b__0()
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
       at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
       at Microsoft.Exchange.Transport.Components.Activate()</Data>
      </EventData>
    </Event>

     

    Any help would be greatly received.

     

     

    Thursday, July 17, 2008 3:15 PM
  • The same fix ( http://support.microsoft.com/kb/556055 , see Rasmus Jacobsen's post above) allowed me to finish Exchange installation too. Just it has to be applied after enabling TCP/IPv6. Thanks!

    Wednesday, August 27, 2008 10:10 PM
  • Worked for me as well. IPv6 was set to Dynamic, and restarted server. Worked like a charm, thank you very much!!
    Thursday, September 18, 2008 5:55 PM
  • Scott,

     

    I have never posted here before. But I want to that you so much for this solution. It worked for me as well!!!!!! I had disabled IPv6 during domain controller installation because I was not sure how to enter one.

     

    You rock. You would think microosft would warn you not to deselect IPV6. This also solved the problem of Setup cannot detect an SMTP or Send connector with an address space of ''.

     

    Thank you sir!


     

    Saturday, September 20, 2008 8:38 PM
  •  

    Here are the steps:

    1. Install Windows Server 2008 32bit or 64bit

    2. Disable IPv6 and install ADS "dcpromo"

    3. Install DNS with Forward Look up and Reverse Look up { check with "nslookup" at command prompt}

    4. Then Install IIS 7 and website ex: www.xyz.com 

    5.Now enable IPv6

    6 install , just copy paste at command prompt

    ServerManagerCmd -i RSAT-ADDS
    ServerManagerCmd -i Web-Metabase
    ServerManagerCmd -i Web-Lgcy-Mgmt-Console
    ServerManagerCmd -i PowerShell
    ServerManagerCmd -i Web-Server
    ServerManagerCmd -i Web-ISAPI-Ext
    ServerManagerCmd -i Web-Metabase
    ServerManagerCmd -i Web-Lgcy-Mgmt-Console
    ServerManagerCmd -i Web-Basic-Auth
    ServerManagerCmd -i Web-Digest-Auth
    ServerManagerCmd -i Web-Windows-Auth
    ServerManagerCmd -i Web-Dyn-Compression
    ServerManagerCmd -i RPC-over-HTTP-proxy
    ServerManagerCmd -i ADLDS
    ServerManagerCmd -i Web-Server
    ServerManagerCmd -i Web-ISAPI-Ext
    ServerManagerCmd -i Web-Metabase
    ServerManagerCmd -i Web-Lgcy-Mgmt-Console
    ServerManagerCmd -i Web-Basic-Auth
    ServerManagerCmd -i Web-Windows-Auth
    ServerManagerCmd -i Desktop-Experience

    7. Restart the System { very important}

    8. Install Exchange 2007 sp1 { not exchange 2007} with typical setup

     

    i hope i works fine

     

    bye take care Smile

    Sekhar

    Thursday, October 23, 2008 2:31 PM
  •  

    RESOLUTION
    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems
    might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
    322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows
    To resolve this problem, use one of the following methods: • Enable IPv6 in Local Area Connection on the Windows Server 2008-based computer.
    • Use Registry Editor to completely disable IPv6 on a Windows Server 2008-based computer.

    To completely disable IPv6 on a Windows Server 2008-based computer, follow these steps:


    1. Open Registry Editor.
    2. Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
    3. In the details pane, click New, and then click DWORD (32-bit) Value.
    4. Type DisabledComponents, and then press ENTER.
    5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.
     
    Note The 0xffffffff value or the 4294967295 value disables all IPv6 components, except for the IPv6 loopback interface.

    Friday, October 24, 2008 2:32 PM
  • Hi Guys,

    I had the same issue, and as you say, I just enabling the IPV6 and now the installlation is working well.

    Thank you
    Wednesday, November 26, 2008 8:02 PM
  • I can't believe how ridiculious this is... After all that, all you had to do is enable IPv6!... I've spent countless hours on this... Thank you soo much...
    Suler Abou
    Thursday, December 11, 2008 4:54 AM
  • People;

    I switched from Virus Exchange a couple of years ago. There are lots of viable alternatives out there. I went with Kerio. Instead of buying a new Virus Exchange server it runs on top of an existing file/print server servicing 200 people. It cost 1/4 in licensing, even less in cost of ownership. A disaster recovery only takes 5 minutes + data restore, about 30 minutes total with 40GB of data when I tested. A single user can have a GB mailbox with no performance hit. Everything on this P4 2 GHz server with Kerio outperforms any Exchange server with 100 cores and 10TB of memory. Yeah, really. Searches are almost instant accross many GB.

    It is time to tell M$ where to put this legacy Exchange system.

    Sunday, January 11, 2009 3:26 PM
  • Thanks the IPV6 and the restart the Transporter Services work well.
    Wednesday, March 18, 2009 12:22 PM
  • Enabling ipv6 worked in my case too. Do you know if we can then disable it after the installation is complete?
    Monday, May 11, 2009 5:20 PM
  • You can disable IPv6 after you install Exchange 2007 SP1, however, note that IPv6 is required in order to install Exchange 2007 on Windows 2008.

    Check this FAQ on IPv6: http://technet.microsoft.com/en-us/network/cc987595.aspx and look for "How do I disable IPv6 in Windows Vista and Windows Server 2008?"


    Also see:

    IPv6 Support in Exchange 2007 SP1

    http://technet.microsoft.com/en-us/library/bb629624.aspx

    SF - MCITP:EMA, MCTS
    Tuesday, May 19, 2009 2:04 AM
  • Enabling IPv6 did it for me.  I kept a static IPv4 address, and let Windows Server 2008 manage the IPv6 stuff.
    I wracked my brain for about an hour before checking this forum.  Thanks for your expert advice.  It's much appreciated.

    Thursday, May 21, 2009 3:53 AM
  • Same solution for me for Exchange 2010... thanks!
    Thursday, September 03, 2009 1:42 AM
  • Enabling IPv6 did not work for us .. The same "error message" after enbling IPv6, restrating server and Re-starting installation .. Reinstallation stoppet at the same place.
    Anyone knows if there is anything spcial when enabling IPv6?

    Thanks
    Wednesday, September 09, 2009 10:44 AM
  • is SMTP installed on the server?  If it is remove it.

    What version of Windows are you using?
    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
    Wednesday, September 09, 2009 12:07 PM
  • Thanks, Scott .. We will try your tip .. Windows 2008 is on that server ..
    Right now I'm " waiting for the installation to fail again ", after trying a tip of disabling IPv6 : http://support.microsoft.com/?kbid=952842 ..
    But I'll try your tip soon .. I'll let you know how it went .. But would you prefer IPv6 being installed before uninstalling SMTP?

    -- Hiwa
    Wednesday, September 09, 2009 12:43 PM
  • SMTP was NOT installed !!
    Wednesday, September 09, 2009 12:50 PM
  • IPv6 should be installed for the Hub Transport role to sucessfully install on W2K8.  What version of W2K8 are you using?  SP1?  Sp2?  R2?

    SMTP should NOT be installed which is good.

    What kind of error are you seeing?
    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
    • Proposed as answer by Hiwa M. _ Thursday, September 10, 2009 7:43 AM
    Wednesday, September 09, 2009 3:19 PM
  • Hi Scott ..
    Windows 2008 Standard " version 6.0 " Service Pack 2
    *****************************
    Hub Transport Role Status: Strating the Microsoft Edge Transport service Elapsed Time: ....
    ****************************
    After around 12 minutes it fails:
    Error:
    Service 'MSExchange Transport' failed to reach 'Running' on this server. Elapsed Time: 00:12:15
    In the EventViewer I found these two Error Events:
    Event 2114, MSExchange ADAccess
    Error:
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1792). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

    Event 7005, MSExchangeTransportLogSearch
    Error:
    Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server localhost did not return a suitable domain controller.
    at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
    at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts() at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext() at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId) at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)
    at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
    at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
    at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindServerByFqdn(String serverFqdn)
    at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindLocalServer()
    at Microsoft.Exchange.Transport.LocalServerConfiguration.<>c__DisplayClass2.b__0()
    at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
    at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount).

    Thursday, September 10, 2009 7:54 AM
  • Based on your error it sounds like it is AD related.  Are your domain controllers in the Active Directory site where exchange exists at least W2K3 SP1? 

    Are you deploying at least Exchange 2007 SP1? 
    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
    Thursday, September 10, 2009 11:56 AM
  • Another thought could me permissions to manage the autiting logs: http://balld31.blogspot.com/2008/09/exchange-servers-need-manage-auditing.html


    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
    Thursday, September 10, 2009 1:25 PM
  • Hi

    The answer is Yes to both questions.

    Regards, Hiwa

    Friday, September 11, 2009 11:03 AM
  • K.  Check the auditing log permissions based on the URL above.

    You may also want to do a setup /p /on:org name again. 

    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007
    Friday, September 11, 2009 3:42 PM
  • I also enabled IP V6, then ran install again and was sucessful.
    Wednesday, September 23, 2009 4:31 PM
  • All I can say is I've never installed so much stuff just to get an Exchange Server running. I could care less about IPv6 but re-enabling did the trick just as it did for everyone else on this page. I'm just glad I ran across this article and am most grateful for a lot of you die hards. :)
    Friday, November 13, 2009 6:26 AM
  • Glad to see this Thread is helping so many users!
    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007 -- http://www.scottfeltmann.com
    Saturday, November 14, 2009 10:47 PM
  • Enabling IPv6, and restarting all Exchange Service did it for me as well.


    Mohammed
    Thursday, November 19, 2009 11:30 AM
  • Hi Guys,

    First post! I am attempting an install of Exchange 2007 (SP1) onto Server 2008 (x64) and I am having the same problem that is being described in this thread. However, after trying ALL of the proposed fixes, I am still getting the same service error, i.e.

    Service 'MSExchangeTransport' failed to reach status 'Running' on this server.

    I have tried the following:

    - IPv6 was already enabled so I tried auto IPing and a static IP - no luck
    - Adding a '*' send connector - no luck
    - disabling IPv6 fully - i.e. registry edit method

    Unfortunately none on the above is working for and at this stage I am at a total loss. Any help and/or suggestions would be GREATLY appreciated!

    Thanks...






    Monday, November 23, 2009 1:56 PM
  • What other Role/Application is on your exchane server?

    Can you by chance post any event logs with errors in them for examiniation?


    SF - MCITP:EMA, MCTS: MOSS 2007, OCS 2007, Exchange 2007 -- http://www.scottfeltmann.com
    Monday, November 23, 2009 3:04 PM
  • Error:Service 'MSExchange Transport' failed to reach status 'Running' on this server.

    Hi,

    I had IPv6 feature on my network card disabled as I set a static IPv4 IP address for that adapter. Even though all prep work for my installation was done my Hub Transport instalation kept failing resulting in the rest of the installation failing.
    After reading this post I enabled my IPv6 feature on the Network card and my installation completed successfully without any issues.
    This is for a Server 2008 SP1 x64 installation and 2007 Exchange x64 SP1.


    So thanks for this post made you saved my bacon but I still cant find any info on why the IPv6 feature is so important if I'm using IPv4 addressing schem.

    Sunday, December 27, 2009 3:29 PM
  • Error:Service 'MSExchange Transport' failed to reach status 'Running' on this server.

    Hi,

    I had IPv6 feature on my network card disabled as I set a static IPv4 IP address for that adapter. Even though all prep work for my installation was done my Hub Transport instalation kept failing resulting in the rest of the installation failing.
    After reading this post I enabled my IPv6 feature on the Network card and my installation completed successfully without any issues.
    This is for a Server 2008 SP1 x64 installation and 2007 Exchange x64 SP1.


    I still cant find any info on why the IPv6 feature is so important if I'm using IPv4 addressing schem.
    • Proposed as answer by Funnybaai Sunday, December 27, 2009 3:31 PM
    Sunday, December 27, 2009 3:31 PM
  • Enabling IPV6 did the trick !!! Thank you Scot, you the Man !!!

    Cheers

    Steve

    Thursday, April 29, 2010 3:41 PM
  • Also worked for me... irritating though since I will not be using IPv6. 
    Monday, June 07, 2010 1:35 AM
  • Enabling IPV6 did the trick. Hats off to u guys!! Cheers
    Wednesday, June 09, 2010 9:50 AM
  • it is worked for me.... thanks alot 

    shahul

    Saturday, November 13, 2010 9:05 AM
  • Thanks for posting that reply.  That was exactly the solution that worked for me too.  Strange that it is required. 
    Mark Hill
    Wednesday, December 01, 2010 11:45 PM
  • I had the identical problem, when install Exchange 2007 on Windows 2008 SP2.

    Hub Transport Role Failed
    Error: Service 'MSExchangeTransport' failed to reach  status 'Running' on this server

    Enabling the IPv6 protocol, restarting the server and then re-running the install did it for me ;o)

     

    Thanks Scot

    Friday, December 10, 2010 10:40 PM
  • Scott,

     

    Thanks for the info. I was ten seconds from rage quit on this issue.

     

    BTW.  This was 2010 on a 2008 SP2 box

    Saturday, January 29, 2011 9:25 PM
  • Scott,

     

    Thanks for the info. I was ten seconds from rage quit on this issue.

     

    BTW.  This was 2010 on a 2008 SP2 box


    Tuesday, March 22, 2011 10:08 AM
  • Thanks Scott. Same error with Exchange 2010 SP1 on Windows Server 2008 SP2. I enabled IPv6, I rebooted and rerun the Exchange setup ... and everything started to work :-).
    Saturday, April 23, 2011 1:05 AM
  • Thank You,  badazdk.... Worked for me...
    Saturday, April 30, 2011 10:26 AM
  • i enabled IPv6, rebooted the Server, and re-run. now every thing is ok. 
    Wednesday, July 06, 2011 9:48 PM
  • Enabling IPv6 on my Windows 2008 Server worked for me.  I re-enabled IPv6, reboot the server, and then re-ran the Exchange wizard.  Now I am all set.
    Wednesday, August 10, 2011 12:24 AM
  •  Scott N. Weber wrote:

    I solved the problem by installing IPv6 protocol. I originaly turned it off because Exchange wanted a static IP address and I could not set it on the IPv6 because it kept telling me it was invalid. If anyone has information on this please let me know.

     

     

     

    Worked also for me.!!! thanks Scott!

     

    this also worked for me, thanks scott!

    Its seems like the topology scan does not complete if IPV6 is not enabled and therefore the Transport role will not start.


    Tuesday, September 20, 2011 12:47 PM
  • I solved the problem by installing IPv6 protocol. I originaly turned it off because Exchange wanted a static IP address and I could not set it on the IPv6 because it kept telling me it was invalid. If anyone has information on this please let me know.


    Yes, it still works - also applicable to Exchange 2010 on 2008 R2 Server.
    that was almost but not quite entirely unlike me
    Friday, October 07, 2011 5:28 PM
  • Very right indeed, had the same problem i thought what da hack? But just enabling v6 and installation went further on. Didnt need a reboot.
    Monday, December 19, 2011 2:18 PM
  • I hadn't disabled IPv6 and it bit me! Heres some more information that might be helpfull,


    Exchange 2010 Install Error - 'Service 'MSExchangeTransport' failed to reach status 'Running' on this server'


    Pete
    PeteNetLive
    Friday, March 02, 2012 9:05 PM
  • It does work for me too. Many thanks
    Sunday, April 29, 2012 1:29 PM
  • I had the same issue, resolved after setting McAfee Services to "Manual" and reboot the server.
    Wednesday, June 13, 2012 6:39 AM
  • Worked for me too..... Great solution.

    Amol

    • Proposed as answer by Amol_scripting Saturday, October 12, 2013 3:41 AM
    • Unproposed as answer by Amol_scripting Saturday, October 12, 2013 3:41 AM
    Saturday, October 12, 2013 3:40 AM
  • IPv6 fix did not work for me.I had to call Microsoft and this was my fix on 2 Exchange 2007 SP3 (virtual) servers.

    When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process and the attached debugger while you are trying to debug. To adjust this time-out period, follow these steps:

    1. In Registry Editor, locate, and then right-click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    1. Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
    2. Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
    3. Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify. The Edit DWORD Value dialog box appears.
    4. In the Value data text box, type TimeoutPeriod, and then click OK

      Note
      TimeoutPeriod is a placeholder for the value of the time-out period (in milliseconds) that you want to set for the service. For example, if you want to set the time-out period to 24 hours (86400000 milliseconds), type 86400000.
    5. Restart the computer. You must restart the computer for Service Control Manager to apply this change.

    Hope this helps some one.

    Thursday, June 04, 2015 4:01 PM