Symptom
- HA Cloud connectors are both stuck in Shadow State;
- The "Switch Role" button is not available:
- ljs_trace.log/scc_core.trc trace on the Shadow Instance might show the followings:
#PingToMaster failure
com.sap.scc.ha.HaHttpClientException: request https://<hostname>:<port>/shadow failed with 400 (Bad Request) A shadow system cannot connect to a shadow system. Check master host and port.
Note: "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
SAP Cloud Connector release independent.
Product
Keywords
shadow-shadow state, shadow instance, SAP Cloud Connector, master role, shadow role, master-shadow state, haRole, SCC, SCC configuration, There is no trust with Cloud Connector on, trust, certificate, SSL, HA, high availability, stuck, master-master, shadow, master, bad request, HTTP 400, 400, timeout, time out, com.sap.scc.ha.HaHttpClientException, pingtomaster Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." , 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.