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 the processing of large files.

To resolve this issue, ensure the username entered in the Mailbox settings and the Configure OAuth screens are 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.

This issue occurs if the Stay signed-in option is enabled 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 proxy server settings for your MS Graph are correct in:

• In the "MS Graph/EWSproxy settings" tab of Message Connector Configuration.

• MS Graph connection in Capture Plug-In.

Connection to passive input <Name of the import connector> cannot be established. Error: Net connection to local folder <Folder configured for polling the documents> with user <username> failed, LogonUser() error=1326 with folder import source

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

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

If this error is logged in the Windows Event Viewer, it indicates that the password of your mailbox (EWS/POP3/IMAP/MS Graph) has changed, but is not updated in the mailbox connection configuration of Capture 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 log in as an ADFS (Active Directory Federation Services) federated user.

For an 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.

This error occurs only on server SKU operatingsystems such as Windows Server.

To resolve this error, 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.

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

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

• This error may occur due to any other exceptions raised by the Tungsten Capture import API. Check log files for exception details.

Could not create the document.

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

This error may occur due to any other eventual exceptions raised by the Tungsten Capture import API. Check log files for exception details.

Could not create the folder.

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

This error may occur due to any other eventual exceptions raised by the Tungsten 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 Tungsten Import Connector checks for the existence of all the configured batch, document, and folder classes when the service starts and cannot find them.

Could not log in to Tungsten Capture.

• This error occurs due to an incorrect user ID or password. Refer to the General settings window of Tungsten Import Connector.
• This error may occur due to any other eventual exceptions such as insufficient permissions, raised by the Tungsten Capture import API.

Out of Tungsten Capture scan licenses.

This error occurs when the number of pages to import exceeds the license limit supported by Tungsten Capture.

Tungsten Capture could not close the batch.

This error occurs when a condition prevents the Tungsten Capture 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 Tungsten Capture.

Delayed due to shutdown.

This status message is displayed when the Tungsten Import Connector service is stopped with messages still in the queue.

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 Tungsten 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 due to issues 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)

This error occurs when XmlMapping.xslt is missing in the 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\Tungsten\Import Connector\Capture PlugIn\config\Schemas.

This error occurs when any of these destination folders are deleted,and the Tungsten 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

This error occurs when filling the data in the respective field in a batch. For example, the mapping field is of a different data type and incompatible with the field 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 Tungsten Import Connectortries to import a field that does not exist in Tungsten Capture.

For example, table does not exist in Tungsten Capture, or auto import XML tries to import a table but the definition does not exist in the batch class in Tungsten 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 specified in the XML file (for AutoXML or generic XML) is not defined in the batch class in Tungsten Capture.

The error may also occur due to any other eventual exceptions thrown by the Tungsten Capture import API.

You must check the log files for the exception details.

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

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

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

Could not create duplicate batch

This error occurs when Tungsten Import Connector rejects messages if a batch with the same name already exists in Tungsten Capture.

To resolve this error, configure the following settings for Tungsten Import Connector to reject messages when a duplicate batch is found:

• Set DuplicateBatchRenameOff in the Tungsten 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

This error occurs if the file name is very long (more than 260 characters). Tungsten Import Connector tries to rename the file to "Renamed.ext". However, if the file name length still exceeds 260 characters, the operating system cannot create the file.

The message could not be imported into Tungsten 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.

To resolve this error, for example, if you configure XML Import Connector compatible mapping, include original content, and conversion to PDF/TIFF, and enable message rendering.

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

When Tungsten Import Connector is configured for AutoImport XML, Capture Plug-In tries to compare the file list in XML to the files imported from Message Connector.

This error occurs If any files are found missing.

This error may also occur in other cases as a reception error, for example, when an incomplete fax is received.

The message could not be imported into Tungsten 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 at least 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 Tungsten Import Connector receives a message without any content. It could also be a configuration issue, for example, Tungsten Import Connector is configured to process only attachments and ignore the body, but the message contains only a body and no attachments.

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

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