Symptom
When checking sub-account status from SCC -> "Connector", you perceive it's not connected, and it keeps on failure status.
Upon selecting the sub-account itself from SCC -> <sub-account name from the left menu>, similar error below is raised.
Unable to connect: A different cloud connector instance with the same value for location ID is already connected to this subaccount
Finally, from SCC trace (ljs_trace.log (<2.17)/scc_core.trc (>=2.17) brings the following:
#ERROR#com.sap.core.connectivity.tunnel.core.handlers.TunnelClientErrorHandler#tunnel-client-678-4# #Unexpected problem during tunnel processing in channel [id: XXXXXXXXXX, L:0.0.0.0/0.0.0.0:61020 ! R:aws-eu-de.accounts.ondemand.com/X.XX.XX.XXX:443]; Reason: Invalid status of handshake response: 400 Invalid Upgrade Request; Exception type: com.sap.core.connectivity.tunnel.core.handshake.TunnelHandshakeException
202X-XX-XX XX:XX:XX,XXX +0200#ERROR#com.sap.scc.rt#https-jsse-nio2-8443-exec-5# #Tunnel account:///XXXXXXXXXX connect failed
com.ap.core.connectivity.tunnel.core.handshake.ClientConflictHandshakeException: Invalid status of handshake response: 409 Conflict
Read more...
Environment
- SAP Cloud Connector release independent;
- SAP BTP Cloud Platform.
Product
Keywords
multiple, cloud connector, Location ID, ClientConflictHandshakeException, 409, Conflict, Unable to connect: A different SAP Cloud Connector instance with the same value for location ID is already connected to this subaccount, scp, sap cloud platform, location, id, connector, failed, , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , 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.