Could not login for a ADFS (Active Directory Federation Services) federated user.

Steps

For a ADFS (Active Directory Federation Services) federated user:

1. Enter the username.

   It redirects to the ADFS server logon page.

2. Click the Login button.

The login page remains intact and login does not happen.

Do the following:

1. Go to Server Manager > Local Server.

2. Set the value of IE Enhanced Security Configuration to Off.

The token contains no permissions, or permissions can not be understood.

Could not create batch

Configured batch class does not exist in the Kofax Capture. For example, this error occurs if a batch class is renamed or removed while Kofax Import Connector is running and Kofax Import Connector tries to send message to the destination which is configured to use this particular batch class.

Any other eventual exceptions thrown by the KC import API. Check log files for exception details.

Could not create document

Configured document class does not exist in the batch. For example, this error occurs if a document class is renamed or removed while Kofax Import Connector is running and Kofax Import Connector tries to send message to the destination which is configured to use this particular batch.

Any other eventual exceptions thrown by the KC import API. Check log files for exception details.

Could not create folder

Configured folder class does not exist in the batch. For example, this error occurs if a folder is renamed or removed while Kofax Import Connector is running and Kofax Import Connector tries to send message to the destination which is configured to use this particular batch.

Any other eventual exceptions thrown by the KC import API. Check log files for exception details.

Configured batch class does not exist

Configured document class does not exist

Configured folder class does not exist

Kofax Import Connector checks for the existence of all the batch, document, and folder classes when the service starts. If it does not find the configured batch, document, or folder classes, it displays the error message.

Could not login to Kofax Capture

Incorrect user ID or password. Refer to the General settings window of Kofax Import Connector.

Any other eventual exceptions thrown by the KC import API, for example, insufficient permissions.

Out of Kofax Capture scan licenses

When the number of pages to import exceeds the license limit supported by Kofax Capture, Kofax Import Connector throws this error.

Kofax capture could not close the batch

Any condition that would prevent the KC import API to close the batch, for example when the message is empty (when all pages were blank and VRS removed them) and there is nothing to import into Kofax Capture.

Delayed due to shut down

When Kofax Import Connector service is stopped while there are messages in the queue, Kofax Import Connector shows this status message.

Empty folder can't be created

Folder with the folder class does not contain any documents.

Could not import image Could not import images

When Kofax Capture rejects importing of an image, for example, if the image is not in supported format.

Custom script execution failed

When there is an exception thrown other than ScriptException and ScriptIgnoreMessageException while executing a custom script.

Xml input contains more than 1 batches

When AutoXML is configured and the incoming XML contains more than one batch tag. Note that the current Kofax Import Connector limitation is one batch per imported XML file.

Xml mapping Xslt transformation failed

When there is an error in performing XSLT transformation for XML mapping, for example, XmlMapping.xslt provided for the transformation file is not correct.

Xslt stylesheet missing (deactivate Xml mapping or create the mapping stylesheet)

XmlMapping.xslt is missing in schemas/destination folder.

Stylesheet files for Xml mapping missing

For each configured destination, a folder with the respective files is created with the destination name at the location C:\ProgramData\Kofax\KIC-ED\KCPlugIn\config\Schemas. When any of these destination folders are deleted and Kofax Import Connector tries to access the location, this error is thrown.

Xml import failed

XML import failed due to any unexpected issue. Check log files for exception details.

Could not populate batch fields

Could not populate folder fields

Could not create table row

Could not populate document table field

Could not populate expected total field

An unexpected error occurred when filling the data to the respective field in the batch. For example, the mapping field is of different data type and is not compatible with the field that is configured in the batch

Batch / folder / table row / table / expected total / document field mapping failed. Mismatched configuration

If Kofax Import Connector tries to import a specific field and if the respective field doesn't exist in Kofax Capture, it throws errors related to the missing fields.

For example, table does not exist in Kofax Capture. Auto import XML tries to import a table but the definition does not exist in the batch class in Kofax Capture.

Received <ImportSession> element corrupted (no batch element available)

The AutoXML is invalid. The batch element is missing in the XML document.

Could not create batch with XmlAutoImport or generic Xml mapping

Batch class required for XmlAutoImport or generic Xml mapping does not exist

FormType required for XmlAutoImport or generic Xml mapping does not exist

Folder class required for XmlAutoImport or generic Xml mapping does not exist

BatchClassName or folderclass or FormType which is specified in XML file (for autoXML or generic XML) is not defined in the batch class in KC.

Any other eventual exceptions thrown by the KC import API. Check log files for exception details.

Attachment is missing. The message could not be imported into Kofax Capture due to message reception error code.

When Kofax Import Connector is configured for Auto Import XML, KC Plug-In tries to check the file list in XML to the files that are imported from Message Connector.

If it finds any file is missing, it throws this error.

Could not create duplicate batch

Kofax Import Connector rejects messages when a batch with same name already exists in Kofax Capture. The following settings must be configured so that Kofax Import Connector rejects messages in this case:

• Set DuplicateBatchRenameOff in the Kofax Capture registry (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Kofax Image Products\Ascent Capture\3.0) to 1.

• Set Kofax_RejectOnDuplicateBatchName in Kofax.Kcs.KcImport.exe.config to True.

Cannot create batch. File name is too long

If the file name is too long (more than 260 characters), Kofax Import Connector tries to rename the file to "Renamed.ext". If the file name length still exceeds 260 characters, the operating system cannot create the file.

The message could not be imported into Kofax Capture due to a document conversion error. The error is: Root Xml document could not be converted as Xml rendering is disabled.

Message rendering option should be enabled for importing XML file as PDF/TIFF. For example, if you configure XML Import Connector compatible mapping, include original content, and conversion to PDF/TIFF, message rendering option should be enabled. If not, Kofax Import Connector throws this error.

The message could not be imported into Kofax Capture due to message reception error code.

When Kofax Import Connector is configured for AutoImport XML, KC Plug-In tries to check the file list in XML to the files that are imported from Message Connector. If it finds any file is missing, it throws this error.

This error can be thrown also in other cases of reception error, for example incomplete fax received.

The message could not be imported into Kofax Capture due to message reception error level 2

Message was not received completely and ended with an error. For example, if the received fax does not even contain a single page. Check log files for exception details.

Reception error level 1 of message {0}

Message was partially received and ended with an error. For example, if reception of a fax ended with an error, at least 1 page has been stored, but further pages may be missing. Check log files for exception details.

The message has no content

Empty message

The message has no RootXml attachment

The message has no RootXml attachment, but the destination expects it.

The message has no body and no attachments

Kofax Import Connector receives the message without any content. It could also be a configuration issue, for example, Kofax Import Connector is configured to process only attachments and to ignore the body, but the message contained only a body and no attachments.

The message could not be imported into Kofax Capture due to a document conversion error

This error appears if Kofax Import Connector is configured to Reject message and if the document conversion fails. Document conversion can fail due to the following reasons:

• Respective conversion tool/software is not installed.

• The conversion tool itself is unable to convert the document.

• VRS fails processing a document.