AFX Connectors remain in a Deployed state and 'Failed to get flows for server. No associated server id' error in RSA Identity Governance & Lifecycle
Originally Published: 2015-05-01
Article Number
Applies To
RSA Version/Condition: 6.9.1, 7.0.x, 7.1.x
Issue
The $AFX_HOME/esb/logs/esb.AFX_INIT.log has the following error:
2019-04-24 00:00:03.882 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:118 - Unable to get status for all Connectors from MMC com.aveksa.afx.server.manager.MMCException: Failed to get flows for server. No associated server Id. Check Request Manager Initialization
Cause
The mmc-console collects connector information in order for the connectors to run. If mmc-console fails to start, then the connector information is never collected and the connectors cannot move from Deployed to Running.
Resolution
- Check that Java is installed on your AFX server and that it is the same version of Java that is required by your version of RSA Identity Governance & Lifecycle. If Java is not installed, or the incorrect version of Java is installed, then install the appropriate Java version on your AFX server. For example, RSA Identity Governance & Lifecycle 7.1.1 requires Java 1.8.
- Check that the AFX environment has been set up properly as per RSA Knowledge Base article 000034089 -- How to install Access Fulfillment Express (AFX) for use with RSA Identity Governance and Lifecycle. Look for the section entitled Configure the AFX environment.
