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
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to Download OTP Token Seed Files from myRSA Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
