SAP Knowledge Base Article - Preview

3131978 - General troubleshooting for error 400 Bad Request


Possible symptoms:

Connection between SAP DI and ABAP system via SCC stops working, in the SCC ljs_trace.log file, the following error is found (see Note 2452568 for SCC logs and traces):

xxx-xx-xx xx:xx:xx,xxx          #Invalid status of handshake response: DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 400 Bad Request
Date: Wed, xx xxx xxxx xx:xx:xx GMT
Content-Type: text/html
Content-Length: 230
Connection: close|
xxxx-xx-xx xx:xx:xx,xxx          #Unable to open tunnel connection: Invalid status of handshake response: 400 Bad Request|
xxxx-xx-xx xx:xx:xx,xxx          #Tunnel handshake failed! Closing the tunnel channel immediately Invalid status of handshake response: 400 Bad Request

In SAP DI tenant, connection test returns:

Connection Id: xxx
Status code from service response: 400, Message: Failed to validate connection xxx.



SAP Data Intelligence


SAP Data Intelligence Cloud all versions


KBA , CA-DI , Data Intelligence , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-CP-CON-ABAP , ABAP Cloud to On-premise Connectivity service , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.