2696907 - Best practices from SCC's perspective for addressing "503 Service Not Available" error when Cloud to On-Premise Connectivity fails

Symptom

***Note, that applying this KBA do not solve the issue, rather helps to investigate the root cause.***

Example scenario:

A destination is created in SAP Cloud Platrofm WEB IDE that points to an on-premise Backend system. WEB IDE tries to call SAP UI5 ABAP Repository from the Backend via SAP Cloud Connector (SCC) and shows "No Applications to display" and "503 Service Not Available" messages.

Environment

SAP Cloud Platform Cloud To On-Premise scenario with SAP Cloud Connector involved

Product

SAP Connectivity service 2.0

Keywords

503 Service Not Available, SCC, SAP cloud connector, Virtual host, Internal host, Access allowed, Cloud connector, No Applications to display , 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.