JCO_COMMUNICATION_FAILURE error in PI7.0

Hello
Till date we have been working with SAP XI 3.0 from last one year, and I have to work with PI 7.0. I creatd a sample scenarion "File to File"in PI 7.0. The sender adapter is picked the file. in SXMB_MONI Error ID showing JCO_COMMUNICATION_FAILURE. Plz suggest me how to resolve this problem.
Thanks
san

Hello San,
Your AI RUNTIME JCOSERVER and AI DIRECTORY JCOSERVER (names - not exact I think) should exist at SM59 of your ABAP stack as well as under JCORFC PRovider in Visual Admin.
Go to the Post isntall steps of XI 3 Install guide (most of the steps are relevant for PI7 also) (page 31 onwards) and you will have all the necessary details. There should be two more RFC destinations SAPSLDAPI adn LCRSAPRFC alongwith the above two.
However the other two are for communicating with SLD mainly.
Hope this helps.
Thanks,
Bhaskar

Similar Messages

401 unathorized error in PI7.1

Hi experts,
We are getting the 401 unauthorized error in PI7.1 as shown below . PLease check and assist ASAP.
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Rgds
Kishore

In Runtime workbench this is what i have observed in the Cache status overview,
The Central Adapter engine , Mapping Runtime cache( Central Adapter Engine) are showing up in red.
In the Mapping Runtime Cache the error is as follows:
Connection to system DIRECTORY using application DIRECTORY lost. Detailed information: Error accessing "http://sapqpi01:50000/dir/hmi_cache_refresh_service/int?container=any" with user "PIISUSER". Response code is 401, response message is "Unauthorized
We have accomplished delta cache refresh, complete cache refresh in SXI_CACHE.
Can you anyone suggest what needs to be done to refresh this cache in Cache status overview?
Rgds
Kishore

JCO_COMMUNICATION_FAILURE Error at message procesing

Hi all,
At a productive XI server we are having a lot of errors in message procesing.
Please take a look:
<SAP:Error xmlns:SAP=" http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustU
nderstand="">
<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>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connection
</SAP:Stack>
<SAP:Retry>A
</SAP:Retry>
</SAP:Error>
I taked a look at: JCO_COMMUNICATION_FAILURE
but i still can't find the problem.
Thanks in advance for your help,
Regards

