Kofax Communication Server 9.2.0 - Manual (Page 24)

Resolved Issues
24 Kofax Communication Server Release Notes
Capture Connector: Color PDF Loses Color
When importing via KCS Capture Connector to Kofax Capture, PDF attachments with long
names including foreign characters sometimes had their extension truncated. That resulted in
problems with document conversion, such as a color PDF converted to black and white. This
issue has been resolved. (SPR00111643)
Capture Connector: Periodic Restarts If One of Multiple Connections
Down
If KCS Capture Connector was restarted and at least one of several configured connections
was not available, Capture Connector kept restarting and then it failed. This issue is now
resolved. (SPR00122046)
Capture Connector: Invalid Characters in File Name
If KCS Capture Connector encountered an invalid character in a file name, it would restart
periodically. This issue has been resolved, and invalid characters are filtered. (SPR00121185)
Capture Connector: Additional Automatic Reactivations
Under a heavy load, KCS Capture Connector occasionally fails to import messages. Messages
are imported successfully after a manual reactivation. (SPR00118510)
The issue has been resolved. KCS Capture Connector now automatically reactivates some
messages that it previously failed to deliver.
Capture Connector: COMException Bad Variable Type
Under a heavy load, occasionally batches from KCS Capture Connector are rejected. Traces
show
COMException (0x80020008): Bad variable type
. The import functions correctly
when resubmitted. This issue has been resolved. (SPR00112858)
Capture Connector: COM API Error When Retrieving Folder Fields
Information
Kofax Capture sometimes returns a COM API error when KCS Capture Connector tries to
retrieve folder fields information through the API. This issue has been resolved by improving
error handling. (SPR00111088)
Capture Connector: DEBUG and Large Files Information
When the trace level of KCS Capture Connector is set to “DEBUG,” sending large files can
result in an out of memory exception. This issue has been resolved. (SPR00092253)