Component Monitoring returns error -- SLD access not ok ????

[Hannes2]

dear all

if i try to start the component monitoring from the runtime workbench i get the following error .

transaction SLDCHECK works fine and also the configuration in the visual admin (SLD data supplier ) works fine ==> test get data from SLD.

the SLD is running on another server .

definitions in sldapicust are done !!

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

stack trace:

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:1358)

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

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

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

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

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

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

at com.sap.aii.rwb.web.application.model.AppMainModel.getSelectedDomain(AppMainModel.java:136)

at com.sap.aii.rwb.web.componentmonitoring.model.DomainRep.build(DomainRep.java:101)

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

at jsp_component_monitoring1133863088524._jspService(jsp_component_monitoring1133863088524.java:207)

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

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:295)

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

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

at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)

at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)

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

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

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

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

at jsp_FC_Secure1133863082937._jspService(jsp_FC_Secure1133863082937.java:26)

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

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:95)

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

the "configuration" button in the runtime workbench gives the following error :

Unable to read XI domain from the SLD. Monitoring cannot therefore be configured. Error message: com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access

which user is used for this connection and where is this definition done ?

many thanks for your help

hannes toefferl

[Former Member · Accepted solution]

Hannes, if you check your SLD log, it should give you the details on what user tried to log in and why it denied access(SLD -> Administration -> server log).

Also If you go to SLD -> Technical Landscape -> choose category "Exchnage Infrastructure" from the drop down, you should see IR, ID, IS & RWB listed and should have domain entry against them. If not, then there is a problem.Chk this and let know what you see.

Regards

Saravana

[Hannes2 · Accepted solution]

dear all

many thanks for your fast and helpful response .

1) i can't see anything in the SLD log , because the user is not able to login to the SLD as you can see at the bottom of my first post.

2) the domain entries in the SLD are done and also correct .

3)our SLD ist running on the productive XI system in the J2EE of the XI system . we use the ABAP UME of this XI system . there i can see , that the user "XIRWBUSER" is locked after several attempts . so it seems to me , that the password of this user is wrong .

now my questions : where can i change the user and password for this connection ?

4) i get the error with SLD connection for all the other components as well (only in the runtime workbench) . the XI itself works fine.

thank you

hannes

[Former Member · Accepted solution]

Hannes, Since XI service user/pwd is maintained in multiple places , this could happen. You can unlock the service user in SU01. This note 721548 gives an idea where we may have to check/modify service user pwds if for some reason they keep getting locked. Hope it helps

Thanks

Saravana

[Hannes2 · Accepted solution]

hi saravana

thank you , the problem is fixed . the error was , that i had different passwords for the user XIRWBUSER in the different sap systems ==> the communication didn't work , either to the SLD or to the XI itself.

now i synchronized it and now it works !

thank you

hannes

[Former Member · Accepted solution]

Hi hannes ,

What were exact steps you did to synchronize XIRWBUSER in different sap systems. We are running a central SLD for XID,XIQ & XIP.

Thanks in advance

Ranjan

(r_mohapatra@hotmail.com)

[Former Member]

Check if the user with which you are trying to access RWB--> Component Monitoring is locked.

Rgds,

Amol

[Former Member]

Hi Hannes,

Please can you check the details of parameters given in Runtime Workbench and Connections in the Exchnage profile?

Are u getting the same error for all the components of Runtime workbench or only Component Monitoring?

Regards

Vijaya