Question / Problem:
This article lists all known issues for the KCS 10.2 release.
Answer / Solution:
Bug 1163619 – CPU Usage much higher after update
After the update from KCS 10.1.1 to KCS 10.2 the cpu usage increased from approx. 30% to approx. 90%. This happened on a system with many links connecting to TCOSS.
Use the TCTI32.dll of KCS 10.1.1
LS1 RLA tool
Bug 1159457 – RLA from KCS 10.1.1 or later cannot be used to change the LS1 password
Changing password via RLA is not possible anymore and result in error "Environment variable <Password> invalid."
- Use Line Server Diagnostics (LSD) to change to password
- Downgrade LS1 firmware to KCS 10.1, change the password and upgrade the LS1 firmware.
Bug 1162547 – Not possible to start the TC/MMC for TC/Probe configuration
With KCS 10.2 TC/Probe also supports Windows Authentication. If you update an existing system the registry value TCPROBE\Authentication is set to 0
TC/LINK-SM, -SC7, -SDD, -MFP, -OC
Bug 1170646 – TCMIME: Decoding of name attribute in Content-Type still faulty, resulting in additional space in outgoing messages
With KCS 10.2 it can happen that attachments in outgoing messages contain additional spaces depending on line breaks in the MIME header of received messages
Bug 1174394 – IMCEA-Syntax does not work anymore
With KCS 10.2 it is not possible anymore to send with the KCS-Specific Address like [FAXTC:number].
Use SMTP syntax.
Note: Exchanging TCMIME.dll and TCLSM.dll with an older version does not solve the problem.