000025082 - RSA SecurID Appliance: RSA Authentication Manager Services fail to start upon system startup.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025082
Applies ToRSA SecurID Appliance 2.0
RSA SecurID Appliance 2.0.1
RSA SecurID Appliance 2.0.2
RSA Securid Appliance enabled for "Automatically start services on system startup".
IssueRSA Authentication Manager services need to be automatically started on system startup in order to ensure remote connectivity to the box.
RSA Authentication Manager Services fail to start on system reboot or startup. With default configuration of user accounts this leaves all remote securid challenged users locked out and the only possible access as the non-challenged rsalocaladim account with a direct connection to the box.
The application event log reports an error, with source ASLCD; "Error: Process timeout retrieving install type".
This will be followed by two errors, with source ACESERVER6.1; "General error in broker server. Lockfiles exist in the ACEDATA directory that could not be removed, error=32".

Access the RSA SecurID Appliance via local connection or rdp if available. Go to administration, services, and select the LCD service. Set the service to disabled and reboot the box. You should notice the RSA Authentication Manager Services properly start upon reboot. Go back to administration, services, select the LCD service and set it to automatic. Reboot the box and you should see the RSA Authentication Manager Services still start upon reboot. The services should continue to properly start on reboot or system startup from thereon.

Note: The service name is ASLCD, however its display name is "LCD Service" from the Services MMC.

Legacy Article IDa39044