Article ID: 839803
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
The Windows Trace Session Manager service does not start in the timeout value that is specified by Service Control Manager (SCM). By default, the timeout value is 30000 milliseconds (30 seconds).
Additionally, the system event log indicates this timeout failure by a log entry that is similar to the following: This problem becomes apparent when the installation of Microsoft Enterprise Instrumentation Framework (EIF) is not completed. This problem may also become apparent during the computer startup.
To work around this problem, increase the default timeout value for the service control manager in the registry.
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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To increase the timeout value in the registry, follow these steps:
After you increase the ServicesPipeTimeout value in the registry, the service control manager waits for the services to use the whole ServicesPipeTimeout value before the system event log reports that the program did not start.
For services that depend on the Windows Trace Session Manager service and that require several minutes of startup, a value of 60 seconds may not be sufficient time. Therefore, increase the ServicesPipeTimeout value appropriately. This increased value will give all the dependent services sufficient time to start.