FTP or SOAP receiver:in sxmb_moni succeed but in RWB failed

PI version:7.1
I configed a asynchronous interface: ABAP proxy SENDER--->FTP RECEIVER, and create message.
the status of messages in sxmb_moni are all ok, but on the FTP server no file received, then check RWB, the FTP RECEIVER adapter contain error:
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error when getting an FTP connection from connection pool: com.sap.aii.af.lib.util.concurrent.ResourcePoolException: Unable to create new pooled resource: ConnectException: Socket connection timed out: 192.168.100.98:21"
then i have two questions:
1. why in sxmb_moni no error? the message can not restart because the status is successful but in fact, we should restart it again. is it possible to resolve this problem?
2. how to resolve the adapter error:Unable to create new pooled resource: ConnectException: Socket connection timed out
thank you very much

> then i have two questions:
> 1. why in sxmb_moni no error? the message can not restart because the status is successful but in fact, we should restart it again. is it possible to resolve this problem.
Add time out values in File receiver channel and are you able to access FTP server using telnet??ping your FTP server using telent.
> 2. how to resolve the adapter error:Unable to create new pooled resource: ConnectException: Socket connection timed out
>
SEARCH in SDN,many people faces similar issues,so you will find solution for the same.
Reagrds,
Raj

Similar Messages

I tried downloading Adoboe Photoshop CC and it says: Installation succeeded but a patch failed. How do I fix this?

Let me explain. I have an HP 2000 series laptop running Windows 7 Home premium with a 500gb hard drive. I currently have Adobe Photoshop CS4 on my computer but I uninstalled it first before downloading the trial of CC. I figured when my 30 day Photoshop CC trial was over I could go back and download CS4 with the CD again. I just wanted to try CC to see how different it was from CS4 and for some reason when I install it gets to 99% and when it finally reaches that 100% the error message comes up "Installation succeeded but patch failed." I have tried to hit the retry button a number of times and each time it still gives me the same error message. I tried restarting my laptop to see if this would fix the issue and it did not. What does this "patch failed" error mean and how do I fix this so I can download my adobe photshop CC trial?

Yeah for some odd reason out of no wear i am able to successfully download everything. Ill be honest i couldn't download everything properly while watching Netflix. ha Weird. But yea i just got Photoshop and flash to download fine! so thats awesome thank you for the tip i will be sure to add that next time i have a problem thank you!

Installation succeeded, but a patch failed

Unable to extract the downloaded files. Press Retry to download again. (U44M1I210)
Already did - no changes. No idea what to do. It seems Adobe makes it really hard with the iCloud to make programs work. Shouldn't it be just straight forward?!
Please help!

Hi primerl,
Please refer the knowledge base article: http://helpx.adobe.com/creative-suite/kb/error-u44m1i210-installing-updates-ccm.html.
Regards,
Romit Sinha

Error in the SOAP Receiver communication channel

Hi ,
My scenario is RFC - to -SOAP (synchronous ) i have specified the TARGET URL inthe SOAP receiver comminication chanel.. but while testing the interface by providing the test data from R/3 .. I'm not getting any Respose.. ..
If I check in the SXMB_MONI in i'm getting the following message .. but the URL whicjh i provided that is fine.. but my doubt is through XI may be it's not able to connect the Target System... .. so, please suggest me...
<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: www.webservicex.net</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
regards
Jain

By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Also have a look here
SAP Note 856597
reward points if solution found helpfull
regards
chandrakanth

SOAP Receiver Channel error

Dear PI and SOAP experts:
I have been having trouble getting a SOAP Receiver channel working for a webservice. I get the following error in the SOAP receiver channel:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: content-type of the request should be text/xml
I also forced the content-type as text/xml;charset=utf-8 from PI by using the MessageTransformBean as a module in the SOAP Receiver channel, but still getting the same response.
When I called the same w/s using XMLSpy and SOAPUI, it works fine and I get a positive response. So there is no problem with the webservice.
I also tried calling a different webservice from PI and that works fine too. So there is no problem with outbound communication with PI and the SOAP receiver channel either.
But whenever I send the request from PI to the first webservice it gives me the above error.
Thank you.
Param.

