I tried to install the HubTransport Role on a fresh installation. Setup fails with the error message: Error:Service 'MSExchangeTransport' failed to start. Check eventlogs for possible reasons for the service start failure. When I look in the application eventlog I see that the transport service continously tries to start but produces an error. The eventid's are: MsExchange Common(General) 4999, Microsoft Exchange Server 5000 and Microsoft Exchange TransportService(ProcessManager) 1016. Also the Setup Logs have no specific error: [29.07.2006 19:42:33] [2] [ERROR] Unexpected Error[29.07.2006 19:42:33] [2] [ERROR] Service 'MSExchangeTransport' failed to start. Check eventlogs for possible reasons for the service start failure.[29.07.2006 19:42:33] [2] Ending the task's processing.[29.07.2006 19:42:33] [1] The following 1 error(s) occurred during task execution:[29.07.2006 19:42:33] [1] 0. ErrorRecord: Service 'MSExchangeTransport' failed to start. Check eventlogs for possible reasons for the service start failure.[29.07.2006 19:42:33] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceFailedToStartException: Service 'MSExchangeTransport' failed to start. Check eventlogs for possible reasons for the service start failure.[29.07.2006 19:42:33] [1] [ERROR] Service 'MSExchangeTransport' failed to start. Check eventlogs for possible reasons for the service start failure.[29.07.2006 19:42:33] [1] Setup is halting task execution because of one or more errors in a critical task.[29.07.2006 19:42:33] [1] Finished executing component tasks.[29.07.2006 19:42:33] [1] Ending the task's processing.[29.07.2006 19:44:49] [0] ExsetupUI Run method returned 0[29.07.2006 19:44:49] [0] End of Setup[29.07.2006 19:44:49] [0] ********************************************** I sucessfully installed Mailbox and CAS Roles on other servers. The servers have the same configuration, because I use virtual machines... The only non-standard parameters I use is that I install the server on d:\exchsrvr and not at the deafult path... Any help would be appreciated! Christian Schindler

There used to bea known issue where if you had connectors created during previous builds, the latest transport would refuse to start. Is this a clean install?You might try setting the eventlog ligher as well. You can run get-eventlog (the output is a little too verbose right now) to see the different services and their logging level and then change it using set-eventlog to something higher: http://www.microsoft.com/technet/prodtechnol/exchange/E2k7Help/797f1691-32b7-4752-bb01-fea54cc28e1c.mspx?mfr=true Set-EventLog componentName -level High Thanks, ~vivek

Vivek,thanks for your "lightning fast" reply! Now I installed the HUB role with the /DoNotStartTransport Option. So setupcompleted at least. But the service still doesn't start...One of the eventlog entries has an error message of "m.e.isam.isamdatabasedirtyshutdownexception; c428"...I assume that the transport database is causing the error because it is in a dirtyshutdown state...strange.Anyway I will change the logging level and have a look again.Thanks!Christian

Increasing the eventlog level to "high" had no effect...the same errors are logged.Is there a way to increase the logging level for ESE?ThanksChristian

I got it working:After using the default install path, everything was fine.It seems that there's an issue when you use a non standard-path to install the HUB-Role...BTW: Before I started the install in the default path I had a second look at the eventlog...I found the following error message:Source:MSExchange TransportServiceCategory:ProcessManagerID:1016Message:The worker process crashes continuously on startup: D:\exchsrvr\Bin\edgetransport.exe. The service will be stopped.The edge role isn't installed at the server(must not be)! Maybe this is the cause for this...Should I open a bug report?ThanksChristian

Great catch---yes please go ahead and file a bug. Thanks, ~vivek

One work around to this problem, that I discovered, is to use a Domain Administrator user to start the MS Exchange Transport service. Once I removed the Network Service user, the service started without an issue. Then I reinstalled the Hub Transport Role, without an error.

I discovered the same problem and changing service account didn't help.Anyway, Ifound another workaround to this problem: I uninstalled the failed installation with PowerShell's basic uninstall option ./setup /mode:uninstall (I had only HT role in this virtual machine) and then installed it again using PowerShell command ./setup /role:HubTransport. Everything went fine and lot fasterthan using grapihal installation (I guess:-) )

I have the same probelm and I didn't discover any change with Domain Admin user. Now I'm reinstalling HT role from MSH.

What is the exact syntax from the EMS for installing the hubstranport. I keep getting a pop up telling to go to control panel to install it. I can't increase logging level either, keeps returning error saying not a valid cmdlet

Hi! The syntax should be: ./setup /role:HT /OrganizationName:whatyouwant /TargetDir:whatyouwant By the way I tried everything but the only solution was reinstalling it to default directory. JF

This worked for me as well. I did not try installing to default location, but I did try re-installing with no success. However when I changed the account to my admin account instead of the network service account. I did add/remove and tried re-installing the hub transport and it completed successfully. Thanks for the tip! :)

Hello, I had exactly the same error message as you described in your post. I tried the solutions suggested by the replies... Changing the account used to start the Transport service to a domain admin count permitted to start the service, but then I had problems with the mail not being delivered in the user's mailbox, but they queued up. After searching a while, I decided to call Product Support. It seems that there is an issue with the transport service if you install it on a server which is a Global Catalog. There is a workaround for this: start the service with the Local System Account. If you want more info about this; send me an e-mail tom [at] synergysolutions [dot] be Tom

