Runtime Workbench Component Monitoring ALL Display: error on page

Dear all,
when go in to Runtime Workbench >Component Monitoring > select ALL and press display ==> nothing coming and showing warning message at status bar that error on page.
what to do?
Best regards.
dushyant,

Hello,
Reinstall you internet explorer and use IE 6.0 and you can work on Mozilla Firefox also
Regards,
Ramesh P

Similar Messages

Error in Runtime WorkBench/Component Monitoring

Hi all,
1. I have configured an AS ABAP system to connect to the SLD successfully. In the Technical System List of SLD, it's named "TE1 on sap0810". (Successful)
2. After, i have created a Business System corresponding for this Technical System "TE1 on sap0810" with Client 810. In the Business System List of SLD, it's named "BUSINESS_SYSTEM_TE1CLNT810". (Successful)
3. And after, i log on into Runtime WorkBench and choose "Component Monitoring" Tab and choose Display all component, i get an error about the Business System "BUSINESS_SYSTEM_TE1CLNT810" for "Ping Status" and "Self-Test Status" as message below: (Error)
Ping Status: Unable to log on to system BUSINESS_SYSTEM_TE1CLNT810 in language en with user PIRWBUSER Last Retry Jul 28, 2008 5:48:56 PM ICT ... Details
Self-Test Status: Unable to log on to system BUSINESS_SYSTEM_TE1CLNT810 in language en with user PIRWBUSER Last Retry Jul 28, 2008 5:48:56 PM ICT ... Details
Anyone can please help me to resolve this problem?
Thanks a lot in advance,
<removed by moderator>
Vinh Vo
Edited by: Mike Pokraka on Jul 28, 2008 5:07 PM

hi friend
If you have created the TS & BS correctly in SLD
check the following points:
1)The JCO service might have been down...check it out....Sometimes it happens due to overloading of server...try to restart the server.....after clearing queue and cache restarting the server
2)check the RFC destinations AI_DIRECTORY_JCOSERVER, AI_RUNTIME_JCOSERVER.
regards
kummari

Error in Runtime Workbench, Component Monitoring, Proxy Runtime

Hi,
I have the following error in the Runtime Workbench, under Component Monitoring->Integration Engines->Proxy Runtime. The error message is Ping Status: Unable to logon to system xxx in language EN with user XIRWBUSER. However, I am unable to find out where the account and password are specified in order to correct this. Any help would be appreciated.

Hi,
it can be for some system configured on http destination or the sld system configured for this server.
take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
regards.
roberti

Runtime Workbench Component monitoring BPE fails

Hi,
When I am in the RWB->Component monitoring and attempt to display the Business Process Engine status I receive the following error:
Self-Test Status JCo request failed Last Retry Dec 7, 2005 11:09:31 AM MST
Details for 'Self-Test Status'
Message: JCo request failed
Stacktrace:
com.sap.aii.rwb.exceptions.JaycoRequestFailedException: JCo request failed
at com.sap.aii.rwb.rtcheck.rtcclient.JaycoConnector.selftest(JaycoConnector.java:202)
at com.sap.aii.rwb.rtcheck.rtcclient.JaycoConnector.selftestBPE(JaycoConnector.java:173)
at com.sap.aii.rwb.core.XIBusinessProcessEngine.selftest(XIBusinessProcessEngine.java:118)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doSelftest(CompTestModel.java:606)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doSelftest(CmDynPage.java:303)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:371)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:384)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:336)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
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:292)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:348)
at jsp_FC_Secure1128709178254._jspService(jsp_FC_Secure1128709178254.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:392)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
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:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:159)
Does anyone know what may be the cause of this (or what configuration may be missing)?
Regards,
Dan

Thanks Sundararamaprasad,
I had tried recycling the entire system as well as restarting the Jco service from the VA.
RFC destinations AI_DIRECTORY_JCOSERVER, AI_RUNTIME_JCOSERVER,
LCRSAPRFC, SAPSLDAPI all check successfully.
Transaction SWF_XI_CUSTOMIZING checks ok as well (all activities show green check mark).
Regards,
Dan

Runtime Workbench - Component Monitoring

We have just finished installing SAP XI 3.0 SP 15. When I go to Runtime work bench Component Monitoring and click on Integration Server the status is Yellow. All the results of test check are green except for Is Web service security available which is yellow? The details for this test says "Communication error Proxy calls on the sender or receiver side are not permitted on the IS (client)".
Similary for BPE the status is yellow. The test "Check Entries from HR Control Tables" has yellow status. The details says "Check entries from HR control tables = Check unsuccessful".
Can anyone help me in fixing these propblems if these are problems?

