Exchange 2007 HUB Transport service will not start

  • [アーティクル]

We are seeing lots of this issue today after customers install security updates.  You may also see these events in your applicatiopn log:

Event ID   : 7009
Type        : Error
Message  : Timeout (30000 milliseconds) waiting for the Microsoft Exchange Transport service to connect.

Event ID  : 7000
Type       : Error
Message : The Microsoft Exchange Transport service failed to start due to the following error: %%1053

 We are seeing several different things resolve this one, depending on what else you are running on the box.  

The quick & easy one that seems to work in all cases is to change the Transport Service to use the local system account.  (NOTE:  Please don't use this long term, just to get you up and running until we have a better answer.)

Other possibilities for resolution:

  • Read the article on our Exchange Team Blog:  https://msexchangeteam.com/archive/2008/07/08/449159.aspx
  • Look at KB944752 and set the timeouts.
  • Remove RU3
  • Remove the other updates that were applied.
  • Look for event 4999 in the application log.  It points to calculateTiServerRoutes.  Do you have a 3rd party app that uses the same virtual server names as Exchange?  For example; Legato CoStandby Server?  If so,use adsiedit and check the attributes of the server.  I suspect that you will see the same value for ncacn_p_tcp in the networkaddress attribute.  This is the problem.  One needs to be removed or changed.

I will keep updating this blog as we get new information on this one.

Comments

  • Anonymous
    January 01, 2003
    I've had a nightmare time with this problem the last two days. I have googled the issue to find hardly any info. I came across the post and followed the instruction of give the LOCAL SYSTEM account the log on as right. I will be keeping tabs on this post to see what other users come up with and to also see what the Transport service accoutn should be eventually set to.

  • Anonymous
    January 01, 2003
    Any suggestions on the following error: Event ID: 4999 Watson report about to be sent to dw20.exe for process id: 3992, with parameters: E12, c-RTL-AMD64, 08.01.0375.002, edgetransport, M.E.Transport, M.E.T.C.RoutingTables.CalculateE12ServerRoutes, System.ArgumentException, cb00, 08.01.0375.002

  • Anonymous
    January 01, 2003
    For me at least, this was a managed code issue (Discussed in the team blog linked above).  My exchange servers do not have internet access (as I imagine is the case for thousands of installs).  Quickest fix is to set up your hosts file to point at localhost for the crl servers.  (set crl.microsoft.com, crl1 – crl5.microsoft.com to 127.0.0.1 in your HOSTS file).