Symptom
While checking the central SLD you notice that information which should be same on two or more SLDs are not in accordance as systems are not getting updated on the target SLDs by the Bridge Forwarding, also you can see the below log errors under target SLD tab "Administration" -> "Log".
Erros #97 12/27/2017 11:39:31.964 [SLD Data Supplier Forwarding] ERROR com.sap.lcr.sagent.BridgeCommunicationHTTP: Can not send data to http://<targethost>:<port>/sld/active/: 503 Service Unavailable Erros #96 12/27/2017 11:39:31.949 [SLD Data Supplier Forwarding] ERROR com.sap.lcr.sagent.BridgeCommunicationHTTP: Can not send data to http://<targethost>:<port>/sld/: 503 Service Unavailable Erros #95 12/27/2017 10:40:12.217 [SLD Data Supplier Forwarding] ERROR com.sap.lcr.sagent.BuilderDirector: Can not send data to http://<targethost>:<port>/sld/active, system is still unavailable Erros #94 12/27/2017 10:39:51.210 [SLD Data Supplier Forwarding] ERROR com.sap.lcr.sagent.BuilderDirector: Can not send data to http://<targethost>:<port>/sld, system is still unavailable |
Read more...
Environment
SAP AS NetWeaver Java release independent.
Product
Keywords
SLD, SLD bridge forwarding, bridge forwarding, not updated, SLD sync, sync, push data, push data between slds, niping, sld connection test, /sld, RZ70, data suppliers, DS, Centra SLD, pushing data, sld oudated , KBA , BC-CCM-SLD , System Landscape Directory / Component Repository , 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.