Hi,
these shouldn't be very serious problems. For the BPE, just follow the instructions provided in the post installation guide. Goto transaction SWF_XI_CUSTOMIZING and make sure that all indicators show a green light. In your case you might see one with out it. In this case you'll have to run report RHTTCP77.
Regarding the other problem, do not worry excesively. It should be a warning saying that message level security has not been configured yet. Please have a look at XI configuration guide, section 12.4
Best regards, Jaime

Log on to Runtime Workbench : click display error on page

Dear all,
when i try to log on to Runtime Workbench and click on display message , i am getting error that error on page,
we have already done post implementation steps for PI(XI),,
what to do, to test the senario from Runtime Workbench.
Best regards,
dushyant.

Hi,
This will help you
SAP Note-768456 & SAP Note-928862
http://help.sap.com/saphelp_nw2004s/helpdata/en/06/5d1741b393f26fe10000000a1550b0/content.htm
Regards
Agasthuri Doss

Cache Monitoring in Runtime Workbench not showing status/throwing error

Hello Friends,
The Cache Monitoring in Runtime Workbench is not showing the status at all. Below is the error message that is displayed.
Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "https://us-medpiqas.ww005.siemens.net:50001/run/value_mapping_cache/int?method=InvalidateCache" with user "null". Status of response is HTTP/1.1 401 Unauthorized - Unauthorized
It was working fine few days before. Now the messages are not getting processed as they are not able to access the message mapping at runtime. I am surprised as to how this happened. Can anyone of you tell me what I can do to proceed with the problem?
FYI: SXI_CACHE in ABAP Stack shows updated status and is green.
Thanks & Best Regards,
Anand Patil
Edited by: Anand Patil on Dec 22, 2010 4:06 PM

Hi,
Restarting the XI: CPA Cache Service in https://<host>:<port>/nwa -
> Systems---->Start & Stop. After restarting the CPA Cache service. The error is no more shown.
This works!
Thanks & Regards,
Anand Patil

Component monitoring 403 fornidden error

Hi ,
In the runtime workbench when i try to send a test message from component monitoring with my user account i get a 403 forbidden error . But when i use other user credentials it goes through and other users doesn't have this problem. So i suspect that its some issue with my privileges or something, How can i debug this issue.
Thank you

Hi Sudheer
error code 403 stands for Forbidden
This code indicates that the resource cannot be accessed, regardless of any authentication credentials. For example, this happens if a directory or file is unreadable due to file permissions.
for more details on error code follow the link
http://www.web-cache.com/Writings/http-status-codes.html
Check whether you have given the right credentials. If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine
steps to restart J2EE engine
1) run transaction SMICM
2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
Thanks
sandeep sharma
PS ; if helpful kindly reward points

Component monitoring - adapter engine error, but no channel in error actual

Hi,
We have a problem in displaying a status of Adapter Engine in RWB. In component monitoring there's a red light and the status - "Are communication channels without errors?" says there's an communication channel in error. But when I click the Communication channel monitoring, everything's green there. Yes, there was an error before, but it's ok now. Why is the AE item in Component monitoring still red? How to make it to reflect the current status?
Thank you,
Olian

Hi Olian,
i am saying to use the cache connectivity test button option from RWB -> compnent monitoring , so have you done cache test using this? if yes, click on refresh display to see the latest adapter engine status..............if it is green, then it is okay..............but if it is red here, it means some comm channel is erroring sometimes - i guess it can be a file adapter using ftp or some rfc adapter......................
if it is green here and compnent monitoring - adapter engine status is red because some comm channel errored in past.........then i think some cache is not getting refreshed - i do not know exactly how to rectify it...........but i can tell you some workaround for it..............the comm channel which was erroring just stop it from comm channel monitoring........then close RWB and again open it and see compnent monitoring - adapter engine status again in it - i think it should be green now.......or try by changing any comm channel description data in ID and save and activate it.........then again check your compnent monitoring - adapter engine status..................but dont worry i think this is a temporary problem
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Mar 26, 2008 11:50 AM

Error while opening Adapter Monitoring in Runtime Workbench

