Known issues, Nlb port control feature not working, Restart etl agent in case of memory errors – Kofax Capture User Manual
Page 9: Stopping etl agent may take several minutes, Chapter 3

Kofax Reporting Release Notes
9
Chapter 3
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 Network Load Balancing still works correctly when the entire node
goes down. (SPR00093026)
Exception in Application When Another 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 and should be fixed in SQL CE service pack, planned for release in the second
half of 2012 together with Visual Studio 2011. Refer to MS Support Request 112021740670188.
(SPR00092765)
Restart ETL Agent in Case of Memory Errors
If the ETL Agent runs out of memory, it may result in an error “Error data transformation
task TransformKcBatchAction System.Data.DuplicateNameException: A column named
'export_date_key' already belongs to this DataTable.” This may rarely happen in high-load
situations. (SPR00093448, SPR00093253, SPR00092747)
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 on error and processing of data will start anew after
service restart.
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 popup (service cannot be stopped in a timely fashion).
(SPR00091858)