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.
Anonymous October 17, 2009 at 11:57 am
THe same problem exist with EXC 2010. This solution works
Thanks!
NorDemoniac November 5, 2009 at 7:21 pm
YES!
Thank you so much.
EXC 2010 was bugging me SO much…
Do you have any idea why this happens?
Rajith Jose Enchiparambil November 6, 2009 at 8:33 am
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.
Anonymous February 3, 2010 at 2:45 pm
The solution provided here worked for Exchange 2010 as well.
Thanks a lot!!!!
Rajith Jose Enchiparambil February 3, 2010 at 2:48 pm
Thanks for the update Anonymous.
Anonymous February 25, 2010 at 4:22 pm
The same problem is observed in Exchange 2010. The solution provided here works just fine. Thank you!!!!
Rajith Jose Enchiparambil February 25, 2010 at 4:33 pm
Glad to know that the article helped you.
Anonymous June 2, 2010 at 7:55 pm
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
Rajith Jose Enchiparambil June 3, 2010 at 8:28 am
Thanks Asgeir.
Manuel Alberto (-ECUADOR-) October 28, 2010 at 2:58 pm
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
Rajith Jose Enchiparambil October 29, 2010 at 3:42 am
Thanks Manuel.
gf04020803 November 23, 2010 at 2:09 am
Wow!! You're my saver.I also encounter this hell problem.I'll try your solution.Thanks.
Rajith Jose Enchiparambil November 23, 2010 at 3:46 am
Thanks Gf04020803
Anonymous November 23, 2010 at 3:21 pm
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
Rajith Jose Enchiparambil November 24, 2010 at 4:39 am
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.
MSkirl February 16, 2011 at 3:38 pm
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.
Alex Dybenko February 19, 2011 at 12:33 pm
Thanks, works for my Exchange 2010 installation!
Rajith Jose Enchiparambil February 19, 2011 at 12:50 pm
Good to know that it helped you Alex.
JesuitJeff June 22, 2011 at 2:53 pm
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!
Rajith Jose Enchiparambil June 22, 2011 at 6:13 pm
Glad to know that it helped you JesuitJeff
Prethesh Kumar Bhalotia January 12, 2012 at 5:29 am
Thanks a lot. It really worked:)
Rajith Enchiparambil January 13, 2012 at 10:29 am
Prethesh, Glad that the post helped you.
amodi January 13, 2012 at 3:26 pm
thanks you i solve the problem
Rajith Enchiparambil January 13, 2012 at 4:16 pm
Glad that the post helped Amodi.
francis (GHANA) April 25, 2012 at 3:38 pm
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)
Rajith Enchiparambil April 26, 2012 at 3:05 pm
Glad to help Francis. Thanks.
vlad May 17, 2012 at 2:02 pm
Спасибо Вам Большое!!!
Rajith Enchiparambil May 22, 2012 at 9:16 am
Thanks Glad.
Rakesh August 31, 2012 at 3:41 pm
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
Rajith Enchiparambil September 17, 2012 at 10:27 am
Hi Rakesh,
Did you try a restart before attempting to install again?
Dandy September 18, 2012 at 3:08 pm
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
Rajith Enchiparambil September 19, 2012 at 7:58 am
Thanks for the tip Dandy.
alaa kamal January 13, 2013 at 12:19 pm
the same problem exist
Rajith Enchiparambil February 1, 2013 at 8:15 am
Is it fixed?
Kiran March 14, 2013 at 5:16 pm
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!!!
Rajith Enchiparambil April 22, 2013 at 7:06 pm
That is another way of doing it.
Thanks Kiran.
md sohrab alam April 20, 2013 at 7:21 am
hi dear
thanks for writing solution
i have got the soution for this problem
thanks
Rajith Enchiparambil April 22, 2013 at 6:50 pm
Thanks Sohrab