Access Fulfillment Express (AFX) connector export fails with 'Could Not Create Connector Package' and 'duplicate entry' errors in RSA Identity Governance & Lifecycle
Originally Published: 2018-11-02
Last Modified: 2022-06-20
Article Number
000040517
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0
Issue
When exporting an Access Fulfillment Express (AFX) connector and an AFX template with the same name to the same export file, the AFX export fails with:
 
     Cannot Export: Could Not Create Connector Package
 
User-added image
 
User-added image

The following error is seen in the aveksaServer.log: 
07/16/2018 12:19:42.951 ERROR (default task-21) 
[com.aveksa.afx.common.packagemgmt.connector.ConnectorPackageComponent] 
Cannot_Archive_XML : AirWatch/CONNECTOR_TYPE/ConnectorType.xml
java.util.zip.ZipException: duplicate entry: AirWatch/CONNECTOR_TYPE/ConnectorType.xml
	at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:232)

Please refer to RSA Knowledge Base Article  000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment.
Cause
This is a known defect reported in engineering ticket ACM-88958.
Resolution
This issue is resolved in RSA Identity Governance & Lifecycle  7.1.1
Workaround

Workaround 1

Do not check both the template and the connector to be exported at the same time in the same export. Instead export them separately with two different exports.


Workaround 2

 Alternatively, avoid naming an AFX connector with the same name as an existing AFX connector template.

Related Articles

Trending Articles

Don't see what you're looking for?