Troubleshooting

To resolve this issue, add the MaxMessageSaveSec parameter to the timeout value in the Create_Config.xslt file as follows:

<xsl:template match="*" mode="WriteAttachment">
  <!-- processes discrete (non-composite) message content of type "text" or "binary" or "xmltext" -->
  <!-- is called with parameter $exp containing the "Export" structure -->
      <xsl:variable name="fprop">
               <xsl:apply-templates select="." mode="GetFileNameExt"/>
      </xsl:variable>
  <tsl:invoke tsl:target="file" tsl:discard-output="1" tsl:timeout="{$MaxMessageSaveSec}">
    <CreateFile>
      <Opt>

By default, the value of the MaxMessageSaveSec parameter is 18000s/5 hours. Adding this parameter to timeout increases the timeout value and allows processing of large files.

To resolve this issue, make sure that the username entered in the Mailbox settings and the Configure OAuth screens is the same.

When configuring the mailbox using the Authorization code grant, clicking the Authorize button on the Configure OAuth screen may not display the login pop-up.

In this case, the user may have enabled the Stay signed-in option in the previous login session.

To resolve this issue, delete the browser cookies and try again.

MSGraph.CertificateValidation error in cert. chain=PartialChain

Verify that the certificate for your MS Graph mailbox is valid.

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

The remote name could not be resolved: 'graph.microsoft.com'

If this error is logged in the Windows Event Viewer, verify the following for your MS Graph settings:

• The proxy server settings in the "MS Graph/EWSproxy settings" tab of Message Connector Configuration are correct.

• The proxy server settings for the MS Graph connection in KC Plug-In are correct.

Connection to passive input FolderImport1 cannot be established. Error: Net connection to local folder C:\Watchfolder with user kichyd\ktaauto01 failed, LogonUser() error=1326 with folder import source

If this error is logged in the Windows Event Viewer, this means that the password of your system has changed, but the same is not updated in the folder connection configuration of KC Plug-In.

Where,

FolderImport1: Name of the import connector.

C:\Watchfolder: Folder configured for polling the documents.

The request failed. The remote server returned an error: (401) Unauthorized

If this error is logged in the Windows Event Viewer, this means that the password of your mailbox (EWS/POP3/IMAP/MS Graph) has changed, but the same is not updated in the mailbox connection configuration of KC Plug-In.

-ERR [AUTH] Username and password not accepted.

IMAP Command >0001 LOGIN *******< returned error: >0001 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)

The access token has expired or is not yet valid.

Conversion of HEIC to PDF resulting in very large size output files.

If the compression value is not defined for an input HEIC file, conversion of such file may result in a PDF of very large size. To resolve this, see Conversion of HEIC to PDF.

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

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 cannot be understood.

Could not create a batch.

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

  Kofax Import Connector acknowledges the changes in the batch only when they are published in Kofax Capture.

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

Could not create the document.

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

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

Could not create the folder.

The configured folder class does not exist in the batch. For example, this error occurs if a folder is renamed or removed while Kofax Import Connectoris running and trying to send a message to the destination that is configured to use this batch.

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

The configured batch class does not exist.

The configured document class does not exist.

The configured folder class does not exist.

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

Could not log in to Kofax Capture.

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

Any other eventual exceptions such as insufficient permissions, thrown by the KC import API.

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.

This error occurs when a condition prevents the KC import API from closing 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 shutdown.

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

Empty folder can't be created

This error occurs when the folder with the folder class does not contain any documents.

Could not import image Could not import images

This error occurs when Kofax Capture rejects importing an image, for example, if the image is not in supported format.

Custom script execution failed

This error occurs when an exception other than ScriptException and ScriptIgnoreMessageException is thrown while executing a custom script.

Xml input contains more than 1 batches

This error occurs when AutoXML is configured, and the incoming XML contains more than one batch tag.

Xml mapping Xslt transformation failed

This error occurs when there are issues performing XSLTtransformation 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)

This error occurs when 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.

This error occurs when any of these destination folders aredeleted,and the Kofax Import Connector tries to access the location.

Xml import failed

This error occurs when XML import fails due to an unexpected issue.

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 a 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

This error (related to a specific field) occurs when the Kofax Import Connectortries to import a specific field and that field does not exist in Kofax Capture.

For example, table does not exist in Kofax Capture or 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)

This error occurs if AutoXML is invalid, or 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

This error occurs if BatchClassName, folderclass, or FormType that is specified in the XML file (for AutoXML or generic XML) is not defined in the batch class in Kofax Capture.

The error may be due to any other eventual exceptions thrown by the Kofax Capture import API.

You must 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 for the files that are imported from Message Connector.

This error occurs if KC Plug-In finds any file is missing.

Could not create duplicate batch

Kofax Import Connector rejects messages when a batch with the same name already exists in Kofax Capture. You must configure the following settings for Kofax Import Connector to reject messages when a duplicate batch is found:

• 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.

This error occurs if the Message rendering option is not enabled for importing XML files as PDF/TIFF.

For example, if you configure XML Import Connector compatible mapping, include original content, and conversion to PDF/TIFF,and enable the message rendering option, this error does not occur.

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 compare 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

This error occurs when the message is not received completely and ends with an error. For example, if the received fax does not contain even a single page.

Reception error level 1 of message {0}

This error occurs when the message is partially received and ends with an error. For example, if the reception of a fax ended with an error, “At least 1 page has been stored, but further pages may be missing.”

The message has no content

This error occurs when the message is empty.

The message has no RootXml attachment

This error occurs when the message has no RootXml attachment, but the destination expects it.

The message has no body and no attachments

This error occurs when 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 contains only a body and no attachments.

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

This error occurs if Kofax Import Connector is configured to reject the 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 is unable to convert the document.

• VRS fails to process a document.