SLD ISSUE communication with System Landscape Directory

[Former Member]

Hi Expert,

long back SAPXI system has been installed, we are able to login to

http://sapxi:50000/rep/start/index.jsp

But after login when we run Runtime Workbench from the screen it give me below error

Error during communication with System Landscape Directory: User credentials are invalid or user is denied access

See the Stack trace for the above error message is:

com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access

at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1472)

at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:773)

at com.sap.aii.rwb.agent.server.SLDAgentBean.provideSld(SLDAgentBean.java:269)

at com.sap.aii.rwb.agent.server.SLDAgentBean.getXIDomain(SLDAgentBean.java:711)

at com.sap.aii.rwb.agent.api.SLDAgentObjectImpl0.getXIDomain(SLDAgentObjectImpl0.java:375)

at com.sap.aii.rwb.agent.api.SLDAgent_Stub.getXIDomain(SLDAgent_Stub.java:436)

at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:255)

at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:137)

at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:100)

at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:102)

at jsp_component_monitoring1224651690000._jspService(jsp_component_monitoring1224651690000.java:209)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)

at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doGet(CmPageProcessor.java:27)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at jsp_FC_Secure1224651687796._jspService(jsp_FC_Secure1224651687796.java:24)

at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

if any one has has resolve this issue please help me with the solution

Thanks

DDM

[Former Member]

I suppose you are using other that Netweaver 7.1. Login to Visual Administrator, go to server - services - SLD Data supplier. I Runtime tab, check used parameters and if they are not right, change them in HTTP Settings and in CIM client settings. You can test these triggering SLD data manually and by CIM client test. Check also if the needed ports are open to SLD (ie. using telnet to SLD host and port).

[Former Member]

Hi Jani,

I am using SAP NetWeaver 2004s componet version

I Login to Visual Administrator and SLD Data supplier. I Runtime tab, check used parameters and right HTTP Settings and in CIM client settings. when I triggering SLD data manually and by CIM client test. It give me error as below

Failed to generate and test CIMOMclient object

Check also if the needed ports are open to SLD (ie. using telnet to SLD host and port).

I checked the RFC connection between ABAP (SM59) and Java (Visual Administrator) it working fine see the message as mention below

Properties of RFC destination SAPSLDAPI

RFC host: %%RFCSERVER%%

Program id: SAPSLDAPI_PXI

Gateway host: SAPXI

gateway service: sapgw00

Testing the RFC connection to the SLD java client...

RFC ping was successful

SLD server access settings:

host name : SAPXI

port number : 50000

user : xiuser

Use transaction SLDAPICUST if you wish to maintain the SLD server access data

Launching the SLD GUI in a separate browser window...

=> Verify in the browser GUI that the SLD is in a healthy running state!

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call returned exception code 4

=> Check whether the SLD is running!

Summary: Connection to SLD does not work

=> Check SLD function and configurations

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC

RFC host: %%RFCSERVER%%

program id: LCRSAPRFC_PXI

gateway host: SAPXI

gateway service: sapgw00

Testing the RFC connection to the SLD java client...

RFC ping was successful

Step2 :- I Have checked SLDAPICUST tcode in that Hostname , user name and password is correct

none of the user is lock in the system.

Step3:- I checked sld is working fine or not by using SXMB_ADM t-code:

Execute integration engine and configuration

In application toolbar check the first icon it will shows the status of SLD.

Role of Business System: Integration Server

http:// sapxi: 50000/sap/xi/engine?type=entry

Role of Business System: Current Configuration = No access to system landscape at present (Red in color)

After that I check whether SLD is properly configured or not by using SXMB_Ifn T-code web page is open than --> runtime workbench

Following error occurred while executing the application:

Error during communication with System Landscape Directory: User credentials are invalid or user is denied access

[Former Member]

<b>Failed to generate and test CIMOMclient object </b>

What if you change user and password to same as in HTTP settings? Does it work then?

[Former Member]

I change user name and password still it wont work give us same error

[Former Member]

Are you sure you typed password right?

Change also in SXMB_ADM integration server port to 8000. That should be right port to that one.

[Former Member]

password right I am able to login to system by using same password

As you said to Change also in SXMB_ADM integration server port to 8000.

Can please tell me how to change this port because mu port is 50000

http://sapxi:50000/sld

[Former Member]

SXMB_ADM - Integration engine configuration - press specific configuration, goto edit mode and change port under IS_URL. Save and it is done. Did you mean this one?

[Former Member]

no because that port no 50000

http://sapxi:50000/sap/xi/engine?type=entry

[Former Member]

If you are talking about service port then it is 8000

[Former Member]

This is a silly question, but does it give (this http://sapxi:50000/sap/xi/engine?type=entry) you a dialog box when you open it in a browser?

[Former Member]

yeh this what we have to give