Error: 'Unable to contact RuntimeAPI' in RSA Federated Identity Manager (FIM)
Originally Published: 2004-12-30
Last Modified: 2023-10-06
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
How to process PKCS#10 Certificate Signing Request (CSR) from WebSphere 39Number of Views Securid PAM agent for AIX 5.3 - unable to use ldap groups 3Number of Views Apache will not start - Error logged : Init: Pass phrase incorrect 39Number of Views How do you merge FSM audit logs? 1Number of Views Interoperability between RSA Authentication Agent 7.x for Microsoft Windows and RSA Authentication Agent for Web for IIS 186Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?