Hi Param,
Also, please do have a look at the following link which could be of help to you.
https://wiki.sdn.sap.com/wiki/display/XI/SOAPMessagesin+XI
Best Regards

No Receiver in SOAP header in sxmb_moni

Hi all
My scenario is using the HTTP sender channel.the url is like this:
http://xiserver:8000/sap/xi/adapter_plain?namespace=http%3A//my&interface=MI_Leo_HTTP_Sou_OB&service=ZBS_Leo_Http&party=&agency=&scheme=&QOS=EO&sap-user=*****&sap-password=****&sap-client=001&sap-language=EN
after i trigger the scenario, i got the message'status scheduled
and the info of SOAP Header in sxmb_moni as followed:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>7603ACFE-A4DB-5F48-8F6A-A9DFC3CB97CB</SAP:MessageId>
<SAP:TimeSent>2007-11-01T03:34:43Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>ZBS_Leo_Http</SAP:Service>
<SAP:Interface namespace="http://my">MI_Leo_HTTP_Sou_OB</SAP:Interface>
</SAP:Sender>
 <SAP:Interface namespace="http://my">MI_Leo_HTTP_Sou_OB</SAP:Interface>
</SAP:Main>
i think it's really wired, in the info, i couldn't find the receiver info, while my receiver determination is really ok.
the bold highlighted aboved should be like this:
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>*******</SAP:Service>
<SAP:Interface namespace="****">*****</SAP:Interface>
<SAP:Mapping notRequired="X" />
</SAP:Receiver>
but it's wrong.how should solve this????
and i restarted the message, it became manual restart status, it didn't work
Please help me.
Thank you in advance.

it works now

No Payload in the soap receiver call adapter ?

Hi Guys,
configured Proxy-SOAP Asynchronus process and in the sxmb_moni, i am unable to see the payload under call adapter in sxmb_moni, but i am able to see the payload under RWB in MDT. The message is checked successful in monitor.
I am not understanding why i am unable to see the payload under call adapter in sxmb_moni. I am not getting the data into my receiver system.
Do i need to mention the QOS as EO in the soap url in the soap receiver adapter configuration ?
any help would be really appreciated
Thanks,
srini

Hi,
You can only see the Payload(both with and without transformation) in MONI. message that is handling by adapter can only seen in Adapter Framework using RWB-Message Monitoring or using Communication Channel Monitoring.
Regards,
Farooq.

Rewards points if you find it usefull.

No SOAP Envelope error in SOAP Receiver Adapter

Hello Friends,
Informaiton:-
I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
Outbound and Inbound service interfaces have Request/Response and Fault messages.
Issue:-
While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 {}RESPONSES; HTTP 200 OK
I also found that Request message is not reaching to the Java Web server.
I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
please suggest.
Thanks & Regards
Jagesh