Hi,
I am unable to open Adapter Monitoring from
Runtime Workbench -> Component Monitoring -> Adapter Monitoring
When I tried to open, I am getting following message in the new window:
"The page cannot be displayed"
Please let me know where I can enable this option.
Thanks,
Yogi.

Hi,
Go thru this SAP Note- 768456,928862
Also this doc may help u-https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
Regards,
Moorthy

Errors in Runtime workbench after support pack stack 12

We have installed support pack stack 12 and now the runtime workbench - component monitoring is not working. I get a page of errors. here are some of the errors
Unknown error: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:250: cannot resolve symbol symbol : method getTestModel () location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel CompTestModel testModel = cmMainModel.getTestModel(); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:283: cannot resolve symbol symbol : method getTextFromCore (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_tray_0.setTitle( cmMainModel.getTextFromCore("component_monitoring") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:391: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_0.setValue( cmMainModel.getText("all_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:415: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_1.setValue( cmMainModel.getText("red_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:439: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_2.setValue( cmMainModel.getText("redYellow_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:486: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_0.setText( cmMainModel.getText("go_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:647: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_1.setText( cmMainModel.getText("tree_view_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:662: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel String label = cmMainModel.getText("switchToTableView"); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:703: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_2.setText( cmMainModel.getText("ccms_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:808: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_group_1.setTitle( cmMainModel.getText("searchResults_group") );
I have done the java support pack again to make sure it was installed properly.
Thanks,
Dede Logan

Well after the SAP XI server was restarted and I tried to go back into the runtime workbench and then into the Component Monitoring I am getting another error.
Unknown error: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_jsp_error1117123949279.java:74: setFeedbackToUser(com.sap.aii.rwb.web.util.Feedback) in com.sap.aii.rwb.web.application.model.AppMainModel cannot be applied to (com.sap.aii.rwb.util.web.Feedback) appMainModel.setFeedbackToUser( ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_jsp_error1117123949279.java:79: setFeedbackToUser(com.sap.aii.rwb.web.util.Feedback) in com.sap.aii.rwb.web.application.model.AppMainModel cannot be applied to (com.sap.aii.rwb.util.web.Feedback) appMainModel.setFeedbackToUser( ^ 2 errors .
does anyone know how to correct this error or what the cause of the error.
dede

Adding entries in Audit Log Tab in Component Monitoring under Runtime Workb

Hello Experts,
I am trying to add my own audit log entries to the Audit Log Tab under Runtime Workbench -> Component Monitoring. I found this sap help link (http://help.sap.com/saphelp_nwpi71/helpdata/en/3b/6fe540b1278631e10000000a1550b0/frameset.htm) I am not sure if i am going in the right direction or not. But, when I tried to use the code in my User Defined Function in Message Mapping it gives me java error on PublicAPIAccess.
Can anyone please let me know what am i doing wrong or if I am going in a totally wrong direction to achieve me goal.
I am using PI 7.1 without EP1 and my example uses File adapter.
Thanks!!

Hi,
if you are trying to add custom audit log for system monitoring in RWB in component monitoring, then i think it is not feasible........moreover for this thing, you can ask your basis guys to configure CCMS in your XI system to recieve alerts for your system.............
if you are trying to add custom audit log msgs for your msg processing, then you should develop a custom J2EE adapter module and add your audit log entries in the process method of your adapter module..............
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on May 6, 2009 7:12 AM

Problem with Runtime Workbench and with sending data from XI to SLD

Hello 
 
Could I have a little help, a hint in the two following topics: 
 
1. I run Runtime Workbench -> Component Monitoring -> Display All and I get this error: 
 
Error during communication with System Landscape Directory: User credentials are invalid or user is denied access 
 
In filesystem log I can find like this: 
 
XIRWB.com.sap.aii.mdt.frames.jsp_error [SAPEngine_Application_Thread[impl:3]_40] Fatal: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access 
Thrown: 
MESSAGE ID: com.sap.aii.rwb.agent.server.rb_LCRAgent.landscapeCommunicationError 
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_0.getXIDomain(SLDAgentObjectImpl0_0.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:138)
 at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
 at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117) 
 at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
 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_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.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:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 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(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
Root cause: 
com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access 
 at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577)
 at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341)
 at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:280)
 at com.sap.lcr.api.cimclient.CIMOMClient.performBatchOperation(CIMOMClient.java:1251)
 at com.sap.lcr.api.cimclient.CIMClient.performBatchOperation(CIMClient.java:2268)
 at com.sap.aii.utilxi.sld.MRSldProxy.stage1(MRSldProxy.java:989)
 at com.sap.aii.utilxi.sld.MRSldProxy.loadComponents(MRSldProxy.java:918)
 at com.sap.aii.utilxi.sld.MRSldProxy.loadSld(MRSldProxy.java:907)
 at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:373)
 at com.sap.aii.utilxi.sld.SubSystemFactory.createSldFromSld(SubSystemFactory.java:434)
 at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:764)
 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_0.getXIDomain(SLDAgentObjectImpl0_0.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:138)
 at com.sap.aii.rwb.util.web.model.DomainRep.build(DomainRep.java:121)
 at com.sap.aii.rwb.web.componentmonitoring.model.ObjectIdentificationTree.getComponentTree(ObjectIdentificationTree.java:117)
 at jsp_component_monitoring1321125174985._jspService(jsp_component_monitoring1321125174985.java:217)
 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_Secure1321125169379._jspService(jsp_FC_Secure1321125169379.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:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 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(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 
 
 
I don't know what is wrong. 
I have configured: 
- SLDCHECK work properly, 
- none of the users PI* type not lock, 
- password to the PI* users in exchangeProfile entered correctly, 
- In VA in the JCo RFC Provider I have properly configure: AI_RUNTIME_JCOSERVER, LCRSAPRFC, SAPSLDAPI_SID - from the ABAP I can connect to this programs ID 
- In VA in SLD Data Supplier I have properly configure bookmarks HTTP Settings and CIM Client Generation Settings. CIMClient Test is OK 
 
I do not know what else I can see, what else I have properly configured ... I looked at the notes:: 936093 jak i 721548... 
 
 
2. I can't send data from XI to SLD, ie makes me a system definition in Web As Abap and Web as Java but nothing appear to me in Exchange Infrastructure. Exchange Infrastructure is empty - what is wrong?? 
I carried out the recommendation by 764176 and 1031321 notes 
 
I restart below applications (no effect)... 
com.sap.xi.directory (Integration Builder/Configuration) 
com.sap.aii.af.app (Adapter Engine) 
com.sap.xi.rwb (Runtime Workbench) 
com.sap.xi.repository (Integration Builder/Design) 
 
Can I ask for help and guidance in these topics? 
 
Regards 
RP 

I increased logging in the NWA (Configuration -> Log Configuration) - and increased the some things here to log ALL. So that from the NWA (Monitoring -> Logs and Traces) I see a little more information (but does not follow that with which the user is a problem). 
 
Here are some interesting logs ... 
I was most rash or irritation of those that say about the lack of credentials u2013 I must use Viusal Administrator and set good service ... 
 
What do I have done: 
In the Visual Administrator -> Cluster -> Server -> Services -> SLD Data Supplier 
I have set in the HTTP Settings tab the host and port SLD, the user name and password is also entered as it is in the SLD. To be sure, already have set for the user entered here such roles as: 
SAP_SLD_ADMINISTRATOR 
SAP_SLD_CONFIGURATOR 
SAP_SLD_DEVELOPER 
SAP_SLD_GUEST 
SAP_SLD_ORGANIZER 
Maybe we are talking in this place about a different user? 
 
Similarly, when it comes to tab CIM Client Generation Settings - here's all the same thing done. CIMClient test shows that everything is OK. 
When I click the button: This trigger the transfer of data to the SLD gets the message that everything was shipped correctly. Indeed, I received an instance of JAVA in SLD 
Also clicked on this icon: Assign application roles to user group - got information that everything is attached properly. 
 
By ABAP side, the connections: INTEGRATION_DIRECTORY_HMI, SAPSLDAPI, LCRSAPRFC, AI_RUNTIME_JCOSERVER and AI_DIRECTORY_JCOSERVER work correctly, ie I can perform the test - which means that programs ID are properly positioned in JCO Provider in VA. 
 
Puzzling is this message: 
The SLD data is inconsistent. 
 
Strange also that the message (from the ABAP everything is available in SMGW no errors): 
Connect to SAP gateway failed 
 
And what is this error: 
 
could not sync ExchangeProfile: 
Thrown: 
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
 
Below is a list of some interesting logs ... 
 
########### 
 
Insufficient permissions for getting SLD access information. You can add permissions for your application via the SLD service in the 'Visual Administrator'. 
 
############# 
 
SLD is not accessible. Check SLD Data Supplier service settings. 
 
########### 
 
"Warning","2012-02-22","07:53:50:986","Data get on com.sap.sldserv.data.GetSAPBCCentralServiceInstance class processing failed. htThe SLD data is inconsistent. This is an internal processing problem.","/System/Server/SLDService","com.sap.sldserv.DataCollector","n/a","saptest2","Server 0 60_36694", 
 
######### 
 
com.sap.lcr.api.cimclient.UnauthorizedUserException: User credentials are invalid or user is denied access 
 
################ 
 
Full Message Text
CPA Cache not updated with directory data, due to: Couldn't open Directory URL (http://saptest2.unx.era.pl:56000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xit.saptest2), due to: HTTP 503: Service Unavailable
 
################## 
 
Full Message Text 
 
could not sync ExchangeProfile: 
Thrown: 
com.sap.rprof.dbprofiles.DBException: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
Connect_PM TYPE=A ASHOST=saptest2 SYSNR=60 GWHOST=saptest2 GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner 'saptest2:sapgw60' not reached 
TIME Thu Feb 23 07:28:07 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 2 
 
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457) 
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015) 
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238) 
at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:101) 
at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1288) 
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:195) 
at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.readProfile(ExchangeProfilePropertySource.java:177) 
at com.sap.aii.utilxi.prop.rprof.ExchangeProfilePropertySource.sync(ExchangeProfilePropertySource.java:165) 
at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:582) 
at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43) 
at com.sap.aii.adapter.xi.ms.SLDReader.fire(SLDReader.java:52) 
at com.sap.aii.adapter.xi.ms.SLDReader.run(SLDReader.java:167) 
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) 
at java.security.AccessController.doPrivileged(AccessController.java:219) 
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
 