Hi, I've had similar problems and error messages to those described in this post, and some others about the Hub Transport role. Thought I'd share my experiences in the hope that someone might have some ideas, or might help someone else find a workaround. I originally had the error during setup that it could not find the folder "....\64", which does not exist on the CD. Restarting setup got around that one, but then ran into trouble with edgetransport.exe crashing... Our AD topology consists of the root domain and2 child domains - each an individual AD site and geographically separated, connected via WAN. Currently, those 3 sites have Exchange 2003 servers (which are also the sole DCs for those domains). We're adding new Exchange 2007 servers to replace each of those and decommission existing servers, plus adding 2 new child domains (and AD sites) with new servers; and an additional DC to the root domain. Our topology is slowly improving.... Anyway, here's what I ended up trying: DC #1 in the root domain - run Transport service as LocalSystem or Domain admin - error "No such table or object", and various Isam exceptions. Just won't work in any form. DC #2 in the root domain - run Transport service as LocalSystem - works. But then cannot authenticate with Exchange 2003 servers in the organisation. Add this machine's computer account to the Administrators group in the domain - can now run as NetworkService... Member server in forest - installed and worked first time. New DC in existing child domain - installed and worked fine first time. New DC innew child domain - worked first time. SoI don't have a problem with the child domains, except for some authentication trouble between the Hub Transports - but that's another issue. For now the member server is providing the routing group connector to the Exchange 2003 servers, and DC#2 is acting as the Hub Transport for the rest, including incoming/outgoing mail. Not ideal I know to have a DC exposed to the net like that, but we don't have many servers to work with... The member server will be taken out of the loop once the Exchange 2003 servers are gone. I would like to be able to have DC #1 or DC #2 in the forest be able to run the Hub Transport role properly. I can get it to run on DC #2 by adding NetworkService to the Admins group, but would rather not have to do that if I can avoid it. Seems to suggest that there's something wrong in the root domain in the forest, as all child domains new or existing, and any member serverdoesn't present any issue at all with the Transport service. The root domain has been migrated from NT4 domain to a 2000 AD domain, and then to a 2003 domain, so there's probably some leftovers in there somewhere causing trouble, but who knows where... If anyone has any ideas for a long-term solution or better workaround, it would be very welcome!

I had same problems as some of you indicated.I was installing Exchange 2007 from Production Copy DVD of Exchange 2007 Standard. Here is the strategy that I took after receiving the errors on multiple occassions.Background:We have 1 Win2K SP4 DC and 1 Win2k3 R2 DC, so installing Exchange 2007 from GUI is a NONO, atleast according to all the readings that I have done. So the only option is to install from command line using the Unattended setup (Setup.com) with various different switches. You can not use Setup.exe with switches.When I was receiving the error message of:"An unexpected error has occurred and a Watson dump is being generated: Access to the path 'Q:\Setup\ServerRoles\Common\64' is denied.", I was installing all the roles at one time using the following command line:setup.com /mode:install /r:h,c,m,t /t:"d:\program files\Microsoft\Exchange Server" /DomainControllerCNAME /EnableLegacyOutlook /LegacyRoutingServer:LegacyExchangeName /EnableErrorReportingand I would receive the error message.I then tried to install all the roles seperately using the following command lines one at a time and every thing was successful.Solution:PS: Please replace DCNAME with the name of your Win2k3 SP1 DC and LegacyExchangeName with your E2k or E2k3 Exchange Server.1. Client Access setup.com /mode:Install /r:c /t:"d:\program files\microsoft\exchange server"/domaincontroller:DCNAMEWelcome to Microsoft Exchange Server 2007 Unattended SetupPreparing Exchange SetupThe following server roles will be installed Management Tools Client Access RolePerforming Microsoft Exchange Server Prerequisite Check Client Access Role Checks ......................... COMPLETEDConfiguring Microsoft Exchange Server Copying Exchange files ......................... COMPLETED Client Access server role ......................... COMPLETED2. Hub Transport Rolesetup.com /mode:Install /r:h /domaincontroller:DCNAME /LegacyRoutingServer:LegacyExchangeNameWelcome to Microsoft Exchange Server 2007 Unattended SetupPreparing Exchange SetupThe following server roles will be installed Hub Transport RolePerforming Microsoft Exchange Server Prerequisite Check Hub Transport Role Checks ......................... COMPLETEDConfiguring Microsoft Exchange Server Copying Exchange files ......................... COMPLETED Hub Transport Server Role ......................... COMPLETED3. setup.com /mode:Install /r:m /domaincontroller:DCNAME /EnableLegacyOutlookWelcome to Microsoft Exchange Server 2007 Unattended SetupPreparing Exchange SetupThe following server roles will be installed Mailbox RolePerforming Microsoft Exchange Server Prerequisite Check Mailbox Role Checks ......................... COMPLETEDIf Outlook Web Access is in use, you should replicate the free/busy folder on this server to every other free/busy server in the organization. This step shouldbe performed once Setup completes.Configuring Microsoft Exchange Server Copying Exchange files ......................... COMPLETED Mailbox Server Role ......................... COMPLETEDThe Microsoft Exchange Server setup operation completed successfully.Hope this helps someone out.

Had a similar problem of the Exchange Transport service not starting. Looking through the event logs I also noticed that the security log had two failures for each time I tried starting the service. Using ADSIEdit I gave the Network Service the read and write permissions to the ExchangeServer's Computer Account. Services then started up.

Hi, I had same error, I just configured the exchange transport service to start with local account and that worked for me.