SAP Knowledge Base Article - Preview

2779018 - Adding Neo subaccount to SAP Cloud Connector fails - SCC handshake failed: 400 — Bad Request

Symptom

You try to add subaccount to SAP Cloud Connector (SCC) and it fails with the error displayed in the User Interface (UI):

"417 Cloud not download configuration file: 400 — Bad Request"

 400_Bad_Request_Subaccount.PNG

In SCC's ljs_trace the following can be seen:

[...]
#ERROR#com.sap.scc.ui#http-bio-8443-exec-5#          #SCC handshake failed: 400 — Bad Request
com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 400 — Bad Request
[...]


Note: Image/data in this KBA is from SAP internal systems, sample data, or demo systems, and any resemblance to real data is purely coincidental.


Read more...

Environment

  • SAP Cloud Platform Connectivity;
  • SAP Cloud Connector release independent.

Product

SAP Connectivity service all versions

Keywords

400 Bad Request, 400 — Bad Request, SccHandshakeException, SCC handshake failed, 417 An authorization problem,  SAP Cloud Connector, Cloud Connector, SCC, CONNECT refused by proxy, refused by proxy, bad request, HTTP 400, sub-account, subaccount, sub account, Neo, com.sap.core, SAP Cloud connector, SCC, cloud connector, connector,  , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-NEO-CON , Neo to On-premise Connectivity service , Problem

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.