Error: 'Unable to contact RuntimeAPI' in RSA Federated Identity Manager (FIM)
Originally Published: 2004-12-30
Article Number
Applies To
RSA Federated Identity Manager (FIM) 2.5
Issue
Resolution
Also, ensure that any FIM custom plugins that use the RuntimeAPI are also referencing the correct address for the Dispatcher/AServer. Once these changes have been made, the plugins should be recompiled, and "reloaded" into FIM.
Workaround
Related Articles
Best Practices for backup and restoration of FIM configuration and secrets files 14Number of Views Device Settings for Risk-Based Authentication 8Number of Views How do you merge FSM audit logs? 1Number of Views What is procedure to add or reconnect Cisco ESA partner to RSA DLP? 50Number of Views Configure Device History Settings for a Risk-Based Authentication Policy 5Number of Views
Trending Articles
RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor… RSA Release Notes for RSA Authentication Manager 8.8 Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?