Skip to main content
Kofax

Custom Export Connector causes an error Object reference not set to an instance of an object

Article # 3035132 - Page views: 43

Article # 3035132 - Page views: 43

Issue

Custom Export Connector causes an error Object reference not set to an instance of an object, how can this be resolved?

Solution

First of all, make sure that the log4net is not  targeted to .net version higher than .NET 3.5 as Kofax Express 3.2 is based .net 3.5 and it obviously cannot execute .net 4.x assembly.

If Kofax Capture is also present within the KXP environment,  you may expect a COM loading conflict between Express's Export Library and Capture's Export Library.

This is because Kofax Capture and Kofax Express software are installed on the same machine, and Capture's Export Library wins in COM loading because it has been registered with the system, while the Express's Export Library is not. At the Export time, Capture's Export Library is loaded, and therefore any Express's management data object goes to Capture Export Library, and this of course does not meet Capture's Export Library expectation, so "Object reference not set..." error occurs.

Express supports Capture's export connector to be able to reused from Express environment, this integration works well with foreground export, or in an environment that does not have Capture software installed.

Workaround: To use the foreground export (Background export un-checked) for any Capture's derived export connector, and when Capture and Express software are installed on the same computer.

Note that this should be resolved in Kofax Express 3.3

 

 

 

 

Level of Complexity 

Moderate

 

Applies to  

Product Version Build Environment Hardware
KXP

3.1

3.2

     

References

Add any references to other internal or external articles

  • Was this article helpful?