Kofax Import Connector 2.11.0 Fix Pack 8
Build date: February 12, 2025
© 2025 Tungsten Automation. All rights reserved.
Use is subject to license terms.
Introduction
You can install Kofax Import Connector 2.11.0.8 to apply the features added and resolve the issues listed below.
Note: To install Kofax Import Connector 2.11.0.8 successfully, an existing full installation of Kofax Import Connector 2.11.0 is required.
If you need to install the full product, see Kofax Import Connector Installation Help for instructions.
Feature added in this fix pack
ID | Description |
---|---|
2174238 | Kofax Import Connector supports PDF version 2.0. |
Issues resolved in this fix pack
ID | Issue | Solution |
---|---|---|
2170764 | Kofax Import Connector failed to process Portfolio PDFs that contained .rdy file. |
Upgraded a third-party component with this fix pack. |
590748 | Message Connector failed to process a corrupt email and did not poll the remaining emails. |
The corrupt email is flagged as bad content, and the remaining emails are polled. When a corrupt email is received:
|
Previous fix packs
This section includes the features added and issues resolved in the previously released fix packs.
Feature added
ID | Description |
---|---|
2158795 | If an error occurs during the PDF to TIFF or image to TIFF conversion, the error information is displayed in the Message Connector Monitor. |
Issues resolved
ID | Issue | Solution |
---|---|---|
2161289 | The empty spaces were removed from the content during email to MSG conversion. |
Upgraded a third-party component with this fix pack. |
2159444 | The HEIC files were not converted in Kofax Import Connector 2.11.0.4. |
Upgraded a third-party component with this fix pack. |
Field Request closed in this fix pack
2148977: Support for Kofax Import Connector to import folders from Azure NetApps.
Approach
- If the Import Connector is installed on-premises and trying to import from the Azure NetApps, the Azure VPN client needs to be installed on the machine where Import Connector is installed and then connect to the Azure NetApps.
- If the Import Connector is installed on an Azure VM, make sure that the VM is in the same region as the Azure NetApps volume. Connect to the NetApp volume from the Azure VM using the Azure Active Directory Domain service.
Limitations due to SMB protocol
- The Windows SMB client does not support multiple credentials to the same server. It means that an Azure Storage Account can’t be used for multiple tenants.
- The Windows SMB client stores the session/credentials in the user session. This is a security issue when SMB is used to access Azure NetApps storage because access to the storage account is possible without user/password checks.
Recommendation
Due to the limitations of the SMB protocol, it is recommended to use Kofax Import Connector Azure File Share via RESTful service for folder import.
Issues resolved
ID | Issue | Solution |
---|---|---|
2153379 | Messages were delayed by 100 seconds if the Message trace size value was set greater than 1 in Trace settings. |
The functionality has been enhanced to support higher trace values. |
2145825 | The status of the MS Graph connection was shown active (Green) in Message Connector even though the HTTP ports were disabled. |
The connection failure status is sent successfully to Message Connector when the ports are disabled. |
2091050 | Upgrade to Import Connector version 2.10.x failed if the default bin and trace folder locations were changed. |
The required folders if unavailable are created after the upgrade. |
Issues resolved
ID | Issue | Solution |
---|---|---|
2139142 | The email content was cropped after the PDF conversion. |
Upgraded a third-party component with this fix pack. Note: Make sure you configure the ResizeLargeImages parameter in the [EML2PDF] section in the KFXConverter.ini file to 1. |
2131462 | The EML file was incorrectly converted to MHT instead of TIFF. |
Upgraded a third-party component with this fix pack. |
2130026 | The Kofax Import Connector integrated with Tungsten TotalAgility 7.11 had security vulnerabilities using 7-Zip version 23.01. |
7-Zip is upgraded to version 24.07. |
Features added
ID | Description |
---|---|
2111573 | The order of documents extracted from the portfolio PDF can be changed to ascending or the order in which the documents were imported into the portfolio PDF. |
2107942 | The conversion of Visio file format .vsdx is supported. |
2098727 | The SMTP import sources support OAuth 2.0 Client credentials for Exchange Online. |
2100514 | The EMLConversionEngine, HTMLConversionEngine, and MHTConversionEngine parameters are added to the KFXConverter.ini file to enhance document conversion. Note:
|
2060318 | Added support for RPMSG files. For more information see, Manage Identities in KC Plug-In Help. |
1990271 | Added support for polling folders from Amazon Web Services (AWS) S3 Bucket using REST protocol. For more information see, Access AWS S3 Bucket via REST in KC Plug-In Help. |
Issues resolved
ID | Issue | Solution |
---|---|---|
2122281 | KFXConverter failed to convert PDF files of version 1.6 when the third-party component reported false post-analysis errors |
Enhanced the conversion to ignore post-analysis errors. |
2122144 | KFXConverter failed to convert PDF files created using Libre Office 7.4 when the third-party component reported false post-analysis error. |
Enhanced the conversion to ignore post-analysis errors. |
2118295 | KFXConverter failed to convert PDF files of version 1.4. The following error message was displayed: "Document Conversion failed with exit code: 1" |
Upgraded a third-party component. |
2111581 | Fax import took longer than expected when RightFax did not retain the DID/DNIS of the delayed faxes. | The DID/DNIS of the delayed faxes are retained and the remaining faxes are imported. |
2109140 | Attachment names with special characters, such as a colon (:), were not displayed in the message body of the imported mail when the mail subject was used as an EML/MSG attachment name. | Special characters are now supported in the attachment names. |
2101418 | KC Plug-In failed when two processes tried to update the log file simultaneously. | The access to the shared objects (log file) is enhanced; two processes can update the same log file simultaneously. |
2090881 | Document conversion from VCF to TIFF/PDF failed. | Upgraded a third-party component. |
2090012 | When the "FitTableWidthToPage" parameter was set to False, some email contents were lost during the EML to PDF conversion. | Added a new conversion engine for better results. By default, the value of the new parameter "EMLConversionEngine" is set to 1 to use the standard conversion engine. Set the value to 2 to use the new conversion engine. Note: While upgrading from previous versions of Kofax Import Connector, copy this parameter from the default.ini file to the KFXConverter.ini file. |
Features added
ID | Description |
---|---|
2095226 | VRS version 5.3.0.2 is supported. |
2088025 | PDF upscaling or downscaling is supported using VRS. The following parameters are added to set the minimum and maximum PDF page dimensions (height and width) for scaling:
These parameters are available under the PDF Scale To section in Import settings > VRS Settings > VRS parameters. Note:
|
2085158 | MS Graph supports Microsoft 365 Government Community Cloud (GCC) High endpoint URLs. |
Issues resolved
ID | Issue | Solution |
---|---|---|
2101817 | Unable to add the MS Graph import connector to Message Connector passive inputs when the "Resource Owner Password Credentials (Deprecated)" grant type was used. | Fixed the issue with MS Graph mailbox to support the "Resource Owner Password Credentials (Deprecated)" grant type. |
2099105 | Document conversion failed with an error message similar to the following when unknown tags were detected: Convert: Unknown field with tag 32934 (0x80a6) encountered. `TIFFReadDirectory' @ warning/tiff.c/TIFFWarnings/964. |
Unknown tags are ignored and listed as warnings in the log file. |
Feature added
ID | Description |
---|---|
2095207 | Acro form PDF files are supported for conversion. |
Issues resolved
ID | Issue | Solution |
---|---|---|
2095032 | Document field mapping was not saved and removed after the service restart. | Now, document field mapping is saved. |
2094104 | Sometimes, email import failed using MS Graph, and an error message similar to the following was displayed: "The message has no content" |
Functionality is updated to verify if there are any attachments in an email for import. |
2085207 | The Message Connector configuration tool failed due to a time-out error. | The default time-out value has been increased. |
2083525 | KC Plug-In Help did not contain information about the maximum document size allowed for web service input. | KC Plug-In Help is updated to add the maximum document size limit for web service input. |
2067117 | After installing Kofax Import Connector 2.10.0 fix 19676, the logos were missing in the PDF post-conversion. | Enhanced the functionality to retain PDF logos post-conversion. |
known issue
ID | Description |
---|---|
2101817 | Unable to add the MS Graph import connector to Message Connector passive inputs when the "Resource Owner Password Credentials (Deprecated)" grant type is used. |
Applies to
This fix pack includes the features added and issues resolved in Kofax Import Connector 2.11.0.
Files included
This fix pack includes the following files.
File name | Version |
---|---|
KCPlugin-{FILE_VERSION}.msp | version {FILE_VERSION} |
KCPlugin-{FILE_VERSION}.bat | NA |
MC-{FILE_VERSION}.msp | version {FILE_VERSION} |
MC-{FILE_VERSION}.bat | NA |
ReadMe-KofaxImportConnector-2.11.0.8.htm | NA |
Install this fix pack
For best results, install the fix pack during off-peak processing hours.
- Verify that the following applications/services are not running.
- KC Plug-In application and service
- Message Connector Service
- Extract the contents of the .zip file on the computer where Kofax Import Connector is installed.
Run MC-{FILE_VERSION}.bat and follow the on-screen instructions.
Note: To update a single instance or multiple instances of Message Connector on a cluster node:
- Open Command Prompt and navigate to the directory containing the update.
- Execute the following commands:
- Instance 1: msiexec /update MC-{FILE_VERSION}.msp KOFAXPRODUCTVERSION=2.11.0.8.{BUILD_NUMBER} /qb /l*vx MC-2.11.0.8.{BUILD_NUMBER}-Inst1.log /n {ED3A11FC-AEED-43E3-ACB9-346251589F42}
- Instance 2: msiexec /update MC-{FILE_VERSION}.msp KOFAXPRODUCTVERSION=2.11.0.8.{BUILD_NUMBER} /qb /l*vx MC-2.11.0.8.{BUILD_NUMBER}-Inst2.log /n {BECAC22C-F193-4D6F-BE5D-99AD080E776F}
- Instance 3: msiexec /update MC-{FILE_VERSION}.msp KOFAXPRODUCTVERSION=2.11.0.8.{BUILD_NUMBER} /qb /l*vx MC-2.11.0.8.{BUILD_NUMBER}-Inst3.log /n {F6C1303A-7A09-4F2E-AF46-F063E03331F9}
On the computers where KC Plug-In is installed:
- Close Kofax Capture Administration.
- Run KCPlugin-{FILE_VERSION}.bat and follow the on-screen instructions.
- Restart any applications or services that were stopped prior to installing the fix pack.
- Verify that the KC Plug-In and the Message Connector services are running.
Remove this fix pack
For best results, remove the fix pack during off-peak processing hours.
- Verify that the following applications/services are not running.
- KC Plug-In application and service
- Message Connector Service
- To uninstall Message Connector:
- In Control Panel, select Programs and Features > View installed updates.
- On the list of updates, in the Name column, select MC fix pack MC-{FILE_VERSION}.
- Right-click and select Uninstall.
- To uninstall KC Plug-In:
You cannot uninstall the fix pack for KC Plug-In. You must uninstall Kofax Import Connector and install it again without the fix pack.
- Restart any applications or services that were stopped prior to removing the fix pack.