SPE for Secure ICAP scanning and records a large number of "Failed to complete TLS/SSL handshake initiated by TLS/SSL client" messages in the logs in /opt/SYMCScan/log. These messages seem to be coming from SPE and not a server submitting files to be scanned. For example, in the below message, 10.80.246.171 is the IP address of the SPE server.
1603296285|11|2|1|30|Failed to complete TLS/SSL handshake initiated by TLS/SSL client. Error code: |43|10.80.246.171|44|11344|45|596082|120|1603296285574|121|hostname.example.com
There may be multiple causes for the TLS handshake to fail ranging form connection issues to certificate issues to TCP healthchecks. See the Resolution section for both general troubleshooting information and for specific causes.
General Troubleshooting Steps
Note: Gathering a packet capture/trace of the network communication during these steps may provide more information than what is logged, including specific TCP or TLS errors.