‘MsExchange’ Transport Failed To Reach Status ‘Running’ On This Server…

Below is a common error that comes up when you install Exchange 2007 Server on a Windows 2008 Server. The hub transport role fails with an error “MsExchange transport failed to reach status running on this server”. Mailbox & CAS installations are cancelled as well, if it is a typical exchange 2007 installation.

Reason: By default, IPV6 is enabled on a Windows 2008 server and you have disabled it in the network connections properties, but not fully.

Solution is to enable IPV6 in NIC properties, but disable IPV6 in registry and re-run the setup.

To disable IPV6 fully on the 2008 server. Follow the steps to do so.

Launch registry, navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters. In the details pane, click New, and then click DWORD (32-bit) Value. Type “DisabledComponents” (without quotes) and then press enter. Double-click DisabledComponents and type 0xffffffff in Hexadecimal or 4294967295 in Decimal. Close the registry editor.

Now, navigate to C:WindowsSystem32DriversEtc and open the hosts file in notepad. Delete the IPV6 entry.

Save & close. Re-run the setup.

Rajith

Rajith Enchiparambil

Cloud Architect & Blogger with interests in Microsoft 365, AWS & Azure. I am active on Experts Exchange & TechNet forums and I am a technical author for SearchExchange. Follow me on Twitter, LinkedIn or Facebook for the latest updates. For consultancy opportunities, drop me a line.

53 thoughts on “‘MsExchange’ Transport Failed To Reach Status ‘Running’ On This Server…”

  1. Hi NorDemoniac,

    This is because, if you uncheck IPv6 in the NIC properties, it is still enabled for all tunnel interfaces & is not fully disabled. Hence, the registry edit to disable IPv6 completely on all interfaces.

    Reply
  2. Thanks a lot for this solution, it works pretty fin. I have surched the hole IN, for solution on this problem and found this one. So everyone with this problem TRY THIS ONE. It WOOOORKS.

    Asgeir

    Reply
  3. Is a good aport….i aplicate and yes the installation was successful….

    Excelente aporte aunque en mi caso fue necesario formatear mi sistema operativo habilitar el direccionamiento IPV6 que lo habia desabilitado en las opciones del adaptador de red…asignarle cualquier dirección IPV6..valida y listo todo funciono correctamente_____GRACIAS____THANKSSSSS

    Reply
  4. I am getting the same error when trying to upgrade to SP2 from SP1, but the exchange 2007 server is running on Windows 2003 R2 SP2. We were in the process of migrating over from Exchange 2000 to 2007 when we were asked to upgrade to fix a user problem. (all our mailboxes have been migrated but he Exchange 2000 server is the bridgehead and still hosts stuff like the recipient policies and GAL

    Reply
  5. As a start, you need to move all 2000 services to your 2007 server. Co-existence will always bring new issues on a daily basis.

    Reply
  6. did above, still not working, then removed all X07 routing groups etc from X03, then checked BPA on X03, with recommendation of SuppressStateChanges registry entry, then restarted X07 new install, did servermanagercmd according to
    E2007SP1_W2008prepreqXMLs, then Setup.com /PrepareLegacyExchangePermissions, Setup.com /PrepareSchema, Setup.com /PrepareAD. (Did not do any smtp connector to internet, because it screwed up the X03 environment.)
    Not sure, what did the trick, but this did the trick.

    Reply
  7. Rajith you're a lifesaver. Struggled with this problem installing Exchange 2007 on a Windows 2008 R2 server for 2 days and finally found your fix. Worked like a charm. Thank you!

    Reply
  8. THANKS RAJITH, U REALY HELPED ME WHEN ALL HOPE WAS LOST. I’M NOW WAITING TO FINISH MY INSTALLATION OF THE EXCHANGE SERVER 2010. THANKS MAN. AYEKOOOOOOOOOO (THANK U IN GHANAIAN LANGUAGE)

    Reply
  9. Hello Sir,

    I am trying to install a typical Exchange 2010 installation on Server 2008 R2. All is well
    upto the prerequisites but when the process comes on Hub transport Role it shows the
    following error.I applied your resolution but never succeded,it came back with an error.

    The following error was generated when “$error.Clear(); if ($RoleStartTrans
    portService) { start-SetupService -ServiceName MSExchangeTransport }” was run: ”
    Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”
    ‘MsExchange’ Transport Failed To Reach Status ‘Running’ On This Server

    Reply
  10. Thanks to all, what i did was very simple; the ‘Obtain DNS Server addresses was on, so selected obtain DNS Server automatically and then restarted the service and re-ran setup…then all was good.

    Regards

    Reply
  11. We also encountered the same issue in our case we have modified the host file entry as below 127.0.0.1 point it to Crl.microsoft.com

    After modifing the host entry we have ran the setup again it worked!!!

    Reply
  12. Hi Rajith;

    I’ve been having this issue for 4 days sinces the death of one of my DC’s.

    Log Name: Application
    Source: MSExchange ADAccess
    Date: 28-06-2013 11:00:58
    Event ID: 2114
    Task Category: Topology
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: HUGIN.domain.company.dk
    Description:
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3264). Topology discovery failed, error 0x80040920 (LDAP_NO_SUCH_OBJECT). 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 Xml:

    2114
    2
    3
    0x80000000000000

    432529
    Application
    HUGIN.domain.company.dk

    MSEXCHANGEADTOPOLOGYSERVICE.EXE
    3264
    80040920
    LDAP_NO_SUCH_OBJECT

    Have you ever recovered from this type of error?

    Reply
    • Hi Thomas,

      How many other DCs do you have? Is the DC/GC name hard coded in Exchange?
      Run Get-AdServerSettings | fl and paste the output here.

      Reply
  13. Solution is to enable IPV6 in NIC properties, but disable IPV6 in registry and re-run the setup.

    To disable IPV6 fully on the 2008 server. Follow the steps to do so.

    Launch registry, navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters. In the details pane, click New, and then click DWORD (32-bit) Value. Type “DisabledComponents” (without quotes) and then press enter. Double-click DisabledComponents and type 0xffffffff in Hexadecimal or 4294967295 in Decimal. Close the registry editor.

    Now, navigate to C:WindowsSystem32DriversEtc and open the hosts file in notepad. Delete the IPV6 entry.

    Thanks My exchange server 2010 workin ok

    Reply

Leave a Comment