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: http://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.