5 Troubleshooting the Connector

These are the solutions to problems that you might encounter while using the Flat File connector.

Table 5-1 Troubleshooting for the Flat File Connector

Problem Reason Solution

The following error message is encountered:

org.identityconnectors.framework.common.exceptions.ConnectorException:

Error in processing all files in Flat file directory.

{filenamexxxx=Mandatory Field Column "xxxxx" not present}. Refer log for more details.

The reason for the error could be any one of the following:

  1. The field that is marked as mandatory in the schema file is not present in the header of the flat file.

  2. The header line in the flat file is commented.

  3. The 'fieldDelimiter' specified in the flat file connector configuration is not present in the flat file.

The following are the solutions to their corresponding causes mentioned in the Reason column of this row:

  1. Ensure that the mandatory fields are present in the header.

  2. Uncomment the header field if commented.

  3. Update the correct field delimiter in the Flat File connector's main configuration lookup definition.

The following error message is encountered:

org.identityconnectors.framework.common.exceptions.ConfigurationException:

Directory does not contain normal files to read xxxx

The flat file directory is empty.

Ensure that the directory is valid and contains files to be parsed.

The following error message is encountered:

org.identityconnectors.framework.common.exceptions.ConnectorException:

Specified class not found xxxxxx

The reason for the error could be any one of the following:

  1. The value given for the parserClassName, preProcessClassName, or postProcessClassName entries of the main configuration lookup definition is invalid.

  2. The custom class is not available to the class loader.

The following are the solutions to their corresponding causes mentioned in the Reason column of this row:

  1. Ensure that the fully qualified class name is mentioned for the parserClassName, preProcessClassName, or postProcessClassName entries of the main configuration lookup definition.

  2. Upload the custom parser, preprocess, or postprocess handler JARs to Oracle Identity Manager.