Why does Voice Elements SIP Platform (formerly HMP Elements) Time Out When Starting Up

From VESupport

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
-
We sign our HMP Elements executable. This means that when you start it up, Microsoft tries to verify the signature with our certificate authority. However, sometimes this can take longer than the time allotted to a service to start up, so Windows may cancel the service startup.  To fix this issue, we recommend changing the default timeout time to 120 seconds from 30 seconds, you can do this by doing the following:
+
<seo title="Voice Elements, Timing Out Upon Start Up" metakeywords="Voice Elements software, IVR" metadescription="When you start up a VE app, Microsoft tries to verify the signature with our certificate authority. However, sometimes this can take longer than the time allotted to a service to start up, so Windows may cancel the service startup." />
 +
 
 +
We sign our Voice Elements Platform (HMP Elements) executable. This means that when you start it up, Microsoft tries to verify the signature with our certificate authority. However, sometimes this can take longer than the time allotted to a service to start up, so Windows may cancel the service startup.  To fix this issue, we recommend changing the default timeout time to 120 seconds from 30 seconds, you can do this by doing the following:
Open up the Registry Editor by opening "RegEdit" from the command line, and browse to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Open up the Registry Editor by opening "RegEdit" from the command line, and browse to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

Revision as of 04:14, 23 April 2013

We sign our Voice Elements Platform (HMP Elements) executable. This means that when you start it up, Microsoft tries to verify the signature with our certificate authority. However, sometimes this can take longer than the time allotted to a service to start up, so Windows may cancel the service startup. To fix this issue, we recommend changing the default timeout time to 120 seconds from 30 seconds, you can do this by doing the following:

Open up the Registry Editor by opening "RegEdit" from the command line, and browse to the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

From the details pane look for an entry named "ServicesPipeTimeout". If it does not exist, then you should create it. You can do this by right clicking and selecting "New DWORD" in the details pain. Give it the name "ServicesPipeTimeout"

Once it's created, right-click the ServicesPipeTimeout entry and then click "Modify".

Click Decimal, enter the new timeout value in milliseconds. We prefer 120000 (120 seconds), and then click OK.

Restart the server.

Personal tools