3767359 - Connection validation fails for S/4HANA on‑premise (message server) when virtual host differs from internal host via cloud connector - SAP Datasphere

• Connection validation to an on‑premise S/4HANA system using load balancing with message server fails if the virtual host is different from the internal hostname; it works when both are identical.
• Error: Remote Tables: Unable to connect remote source: DPAdapterAccess::Connect: Initialization of destination … failed: Connect to message server on host [message server host] failed.
  LOCATION CPIC (TCP/IP) on local host with Unicode; ERROR hostname '[message server host]' unknown; Code: 5921; SQL State: HY000.

• Product: SAP Datasphere
• Connections
• S/4HANA on‑premise connection (Message Server)
• SAP Cloud Connector (RFC)
• Data Provisioning Agent for Remote Tables

1. Create an S/4HANA on‑premise connection in Datasphere using Message Server (load balancing).
2. Enable Cloud Connector usage for the connection.
3. Maintain the Virtual host different from the internal backend hostname, and set Virtual Destination to derive the virtual host and port from the connection details.
4. Validate the connection and observe the errors for Remote Tables.

The Cloud Connector virtual host was maintained in the Message Server “Connection Details” (or “derive virtual host and port from connection details” was selected), causing the runtime to attempt to resolve the virtual hostname at network level. This leads to “hostname unknown” and message server connect failures. For Cloud Connector scenarios, the virtual host and port must be configured only in the Cloud Connector section, while the Message Server field must contain the actual backend message server host.

1. Edit the Datasphere connection and in the Connection Details section, enter the actual backend Message Server host and the correct port and group.
2. In the Cloud Connector section, set Virtual Destination to “Enter Virtual Host and Port in Separate Fields”.
3. In the Cloud Connector section, enter the Cloud Connector virtual host and virtual port.
4. Save the connection and validate again.
5. If issues persist, verify the Cloud Connector system mapping and access control for RFC as per SAP Help Portal, then revalidate.
6. For structured checks of Cloud Connector scenarios, refer to the pre‑analysis KBA 3456850 and adjust configuration as needed.

• KBA 3456850 - Pre-analysis Cloud Connector related issues when creating a connection in Datasphere
• KBA 3440815 - RFC_COMMUNICATION_FAILURE in S/4HANA On‑Premise Connection - Datasphere
• SAP S/4HANA On-Premise Connections | SAP Help Portal
• Configure Cloud Connector
• Configure Access Control (RFC)
• Datasphere ABAP-based On-Premise System Connection Troubleshooting KBAs | SAP Help Portal

datasphere, s/4hana on‑premise, message server, cloud connector, virtual host, internal host, rfc, remote tables, dp agent, abap adapter, hostname unknown, connect to message server failed, connection validation, virtual destination, load balancing, system mapping , KBA , DS-DI-CON , Connections , Problem