RSA Authentication Agent 8.6 API does not prompt for passcode with Epic Hyperspace 2016 on Windows Server
Originally Published: 2017-05-23
Article Number
Applies To
RSA Product/Service Type: Authentication Agent API
RSA Version/Condition: 8.5, 8.6
Issue
Cause
An older version of this problem might have been caused by not copying the aceclnt.dll and the sdmsgs.dll to the Windows Server with the Agent API 8.5 or 8.6, such as Epic Hyperspace.
Resolution
- Find the spelling mistake in the rsa_api.properties file. The rsa_api.properties file contains entries such as:
RSA_AGENT_NAME = <hostname> SDCONF_LOC = C:\ProgramData\Epic\RSA\sdconf.rec RSA_LOG_FILE_LOC = C:\scripts\Log
The sharp (#) in front marks the line not parsed or is a comment.
- If there is a spelling mistake or a path is wrong or non-existent, the RSA passcode prompt does not display, so you have to find the mistake. One easy trick is to comment out lines with the # until the RSA prompt finally displays. For example, if the following entry for SysWOW64 is in the file, but you are on a 32-bit system, \Windows\SysWOW64 does not exist, and will prevent the RSA prompt from displaying, so comment this line out as a test. Change from:
RSA_BSAFE_LIBRARY_PATH = C:\Windows\SysWOW64
to
#RSA_BSAFE_LIBRARY_PATH = C:\Windows\SysWOW64
- When done, save the changes and test.
- Repeat steps above until the passcode prompt displays.
Notes
- Copy the following files to C:\Program Files (x86)\Epic\v8.3\Shared Files:
- aceclnt.dll
- aceclnt_tcp.dll
- ccme_asym.dll
- ccme_base.dll
- cryptocme.dll
- cryptocme.sig
- sdmsg.dll
- xeres-c_3_1_vc80.dll
- Add RSA_BSAFE_LIBRARY_PATH = C:\Program Files (x86)\Epic\v8.3\Shared Files to the rsa_api.properties file.
One customer was using Citrix VDI desktops to deploy their Epic Hyperspace servers, but these were 32-bit VDIs, and did not have a C:\Program Files (x86)\Epic\v8.3\Shared Files, so this line was the cause of the missing RSA prompt, and needed to be customized in this case to C:\Program Files\Epic\v8.3\Shared Files
Also, because these VDIs were deployed in large numbers from a standard or gold image, the gold image commented out the #RSA_AGENT=<hostname> even though the implementation guide said to change it to the FQDN. However autoregistration worked with TCP to read the system FQDN and use that for logging and to register.
Related Articles
Accessing the Portal via IWA always prompt for sign in access authorization over the IWA server URL. 9Number of Views Cisco AnyConnect client displays a second login prompt where RSA Authentication Agent 7.2.1 for Windows is installed 63Number of Views RSA Authentication Agent 7.3.2 for Microsoft Windows SecurID passcode prompt does not appear if the lockout is automatic 69Number of Views How to create an Aveksa Statistics Report (ASR) from the linux command line prompt using SQL in RSA Identity Governance & … 400Number of Views When switching to root the RSA Authentication Agent 8.1.3 for PAM is not prompting for a passcode 169Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU
Don't see what you're looking for?