Hub Transport Service fails to start after installing Exchange 2007 SP2

Each time I have installed Service Pack 2 on an Exchange 2007 server running Hub Transport role, I find the Transport Service does not start when the server is rebooted. I think its just a timing issue though I’m not certain, but the following Microsoft “fix” has resolved my problems.

Configure the Service Control Manager (SCM) time-out value

Increase the default time-out value for the SCM in the registry. To do this, follow these steps:

1. Start Registry Editor.

2. Change the value data for the ServicesPipeTimeout DWORD value to 60000 in the Control subkey. To do this, follow these steps:

a. Click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
b. Click the Control registry subkey.
c. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
d. Click Decimal.
e. Type 60000, and then click OK.

If the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 60000 in the Control registry subkey. To do this, follow these steps:

a. Click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet.
b. Click the Control registry subkey.
c. On the Edit menu, point to New, and then click DWORD Value.
d. Type ServicesPipeTimeout, and then press ENTER.
e. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
f. Click Decimal.
g. Type 60000, and then click OK.

6 Comments

Filed under Microsoft, Windows Server

6 responses to “Hub Transport Service fails to start after installing Exchange 2007 SP2

  1. Malik

    Thanks David, i faced the same problem the other day and probably this key helped me , did you face any other issues after that or is your Hub transport service running successfully.

  2. Hey Malik,

    I have no seen any additional issues and the Hub Transport service is running fine.

    Dave

  3. Malik

    By the way where did you get this resolution from ? as not many forums or technical articles has this issue resolved.

  4. This comment has been removed by the author.

  5. I Experienced this issue as well

    (A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Transport service to connect.)

    With MS support found this article (http://support.microsoft.com/kb/944752) and added the line “generatePublisherEvidence enabled=”false” to the MSExchangeTransport.exe.config file

    service starting up fine now
    Sander

  6. Anonymous

    Hi found your comment looking for similar problem with software StarMoney (Update) – added this param w/ W7H32 w/o success – still shown 30000ms instead of 60000 – what else could be the problem ?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s