Error in SOAP to file scenario

Hey guys
i m doing a SOAP to File scenario and getting the following error.
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
any idea where should i look ?
thanx
ahmad

Hey
i m still getting a red flag in MONI,the error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
i checked my mapping by copyin payload from MONI,its working fine.
thanx
ahmad

Similar Messages

File to Web service (SOAP) to File scenario with out BPM in PI 7.1

Hi All,
I have scenario File to Web service (SOAP) to File scenario with out BPM.i am getting the below error:
1) Error MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
2) Error ROB: error during processing: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Processing Error
PI server is 7.1 with SP:8
I have configured the scenario like this
1) 2 File channels - Sender & Receiver ,1 RFC channel - Receiver. We need to note that, the additional Module parameters need to be added only for sender File channel
2) Created Sender Agreement
3)Created Receiver Determination
4)Created Interface Determination
5)Created Receiver Agreement
Regards,
Ramesh

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

JCO problem in SOAP to file scenario

Hey guys
i m doin a SOAP to file scenario and getting a JCO error in moni,the status of my queue in SMQ2 is SYSFAIL,when i check the TCP/IP connection in SM59 i find error in two places
AI_DIRECTORY_JCOSERVER and AI_RUNTIME_JCOSERVER .when i test connection for both of them i get the followin error "Error opening and RFC connection".
is this error dues to some server problem of something wrong in my scenario.?
the SOAP adapter in RWB is green.
i tried to unlock and delete the queue in SMQ2 but when i execute my scenario again,it gets SYSFAIL error.
thanx
ahmad

Hi,
If you restart the J2ee engine, it will work.
But The error may because of many reasons
-Might be because of lots of messages are to be processed simultaneously.
-Increasing the number of processes in VisualAdmin (VisualAdmin>JCO RFC Provider>AI_RUNTIME_<SID>) and see if that helps.
-This SAP Note may help u -709140.
Hope this helps,
Regards,
Moorthy

Soap to File Scenario with BPM

Hi Guys
I have create my Soap to File Scenario using BPM to split the file on "Transformation step" into 7 files and it must save these files to my FTP Server, when testing on sxmb_moni I don't get any errors but when checking on the FTP server no files are created, and I understand that it should be showing all seven processing on the sxmb_moni, but that is not happening.
I have used the ForEach mode on my Block.
What could I be doing wrong.
Thanks!!
Yonela

go to runtime work bench to see communication channel, especailly the receiver channel.
To see what happened on it

Business systems for Soap to file scenario

Hi Experts,
I am working on a soap to file scenario.Which type of business systems shall i create i.e Third party,As ABAP,As Java etc.Please suggest.
Thanks
Veeru

Hi,
Normally Business systems are created in SLD when you are provided with relevant system details. A business service is used in case of the system being an abstract unit.
In your case, it is better to go for Business service because you generally don't have such details for third party system.
Just go through this link for more understanding...
Difference between Business System and Business Service
Regards,
Chandra

Doubt Regarding SOAP to File Scenario

Hi All,
I am trying to create a SOAP to File scenario .These are the following things I have done so far :
IR - 2 datatypes ( 1 for soap message and 1 for file message )
       2 message types for the corresponding messages
      2 Message interfaces, both are asynchronous
      1 message mapping
      1 interface mapping
ID- 2 business systems (1 to send soap, 1 to recieve file )
    2 communiccation channel (soap sender, file receiver )
soap sender adapter parameters - Interface Name - Message interface for soap message
                                                  interface namespace - scenario namespace
Then, i generated a wsdl file to expose the outbound message interface for soap message as a web service, url for message interface : http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
After generating the wsdl file, i imported it in external definition
Could anyone plz. tell me, is this the right approach to creat this scenario ? how can I test this scenario?using altova spy ?

Hi,
The URL you have mentioned to genarate WSDL is not a valid one
http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
Check the below valid URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel.
You no need to import this to the Eexternal Definition as you already have DT,MT and MI, Any way this dosn't make any difference.
You can use SOAPGUI Tool to test:
->Create New Project -> provide WSDL you have genarated.
->Select Request and provide username and password and click the green button on top(Submit request to end URL).
Using altova spy:
Select SOAP Menu->Create New SOAP Request and provide your WSDL file and
SOAPMenu->Send Request To Server
Then you will get response..
Regards,
Prasanna

Testing of SOAP to FILE Scenario

Hi all
I have done with SOAP to FILE scenario.
--> while defining web service what we need to give in the URL????
--> How to test this SOAP to FILE scenario to see wheather it is working fine or not, what are the all options
Thanks
Dheeraj

Hi Dheeraj,
Definitely you can test it through the microsoft infopath tool.
steps to follow:
Executing wsdl File Using Microsoft Info Path
1.>Click on the design a from template
2.>Select the Web service icon and click ok
3.>Select the radio button u2018receive and submit datau2019 and click on next.
4.>Enter the path of the generated wsdl which u have saved and click next.
5.>Select the interface and click next
6.>Select the interface and click next.
7.>Double click on parameters.
8.>Double click on the parameter (which you want to send as request). Then click on the query field and click ok.
9.>Click next. And click Finish
10.>Now drag the query fields on the data fields to the left side. And click preview.
Please follow these steps I hope you will be able to test it.
Thanks and regards,
Nutan

Error in IDoc to file scenario

