Hello, Recently we have installed .net Framework 2.0 Sp 1 on Exchange 2007 servers. After rebooting the server, some Exchange Services did not start. Services where: Exchange Service Host, EdgeSync, Transport Log Search. In the event viewer we get the message: Event Type: Error Event Source: Service Control Manager Event ID: 7000 Description: The Microsoft Exchange Transport Log Search service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Event Type: Error Event Source: Service Control Manager Event ID: 7009 Description: Timeout (30000 milliseconds) waiting for the Microsoft Exchange Transport Log Search service to connect. We have the following work-around: Start the Exchange Service Host services, first time it failed, the second time it started en then we can start all the services. Did anyone have a idea what to do? Greetz Heinrich

Hi Greetz, Its looking that net Framework 2.0 Sp 1 did not installed in sevrer correctly. For your problem of not starting service in timely manner you can increase time out vale in exchange to resolve this. By default, the timeout threshold is defined as 30 seconds. This default can be modified for the machine by changing the following registry setting: If this value does not exist then you ned to create it. Name: ServicesPipeTimeout Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control Type: DWORD The value is defined in milliseconds. Increasing the ServicesPipeTimeout value (for example, to 60000 or 90000) can increase the probability that all Exchange services will start successfully without a timeout error. http://msexchangeteam.com/ Anil

Resources: Exchange 2007 services fail to start on boot Exchange Server 2007 managed code services do not start after you install an update rollup for Exchange Server 2007James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com