Qlik Community

Ask a Question

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Support Cases coming to Qlik Community Oct. 4! Start chats, open cases, explore resources. Prep for the big move: READ DETAILS

Qlik Sense: "Error 1053: The service did not respond to the start control request in a timely fashion when trying to start the services"

pbr
Employee
Employee

Qlik Sense: "Error 1053: The service did not respond to the start control request in a timely fashion when trying to start the services"

When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the time-out period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this time-out period, the Service Control Manager terminates the process that hosts the service. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process with the following being registered:


...

Error 1053: The service did not respond to the start control request in a timely fashion when trying to start the services.
...

Error 1053 The service did not respond to the start or control request in a timely fashion.png

The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.

For QlikView, see QlikView: "Error 1053: The service did not respond to the start or control request in a timely fashi...

 

Environment:

 

 

Known Root Causes

 

  1. An installed Microsoft Patch

    There is a Windows defect that was found related to .NET Framework 4.5.2 / 4.6 and Microsoft patches KB3098779 and KB3097997, which caused repeated installation failures. 

    Resolution: Uninstall the Microsoft patches and restart the Qlik Sense services. 

    The complete Microsoft KB article can be found here: https://support.microsoft.com/en-us/kb/3118750

  2. Service Account Expired

    The service account needs to be extended. After adding the extension you may need to reset the password and re-login to the Qlik Sense service as the service user with the new password.

    Resolution:

    If the above cannot be performed and a new service account is needed, see the following steps:
    1. Check the policies and see if the service user account needs a password reset.
    2. Go to the Qlik Sense services in the Windows Services snap-in.
    3. Re-login to the Qlik Sense service as the service user with the new username and password.

      Note: See Changing the Qlik Sense Service Account and what to consider
       
    4. The Qlik Sense service will now start to run again with the updated service account.

  3. Service Account lost permissions

    Repository logs may show:

    WARN that Duplicate certificates are not allowed

    Proxy logs may show:

    Error setting up performance counters: Access to the registry key 'Global' is denied

    Resolution: Qlik service account to be added to the Local Administrators group

    Possible Root Causes for the removal of permissions:
    • A Group Policy at the client system has removed the Qlik service account from the Local Administrators group
    • Another entity has removed the Qlik service account from the Local Administrators group

  4. Connection String is empty or has a wrong password

    Resolution:
    1. Open the connection String Editor in C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil
    2. Make sure the passwords are correct

  5. Service Timeout

    Increase the default timeout value for the Service Control Manager in the Registry.

    Resolution: 

    Source: Microsoft Knowledge Base 839803.

    Warning: Serious issues might occur if you modify the registry incorrectly by using Registry Editor or using another method. Changes to Windows registry are not supported by Qlik Support. These issues 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: 

    Note This change does not take effect until the computer is restarted.

    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.


Labels (1)
Version history
Revision #:
2 of 2
Last update:
‎2021-05-07 02:19 AM
Updated by:
 
Contributors