SAP Knowledge Base Article - Preview

2731253 - Europe Frankfurt regions for subaccounts in SAP Cloud Connector


When adding a subaccount based in Frankfurt in SAP Cloud Connector, there are two available regions:

  • Europe (Frankfurt)
  • Europe (Frankfurt) - AWS

 You aren't sure which to select, or possibly you have selected one or the other and your connections are routed to the wrong environment. In that case you might find entries in the Cloud Connector ljs_trace.log similar to these:

#Creating an sslContextProvider for account <subaccount_id> without SSLContext. Keystore did not contain a certificate.|
2020-02-14 17:54:05,531          #Will retrieve Connectivity CA certificate from SAP Cloud Platform|
2020-02-14 17:54:05,531          #Executing Http Get request to<subaccount_id>|
2020-02-14 17:54:06,296          #Returned Http Response with code 500|
2020-02-14 17:54:06,299          #Stopping service channels on <subaccount_id>|
2020-02-14 17:54:06,299          #Tunnel account:///<subaccount_id> is inoperative. SccEndpoint ok, and context == null|
2020-02-14 17:54:06,305          #SCC handshake failed: 500 — Internal Server Error SCC handshake failed: 500 — Internal Server Error

in the above trace the wrong landscape is when it should be Expect to see in the traces in the reverse case.



  • SAP Cloud Platform Connectivity
  • SAP Cloud Platform


SAP Business Technology Platform all versions ; SAP Connectivity service 2.0

Keywords, , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , 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.