Hi,
Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
(1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
(2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
(3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
HTTP Protocols in Point 1 (Through PI).
POST HTTP/1.0
Accept: /
Host: 172.24.138.142:4544
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
CallingType: SA
content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 1195
SOAPACTION: "Action1"
HTTP Protocols in Point 2 (Through Altova).
POST / HTTP/1.1
Content-Type: text/xml
User-Agent: XML Spy
SOAPAction: "Action1"
Host: 172.24.138.142:4544
Content-Length: 1195
Connection: Keep-Alive
Cache-Control: no-cache
Thanks to Mr. Stefan Grube for writting such a nice blog.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Experts, please suggest me further.
Thansk & Regards
Jagesh

SOAP Receiver with HTTPS(without certificate)

Hi experts
Receiver system not using any certificate. Without certificate How PI can send message through HTTPS using SOAP.
How to choose HTTPS transport protocol. (Here Target Url have Https://.....)
Here I am using PI7.1 EHP1.
I configured Receiver SOAP CC as
Transport protocol as HTTP
Taget Url https://api-demo.e-xact.com/transaction
It will work? if not how to enable Https in SOAP receiver
but I am getting below error In adapter
Adapter Framework caught exception: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier
Thank you
Srini

Hi Srini,
The main reasons for this error "Peer certificate rejected..." be appearing are the following:
1. The correct server certificate could not be present in the TrustedCA keystore view of NWA. Please ensure you have done all the steps described in the URL below:
Security Configuration at Message Level
http://help.sap.com/saphelp_nwpi711/helpdata/EN/ea/c91141e109ef6fe10000000a1550b0/frameset.htm
2. The server certificate chain contains expired certificate. Check for it (that was the cause for other customers as well) and if it's the case renew it or extend the validation.
3. Some other customers have reported similar problem and mainly the problem was that the certificate chain was not in correct
order. Basically the server certificate chain should be in order Own->Intermedite->Root. To explain in detail, if your server certificate is A which is issued by an intermediate CA B and then B's certificate is issued by the C which is the root CA (having a self signed certificate).
Then your certificate chain contains 3 elements A->B->C. So you need to have the right order of certificate in the chain. If the order is B first followed by A followed by C, then the IAIK library used by PI cannot verify the server as trusted. Please generate the certificate in the right order and then import this certificate in the TrustedCA keystore view and try again. Please take this third steps as the principal one.
4. If the end point of the SOAP Call(Server) is configured to accept a client certificate(mandatory), then make sure that it is configured correctly in the SOAP channel and it is also within validity period.
(This certificate is the one which is sent to Server for Client authentication)
As a resource, you may need to create a new SSL Server key.
The requirement from SAP SSL client side is that the requested site has to have certificate with CN equal to the requested site. I mean if I request URL X then the CN must be CN=X.
In other words, the CN of the certificate has to be equal to the URL in the ftp request. This can be the IP address or the full name of the host.
Request the url with the IP of the SSL Server and the certificate to be with CN = IP of the server.
In any other case the SSL communication will not work.
Regards,
Caio

SOAP receiver exception problem

Hi XI expert,
I am using scenario as following:
ABAP proxy -> xi -> soap receiver -> webservice
in sxmb_moni, the message runs ok. but in RWB, there are some error in CC monitor.
2007-07-07 11:33:54 Success SOAP: continuing to response message e305dd90-2c3a-11dc-95af-0015c5f7cd3b
2007-07-07 11:33:54 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
2007-07-07 11:33:54 Success SOAP: sending a delivery error ack ...
2007-07-07 11:33:54 Success SOAP: sent a delivery error ack
2007-07-07 11:33:54 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
2007-07-07 11:33:54 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors
2007-07-07 11:33:54 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:     Compilation Errors.
2007-07-07 11:33:54 Success The asynchronous message was successfully scheduled to be delivered at Sat Jul 07 11:38:54 CST 2007.
2007-07-07 11:33:54 Success The message status set to WAIT.
What is the problem? and how can I deal with to identify the problem?

hi
Go through this links
Check out these threads..
RFC -> XI -> External web service
How to resolve this RFC_adapter_sender to SOAP_adapter_receiver Exception?
Why getting "DeliveryExcetion" in SOAP->XI->RFC scenario?
You may refer these fallowing weblogs
/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Thanks & Regards
Sridhar.Bommireddy

SOAP Receiver Response Message

I have setup the following scenario:
Create PO in EBP --> XI --> Webservice
In the Repository I have set up both the outbound and inbound message interfaces as Synchronous. The interface mapping has been setup to map both the request and response messages.
In the Directory I have set up the SOAP receiver adapter and the receiver/interface determination and receiver agreement for EBP as the sender system and the external webservice as the receiver party/service.
When I create a purchase order in EBP the webservice is called successfully and the PO gets created on the target system. The webservice returns a response message which I am expecting to see via SXMB_MONI but is not currently showing!! Is there some Directory configuration that I am missing?
Any pointers would be appreciated.
Regards
Mark Briggs

Hi Mark,
>>>>n the Repository I have set up both the outbound and inbound message interfaces as Synchronous
is your scenario sync or async?
do the ID config with ID wizzard if you're not sure
if will guide you
if you have a sync scenario you shoudl see and error
if you have no response withint the timeout
do you see that in the calling application or in the XI ?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Issue while passing Target URL dynamically in SOAP Receiver Adapter

Experts,
I am stuck with an issue while passing the Target URL dynamically.
The UDF required for this works just fine. I can see the Target URL in Dynamic Configuration header(The Key is TServerLocation) in SXMB_MONI but the request that I am sending is not reaching the web service.
Some posts have suggested to hard code the Target URL as http://.
Below is the error that I am getting when I hard the Target URL as http://:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <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: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
 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:834)
 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>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
When I hard code the Target URL as Test (any dummy value), the error that I get is different. (Detailed error shown below)
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <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: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: no scheme
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
 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:834)
 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>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
I've referred the post [Dynamic URL for SOAP receiver adapter;.
I am on PI 7.0.
Any help in this regard is highly appreciated.
Best Regards,
Vijay

Issue resolved... by doing this:
DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TAuthKey");
conf.put (key2, "username");
In the advanced tab of the communication channel, set the flag "View Authorization keys", and then added "username" (user to access the dynamic target url) and the password (2 times).
That's it...

SOAP URL in SXMB_MONI

Hi,
We are sending MATMAS idocs to external system using SOAP adapter at receiver. The message status in SXMB_MONI is successful , but the message is not delivered. When we check the same in web based message control , we could see error message 'Connection refused'. We corrected the URL in SOAP adapter , but still the message persists in message control.
Is is possible to see this SOAP URL in SXMB_MONI ? or in some other way ?
I just want to confirm that the message is being sent to the updated and correct URL.
Regards,
Tushar

The message gets delivered successfully using soapUI , but fails when sent via XI. This error is not displayed in SXMB_MONI, but in Audit Log. I tried changing the URL again , but the error persists. I put a random URL , but still the same error. Success in SXMB_MONI , but Non delivered in audit log.
Here's the Audit log. Kindly advice.
Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
Error Exception caught by adapter framework: Connection refused: connect
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect.

Problem with SOAP receiver

Hello,
Our PI system is 7.4 . We have a lot of interface with related to proxy to soap.When they are used very intensively, errors occur in soap receiver .
Types are error:
503 server not avalibale,
401 unauthorized ,
invalid content type for SOAP:TEXT/HTML such as...
When system is restarted, mostly it is worked but after while again errors occur and a lot of message is waiting in queue.
what can we do for it?
Thanks in advance,
Nurhan

Hi Claudia,
It is dual stack installation. While calling soap receiver adapter, error occur. In sxmb_moni display error as follows:
After restart, we have new error:
It is abap proxy to soap scenario. It's synchronous communication.
Thanks,
Nurhan

Error in SOAP Receiver channel

Hi,
We are working on IDOC to SOAP Scenario (Connecting to third party).
We have configured the SOAP Receiver channel with the Target URL and teh corresponding SOAP Action.
But the SOAP Receiver channel gives the error while processing and sends back the following error message in log :
"Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Value cannot be null. Parameter name: s."
Payload seems to look fine in XI and SAP.
Any help on this ?
Thanks and regards,
Vikas

Hi Vikas,
Copy the payload from SXMB_MONI after mapping and check with SOAPGUI or Altova, if it working fine then your payload is good. You can use the WSDL to ganarate and send independent soap request from these tools.
Besides this IDOC is Asyc, you need to use RequestResponseBean and ResponseOneWayBean to get the response from SOAP. Check the following and try to simulate it.
https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without+BPM%29
Server was unable to process request. ---> Value cannot be null. Parameter name: s."
The error specifies that the request has null value, check the parameter specified in the error message and make sure that is not null while you are sending the request.
Regards,
Prasanna

FTP or SOAP receiver:in sxmb_moni succeed but in RWB failed

Similar Messages

Maybe you are looking for