User guide

Kofax Reporting Release Notes

Chapter 3

Known Issues

This section contains information about potential issues that you could encounter while using

Kofax Reporting.

Restart ETL Agent in Case of Exception

In high load situations the ETL agent occasionally ends with an error: (284104)

System.NullReferenceException: Object reference not set to an instance of an

object.

Other errors can occur in similar situations.

Workaround: Restart the ETL Agent. Data integrity is not affected in any way: operation

will be rolled back upon the error, and data processing will start anew after the service is

restarted.

Silent Installation of ETL Agent

Installing the second instance of the ETL Agent in silent mode fails unless you specify the

service name in the command line. (292784)

Workaround: Specify the command line parameter SERVICE_NAME when installing the

second instance of the product, for example:

setup.exe TRANSFORMS=:Instance2 MSINEWINSTANCE=1 SERVICE_MODE="ETLAgent2"

INSTALLDIR="C:\Program Files (x86)\Kofax\Reporting\ETLAgent2" /quiet

NLB Port Control Feature Not Working

The Windows NLB Port Control feature of Kofax Reporting is not working properly.

For example, when the WSA Receiver is stopped manually on the second NLB node,

the port control feature fails to notice that and does not disable the configured NLB port

automatically. Windows NLB still works correctly when the entire node goes down.

(SPR00093026)

Exception When Another Application Ends Unexpectedly

When multiple Kofax application processes run on the same computer and one of the

processes ends unexpectedly while WSA Sender is not available, the other processes might

end as well with an exception (read or write protected memory). This is an error in Microsoft

SQL CE 4.0. Refer to MS Support Request 112021740670188. (SPR00092765)