Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

Increasing the Timeout on Startup Services

Last Update: 11/12/2018

When a service starts, it communicates to the Service Control Manager how long it has to start in what's called the service's timeout period. If the Service Control Manager does not receive a "service started" notice from the service within this timeout period, it will terminate the process that hosts the service.

The timeout period is usually less than 30 seconds. If it is not adjusted, the Service Control Manager will end the process. For information on adjusting the timeout, refer to the instructions below.

  1. In Registry Editor, right-click on the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
  2. Next, right-click on Control (in the right-hand pane of the Registry Editor) and select New | DWORD. The name of the new registry entry will be selected for editing. Type "ServicesPipeTimeout" and then press ENTER.
  3. Next, right-click on the new ServicesPipeTimeout registry entry and then click Modify.
  4. In Edit DWORD Value, locate Value and then enter 180000.
  5. Once finished, click OK. Then, restart the computer in order for the Service Control Manager to apply the change.

Note: TimeoutPeriod is a placeholder for the value of the timeout period in milliseconds that will be set for the service. For example, to set the timeout period to 24 hours (86400000 milliseconds), type 86400000.

Related Products