000017861 - Job Engine service fails to start automatically as configured and reports an "Error 1053" message in RSA Archer

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Feb 6, 2020
Version 9Show Document
  • View in full screen mode

Article Content

Article Number000017861
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Job Engine
IssueThe RSA Archer Job engine services fail to start in one of the following ways
  • With the following error:


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

Event viewer on the server has the following entry:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011


  • RSA Archer Job Engine service fails to start automatically during system boot with the following error logged into Event Logs > System > Source: Service Control Manager:


The RSA Archer Job Engine service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Description:
Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.
Resolution

RESOLUTION 1



By default, Windows has a timeout of 30000 milliseconds for a service to start.  We can change the timeout by modifying the ServicesPipeTimeout value in the registry:



  1. Click Start > Run and type regedit in the text box and click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control


  3. In the right pane, locate the ServicesPipeTimeout entry.

    Note: If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:



    1. On the Edit menu, hover over New, and then click DWORD Value (32-bit).
    2.  Type ServicesPipeTimeout, and then press Enter.
  4. Right-click ServicesPipeTimeout, and click Modify.
  5. Click Decimal, type 60000, and then click OK.
         a. The maximum value can be set to be 300000.
         b. Sometimes, depending on the environment, the maximum value has to be used.

    This value represents the time in milliseconds before a service times out.


  6. Restart the computer.
 

RESOLUTION #2



  1. Run the attached PowerShell script as an account with Admin access on the server. The script sets the ServicesPipeTimeout to 300000
  2. Restart the computer.
Legacy Article IDa67132

Attachments

Outcomes