How to extend Windows SCM default timeout of 30 seconds

[Andre_Sostizzo]

Description:

If you get errors like:

• Error 1053: The service did not respond to the start or control request in a timely fashion.
• Error 1068: The dependency service or group failed to start. (Windows could not start Qlik Sense engine service on local computer)
• The QlikView Engine isn't responding to close command, it will be killed (Please ignore logged errors about the kill).

and/or in QlikView logs...
 

Error Could not request the QlikView Engine process to quit.. Exception=System.Runtime.InteropServices.COMException (0x80010108): The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED))

at QlikView.ApplicationClass.Quit(Int32 _ExitCode)

at QVBWrapper.Document.NiceCloseThread(ILogBucket i_LogBucket)

most likely that the default 30 seconds Windows timeout is not enough.

Environment:

• Windows Server running Qlik Products

Resolution:

To work around this problem, increase the default timeout value for the Service Control Manager (SCM) in the registry. Source: http://support.microsoft.com/kb/839803/
 

Warning: Modifications to the Windows Registry cannot be supported by Qlik. Always ensure you have a viable backup before beginning this procedure. Modify the registry at your own risk.

Increase the timeout value:

Manual steps through Windows Registry Editor: 

1. Start Registry Editor (Regedit.exe).
2. To change the value data for the ServicesPipeTimeout DWORD value to 300000 in the Control key, follow these steps:
   1. Locate and then click the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
   2. Click the Control subkey
   3. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
   4. Click Decimal.
   5. Type 300000, and then click OK.
3. If the ServicesPipeTimeout value is not available, add the new DWORD value, and then set its value data to 300000 in the Control key. To do so, follow these steps:
   1. Locate and then click the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
   2. Click the Control subkey.
   3. On the Edit menu, point to New, and then click DWORD Value.
   4. Type ServicesPipeTimeout, and then press ENTER.
   5. Right-click the ServicesPipeTimeout DWORD value, and then click Modify.
   6. Click Decimal.
   7. Type a value of 300000, and then click OK. 
      The value is 300000 milliseconds and is equivalent  to 5 minutes.
4. Restart the computer. 

Scripted change through PowerShell:

The below PowerShell script increases the default timeout value for the service control manager in Windows.
The change is applied in the Windows registry and requires administrator privileges to be executed.

$Path_CurrentControlSetControl =  "HKLM:\SYSTEM\CurrentControlSet\control"
$Path_ServicesPipeTimeout = $Path_CurrentControlSetControl + "\ServicesPipeTimeout"
if(-Not (Test-Path $Path_ServicesPipeTimeout)) {
    Set-Location "$Path_CurrentControlSetControl" 
    New-ItemProperty -Path "$Path_CurrentControlSetControl" `
                     -Name "ServicesPipeTimeout" `
                     -Value "300000" `
                     -PropertyType "DWord" `
                     -Force
}

CAUTION is advised for any changes in Windows registry. Make sure you have a recovery plan, in case of incorrect or accidental configuration.

NOTE: if the environment has extended timeout value but still failed to starting services, please double check and make sure the service user who is running Qlik Sense service in the local Administrator group

NOTE 2: Due to the company's policies, some customers have asked if it's possible to have the services startup without modifying the registry. For instance, by changing a value in the Qlik Sense config file. This is not possible because the config file is not fully read until the services has started up, and Qlik Sense cannot modify the way Windows handles services.