SAS Viya LTS 2025.09 environments that use SAS/ACCESS® Interface to Hadoop with TLS 1.3 enabled and Java 17 might fail when reading from or writing to HDFS. Note that these failures might be intermittent or consistent.
As a result, the following errors might occur in the SAS log:
error: ERROR: Unable to establish connection to xxxxxxx.com.
error: ERROR: Unable to create stream service from /......./sasdata_e2_102430_825_0000/000001_0. Use the debug option for more
error: information.
These failures manifest as connection errors or stream service creation errors.
The App.tk.eam.ssl logger might also report messages similar to the following:
getParmValueTkessl: Looking for passed in parm SSLCRLCHECK
GetProvParmValue: Enter, cipher=0x7fb913d9df80, parm=SSLCRLCHECK
GetProvParmValue: Exit, status=0x807ff018, value='<null>'
getParmValue: Exit, status=0x807ff018, value='<null>'
The non-zero status code returned by getParmValue should be 0x00000000.
Although this issue was initially observed with SAS/ACCESS Interface to Hadoop, it is not specific to Hadoop. This issue might affect any Java‑based SAS connection that operates under TLS 1.3 with Java 17.
To work around this issue, disable TLS 1.3 and revert to TLS 1.2.
A patch for SAS Viya LTS 2025.09 is available. See Apply a Patch Update for additional information.