When starting the aserver from the aserver.bat file the following error is displayed:
"the system cannot find the path specified"
When stating the aserver from services the following error is displayed:
Could not start the RSAAserver service on the Local Computer
Error 1053: The service did not respond to the start control request in a timely fashion.
The default ClearTrust installation directory on Windows is "C:\Program Files\RSA\ClearTrust 5.5.3". The directory names in these directories exceed the 8.3 DOS file name size. In the aserver.bat file and the registry entry that is used to start the ClearTrust servers the JAVA environment must use short file names as in this example:
set CT_ROOT=C:\PROGRA~1\RSA\CLEART~1.3
Ensure that the path to CT_ROOT uses the correct 8.3 short file names for the directory. If the directory has been copied or renamed the directory names in the batch file may not be correct. At the command line run DIR /X to list the short file name for each directory in the path. Modify the aserver.bat file accordingly.
C:\Program Files\RSA>dir /x
Volume in drive C has no label.
Volume Serial Number is 849E-E1AA
Directory of C:\Program Files\RSA
06/28/2007 10:05 AM <DIR> .
06/28/2007 10:05 AM <DIR> ..
11/24/2008 01:58 PM <DIR> CLEART~1.3 ClearTrust 5.5.3
0 File(s) 0 bytes
3 Dir(s) 3,098,578,944 bytes free
Ensure that the Windows volume where ClearTrust is installed is able to support 8.3 file names. This feature is enabled by default, but can be disabled for some volumes. See Microsoft Knowledge Base Article KB121007
How to Disable the 8.3 Name Creation on NTFS Partitions
http://support.microsoft.com/kb/121007
Related Articles
Authentication Manager 8.x ./rsautil store -a update_config gives WARNING cannot find the config name 311Number of Views New feature for RSA Identity Governance & Lifecycle 7.1: Workflow System Status 318Number of Views CyberArk and RSA Authentication Manager integration is unable to perform password change for RSA Security Console user ID 341Number of Views Connecting to or querying the database using pgSQL in RSA Authentication Manager 8.x 1.79KNumber of Views Reporting Engine service is not running due to reportstatusmanager.h2.db corrupt 14Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA-2026-07: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide