3479260 - Error: "Open request could not be performed due to error: Server Busy Try again later."

When validating connection in SAP Datasphere, the following error occurs:

---------------------------------------------------------------------

Connection "XXX" couldn’t be established. - Data flows can’t be used because of errors in the connection.

Data Flows: Cause: Open request could not be performed due to error: Server Busy Try again later.

Correlation ID: XXXX-XXXX-XXXX-XXXX-XXXX

---------------------------------------------------------------------

The SAP Cloud Connector logs have some logs similar to the following:

2024-01-16 13:32:23,853 -0600#ERROR#com.sap.core.connectivity.tunnel.client.reconnect.AbstractReconnectableClient#notification-client-23-1#          #Connect client to 'connectivitynotification.cf.us10.hana.ondemand.com:443' failed: handshake timed out after 10000ms
2024-01-16 13:33:05,324 -0600#ERROR#com.sap.scc.rt#https-jsse-nio2-8443-exec-10#          #Tunnel account:///29cf9b98-c4b1-4af0-8d0c-83b7ba80f57e/CPITEST connect failed
io.netty.handler.ssl.SslHandshakeTimeoutException: handshake timed out after 10000ms
2024-04-23 00:42:11,293 -0500#ERROR#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-34-1#0xf28e9aa4#Unable to open connection to backend system: error 111 - Connection refused: gt5b4devas01.gst.ibmcloud.local/10.110.18.10:8040

SAP Datasphere

Server Busy

1. Refer to the KBA 3456850 - Pre-analysis Cloud Connector related issues when creating connection in Datasphere to verify the configuration.
2. If the configuration mentioned in the above KBA matches for both SAP Cloud Connector and Datasphere, and the same error is still reported when validating the connection, it means that the server is busy as described in the error message. Please try again after some time. (Usually this takes about 2 days, so please be patient)

SCC, DS, SAP Cloud Connector , KBA , DS-DI-CON , Connections , Problem