Exchange Server 2007 SP1 installation: Hub Transport Role fails to install
Hi All;I installed and configured WS 2008 Enterprise 64 bit on an HP ML-350 G5 with 2 X Quad Processors (8 cores in total), 16 GIGA RAM, 2 SAS Drives in RAID 1 (OS and Program Files), 2 SAS drives in RAID 1 for Logfiles and 4 SAS drives in RAID 5 for Databases/Data Files.I installed AD DC, DNS server, IIS 7 and TS. I also ran the xml files to ensure WS 2008 Prereguisites for Exchange Server 2007 SP1 (Base >reboot), MBX, CAS and UM).Installing Exchange Server 2007 SP1, successfully completes the Readyness Checks (Organization Prerequisites, Hub Transport Role Prerequisites, CAS Role Prerequisits and Mailbox Prerequisites, UM Prereuisites).During installation the Organization Preparation, Copy of Exchange Files and Management Tools complete successfully.However The Hub Transport Role install almost to the end, but ultimately hangs at Status: Starting the Microsoft Edge Transport Service.It finally fails to install "Error: Service "MS Exchange Transport" failed to reach status "Running" on this server."Subsequently all other roles are cancelled for installation.Aynone who can give me a hint what I am doing wrong here? What should I have done what I didn't do? Please note that I don't have installed an Edge Server on a separate hardware server or on a virtual server. I only plan to use the Hub Transport Role for now.I also know, that TS actually should be installed on a separate hardware server as well.This setup is intended for serious testing.I look forward to receiving advise from you.Kind regards,switch6343
December 9th, 2008 11:57am
Dear Moderator,could you please move this thread to the "Deploy" section?Thanksswitch6343
December 9th, 2008 12:23pm
Hi, There is a know issues if you have just disabled IPv6 at network settings and you need to change a registry key also. Refer below article for further detail. The installation of the Exchange Server 2007 Hub Transport role may be unsuccessful on a Windows Server 2008-based computer http://support.microsoft.com/?kbid=952842 If you didnt disable the IPv6 then it might be other issue and in that case you need to post the reverent info from setup log to here. Exchange 2007 setup logs and how to use them to troubleshoot setup http://msexchangeteam.com/archive/2007/05/07/438433.aspx However it is not recommended to install Exchange server on Domain controller if it is your production environment otherwise it is okay in testing environment.
December 9th, 2008 3:22pm
Dear customer: In order to better troubleshoot the issue, please help collect the following information: 1. On computer that you have perform Exchange installation program, open Event Viewer, navigate to Windows Logs Application, right click Application and save Events log as .evtx file, send the file to firstname.lastname@example.org for analyze. 2. On computer that you have perform Exchange installation program, navigate to <system drive>\ExchangeSetupLogs\ foler, send ExchangeSetup.log to me. Note: when you send e-mail to me, please let me know the subject of the post. Thanks for your cooperation. Rock Wang - MSFT
December 10th, 2008 5:06am
Hi Amit,thanks for your response. I indeed had disabled IPv6 in all NICs. I now enabled IPv6 in all NICs again and disabled IPv6 by entering the required Registry change, according KB 952842. And that did the trick. Now the installation routine for Exchange Server successfully completed all Exchange Server roles.Thanks so much for making me aware of this KB,Question: as it now has been installed successfully, can I reverse the Registry change again? Or would that create havoc?Please advise.Thank, switch6343
December 10th, 2008 11:54am
Hi Rock,I'll email it to you sometime today.Cheers.
December 10th, 2008 12:00pm
Dear customer: I am very glad to hear that you have resolved the issue. By default, IPv6 is enabled in Windows 2008. Of course, you can delete the registry that you have added and Enable IPv6 in Local Area Connection on the Windows Server 2008-based computer. Hope it helps. Rock Wang - MSFTRock Wang MSFT
December 11th, 2008 10:31am
Hi Rock, I reversed the registry entry and disabled IPv6 again, to reverse what I did as described in my posting before, but that did not work. The system hung. So, I made the registry entry again and enabled IPv6. Everything went fine again.
January 21st, 2009 10:36pm