Error in proxy runtime

Hi,
I am using a ABAP Proxy to push the data into the BW system. In the RWB, the following listed is RED in colour.
Are roles in SXMS_CONF_ITEMS and SLD consistent?
pls can anyone help in solving this.
Thnkz n regards,
Anup

Hi Manish,
Thanks for your response. I did re-generated it and activated it .. initially after seeing that its inactive and everything looked fine..
The interesting part is I am able to see the output properly in the Response tab but the same isn't sent to PI ..
Pls advice
Regards
RK

Similar Messages

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)

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

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 -

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

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

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 cant 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

Powershell Error for SharePoint Online -"The remote server returned an error: (407) Proxy Authentication Required."

I am trying to call sharepoint online from powershell. Below is the code. I get
Exception calling "ExecuteQuery" with "0" argument(s): "The remote server returned an error: (407) Proxy Authentication Required."
$loadInfo1 = [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client")
$loadInfo2 = [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.Runtime")
$webUrl = "ZZZZ"
$username = "XXX"
$password = "YYYY"
$ctx = New-Object Microsoft.SharePoint.Client.ClientContext($webUrl)
$ctx.Credentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $password)
$web = $ctx.Web
$lists = $web.Lists
$ctx.Load($lists)
$ctx.ExecuteQuery()
$lists| select -Property Title
Raj-Shpt

Hi,
About how to access SharePoint online site using PowerShell, the blog below would be helpful:
http://social.technet.microsoft.com/wiki/contents/articles/29518.csom-sharepoint-powershell-reference-and-example-codes.aspx
Another two demos for your reference:
http://www.hartsteve.com/2013/06/sharepoint-online-powershell/
http://www.sharepointnutsandbolts.com/2013/12/Using-CSOM-in-PowerShell-scripts-with-Office365.html
Thanks
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

ABAP Proxy runtime is showing status as red

We have ABAP Proxy runtime for four different ABAP systems. Except one all the other three proxies are showing the status as red. Could you please help me with this regard - Points guaranteed

Hey,
Go to SM59 -
> R/3 connection to ABAP Systems -
> INTEGRATION_DIRECTORY_HMI
Now press the Connect Test button, and chek it every thing is ok. You should not get any error!!.
If above one is ok in all three systems, then second option is
Go to tcode SICF -
> default_host --->sap -
>xi check if all the services are active (if active, will be in pure black color), if not active then activate them, may be you will require authorizations for this work.
Try the above solution and it will work.
Regards,
Sarvesh
****Reward points if it helped you.

Base64 in Proxy Runtime

Hi gurus,
I'm planning to use Base64 for sending/receiving binary data to R/3. I generated a proxy for a receiver interface which has a field of type Base64 and it is generated as RAWSTRING.
When I send a test XML through a web service (for my SOAP-PI-Proxy scenario) which has a correct Base64 data in the relative field, the proxy runtime in R/3 throws "Error in Control Framework" in SMQ2, even before the message reaches the proxy code.
How does the proxy runtime handle Base64? Does it actually convert it to RAWSTRING or I should use different xsd types for inbound interfaces(such as hexString maybe?). If yes, how to convert?
And what about sending? Is it possible to send Base64 from client proxies?
Regards,
Gökhan

what is the Type that you have defined in DT of XI/PI....it should be xsd:base64Binary.......then you can build your proxy accordingly to accept the base64 message...check it out...
Regards,
Abhishek.

Runtime Workbench - Proxy Runtime

In the Runtime Workbench, I got an error status in the component "Proxy Runtime".
Result of Self-Test:
    Can the SLD be reached?   (successful)
    Does the Integration Engine know the business system? (error)
    Are roles in SXMS_CONF_ITEMS and SLD consistent? (error)
Details:
    Tested: RFC destination, ping, getLCR server, read cache, BS defined
    Function LCR_GET_OWN_BUSINESS_SYSTEM failed (return code = 1)
    No role for business system defined in System Landscape
Can anyone tell me how to solve this problem?

Hi,
This basically means that your back end system where you generate your proxy, was NOT registered in SLD properly.
Proceed as follows in SLD:
1. If your system has not been registered as a technical system, you will have to register it using transaction RZ70 (Prior to that, you also need to make sure the RFC destination SLD_UC has been properly configured to point to your SLD program registered in PI gateway )
2. Create your business system referring to the technical system above, pointing to the client where you want to generate your proxy.
Hope it helps,
Lim...

DYNAMIC_CALL_FAILURE - Error in Proxy Inbound

Dear Experts,
this is my Scenario...
Legacy System SAP ECC
============ =======
Web Service synchronous -
> Proxy synchronous.
sometimes I have this error (NOT Always): in SAP PI:
"Error during proxy processing Message E MC 601 cannot be processed in plugin mode HTTP"...
MC 601 = mc(601) -> "Object requested is currently locked by user &"..........
the same error in the Runtimer Workbench:
Error Category : ABAP
Error Code : DYNAMIC_CALL_FAILURE
Message Type : S
User : PIAFUSER
this error occurs sometimes... not always..
when I get this error, resend the message and it WORKS fine...
I can't recreate the error, I don't know the cause of this.. and less how to repair.
Thanks in advance.
Regards.

I have checked the ST22, and there is nothing....
executed the web service with the SOAPUI... and this is the error...
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>RecoverableException</code>
 <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:DYNAMIC_CALL_FAILURE:
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:456)
 at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
 </s:SystemError>
