01 What happened
A SAP Community report describes custom SAP NetWeaver Java JDBC DataSources failing to connect to Microsoft SQL Server after an upgrade to NetWeaver 7.5 SP35.
02 Key details
- In the reported environment, SAP JVM 8.1 Patch Collection 74 (build 8.1.074) disabled TLS 1.0 and TLS 1.1 by default; the legacy Microsoft SQL Server JDBC Driver 4.0 (sqljdbc4.jar) was in use.
- The logs reported “No appropriate protocol (protocol is disabled or cipher suites are inappropriate).” Affected DataSources were SAPMEINT, SAPMEINTXA, SAPMEWIP, dmPool, odsDiagPool, odsPool, reportPool, and wipPool.
- The report cites SAP Note 3046818. As a workaround, its author removed TLSv1 and TLSv1.1 from jdk.tls.disabledAlgorithms in the active java.security file and restarted the system.
- The DataSources and ME application functions, including the CTC task, were then validated. Re-enabling obsolete TLS 1.0 and 1.1 is not the preferred long-term solution; where feasible, the report recommends evaluating a supported TLS 1.2 configuration.
03 Why it matters
The incident shows how a change to SAP JVM security defaults can disrupt an existing database connection after an upgrade. The workaround relaxes security, so the report’s recommendation to evaluate TLS 1.2 compatibility without relaxing JVM security also matters.
04 Who it matters to
SAP Basis teams, SAP system administrators and SAP integration teams.
Original source