Kofax Capture - Manual (Page 7)

Kofax Reporting Release Notes 7
Chapter 2
Known Issues
This section contains information about potential issues that you could encounter while using
Kofax Reporting.
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)
Restart ETL Agent in Case of Memory Errors
If the ETL Agent runs out of memory in high load situations, it may result in an error:
(SPR00093253, SPR00092747)
Error data transformation task TransformKcBatchAction
System.Data.DuplicateNameException: A column named 'export_date_key'
already
belongs to this DataTable.
Also, if the SQL Server in a MS SQL Cluster Server environment is manually set offline, the
DataTable already belongs to another DataSet
error can occur. Other errors can occur
in similar situations.
Workaround: Restarting the ETL Agent solves both problems. 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.
Stopping ETL Agent May Take Several Minutes
If you attempt to stop the ETL Agent service when the service is busy (e.g., performing
complex database operations), it may take several minutes until the service is stopped safely.
You can ignore the warning message that says the service cannot be stopped in a timely
fashion. (SPR00091858)