MsExchange Hubtransport service fails to start when you upgrade Exchange to service pack2

Environment
=========
DC= Exchange 2007 sp1 on w2k3 sp2 (HT, CAS, Mailbox)
CCR= 1 on Windows 2008 sp1.

When you upgrade Exchange 2007 sp1 to SP2 the setup fails.
MsExchange TRansport service does not start.

In the Exchange setup logs you can see the following.

Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.
Cannot start service MSExchangeTransport on computer
The service did not respond to the start or control request in a timely fashion
 Ending processing.
The following 1 error(s) occurred during task execution:


In System Logs you can see event.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date:  4/7/2011
Time:  5:00:07 AM
User:  N/A
Computer: DC
Description:
The Microsoft Exchange Transport service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


To resolve the issue.

You have to modify the configuration file or create a new configuration file.

It is very important to take the backup of your configuration files before you make the change.
 Method 1

Create configuration file

To create a new application configuration file that contains the switch that is introduced in CLR 2.0 SP1, follow these steps:

1. Create a file, and then name it ApplicationName.exe.config.
2. In a text editor, open this file.
3. Add the following code to the file.

   <configuration>
    <runtime>
               
              <generatePublisherEvidence enabled="false" />
    </runtime> 
   </configuration>
   Save the changes to the file. 
   

You may have to create new configuration files for the following services or programs:

• Microsoft.Exchange.AntispamUpdateSvc.exe
• MsExchangeFDS.exe
• MSExchangeTransport.exe

To change an existing configuration file

Important Before you make any changes to the configuration file, save a copy of the current file in a safe location.

If the configuration file already exists for a service, add the following line to the runtime options section in the file.

<generatePublisherEvidence enabled="false"/>

For example, after you add this entry, the runtime options section will resemble the following example.

<configuration> <runtime>
<generatePublisherEvidence enabled="false"/>
<Other entries>
</runtime> </configuration>

Note Replace <Other entries> in this example with the original lines.

You may have to update the configuration files for the following services or programs:

• Bin\EdgeTransport.exe
• Bin\ExBPA.exe
• Bin\ExBPACmd.exe
• Bin\ExTRA.exe
• Bin\Microsoft.Exchange.Cluster.ReplayService.exe
• Bin\Microsoft.Exchange.EdgeSyncSvc.exe
• Bin\Microsoft.Exchange.Monitoring.exe
• Bin\Microsoft.Exchange.Search.ExSearch.exe
• Bin\Microsoft.Exchange.ServiceHost.exe
• Bin\MSExchangeMailboxAssistants.exe
• Bin\MSExchangeMailSubmission.exe
• Bin\MSExchangeTransportLogSearch.exe
• ClientAccess\PopImap\Microsoft.Exchange.Imap4.Exe
• ClientAccess\PopImap\Microsoft.Exchange.Pop3.Exe

Once this is done.
Start Msexchange Transport service and transport log search service.

Rerun the SP2 setup again and reboot the server.

Can refer to this link.
http://support.microsoft.com/kb/944752
=======================================================



Your comments and feedback are welcome..