Micorosft Exchange Service Host fails to start with Event ID 7000
El servicio Microsoft Exchange Service Host no pudo iniciarse debido al siguiente error:
El servicio no respondió a tiempo a la solicitud de inicio o de control."
After having a fresh install of Exchange 2007 on a Server 2008 Box, I ran into issues with Outlook Anywhere and Terminal Services. Reading more about it I learned that Outlook Anywhere runs on the Microsoft Exchange Service Host which happened to be not running. Doing more research led me to this error (a timeout) and finally I was able to find an answer. After reading this forum: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2364090&SiteID=17&pageid=0 I learned the following (quoted):
The reason why some customers experience service startup problem's similar to that described above is due to a problem with .Net Framework code signature authentication. A lot (most? / all ?) of Exchange 2007 executables are .Net Framework 2.0 managed code. These executables are signed to prevent malicious code modifications. For whatever reason the .Net framework is taking too long to authenticate the code signatures for many of the (Rollup 4 & 5) service executables at boot time causing their startup to fail.
See KB936707 for details on the .Net Framework problem. There is a hotfix available but it can only be obtained through Microsoft Support. It is not publicly available on the website.
After applying the .Net Framework hotfix referred to in KB936707 and also modifying the .config files for each of the Exchange 2007 services as per the article, all the services started at boot time.
This fixed the service startup problem we experienced with Rollup 4 and Rollup 5.
Microsoft refunded the support fee for the incident since it was covered under the free support 'bug' clause."
If you don't wish to call for the hotfix, another solution was posted there that worked fine with me. I would recommend you take into consideration your server might need more or less time before it time outs, so don't panic if 60,000 doesn't do it for you. (Obtained from the same URL as well)
Method 3: Configure the Service Control Manager (SCM) time-out value
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
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:
|3.||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:
This change does not take effect until you restart the computer. After you increase the ServicesPipeTimeout value in the registry, the SCM waits for the services to use the whole ServicesPipeTimeout value before the System log reports that the service did not start.
If the services require several minutes to start, a value of 60 seconds may be insufficient. Therefore, increase the ServicesPipeTimeout value to give the services sufficient time to start."