Portuguese English Spanish
Portuguese English Spanish

Failure to start Windows services due to a timeout

Failure

The services fail during startup and do not respond within the timeout period set by Windows. This situation may prevent the services from running correctly, affecting communication between the system and the monitored printers.

Cause

The failure is related to a timeout during the startup of Windows services. There may also be permissions restrictions on the files required for execution or improper configurations for the startup type of the DCA and Cloud Connector services.

Solution

  1. Review the Windows logs

    1. Press Windows + R

    2. Enter eventvwr.msc

    3. Press Enter

    4. Access Windows Logs > System

    5. Locate the events logged during the period when the failure occurred

    6. Check for messages related to service startup, timeout, or unexpected shutdowns

💡

Example

Imagem1-20261105-180206.png
Imagem2-20261105-180216.png
  1. Check the ServicesPipeTimeout parameter in the Windows Registry

    1. Press Windows + R

    2. Enter regedit

    3. Press Enter

    4. Navigate to the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    5. In the right panel, locate the ServicesPipeTimeout setting

    6. Before making any changes, back up the Control key:

      1. Right-click the Control key

      2. Select Export

      3. Choose a location and save the backup file

  2. Create or adjust the ServicesPipeTimeout parameter

    1. If the parameter does not exist:

      1. Right-click in an empty area of the right-hand panel

      2. Select New > DWORD Value (32-bit)

      3. Name the parameter ServicesPipeTimeout

      4. Double-click the newly created parameter

      5. Select the Decimal base and enter the value 120000

      6. Click OK

      7. Close the Registry Editor

      8. Restart the computer to apply the change

    2. If the parameter already exists:

      1. Double-click ServicesPipeTimeout

      2. Check the current value using the Decimal base:

        1. If the value is less than 120000 and you need to increase the timeout, change it to 120000

        2. If it is already set to 120000, there is no need to change it

        3. If the value is greater than 120000, evaluate the existing configuration before making any changes

      3. If the value is changed:

        1. Click OK

        2. Close the Registry Editor

        3. Restart the computer to apply the change

Note

The value 120000 corresponds to 120 seconds (2 minutes).

  1. Review the permissions for the installer directory

Verify that the users responsible for running the services have the necessary permissions to access the installer files and components:

    1. Navigate to the folder where the system installation files are stored

    2. Right-click the folder and select Properties

    3. Go to the Security tab and select each listed user or group

    4. Check the permissions granted, especially reading, writing, and executing permissions, as required by the system

    5. Verify that the user account used by the service or the account responsible for running it has the necessary permissions
      To identify the account used, open services.msc, locate the corresponding service, right-click it, select Properties, and go to the Logon tab.

    6. If any restrictions are identified, click Edit on the Security tab and adjust the necessary permissions for the corresponding account or group
      Grant total control only when there is a justified need and authorization, avoiding excessive permissions

    7. After making the adjustments, try starting the service and verify that it remains running

    8. Also check the Windows logs to identify any errors related to accessing files or components

Warning

Avoid granting total control indiscriminately to all users. Permissions should be adjusted according to the account used by the service and the environment’s security policies.

Last updated: