Symptom
When trying to add a new Subaccount to the SAP Cloud Connector, the following message is received:
417 Could not download configuration file. See "Log And Trace Files" and in particular ljs_trace.log for details. Consult SAP note 2460641 for possible remedies.
When checking the ljs_trace.log file for more information, it's possible to see the following logs:
<date and time> #INFO#com.sap.scc.security#https-jsse-nio2-8443-exec-8# #Returned Http Response with code 500
<date and time> #INFO#com.sap.scc.config#https-jsse-nio2-8443-exec-8# #Stopping service channels on <Subaccount>
<date and time>#ERROR#com.sap.scc#https-jsse-nio2-8443-exec-8# #SCC handshake failed: 500 — Internal Server Error
com.sap.scc.servlets.SccHandshakeException: SCC handshake failed: 500 — Internal Server Error
Read more...
Environment
- SAP Business Technology Platform;
- SAP Cloud Connector.
Keywords
handshake failed, SCC, SAP Cloud Connector, 500 — Internal Server Error, New subaccount, 417 Could not download configuration file, Http Response with code 500, BTP, Business Technology Platform , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-CP-CON , Cloud to On-premise Connectivity service , Known Error
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.
SAP Knowledge Base Article - Preview