Security Compliance

ARM service start timeout

Resolution to an issue in which the ARM does not start after logging in to the service.

First published date

4/1/2019 5:17 PM

Last published date

4/1/2019 5:17 PM

Overview

This article provides a resolution to an issue in which the ARM service does not start due to a timeout.
 

Product section

Access Rights Manager

Cause

It is possible that the default start time of 30 seconds for the ARM service is too short. This leads to the ARM service being unable to start successfully. 

Resolution

The start time for services must be increased by extending the registry entry, if it already exists, or adding the registry entry if the entry does not exist.

  1. Open Windows regedit.
  2. Open the registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  3. Right-click in the right frame, and select NEW.
  4. Select DWORD value (32-bit).
  5. Name the new entry ServicesPipeTimeout

    IMPORTANT: It is very important to use the correct spelling for the registry entry!

  6. Right-click the new entry and choose Change.
  7. Enter the following values:
    1. Value: ea60
    2. Base: hexadecimal
  1. Click OK to confirm.
  2. Restart the Windows Server.

Experience has shown that anti-virus scanners may significantly contribute to the delayed start of the service.

Alternative one-time resolution:

  1. Disable the anti-virus scanner.
  2. Start the service.
  3. Enable the anti-virus scanner.