############## 
 
Full Message Text 
 
Import of software component version list from component repository failed 
Thrown: 
com.sap.lcr.api.cimclient.LcrException: User credentials are invalid or user is denied access 
at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:577) 
at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:341) 
at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:198) 
at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:146) 
at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstancesImpl(CIMOMClient.java:443) 
at com.sap.lcr.api.cimclient.CIMOMClient.enumerateInstances(CIMOMClient.java:747) 
at com.sap.lcr.api.cimclient.CIMClient.enumerateInstances(CIMClient.java:980) 
at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.enumerateInstances(JavaCIMObjectAccessor.java:211) 
at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateInstances(SAP_SoftwareComponentAccessor.java:204) 
at com.sap.lcr.api.sapmodel.SAP_SoftwareComponentAccessor.enumerateSAP_SoftwareComponentInstances(SAP_SoftwareComponentAccessor.java:239) 
at com.sap.aii.ibrep.server.sldaccess.interfaces.CRAccess.getSwcLinks(CRAccess.java:82) 
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.getEoLinks(SwcAccessor.java:59) 
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.getEoLinks(EOAServiceImpl.java:75) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.getEoLinks(EOAServiceBean.java:66) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.getEoLinks(EOAServiceRemoteObjectImpl1_0.java:527) 
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:232) 
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) 
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) 
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) 
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(AccessController.java:219) 
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) 
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
 
############## 
 
Full Message Text 
 
An exception was thrown in the UME/ABAP user management connector. Message: Connect to SAP gateway failed 
Connect_PM TYPE=A ASHOST=localhost SYSNR=60 GWHOST=localhost GWSERV=sapgw60 PCS=1 
 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR partner '127.0.0.1:sapgw60' not reached 
TIME Thu Feb 23 07:28:06 201 
RELEASE 700 
COMPONENT NI (network interface) 
VERSION 38 
RC -10 
MODULE nixxi.cpp 
LINE 2513 
DETAIL NiPConnect 
SYSTEM CALL connect 
ERRNO 79 
ERRNO TEXT A remote host refused an attempted connect operation. 
COUNTER 16

Problem with component monitoring

This is in the runtime workbench, Component monitoring, in that this jobs are not being scheduled. Please check for different options and let me know...
scheduled background job for processing and scheduled backgroud job for re organizing is showing error which is red..
how can i resolve this....
regards,
krushi

have u refreshed ur cache see that ur cache is green if any red is there the messages may not be seen in runtime and no schedule is done
"refesh ur cache "
go to T-code sxi_cache

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

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

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

Runtime Workbench Component Monitoring ALL Display: error on page

Similar Messages

Maybe you are looking for