KB 247 (ABAP): SSL Handshake Error to Dynatrace SaaS: SSSLERR_PEER_CERT_UNTRUSTED
|
Category: Problem |
Priority: High |
|---|---|
|
Platform: ABAP |
Version: 1 from 10.11.2026 |
Description
An SAP ABAP system running PowerConnect stops sending data to Dynatrace SaaS. In the PowerConnect control panel (/n/bnwvs/main), the Dynatrace endpoint in the Upload Scheme screen is shown in red. Running the connection test returns this error:
HTTP receive error. SSL handshake with <tenant>.live.dynatrace.com:443 failed: SSSLERR_PEER_CERT_UNTRUSTED (-102)#Peer's X.509 certificate (chain) validation failed (missing trust?)##SapSSLSessionStartNB()==SSSLERR_PEER_CERT_UNTRUSTED# SSL:SSL_read() failed (536872221/0x2000051d)# => "Failed to v...
Typical signs:
-
Other HTTPS endpoints on the same SAP system, such as a Splunk HEC endpoint, keep working.
-
The PowerConnect batch jobs keep running, but nothing new arrives in Dynatrace.
-
The problem has been reported since around and started without any change on the SAP side.
-
Ingestion can stop silently for several days before anyone notices. See the section Recommended: alert when SAP data stops arriving below.
Cause
Dynatrace SaaS changed the certificate chain served on its *.live.dynatrace.com API endpoints. We have not found an announcement or changelog entry from Dynatrace for this change. The chain now served no longer leads to a root certificate that is present in the SAP SSL client PSE, so the SAP ICM rejects the server as untrusted.
Not every Dynatrace tenant is affected, and the reason why some tenants are affected and others are not is not yet known. Public Certificate Transparency logs show that *.live.dynatrace.com certificates currently exist from more than one certificate authority, including one issued by Let's Encrypt in early October 2026, which is consistent with some tenants receiving a new chain while others do not.
This issue is not related to the security vulnerability disclosed on . It is a trust store problem on the SAP side caused by the Dynatrace certificate change. It is not caused by a PowerConnect defect.
Resolution
Add the Let's Encrypt (ISRG) root certificates to the SSL client PSE that the Dynatrace connection uses. This has resolved the error on every system where it has been applied so far. You need authorization for transaction STRUST. No SAP restart, no ICM restart and no PowerConnect update are required.
Step 1: Download the ISRG root certificates
From letsencrypt.org/certificates, download both root certificates in PEM format:
-
ISRG Root X1 (RSA), file
isrgrootx1.pem -
ISRG Root X2 (ECDSA), file
isrg-root-x2.pem
Save both files on the PC you use to run SAP GUI.
Step 2: Import both certificates in STRUST
-
Run transaction
STRUST(orSTRUSTSSO2) and click Display <-> Change. -
Double-click the node SSL client SSL Client (Standard). This is the PSE that the Dynatrace SSL setup guide uses for the Dynatrace root CA.
-
In the Certificate section, click Import certificate and select
isrgrootx1.pem. -
Check that the subject reads
CN=ISRG Root X1, O=Internet Security Research Group, C=US, then click Add to Certificate List. -
Repeat the import and Add to Certificate List for
isrg-root-x2.pem. -
Click Save.
-
Double-click the node SSL client SSL Client (Anonymous) and repeat the import of both certificates, Add to Certificate List and Save. Both SSL client nodes need the ISRG roots, as in KB 151.
|
STRUST PSE node |
Action |
|---|---|
|
System PSE |
No change |
|
SSL server Standard |
No change |
|
SSL client Anonymous |
Import ISRG Root X1 + X2 here |
|
SSL client Standard |
Import ISRG Root X1 + X2 here |
|
File |
No change |
Node names as shown in STRUST. Your tree may list more nodes.
Do not delete the certificates that are already in the list. Other tenants, other endpoints, or a later change back by Dynatrace may still need them.
Step 3: Re-test the Dynatrace endpoint
No ICM restart is needed: the saved certificates are used on the next connection. In /n/bnwvs/main, go to Administrator → Connection Setup → Upload Scheme (older releases: Administrator → Splunk Setup → Upload Scheme). Select the Dynatrace endpoint on the right side of the screen and click Test. The result should read Connection test successful.
If the test still fails
-
Check that both ISRG roots appear in the Certificate List of both SSL client nodes, SSL Client (Standard) and SSL Client (Anonymous), and that you clicked Save on each.
-
If the SAP system reaches Dynatrace through a proxy that inspects TLS, the proxy's own CA certificate must also be in the SSL client PSE.
-
Alternative: import the full certificate chain that
<tenant>.live.dynatrace.comnow presents (root and intermediate certificates) into the same PSE, using the same Import, Add to Certificate List and Save steps. -
If the error persists, collect an ICM trace as described in KB 111 and open a support incident with the trace and the steps you completed.
Verification
-
The connection test in Upload Scheme returns Connection test successful and the Dynatrace endpoint is no longer red.
-
The three PowerConnect batch jobs (Check, Extractor, Uploader) show green in the
/n/bnwvs/maincontrol panel. If any job is stopped, start it as described in KB 169. -
New SAP data arrives in Dynatrace. Run this query in a Dynatrace Notebook a few minutes after the successful test. Each extractor should show a recent
last_record.
fetch logs, from: now() - 30m
| filter matchesValue(service.name, "sap:abap")
| summarize records = count(), last_record = max(timestamp), by: { dt.source_entity_name }
| sort last_record desc
If you send several SAP systems to the same tenant, add a filter on the attribute that identifies your system ID so that you check the affected system only.
If the control panel shows metrics in error from the outage period, follow KB 113 to send them now that the root cause is fixed.
Recommended: alert when SAP data stops arriving
This error does not stop the PowerConnect jobs, so data can be missing for days without an obvious failure. Create an alert in Dynatrace that fires when no PowerConnect data has arrived for a set period, for example with a Davis anomaly detector based on this query, set to alert when records is 0 for 30 minutes:
fetch logs, from: now() - 15m
| filter matchesValue(service.name, "sap:abap")
| summarize records = count()
Additional Information
-
Recommended - Using SSL Encryption between SAP and Dynatrace (PowerConnect ABAP 9.X) – initial SSL setup, STRUSTSSO2 nodes and root CA import
-
KB 151 - Update SSL Certificates – screenshots of the STRUST import, Add to Certificate List and Save steps
-
KB 197 - PowerConnect Data from ABAP System Not Flowing to Splunk, What Should I Do? – general checklist when data stops
-
KB 111 - Change ICM Logging Level for Connection Troubleshooting – collect an ICM trace for support
-
KB 217 - Dynatrace Endpoint URL definition in SP 8.03+ releases – correct endpoint URL format
-
Let's Encrypt - Chains of Trust – download page for ISRG Root X1 and ISRG Root X2
Product version
|
Product |
From |
To |
|---|---|---|
|
PowerConnect ABAP [NW, S4HANA] with a Dynatrace SaaS endpoint |
* |
* |
Connection type
|
Connection |
Affected |
|---|---|
|
Direct to |
Yes, on some tenants |
|
Through a Dynatrace ActiveGate |
Not expected. SAP validates the ActiveGate certificate, not the SaaS chain. |