Problem Note 58609: The error "SSL negotiation could not complete because the socket was closed by the partner" occurs in SAS® 360 Discover
 |  |  |  |  |
The following error can occur in SAS 360 Discover during the CXT ETL runs.
ERROR: SSL negotiation could not complete because the socket was closed by the partner
This error is related to TCP/IP timing (with packets that are being split) and Secure Sockets Layer (SSL) data in the handshake packet (a single byte is the first byte in the split SSL packet).
For this error to occur, a number of events (that rarely happen) must take place during the SSL handshake. The pertinent events are listed below.
- The SSL handshake is occurring.
- The SSL handshake packets are split into two TCP/IP buffers.
- The first byte in the second TCP/IP buffer is 0x17. SAS 360 Discover misinterprets this data to be an SSL data packet instead of the continuation of a handshake packet.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Customer Intelligence 360 | N/A | 1.0 | 1.0 | ||
A fix for this issue for Base SAS 9.4_M3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/V01.html#58609A fix for this issue for SAS/Secure SSL 9.4_M3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/V53.html#58609| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-08-15 09:59:20 |
| Date Created: | 2016-07-13 14:25:51 |