may br it could help..
thanks.

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

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

Error authenticating proxy while running agent job

I am trying to schedule a SSIS2014 package via SQL Server Agent job. Both SSIS and SSMS are running on my local machine in the same domain. I am running SSMS with the same user
Domain\Admin which is the creator of the SSIS package. SSMS 32-Bit and SSIS 32-Bit are running on Windows 7 64-Bit machine. I can run the package within SSIS without problems.
When I use a proxy account to run the job step, the following message occurs:
Unable to start execution of step 1 (reason: Error authenticating proxy `Domain\Admin`, system error: Logon failure: unknown user name or bad password.). The step failed.
The proxy account uses the credentials identity Domain\Admin. Since the password fields for credential properties in SSMS cannot be left blank, I typed any password although my corresponding windows account has no password. So as mentioned above
it's the same user account that created the SSIS package since Domain\Admin is stated in the CreatorName property of the SSIS package.
With this proxy, I tried to run SSIS jobs using the package ProtectionLevel's
EncryptSensitiveWithUserKey and EncryptSensitiveWithPassword. Running the package manually within SSDT without problems, but from SSMS agent job the same error message appears. I tried the package sources "File System" and, after
importing the package to MSDB, "SQL Server" and "SSIS Package Store". But exactly the same error message appears with each method.
Task manager shows that SSMS is running in administrator mode. Using Windows Component Services I added DCOM permissions for
Domain\Admin to start and activate "Microsoft SQL Server Integration Services 12.0" from local. But the same error message appears. So in my opinion it's a problem with SSMS user account permissions (???) but unfortunately I don't know
what exactly to do here. I tried the following:
In the system database MSDB (full path: Databases / System Databases / MSDB / Security / Logins) I assigned all available role memberships (Including db_ssisoperator, db_ssisltduser, db_ssisadmin) to
Domain\Admin.
In server security (full path: Security / Logins) I assigned all available server roles. In the tab User Mapping, I assigned the MSDB database.
Still the same error message appears when I try to run the job. Does anybody have some ideas what I can try?

If you use the Agent then set the package protection to "Rely on server".
Then Domain/Admin is probably not an actual proxy but the account the Agent is running under, in this or even any case follow http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/ to create the
proper proxy for the packages.
Arthur My Blog

Error in proxy runtime

Similar Messages

Maybe you are looking for