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_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters. 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:\Windows\System32\Drivers\Etc and open the hosts file in notepad. Delete the IPV6 entry.
Save & close. Re-run the setup.
20 comments:
THe same problem exist with EXC 2010. This solution works
Thanks!
YES!
Thank you so much.
EXC 2010 was bugging me SO much...
Do you have any idea why this happens?
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.
The solution provided here worked for Exchange 2010 as well.
Thanks a lot!!!!
Thanks for the update Anonymous.
The same problem is observed in Exchange 2010. The solution provided here works just fine. Thank you!!!!
Glad to know that the article helped you.
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
Thanks Asgeir.
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
Thanks Manuel.
Wow!! You're my saver.I also encounter this hell problem.I'll try your solution.Thanks.
Thanks Gf04020803
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
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.
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.
Thanks, works for my Exchange 2010 installation!
Good to know that it helped you Alex.
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!
Glad to know that it helped you JesuitJeff
Post a Comment