cancel
Showing results for 
Search instead for 
Did you mean: 

SAP cloud connector and SharePoint

0 Kudos

I'm trying to connect the SAP cloud connector with our on-premise SharePoint. Having the settings non-SAP system/HTTPS/internal and virtual host names the same/no principal and after uploading the CA cert, I get:

HTTP/1.1 503 Service Unavailable

entered by the connection validator into the logs.

Why is this and what can I try next?

Accepted Solutions (1)

Accepted Solutions (1)

oppancs
Contributor
0 Kudos

Dear Tom,


"503 Service not available" is a very general error that means the backend service is not running or not availabe for some reason. Message can be found on all 3 parts: Frontent (Cloud), intermediary (SCC) and Backend.


In case you get this error by "check availabity of internal host" this is not a valid error (in case of e.g. Web dispatcher). See for it the KBA for more details:


2695217 - SAP Cloud Connector backend "Not reachable" - 503 Service Unavailable


In case there are no logs recorded in the SCC's ljs_trace the request is most likely not even reaching the backend. The reason in most of the cases that an incorrectly configured destination (e.g. location ID missmatch) in cloud application side. For this check the settings by help of the KBA:


2697040 - Destination connection fails in SAP Cloud Application - There is no SAP Cloud Connector (SCC) connected to your subaccount


In case destination configuration is correct and you see logs in ljs_trace and payload trace it means backend service is indeed not available. For this you can trace the scenario to find the root cause. You can gather best practices according to the KBA:


2696907 - Cloud To On-Premise connectivity fails with "503 Service Not Avaliable" - Best Practices for analyzation from SCC's perspective


Best Regards,
Barnabás Paksi

Answers (1)

Answers (1)

0 Kudos

Thank you very much for your help!

My guess this is probably not a valid error as described in the first article you listed.