SAP Knowledge Base Article - Preview

2611156 - Check Configuration - Load B. <host>:<port> could not be reached

Symptom

 In the Managed System configuration, step "Configuration Check", the following warning is raised:

Additionally, an error is raised if you test the load balancing URL in step Enter System Parameters:

A more detailed error is written to the Solution Manager defaultTrace:

Time: 2018 02 27 11:49:43:521
Severity: Error
Location: com.sap.smd.server
Text: [Setup]The Load Balancing URL http://<host>:50000 could not be reached
[EXCEPTION]
java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine (local port 50062 to address 0:0:0:0:0:0:0:0, remote port 50000 to address <IP address> (<host.domain>))
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
at java.net.Socket.connect(Socket.java:838)
at java.net.Socket.connect(Socket.java:776)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:469)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:583)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:257)
at sun.net.www.http.HttpClient.New(HttpClient.java:345)
at sun.net.www.http.HttpClient.New(HttpClient.java:364)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1031)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:967)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:885)
at com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection.connect(DSRHttpURLConnection.java:103)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1239)
at com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection.getInputStream(DSRHttpURLConnection.java:133)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at com.sap.sup.admin.setup.ManagedServices.checkLBconnection(ManagedServices.java:1184)
at com.sap.sup.admin.setup.ServerSetupStep.runExec(ServerSetupStep.java:247)
at com.sap.sup.admin.setup.ServerSetupStep.execute(ServerSetupStep.java:283)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:691)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1899)
at com.sap.sup.admin.setup.SapCluster.runClusterSetup(SapCluster.java:2141)
at com.sap.sup.admin.setup.ws.SetupWrapper._rManagedSetup(SetupWrapper.java:561)
at com.sap.sup.admin.setup.ws.SetupWrapper.managedSetup(SetupWrapper.java:351)
 


Read more...

Environment

SAP Solution Manager 7.2

Product

SAP Solution Manager 7.2

Keywords

KBA , SV-SMG-INS-DIA , Configuration of Root Cause Analysis related infrastructure , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.