Proxy Runtime Error in RWB.

Hi All,
I am getting following error,
Please, help me to solve this problem
Message: Neither the messager server nor the application server can be reached for system DSM
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Neither the messager server nor the application server can be reached for system DSM
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:863)
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:726)
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:698)
at com.sap.aii.rwb.core.R3System.getRepository(R3System.java:910)
at com.sap.aii.rwb.core.BusinessSystem.getRepository(BusinessSystem.java:802)
at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:97)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:580)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:307)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:381)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:397)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:348)
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:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.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:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks In Advance
Mahesh

Hi Seshagiri,
Actually, i am getting this error in message Monitoring dropdown, i have Proxy Runtime Receiver System option. when i am selecting the same i am getting the following error.
  javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
     at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:456)
     at com.sap.aii.mdt.api.server.IntegrationEngineHomeImpl1_0.create(IntegrationEngineHomeImpl1_0.java:195)
     at com.sap.aii.mdt.api.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:57)
     at com.sap.aii.mdt.util.MonitoringBeanCache.getMonitoringBean(MonitoringBeanCache.java:305)
     at com.sap.aii.mdt.util.WebUtil.getMonitor(WebUtil.java:351)
     at jsp_monitor_new1221049881372._jspService(jsp_monitor_new1221049881372.java:140)
     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:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     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 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:427)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
     at com.sap.aii.rwb.web.messagemonitoring.viewcontroller.MmDynPage.doProcessBeforeOutput(MmDynPage.java:69)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
     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_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.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:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Similar Messages

  • Proxy Runtime error

    Hello..
         In FILE-XI-BW scenario... I'm getting error in adapter monitoring (integration engine --> Proxy runtime )
    Error is..  "Unable to log on to system D03 (BW system) in language en with user XIRWBUSER...
    Can any one tell me what might be the problem..
    Thanks..

    Hi Padma
    Can you check your configuration Tab in Runtime workbench. If there also you are getting this same error.
    Create a port in your business system using Tcode : we21.
    Also have you set in your proxy System the destination to Integration Server?
    If not:
    Goto sxmb_adm -> Integration Engine configuration -> Role of Business System = Application System with corresponding integration server dest//RFCdestinatio2yourIntegrationServer.
    Best Regards
    - lalit -

  • Proxy Runtime errors in Integration Engines at RWB

    Hi Experts,
    We have configured the point to point configuration scenario in our landscape. I have two ABAP systems exchanges data using PI. I have configured both the ABAP systems as Application Systems and Corresponding Integration server as my PI system.
    In RWB of PI I can see both these systems as proxy run time under Integration Engines, but are in error status.
    Path to the same is Component Monitoring>Components>Integration Engines (here I can my systems as Proxy Runtime BSAB200, Proxy Runtime BSID200).
    When run the test got the below error.
    Can the SLD be reached?  RFC destination LCRSAPRFC does not exist
    Does the Integration Engine know the business system? 
    Are roles in SXMS_CONF_ITEMS and SLD consistent?
    Why do we need to create the RFC destination again when we select the related integration server as PI.
    Can any one throw some light whey are these errors are occured.
    Thanks,
    Chinna

    Can the SLD be reached? RFC destination LCRSAPRFC does not exist
    Reached to SLD but not to exchange profile.
    Does the Integration Engine know the business system?
    Yes.
    Why do we need to create the RFC destination again when we select the related integration server as PI.
    A central SLD scenario involves a central SLD, but not a central exchange profile.
    The exchange profile used is always the one on the Integration Server the
    application system connects to the exchange profile using the SM59 destination
    LCRSAPRFC.
    Regards
    Pothana

  • Integration Engine Proxy Runtime Error

    Hello,
    I have  ECC and PI server for my landsacpe. When i ran SXMB_IFR tcode in my ECC server i got the follwing error under Runtime work Bench
    Proxy Runtime - it is shows red color.
    Unable to log on to system ECC120   in language en with user PIRWBUSER  
    Details for Ping Status
    Message: Unable to log on to system ECD210 in language en with user PIRWBUSER
    Stacktrace:
    com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system ECD210 in language en with user PIRWBUSER
    at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:114)
    at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
    at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
    at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
    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:321)
    at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
    at jsp_FC_Secure1229621978943._jspService(jsp_FC_Secure1229621978943.java:15)
    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:566)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
    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:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    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:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    When i checked  my PIRWBUSER password in abap and poratal level there is no conflicts. Password is correct.
    For integration i have created three RFC also
    LCRSAPRFC,SLDAPIRFC,SAPJ2EE all these RFC are working fine and there is no error.
    Can any one suggest me how to resolve this issue.
    I am waiting for your reply.
    Regards,
    Sankaranarayanan.G
    BASIS CONSULTANT

    Hi Tuhin,
    I have one more problem now. Intially i have configured my PI development portal.But after some days in  my PI server when i ran SXMB_IFR is detecting wrong poral now. I have tried to change from my EXCHANGE Profile under integratrion server parameters i have changed PORT,URL and others.
    but it is not come to effect. can you please help me where do i need to chage the portal?
    I am waiting for your reply.
    Regards,
    Sankar.G

  • JMS To proxy Runtime error

    Hello,
          I am doing a JMS to Proxy scenario, so in mapping at run time i am getting
    an error as:
    Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 30, 30, 20(:main:, row:1, col:3) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 30, 30, 20(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error:
    My source file is :
    00  QY040           AM01- NBG IABENT21 A  6257069               21                00000020001                   20070301200703030002167440                                  429900000002167440teealm  tezste          A:10245980-1; 1/1; I/EE-31; 91830; ALMSTETTER,HANS      000000000         10245980-1                                                                                ALMSTETTER,HANS91830
    Can any one throw some light,how does JMS handle incoming data ?
    Regards,
    Anirban.

    Hi All,
    I want to configure JMS to Proxy Scenario , the link provided above doesnt show any blog.
    Can anyone explains what steps I need to follow to configure JMS to PROXY scenario? More specifically configuration and stpes to be considered in case of JMS configuration . (Proxy I know ).
    I do have the XSD , source structrure which will be genrated via MQ .
    Thanks,
    Pushkar

  • Java Proxy Runtime Error - A remote host refused an attempted connection

    I am able to register my Java server proxy with no errors. However when I message is sent through I get the following error in Xi Adapter:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error invoking method someJavaProxyCallIB of proxy bean com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4LocalObjectImpl0_0: A remote host refused an attempted connect operation.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error invoking method someJavaProxyCallIB of proxy bean com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundLocal4LocalObjectImpl0_0: A remote host refused an attempted connect operation.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Doea anyone know why this is happening?

    I guess, that you have Java proxy libraries in the EAR file. Remove them before deploying.
    Regards
    Stefan

  • Proxy Runtime for Business System not visible in RWB.

    Hi,
    We are running SAP PI 7.10 SP7.
    The current landscape contains currently 2 SAP R/3 application systems and 1 SAP PI systerm that are all registered with the SAP PI SLD.
    There is Business Systems configure for both the Application systems in the SLD from the registration.
    In the ID it was possible to import these Bussiness systems and to use them in scenarios. It is even posible to post messages to both IE on these Business Systems. If tcode SPROXY is executed on both these business systems then it connects to the same ESR. On both business systems I have created a "PIRWBUSER" with the same password and roles as on SAP PI.
    Now my ploblem is that I only see one proxy runtime in the RWB under Integration Engines.
    Please can you assist in this matter?
    Regards
    Willie Hugo

    Hi,
    The problem is solved with patches to the following JAVA components.
    MESSAGING 7.19
    SAP_XIAF7.17
    SAP_XITOOL7.14
    Regards
    Willie Hugo

  • Alerts from Proxy Runtime

    Hi,
    I am in the position at the moment where I am able via the ALT framework to sent alerts generated from error message in sxmb_moni on the SAP PI system. This I achived using ALT Framework alert categories and Alert Rules Configuration in the RWB.
    However in A2A scenarios where messages are exchanged between SAP ECC systems SAP PI I would like to enquire about how the proxy runtime errors that occure on the SAP ECC side (Sending and Receiving) is captured and sent as alerts.
    So in essence if a message goes into an error state on the SAP ECC proxy side in sxmb_moni then I would like to receive an alert via mail to this end.
    Your assistance in this regard with be highly valued.
    Regards
    Willie Hugo

    Willem,
    However in A2A scenarios where messages are exchanged between SAP ECC systems SAP PI I would like to enquire about how the proxy runtime errors that occure on the SAP ECC side (Sending and Receiving) is captured and sent as alerts.
    Nothing that PI can do in this situation. PI can raise alerts on IE and AE errors. The ECC system needs to raise alert for errors happening at their end.
    So in essence if a message goes into an error state on the SAP ECC proxy side in sxmb_moni then I would like to receive an alert via mail to this end.
    What do you mean by "receiving an alert via email to this end"? You want the alert email to be sent to PI or to an individual? Either case, it can be achieved. Please elaborate your requirement.
    Regards,
    Neetesh

  • How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

    Hi all,
           In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
    Thanks,
    YiNing

    Hi,
    While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
    I think ur data is worng,if it is wrong then only u will get this type of errors.
    Regards,
    Phani

  • 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

  • PI Proxy runtime RFCSYSTEM

    Hi Every one,
    when i try to active Proxy runtime RFCsystem on runtime workbench i am not able to activate it. i here by enclosing the with following error, Kindly do the needful ASAP
    An error occurred: Message: Exception in Method: CentralTrexManager: activateIndex( String ). TrexException: Failed to activate Trex service. Message: Message: OperationFailedException in Method: CentralTrexManager: setAbapActivation( Sxms_Indexing_Activate_Input ). CentralTrexException: JCO call failed. Root cause: null; severity: FATAL; localized message: Unable to log on to system LXI in language en with user PIRWBUSER; To-String: com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system LXI in language en with user PIRWBUSER; To-String: Class: com.sap.aii.rwb.web.trex.CentralTrexException : Message: OperationFailedException in Method: CentralTrexManager: setAbapActivation( Sxms_Indexing_Activate_Input ). CentralTrexException: JCO call failed. Root cause: null; severity: FATAL; localized message: Unable to log on to system LXI in language en with user PIRWBUSER; To-String: com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system LXI in language en with user PIRWBUSER
    regards
    Ramesh

    Hi Ramesh,
    The PIRWBUSER is used for retrieving data from your R3 backend proxy and XI system.
    This user must exist in your R3 proxy system ie.. backend  with the same password that is in your XI system.
    So, check whether the password is the same in Exchange Profile, in XI and in your R3.
    Furtheremore, check that this user is not locked in any system.
    Regards
    joel

  • Java Proxy Runtime:  failure to locate proxy bean on inbound call

    Hello gurus of the SDN,
    I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code.  My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc.  I successfully deployed the generated java proxies on the same host box as is running the XI instance.  The objects are named as follows
    Message interface on XI = Inbound_MATMAS04
    Generated proxy bean = Inbound_MATMAS04_PortTypeBean
    Implementing class = InboundMATMAS04_PortTypeImpl
    Implementing method = inboundMATMAS04
    I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly.  I used the following entry in my web browser:
    http://nadcp786:50000/ProxyServer/register?
    ns=urn:xiTrainingLabs:groupXX:SAP&
    interface=InboundMATMAS04&
    bean=InboundMATMAS04_PortTypeImpl&
    method=inboundMATMAS04
    I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located.  When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="PARSING">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean.  I think I am missing a configuration step somewhere, but can’t figure out what it is!!  Can anyone help me? 
    Many thanks in advance.
    Regards,
    Nick Simon
    Time Stamp     Status     Description
    2004-10-25 19:47:32     Success     The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
    2004-10-25 19:47:32     Success     Using connection JPR. Trying to put the message into the receive queue.
    2004-10-25 19:47:32     Success     The message was successfully retrieved from the receive queue.
    2004-10-25 19:47:32     Success     The message status set to DLNG.
    2004-10-25 19:47:32     Success     Java proxy runtime (JPR) accepted the message
    2004-10-25 19:47:34     Error     JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
    2004-10-25 19:47:34     Error     Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
    2004-10-25 19:47:34     Error     The message status set to FAIL.
    2004-10-25 19:47:34     Error     Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
    2004-10-25 19:47:34     Error     Asynchronous error reported.
    Message was edited by: Nicholas Simon

    Hi
    How do you determine the JNDI naming of the a EJB?
    I have following entry in JNDI directory in the root
    Object Name FlightQueryIn
    Class Name javax.naming.Reference
    Context Name 
    Object Value Reference Class Name:
    Type: clientAppName
    Content: sap.com/JavaProxyEAR
    Type: interfaceType
    Content: remote
    Type: home
    Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
    Type: ejb-link
    Content: FlightSeatAvailabilityQueryIn_PortTypeBean
    Type: jndi-name
    Content: FlightQueryIn
    Type: remote
    Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
    I tried to register the bean with JPR using:
    http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
    I followed the following blog
    http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
    Thanks,
    Chris

  • Portal runtime error while trying to run a MSS report

    Hello gurus!!
       I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
    The trace file shows the following errors:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[17, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.16.trc]/>
    <!NEXTFILE[defaultTrace.18.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
    [EXCEPTION]
    #1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
         at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         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.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:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
         at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 64 more
    Could anybody please guide me how to fix this error and get the reports working properly?
    Any help with this is much appreciated.
    Thank you!
    ~Maria Kutty~

    Hi,
    Please refer to note 878440.
    Thanks
    Prashant

  • Runtime Workbench Proxy Runtime Configuration

    Hi
    I'm trying to setup the RWB proxy runtime configuration. However our ERP system shows up as an ALE-Logical system and not a Business System in the Configuration tab of the RWB and doesnt appear at all in the Component Monitoring tab so we cant monitor messages from it through the RWB.
    We've tried deleting the business and technical system and re-registering them with RZ70 as well doing a CPA Cache refresh. But that hasnt resolved the issue.
    I have compared this system to another system in the SLD which does show up as a Business System and can be monitored through Component Monitoring. They seem to be exactly the same.
    Is there some kind of setting we are missing on the ERP system?
    Thanks
    Riaz

    Hi Riaz & kesava,
    RWB Proxy runtime setup can be seen from RWB->Component Monitoring under Components section Domain XI->Integration Engine.
    Check the following
    1)Can the SLD be reached?  - RFC destination, ping, getLCR server, read cache, BS defined
    2) Does the Integration Engine know the business system?   - Business system name = BS_100, Role = Application System
    3)Are roles in SXMS_CONF_ITEMS and SLD consistent?   - Role = Application System
    4)Has an Integration Server destination been defined?   Destination 'XIabcd100' to the Integration Server 
    Cheers
    Veera

  • Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

    Hi all,
           In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump. I noticed that this error cannot be caught by CX_ROOT exception class.
           Some told me I can use the CATCH SYSTEM-EXCEPTIONS sentence to catch this runtime error, but it is a old-way syntax and cannot be used with the "try" and "catch".
           So, how can I catch this runtime error and avoid the dump of our program?
    Thanks,
    YiNing

    Hi,
    You are not checking for conversion.
    You are checking ofr logical expression.
    Try below code, it works
    DATA error_ref TYPE REF TO cx_sy_conversion_no_number.
    DATA err_text TYPE string.
    DATA a TYPE i.
    TRY.
        MOVE 'A' TO a.
      CATCH cx_sy_conversion_no_number INTO error_ref.
        err_text = error_ref->get_text( ).
        WRITE err_text.
    ENDTRY.
    Regards,
    Atish

Maybe you are looking for