000030159 - AFX connectors remain in a Deployed state and 'Failed to get flows for server. No associated server id' error in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Oct 28, 2019
Version 25Show Document
  • View in full screen mode

Article Content

Article Number000030159
Applies ToRSA Product Set: Identity Governance & Lifecycle
 RSA Version/Condition: 6.9.1, 7.0.x, 7.1.x
IssueThe AFX Server is in a Running state but the RSA Identity Governance & Lifecycle AFX connectors are stuck in a Deployed state and do not progress to a Running state. For example,
User-added image

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
CauseThis error indicates a problem with mmc-console. We have seen this error when there is a problem with the version of Java installed on the AFX server or there is a problem with the AFX environment setup.

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.
  • 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.
If this does not resolve your issue, please see RSA Knowledge Base article 000038029 -- Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle for additional troubleshooting articles.