Known issues

This topic describes issues that you may encounter while using Kofax Import Connector 2.9.0 and provides workarounds, as applicable.

Important Each conversion tool produces the desired output in a different way. As a result, if you decide to switch to another conversion tool, your converted documents may look somewhat different.

Incorrect documentation for OAuth configuration fields

The documentation for the “OAuth settings” window incorrectly mentions that user can also modify the populated values for the Authorization endpoint URL, Token endpoint URL and Scopes fields.

Workaround: When configuring the OAuth settings, ignore the "You can also modify the populated value." statement for the Authorization endpoint URL, Token endpoint URL and Scopes fields.

Offline help not displayed correctly in Internet Explorer 11

1091840: If the Message Connecter is used in Internet Explorer 11 and the documentation is set to offline mode, the help is not displayed correctly.

Workaround: Use another browser such as Chrome or Firefox.

Archived XML changed unexpectedly

840832: When an XML file is imported, it is modified unexpectedly before it is archived.

Issue with using Total EML Converter

382652: The third-party converter, Total EML Converter, does not function when used with multiple instances of Message Connector running under different user accounts.

Workaround: Use the same user account for all instances of Message Connector.

Third-party archiving tools for Outlook

120375: Some third-party archiving tools for Microsoft Outlook can modify messages and remove attachments. The MSG files can be extracted from the PST file, but some information may be excluded from the MSG files.

Application error when stopping KC Plug-In service

111237: When using Kofax VRS, DL91PDFL.dll may generate an access violation exception after the KC Plug-In is stopped. However, it does not affect document import.

Workaround: Ignore the error message in the event log.

Issue with MS Word document

111225, 111622: Converting a Microsoft Word document with a 64-bit version of Microsoft Office 2010/2013 may result in a document conversion timeout error.

Workaround: Do one of the following:

  • Use a 32-bit version of Microsoft Office 2010/2013.

  • Before conversion, create the folder C:\Windows\System32\config\systemprofile\Desktop.

EWS mailbox polling error

110703: When you attempt to poll an EWS mailbox with more than one connection with single instance mode active, you may run into various message locking problems, such as:

(1a4c/1090/0b50) {2 "EwsDotNet"} Cannot delete message. EWS returned exception. 
Microsoft.Exchange.WebServices.Data.ServiceResponseException: The specified object was not found in the store.

Workaround: Correct your connection configuration for EWS by switching to multiple instances mode.

Insufficient licenses on Kofax Capture Network Server remote site

110565: If you install KC Plug-In on a Kofax Capture Network Server remote site where more connections than your available Kofax Import Connector licenses are configured, the KC Plug-In service restarts every 30 seconds. The following information is written to the log file:

KIC Importer (Instance=0) got no message from master service since 30 seconds. Exiting.

Workaround: Do not configure connections that exceed the number of available licenses.

No XML mapping / rendering without XML type

Destinations without an XML type cannot use XML mapping (to populate Kofax Capture fields using message metadata) or message rendering (for example, to generate a simple cover sheet with metadata). When you enable message rendering or XML mapping and click Show Files for Visual Designer or click OK, the following error message is displayed:

Root element ImportSession cannot be found in the sample XML data file
C:\ProgramData\Kofax\KIC-ED\KCPlugIn\Config\input.xml

Problems with RightFax 9.x software on Windows Server 2012

When installing RightFax client software version 9.x on a Windows Server 2012 operating system, you may run into problems if some RightFax libraries are not properly registered.

Workaround: Do one of the following:

  • Manually register two RightFax 9.x libraries, rfcomapi.dll and rfaxapi.dll. For example, you can use the following commands (assuming default installation paths and English operating system):

    C:\Windows\System32>regsvr32 "C:\Program Files (x86)\RightFax\Shared Files\rfaxui.dll"
    C:\Windows\System32>regsvr32 "C:\Program Files (x86)\RightFax\Shared Files\rfcomapi.dll"
  • Use RightFax client software version 10.x.