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
Error: 'Relying Party servlet: java.lang.NullPointerException' in RSA Federated Identity Manager (FIM) Number of Views Error: 'Unable to locate a configured Relying Party for target URL' in RSA Federated Identity Manager (FIM) Number of Views FIM 'Unable to process the AuthnRequest message' in RSA Federated Identity Manager Number of Views How to back up the SAML configuration in RSA Federated Identity Manager (FIM) 2.0 Number of Views Name resolution errors in RSA Federated Identity Manager (FIM) 2.5 Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme…
Don't see what you're looking for?
