Resolved issues
This topic describes issues that are resolved in Kofax Import Connector 2.9.0.
Import with document conversion failed
1590596: When the messages were imported into Kofax Capture along with document conversion and the conversion took a very long time, the import operation failed with an error.
JPG image normalization issue
1589761: Normalization of JPG images with default settings to 300 dpi color was taking a lot of time.
Include original content issue when importing xml files
1587220: When
Include original content
was selected, importing a file from a folder using the Kofax Capture XML led to an
Object reference
error.
Multi-level nested message issue
1586518: When certain messages with multi-level nested messages were converted and then imported, operation failed and the following error was displayed in the Message Connector Monitor:
"Failed to retrieve message content from server."
XML schema for message archive issue in documentation
1586073: The documentation mentioned that an XML schema for message archive XML may be provided on request.
DELAY status sent to server issue
1581383: The message was not confirmed after completing all retries and the DELAY status was sent to the server after the last retry cycle was completed. As a result, the message was not confirmed properly and no empty/error batch was created after all the retries.
Different batch IDs for Quality Control and archives
1576289: When archiving for import failures and creation of Quality Control batches were enabled, and when the import failed and the batch was deleted, the archives used the batch ID of the deleted batch, which was different than the batch ID in Batch Manager.
Missing inline images
1566161: The inline images were missing from the imported emails when the email header was also selected for import.
Documentation issue: Missing nested emails limit
1565154: The documentation did not mention the level of nested emails supported in Kofax Import Connector.
Document Conversion timeout led to empty batch without error
1564629: If a document conversion failed due to a timeout without displaying an error, Kofax Import Connector created an empty batch, but displayed the message as successfully imported.
CombineBinaries function did not work
1564614: When a custom script was configured to use the CombineBinaries function (IDocumentConverterScript interface) and Message Connector was configured with admin/process/view user, the CombineBinaries function failed with the following exception:
The request failed with HTTP status 401: Unauthorized.
Password issue with IDocumentConverterScript interface
1564611: When Message Connector was configured with the admin/process/view user, the DocumentConversion functions used in custom scripts failed with the following exception resulting in conversion failure:
The request failed with HTTP status 401: Unauthorized.
KfxImportFolderName not returning subfolder structure
1563977: KfxImportFolderName only returned the Subfolder when attempting to get the complete subfolder structure as the MessageProperty.
KfxImportFolderName returned null value
1563943: When the KfxImportFolderName field was configured for a MS Graph mailbox, it returned a null value.
Issue in Message Connector Monitor From field
1562791: After importing a certain MSG file, garbled characters were displayed in the From field of Message Connector Monitor.
Too many original files imported
1556693: If PDF or PNG files were imported along with the original content, two original files were available in the Kofax Capture 200 folder. This issue occurred when "Save to disk" was selected and VRS processing was enabled.
Memory leak issue
1554184: A memory leak issue in KC Plug-In led to an out-of-memory error.
Kofax Capture login failed after upgrade
1544009: Kofax Import Connector was not able to log in to Kofax Capture, if Kofax Capture was configured to use user profiles and "Cache import process instance" was not selected in Kofax Import Connector.
Importing Portfolio PDF with XML issue
1543621: When an XML file with extension .rdy was imported, the import failed with an error.
MS Graph mailbox polling issue
1532389: It was not possible to poll more than 10 folders for an MS Graph mailbox import.
Issue running multiple instances of Kofax Import Connector
1530051: When running multiple instances of Kofax Import Connector, many batches were moved to QC with the following error:
The *.eml file format is not supported for eDocuments. PDF documents are the only file format supported for eDocuments.
Message Connector checked for deprecated parameter
1529481: The Message Connector was checking the deprecated "Content-type Name=" instead of "Content-Disposition filename=" which caused the Message Connector to read a .pdf attachment as a .tmp attachment.
Conversion issue with specific XLSX file
1529453: Conversion of a specific XLSX file resulted in a document conversion error.
Details excluded from MS Graph errors
1523485: Kofax Import Connector was not returning detailed error messages for a test connection to a MS Graph mailbox.
Missing documentation for LibTiff limitation
1523029: The documentation did not mention the limitation that if the PDF to TIF conversion results in a TIF file that is larger than 4 GB, the Message Connector will return an error.
Error message description
1523026: The error message was not clear for a PDF to TIF conversion resulting in a TIF file larger than 4 GB.
Switch to Exchange2010_SP2 EWS schema
1518883: Kofax Import Connector was not able to use Exchange2010_SP2 EWS schema to connect via EWS to the Exchange server.
Missing documentation about shared mailbox on Office 365
1518819: The documentation did not contain information about connecting to a shared mailbox on Office 365 via IMAP.
Missing information in Technical Specifications document
1518148: The Technical Specification document did not mention that Kofax VRS 5.1.1.12 or higher is required.
Maximum log file size exceeded
1515833: The KC Plug-In log file was excessively large due to an issue in enforcing the maximum file size.
CreationDate used Import date instead of MIME creation date
1514627: The Message Connector set the CreationDate as the import date instead of the MIME creation date when a file was imported from a folder.
Upgrade resulted in import of corrupt and empty faxes
1511210: When Kofax Import Connector was upgraded from version 2.4.0.1 to 2.7.0.2, empty and corrupt faxes were imported, resulting in a document conversion error.
Message Connector stopped working
1511013, 1510264: The Message Connector stopped working when some messages were imported and certain skip filter list settings were used.
Conversion failed for MHT files with tables
1511004: Kofax Import Converter was not able to convert MHT files that included tables.
Documentation issue: EWS does not support moving mail to a subfolder
1510702, 1510695: The Kofax Import Connection documentation did not clearly mention that EWS does not support the moving of mail to a processed folder that is a subfolder.
Import failed for concatenated PDF
1510258, 1510118: When "Import Concatenated PDF only" was set and
Skip converting files
and
Skip importing files
were configured, the message import resulted in a document conversion error.
Documentation did not describe the folder fields as expected
1501318: Kofax Import Connector documentation did not clearly describe which message fields should be configured for folder input.
Outdated software requirements in documentation
1499330: The Kofax Import Connector Installation Guide did not contain the latest information regarding software requirements.
Documentation issue: Permissions for MS Graph
1498463: The permissions for accessing MS Graph mailboxes to be configured in Microsoft Azure Active Directory were not correctly documented.
Incorrect API names in documentation
1497712: Some API names were not accurate in the documentation.
Incorrect example in tooltip
1493682: The example mentioned in the tooltip for Processed folder field was not valid for EWS.
Issue with winmail.dat attachment
1493050: When specific emails were imported, the winmail.dat attachment was not resolved and the attachment was lost, resulting in data loss.
Issue after fix applied
1487607: When Fix 10933 was applied to Kofax Import Connector 2.7.0, the Exception.tif file was removed.
Batch creation failed
1475707, 1475690: When the file type for the converted and imported files was the same, Kofax Import Connector was not able to create batches.
Image conversion issue using ImageMagick
1475435: ImageMagick was not able to convert some images.
Message Connector errors
1471881: Document conversion and related errors occurred if a newly installed Message Connector was not restarted before proceeding with processing.
EWS component stopped working
1459941: When an import source was configured to poll an Outlook 365 mailbox using EWS, clicking the
Test Mailbox
button returned the following error:
Target 'ews' is not running. (Current state=4)
.