Hi,
If you want to test your Message Mapping in the IR, then you will not get this JCO error.
You will get this error if you are doing an end to end run of your interface and the communication between the JAVA and ABAP stack is not available. If you are doing an end to end test and still facing this issue ,like mentioned, ask your BASIS team to restart the server. ( out of 10 times this error will vanish when you test your interface after the restart,.
Regards,
Bhavesh

Reciever Determination condition error in PI7.1

Hi Experts,
I done File to File scenario in XI with multiple recievers based on FileName in Reciever Determination, i use context object(FileName, http://sap.com/xi/XI/System/File) in Expession editor, this condition was working in XI, but in PI7.1 it is not working, it is giving error like below.
<?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="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone please help me out of this.
<removed_by_moderator>
Edited by: Juan Reyes on Oct 1, 2010 2:53 PM

Hello ,
I have the same issue with PI system and all IDOCS in PI are in error state.
The issue in our case was the condition for the interface was visible from integration directory in receiver determination , but its not replicated in ABAP stack ( tcode sxi_cache ).
so we have gone in receiver determination in Integration builder-->Receiver Determination
Select a object --> click on Edit mode
Add a space in the description , click on SAVE. Then activate it.

RFCLook up error in PI7.3

We upgraded the PI system from 7.0 to 7.3 recently and we are using RFCLookup in the interface mapping.
When I am doing the Message mapping test I am getting the below error .
Runtime exception when processing target-field mapping /ns0:mt_XXXXXXXX_XXXXX/Order/Header/DChl; root message: exception:[Java.lang.NullPointerException: while trying to invoke the method com.sap.aii.mapping.api.DynamicConfiguration.put(com.sap.aii.mapping.api.DynamicConfigurationKey, java.lang.String) of an object loaded from local variable '<12>'] in class com.sap.xi.tf._mm_XXXXXX_RFCLookUp_ method RFCLookupHDR[0000000775, BS_ERP_XXX_400, CC_Receiver_RFC_XXXXXXX, com.sap.aii.mappingtool.tf7.rt.Context@4b77308e] See error logs for details
I found 2 RFCLookups used in the interface mapping.
How to use the RFCLookup in PI7.3
Thanks
Naresh N
Edited by: Naresh Nelapatla on Feb 27, 2012 3:03 PM

Please make sure that you configure parameterised mapping in the new configuration. Go to parameter tab and see whether you set value for communication channel and so.
Refer this document which is same for PI 7.1 and 7.3
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35?QuickLink=index&overridelayout=true&38543036566484

Reg Sender IDoc error in PI7.3

Hi All,
I am facing the below error while triggering an IDoc from ECC to PI. I could see the error in SM58 and PI log as below:
[JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT, Managed_Application_Thread|XI_IDOC_DEFAULT Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@24a49d74 for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException (raised by system |PI_AAE_IDOC)
Can anyone please help me on the same.
The resource adapter configurations are deleted and created again. Also the RFC destination is working fine.
Cheers,
Neethu

Neethu,
Can you check if you are able to ping PI from the TCP Ip rfc destination in ECC.
Also the program id in the RFC destination created in SAP should match program id in InboundRA
Also the gateway parameters in the inboundRA in PI should be set properly. If you are setting the Gateway to be PI gateway then enable Local to true. If you are using SAP Gateway then set Local to false.

Getting error "JCO_COMMUNICATION_FAILURE"

hi Friends,
I am working with file to idoc & idoc to file scenario
in both the cases i am getting same error in SXMB_MONI
ERROR="JCO_COMMUNICATION_FAILURE".
solutions will be appreciated.
Regards,
RaviKiran.

try a follow up on these threads ... these have various solutions .. hope something might work out for you
JCO_COMMUNICATION_FAILURE
Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping

Idoc configurations in PI7.3

Hi Experts,
For an Idoc scenario prior to PI 7.3, RFC destination, port, logical system and partner profile needs to be created in case of outbound Idoc scenario and again at XI side we need to create RFC destination, port and loading of meta data....
Is the same is applicable for PI 7.3 as well? since Idoc resides in AAE in PI 7.3, I believe there could be some changes applicable for these settings of Idoc....
Pls provide your inputs.....

Hi,
Along with the links provided by Phani and Gayatri you can laso refer this thread for IDoc configuration in PI7.3
IDOC settings from sap r/3 to sap pi7.3
IDoc Packaging in PI7.3
http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/4096a6b3-3dc3-2d10-bf87-f63d5340a916
Configuring PI 7.30 Java IDoc Adapter
PI/XI: PI 7.3 New Java based IDOC adapter's configuration (sender, receiver) - teaser
IDoc Acknowledments in PI7.3
acknowledge handling for IDOC_AAE in sap PI 7.3
IDoc_AAE acknowledgement handling in PI 7.3
IDoc related error in PI7.3
Processing error in Idoc_AAE sender channel
Hope its informative.
Regards,
Amol

HTTP connection to ABAP Runtime failed. Error: 403 Forbidden

Hi ALL
We where testing our scenario using the Test Configuration in Integration Engine.
We have come across the following error in the second step of Determining the receiver.Here is the error message we received...
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: _http://SAPXDV01.sap.client1.local:8000/sap/xi/simulation?sap-client=150 User: PIDIRUSER
Please, do let us know ... if you have received similar error & what solution can be applied...
Your help is greatly appreciated!
Thank you,
Patrick

Hi,
Go through this thread...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0f00c890-0201-0010-beb2-c96050edc426
JCO_COMMUNICATION_FAILURE
Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping
This might help you..
Regards,
Divya

Problem to analyse mapping error

Hi all,
I have a problem to analyse a BPM mapping error on PI7.1. The szenario is as follows: I have 3 different containers (Abstract Interfaces) which data is used to determine the content of a result container.
E.g:
ABSTRACT_INTERFACE_1
ABSTRACT_INTERFACE_2 -> Mapping -> ABSTRACT_RESULT_INTERFACE
ABSTRACT_INTERFACE_3
If have quouted the source interfaces (cardinality 1 for each interface) in my operation mapping and configured the transformation step accordingly. The operation mapping alone works in the integration builder test environment. When I execute the BPM process, the mapping fails. Unfortunately the is no information in the trace leaf of the respective container information. Writing data to the mapping trace doesn't work neither.
Has got anybody an idea what might be the problem?
Kind regards,
Heiko

Hi Heiko,
Pls, do the following:
1. Build a java mapping which is going to write the payload content before the message mapping.
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationException;
import java.io.File;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
public class InputFileWriter implements StreamTransformation {
 public void setParameter(Map map) {
 public void execute(InputStream in, OutputStream out)
 throws StreamTransformationException {
 try{
 File f=new File("C:\PayloadContent.xml");
 FileOutputStream fosPayload = new FileOutputStream(f);
 byte[] content= new byte[in.available()];
 int c;
 int i=0;
 String sb = "";
 while ((c = in.read()) != -1){
 content=(byte)c;
 sb += (char)content;
 i++;
 fosPayload.write(sb.getBytes());
 fosPayload.close();
 out.write(sb.getBytes());
 out.close();
 }catch(Exception ex){
 ex.printStackTrace();
2. Add the javamapping to your interface mapping putting before of message mapping.
3. Run your scenario.
4. Check the file
C:\PayloadContent.xml
5. Test your message mapping in with PayloadContent.xml
And tell me what happened.
Regards
Ivan
Edited by: Jose Iván Reyes Arteaga on Jul 16, 2009 6:05 PM

Error opening an RFC connection

Hello guys,
I am gettinga following Error "Error when determining the receiver: Problem when determining the receiver when using the Interface Mapping: "COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection. Problem when determining the receiver when using the Interface Mapping: "COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection. "COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</"
Can someone help me out in this?
Thanks
Sahil

Check these solved discussions:
SOAP scenario
JCO_COMMUNICATION_FAILURE Error at message procesing
Regards,
Abhishek.

Error while testing SAML service in PI7.1

Hello all,
I am creating a SAML secured service in PI 7.1
I have used WS adapter in sender communication channel and reciever as RFC adapter to extract data from the system.
I have done the necessary config in sender and receiver agreement and created the wsdl manually.
Now to test that service i have created another component as the client.
The sender is the SOAP channel and in the receiver, WS adapter is used.
With these basic configurations, i have created another wsdl file which invokes my previous service.
When i tested the new wsdl i get an error.
<SAP:Code area="INTERNAL">WS_LOGICAL_PORT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while determining logical port Cannot find logical port for agreement 34CBAC01EBEC3F15813332AC002BD3CF and interface http://atl.tarpon.com/SAPGetAddressSAML_C.MI_Inbound_SAPGetAddSAML_C</SAP:Stack>
Kindly guide me as to what is to be done for creation of logical port in *NWA as this tool is available for PI7.1 for me.
Regards,
Kevin

Hi Kevin,
What I meant to say is that there are multiple levels of settings required to enable SAML based communication. I wanted to ask you if you have already done those configurations.
See the image given at following URL.
http://help.sap.com/saphelp_nwpi71/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm
As you can see there is multiple parties involved in the overall SAML authentication process.
May be following blog will be helpful.
SAML Made Simple!
Regards,
Vandana.

Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping

Hi all,
I am unable to execute even a simple scenario on my server.
The status of the message in moni is random. I get either "Scheduled for outbound processing" in,or the following error(in Request Message Mapping):
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: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 tried deleting the queueus in smq1 and smq2.It did not solve the problem.The test connection for INTEGRATION_DIRECTORY_HMI in sm59 is also working properly. But I don't see any entries for t-RFCs in sm58.
Can anyone tell me what could be the problem?
Regards,
Puloma Chaudhuri.

Hi Puloma,
1. go to TCODE: SWEL and check if you have any errors over there
2. go to TCODE: SWF_XI_CUSTOMIZING
- maintaint runtime environment
- configure RFC destination
and check if the password for user WF-BATCH is correct
Regards,
michal

Mapping Error :JCO_COMMUNICATION_FAILURE

Hi All,
Scenario: File ->XI->File
I am getting following error in Mapping (in Runtime)
<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>&quot;COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
This is a simple Message Mapping. Before this error occurs the message is going to Queue with "Running Status" But it never ends.
When I restart the Queues , it goes to SYSFAIL status with the error "XI Error JCO_COMMUNICATION_FAILURE.MAPPING: Queue"
Can anybody come accross this situation ?
Is it because of some Java components are not running ?
Thanks in advance,
Regards,
Moorthy

Hi,
>>>>Can anybody come accross this situation ?
of course:)
>>>Is it because of some Java components are not running ?
no, it's rather because of memory problems + RFC cache
but just have a look at our previous answers
(recreating RFC dest + Udo's answer)
Jco System Failure
Regards,
michal

JCO_COMMUNICATION_FAILURE - CPI-C errors

Hi,
I'm getting some errors in XI but not always, I think it's when the server is on heavy load:
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
In sm21, I see:
14:45:55 RD S23 Connection to CPI-C client 351 was closed
14:45:55 RD S74 > Partner LU name:
14:45:55 RD S0R > Host: r1n0v3
14:45:55 RD S0I > Partner TP Name: jlaunch
14:45:55 DIA 003 700 SAPJSF R49 Communication error, CPIC return code 020, SAP return code 223
14:45:55 DIA 003 700 SAPJSF R5A > Conversation ID: 28232929
14:45:55 DIA 003 700 SAPJSF R64 > CPI-C function: CMSEND(SAP)
14:45:55 RD S23 Connection to CPI-C client 080 was closed
14:45:55 RD S74 > Partner LU name:
14:45:55 RD S0R > Host: r1n0v3
14:45:55 RD S0I > Partner TP Name: LCRSAPRF
14:45:55 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 020, SAP return code 223
14:45:55 DIA 000 700 BERNIER_Y R5A > Conversation ID: 30118701
14:45:55 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMSEND(SAP)
14:46:27 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 002, SAP return code 679
14:46:27 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMINIT(SAP)
14:46:27 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 002, SAP return code 679
14:46:27 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMINIT(SAP)
14:46:35 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 002, SAP return code 679
14:46:35 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMINIT(SAP)
Any idea? How can I fix those CPI-C errors?
Rgds,
Yves

Hi Yves Bernier ,
ABAP stack and JAVA stack makes communicattion Through JRFC using JCO, for this dedicated connections are defined. When communication takes plcae this calls JCo and if that time resource is engaged with another call and it cann not be assigned to the current call then JCO FAILURE ERROR occurs
For this recomended that you shoyuld increase your maximum no of connections (SAP recomonded 300) but you may increase this according to your requirement.this may solve your problem
For CPIC error codes follow this note.
Note 63347 - List: CPIC error codes
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=63347&nlang=EN&smpsrv=https%3a%2f%2fwebsmp102%2esap-ag%2ede
regards
Sandeep
IF helpful kindly reward points

JCO_COMMUNICATION_FAILURE error in PI7.0

Similar Messages

Maybe you are looking for