Dear All, I have installed exchange 2007 sp1 on an Active directory Global catalog server. Checked all the services and logs, checked thed management consoled and all were ok. Restarted the server and installed Update rollup 2 for exchange 2007 sp1. After i installed the service host service of exchange does not start. In event log i get: The microsoft Exchange Service Host service failed to start due to the following error - the service did not respond to the start or control request in a timely fashion. Also in application event log i get errors: Event ID : 2114 - Process STORE.exe (PID=2640). Topology discovery failed, error 0x80040952(LDAP_LOCAL_ERROR(Client-side internal error or bad LDAP Message)). Look up LDAP error code specified in the event description. To do this use the Microsot Knowledge base article 218185, Microsoft LDAP error Codes. use the information in that article to learn ore about the cause and resolution to this error. Event ID 4999 Watson report about to be sent to dw20.exe for process id:2580, with parameters:E12,c-RTL-AMD64, 08.01.0278.002, M.Exchange.ServiceHost,Unknown, unknkown, S.ServiceProcess.TimeoutException, 0,unknown.ErrorreportingEnabled:False Event ID 2102 Process MAD. EXE (PID=4268). All Domain Controller Servers in use are not responding: ibmserver.law.local Please if anyone knows how to start Service Host service please let me know. thanks

Exchange Host Service depends on AD Topology Service. Try to restart all Exchange Services and see hosted services start along with them. Check below article if it helps. This may occur when the domain controller and other Exchange-Server-dependent services did not start completely when Exchange 2007 tries to start their services. Exchange 2007 services cannot start automatically after you install Exchange 2007 on a global catalog server

Hello, Panayiotis. I managed to get the service started and fully functional after stoppingand setting to disabled a service called HP Insight Foundation Agents (C:\WINDOWS\system32\CpqMgmt\cqmghost\cqmghost.exe). I was able to trace that using Filemon and Regmon. I really don't know why or what Xchg Service Host looks on this service. Probably it's because the name of the proccess contains the word "host". If that is true, then it's a bug on Xchg 2k7 SP1 + some rollup pack. For the other errors you encountered, it's seems that you have "Dr. Watson" activated on your system, which is a real-time software debugger for Windows. It jumped on the proccess after it crashed, as a result of the timeout.No big deal. The event log that reports an error on LDAP seems more serious and deserves a cautious investigation. Regards

Dear Amit, Tried that but still the exchange service host does not start. Thank for your help.

Guys,I hit the same issue after applying Exchange 2007 SP1 Update Rollup 2, where the Exchange Service Host service does not start in a timely fashion.What fixed it for me was the info in this article: Exchange 2007 managed code services do not start after you install an update rollup for Exchange 2007 It doesn't explicitly mention the Service Host Service as having the problem, but as soon as I used ProxyCfg.exe to configure the details of our web proxy, the Service started fine on all our updated Exchange servers.It seems that the service is trying to download a revoked certificate list from http://crl.microsoft.com, and times out if it doesn't have access to this.Hope this is helpful.