Hi Experts,
I am working on IDoc to File scenario.IDoc is sccessfully reached XI.In SXMB_MONI it is showing error in request mapping.Error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' No memory availab</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Please suggest me in this issue.
Thanks,
Bhuvan.

Check this link:
http://help.sap.com/saphelp_nw70/helpdata/EN/bb/ad1c3d2b058c4ce10000000a114084/
You might want to refer to the SAP NOTE: 316877
Regards,
Ravi

Error in Idoc-XI-File scenario

dear all,
i am doing one Idoc to Xi and then to a flat file scenario. i have created one BS of type 3rd party for receiver and ont BS of type Web as ABAP. Then I created one namespace and import the Idoc type there. I have not created any DT, MT, MI, MM. I have created one interface Mapping where both sender & receiver has same structure & I have selected there mapping type of ABAP-Class with one Z program name.
Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type.
Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?
Warm Rgards,
N.Jain

<i>Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type. </i>
>>
you dont need a Sender IDoc channel to be configured.
<i>Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?</i>
>>>
1. what does it say in SXMB_MONI ? Has the IDoc come into XI ?
2. In communication channel monitoring what is the error for the recv. file adapter

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

Error in HTTP to file scenario

Hey guys
we have a HTTP to file scenario in which our client has to send the Invoices over HTTP in XML format,when we test the scenario from within our landscape we are getting the output file correctly but when we test from the client site,we get an error message saying that the file has missing semi colon (,the URL which we are getting from the local HTTP client is something like this
http://scosap005.sap.com:8001/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
and the one which we are getting from the client is
http://xx.xxx.xx.xx:8001/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
why am i getting this error?
thanx
ahmad

Hey guys
i m having a very strange problem with my scenario,we are doing a HTTP to file scenario,now as both the sender and receiver have same structure i havent done any mapping,client is sending XML over HTTP from another location which is not in our landscape,he is using web methods Business connector .when he send us the XML message to our XI server some stuffs are added at the top of the payload,its something like this
namespace=urn%253ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=nov_test&sap-password=xi_test&sap-client=100&sap-language=EN&
these are actually the parameters which are used in the URL to send the XML to us.but because of this i m unable to process the XML .
so my XML looks something like this
namespace=urn%253ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=nov_test&sap-password=xi_test&sap-client=100&sap-language=EN&
<?xml version="1.0" encoding="UTF-8"?>
<Invoice transactionPurposeIndicator="Original">
     <InvoiceProperties>
          <InvoiceNumber>0094372098</InvoiceNumber>
          <InvoiceDate>20070319</InvoiceDate>
          <VendorNumber>VENDOR #</VendorNumber>
but when i try this scenario from within our landscape it works fine and nothing is added on top of XML.
they are sayin that nothin extra is being added from thr side and their XML does not have the extra addition on top.
how should i solve dis problem?
its urgent
thanx
ahmad

Error in Proxy to File scenario

Hello All,
I m doing Client Proxy, ABAP proxy to file scenario.
I hv done all the configurations in IR & ID.
I hv also created proxy in sender R3 system.
But messages are not going successfully from R3.
when i checkin SXMB_MONI of R3 i get following error
<SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
Message is in SYSFAIL status in SMQ2.
Any clues how it can be solved??
Thanks in adv.
Mahi

Hi Maheshwari,
Please try as mentioned below
Option 1: Go to SXMB_ADM->Manage Queues and Deregister all the Queues.Use transaction SMQR or SMQ2 to reset the status of queues
For this to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
MONITOR QRFC_RESTART_ALLOWED to value 1
Option 2: Check the user associated with the RFC destination AI_RUNTIME_JCOSERVER in sm59 transaction. It is generally SAPJSF. Might be posisble the user password is expired or locked. Log on to j2ee admin tool on the server side and update the password and then see if it works.
Thanks
Amit
Reward points if answer is helpful

Error on PROXY to FILE scenario

Hi,
I'm working on a Proxy to FIle Scenario. 1 Proxy is triggered and 7 files should be generated at the target side.
Now when the proxy is triggered all the 7 files doesn't get generated. Instead randomly some 3-4 files are getting generated.
Could not see the rest of the entries in MONI also.
Can someone tell how to monitor this and where exactly to check for the error, as message doesn't reach the MONI and we don't have a sender channel beacuse its Proxy.
Thanks,
Vikas

Vikas,
Can someone tell how to monitor this and where exactly to check for the error, as message doesn't reach the MONI and we don't have a sender channel beacuse its Proxy.
> how 7 files will generate ?
From Proxy level @ ECC it don't seems logical/possible as whole data will be passed as a whole to proxy interface and on some condition basis only you would be creating 7...files . so definitely at SXMB_MONI of XI you can see this .
Try to increase trace_level parameter to 3 (only in development box , as it will consume the server very fast) for better monitoring .
Since the no. of files will be created by file adapter only so those many no. of receiver file adapter calls you can see at RWB.
Regards,

CC error in RFC to File Scenario

Hi ,
While am trying to do end-to-end test for a RFC to file Scenario. Am getting this below error. Please help me to proceed further.
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '2008-08-13' too long (>8 for 2. column) - must stop', probably configuration error in file adapter (XML parser error)'
Regards,
Hemanthika

Hi,
Please go through this Blog
RFC Scenario using BPM --Starter Kit
check this blog on how to configure sender rfc adapter.
The specified item was not found.
I hope it helps,
Regards,
Surya

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Error in SOAP to file scenario

Similar Messages

Maybe you are looking for