** JCO$Exception Problem in RFC to RFC scenario

Hi Friends,
I am doing RFC to RFC scenario. We have two IDES system. One XI system. The scenario is to send the Vendor data from First IDES system (Z_APPLE_VENDOR_SEND) to call the RFC (Z_APPLE_VENDOR_INSERT) in the second RFC system. Sync to Sync Scenario. In this case data is passed from source system and mapped to target RFC soruce Structure. But, not able to login into target system. The following error is occured in SXMB_MONI.
com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=aprins05 SYSNR=01 GWHOST=aprins05 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '172.25.12.23:sapgw01' not reached TIME Fri Oct 17 23:28:55 2008 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2764 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER
Friends, I have tested the following : SLDCHECK, Connection between IDES and XI system. Checked the Gateway of receiver side IDES system thru tcode SMGW. All are working fine. But, still the problem comes.
Kindly help me to solve this issue.
Kind Regards,
Jegathees P.

Hi
Restart the Receiver System once and try again.
Go throgh the following thread
(102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Regards
Sridhar Goli

Similar Messages

RFC Adapter - JCO Exception - Please Urgent

I am developing a scenario from File--RFC integration. I am using File and RFC adapter to perform this transaction.
The File Adapter is picking the file properly and the trnaformation (Mapping Program) is also happening properly. But the RFC is throwing the following error. I got this error info from the Runtime Workbench.
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR
Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZPS_XI_ACTIVITY_CREATE in remote system (RfcClient[BAPI_CreateActivity_Receiver]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR.
The RFC is executing without any problem when I execute this from the transaction SE37.
I have created communication channel in Integration Directory in appropriate manner.
I also created RFC destination in the XI system (TCODE SM59) and the same is using in the "Receiver Determiiation - Service".
I have not done any configuration at SAP R/3 side. Is any config required at R/3 end for this scenario - please let me know.
Please throw some light on this. I will greatly appreciate your help.

Friends,
Please suggest on this vague problem that I am facing. Your help would be greatly appreciated.
1. I am using SAP-PS (Projects & Systems) BAPI 'BAPI_BUS2002_ACT_CREATE_MULTI' to create the activities for a project. According to this BAPI documentation,
- First call 'BAPI_PS_INITIALIZATION' before make this BAPI call
- After BAPI call, we should use 'BAPI_PS_PRECOMMIT' and 'BAPI_TRANSACTION_COMMIT'.
2. Hence, I have developed Z-Func Module with Initialize, BAPI call - then Pre Commit and Commit.
3. This is executing from SE37 without any issues. Other parameters to make a remote call is also set properly.
4. To make sure that, I made a JCO call from Java Program using PDK for Java. This is also working fine.
5. But when I used this in the XI scenario (File-XI-RFC) this is showing ABAP dump and this is invoking from Pre-Commit module.
I couldn't figure it out why it's happening like this.
I did lot of troubleshooting and the details are as follows for your reference.
1. The mapping program is working fine without any issues. I confirmed this by writing these input values to the file (ofcourse lot of pain) inside the function module. All the values have been parsed by XI and coming to Func Module as expected.
2. No issues with logical destinations (SM59).
3. I have tried other options such as clearing the Cache...etc.
Hence, please throw up some light. If any body tried with these kind of BAPI (needs initialize, pre-commit and commit) I really appreciate your effort.
Can we enable the debugging of func module when the XI makes a call...? - I tried with Standard options that seems doesn't work.

Problem with RFC adapter (JCO Exception RFC logon failure)

Hi ,
I have SOAP to RFC scenario.
Scenario with same configuration (RFC adapter) is working in QA system.but when I have transported to PRODUCTION system
it is showing
com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE:
I have gievn max conn=10 ;Refresh the cache also
and checked Roles and authorization also but still I am getting the same error.
Regards

Hi ,
I have created all the objects manually. and it is working.
now it is showing other error when I am sending the messages from SOAP side it is showing
MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping Object ID DF2C6D6E40E935CB970DEE3A71049BF9 Software Component C3D5E1D1C75311DDB94DE33C0A1E01B6 does not exist in runtime cache</SAP:Stack>
for this I checked the Interface determination step and receiver determination ,mapping program all looks correct.
I have refershed cache also both Complete and SLD.
but nothing is wroking
Please advice.
Regards

Asynchronous XI- RFC and RFC- XI scenario - strange problem

Hello XI-Xperts,
I've come to really strange problem, which I would like to share with you and possibly get an explanation.
I have an asynchronous scenario with ending XI->RFC. The RFC function in R/3 has got an optional parameter called SENDER, which when is filled, the another asynchronous RFC->XI scenario should be started. (via ABAP code CALL FUNCTION 'Z_XI_RETURN' DESTINATION gc_xi_destination ... etc.)
Now, the direction XI->RFC is configured properly, but the way back NO(!). Anyway I thought that it wouldn't make me a trouble, because those two scenarios are IMHO absolutelly separated. So I'd presume that the the data should come to R/3 without problem, it should be processed, and in case the parameter SENDER is filled the R/3 would establish the RFC connection and the "return data" should go back in different XI thread.
Well I would think like that but the situation is different:
When the parameter SENDER is empty, all goes OK and I can see in Runtime Workbench Message Monitoring - Adapter engine - Detail - Audit log only "successes". But when SENDER is filled with a value and R/3 does CALL FUNCTION with DESTINATION to a non-existing Sender agreement, the R/3 apparently doesn't send a acknowledgement to Adapter Engine of first thread XI->RFC. Intstead of that there are three messages in audit log:
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_FIDATA_INPUT in remote system (RfcClient[IS2RFC_SAP_BG]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, di: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception w

Basically I understand what is happening on the background, but I really can't go over my persuation that in case of the ASYNCHRONOUS SCENARIO this should not happen.
Or is the RFC call (I mean XI->RFC) "pseudo-synchronous" even in asynchronous scenario ? I mean that Adapter engine waits for the result of RFC everytime ... ?!
Thank you
Tomas

Hello again guys,
so I've understood it on the end. My ABAP code didn't contain EXCEPTION part of CALL FUNCTION statement.
CALL FUNCTION 'Z_XI_RETURN'
 DESTINATION gc_xi_destination
 EXPORTING
 <PARS>
 EXCEPTIONS
 communication_failure = 1
 system_failure = 2.
Without it the RFC short-dumped and AE correctly tried to call it 1+3 times. The thing, that the problem was connected to XI related topic, tricked me. Well it's smart, I must admit on the end
Reward points for interest.
THX Tomas

Scenario SAP R/3 --(RFC)-- XI--(RFC)-- JCo.Server

Hello,
I am wondering if anyone can send me some feeback for such scenario. SAP R/3 version is 4.6c, SAP XI is 3.0 and JCo are 2.0.12.
I am having some trouble which I think are link to the fact that the SAP XI is Unicode and not the JCo.Server ... However I was thinking SAP XI will adapt, since it works well for scenario SAP R/3 (RFC)> XI (RFC)> SAP R/3.
Thanks for your feeback.

Hi Grégory,
I guess I faced a similar problem, the problem was that in the receiver RFC adapter you have to specify both an RFC target system and a system to lookup the metadata.
The target RFC system hat to have the same unicodeness of the metadata lookup system that means in your case that if jco server is non unicode also you R3 has to be non unicode otherwhise it will not (never) work, because this is a mandatory requirement of the RFC adapter.
In my case this was not possible so I was redirecting the RFC call to the ABAP stack of XI (where I had exposed the same function module which was simply recalling the same function module to the target system) and it worked/works.
Regards,
Sergio

PI 7.31 (single stack) posting to RFC configuration gives this error: om.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system extern ...

Getting cryptic error while trying to post to a custom RFC from PI 7.31 single stack.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: String index out of range: 0 (raised by system <extern>|pidevhost)
Does anyone recognize this error and/or know of detailed instructions for registering custom RFCs in PI 7.31. I could possibly have configured the target wrong but no error says so.
This is a File-->PI-->RFC scenario. The file processing is super simple and a configuration I have used successfully before. I would assume I'd get a different error if it couldn't parse the file.
Jody

Not shure if you already did but try getting some details with XPI Inspector. Also increasing log level for this category might help. You also may wanna check authorization (even if this should show with a different error text) in ECC using ST01.
My guts feeling is that there is something wrong with payload / signature of RFC.
Cheers
Jens

** RFC to JDBC scenario - SYSTEM_FAILURE exception comes - urgent help

Hi Friends,
I have completed RFC to JDBC scenario. When execute RFC in the system, it throws an exception SYSTEM_FAILURE. What could be the problem ..? The message is not entered into SXMB_MONI. In the backend system itself, it throws error.
Kindly reply, friends.
Kind Regards,
Jeg P.

Hi Jeg,
Check out if u get any info/help in the thread below .. Henrique Pinto's reply and others to this thread.
How to make Real Time connectivity between R3(RFC) Sender and XI
File Adapter: SYSTEM_FAILURE_INTERNAL
More details regarding this exception:
http://help.sap.com/saphelp_nw04/helpdata/en/22/0425e0488911d189490000e829fbbd/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a2/a002416225f023e10000000a155106/frameset.htm
kanan

JCO$Exception when creating RFC model

Hi all,
I'm getting this fatal error when creating an RFC model in Web Dynpro for Java (connecting to a BW system):
com.sap.mw.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
I have absolutely no clue what's going wrong...
The RFC model gets created, but when running the application it doesn't work...
Any help appreciated!
Jeroen

Raj,
Thanks for your reply.
I had already solved the problem... After a long time I found out it was due to the language: when creating an RFC model one should use the language of SLD.
kind regards,
Jeroen

How to handle JCO Exceptions at JCO (RFC) function call

Hello Forum,
I am implementing an JCO Server scenario.
I use dynamic repositories like Example7.java from the JCO documentation.
Example7 throws an JCO.AbapException if anything went wrong, e.g. the function is not implemented.
How to react on this AbapException?
The examples in SAP Help documentation only catch
SYSTEM_FAILURE and COMMUNICATION_FAILURE.
All other RFC modules I have seen which declare the function modules to be used by dynamic JCO repositories (like Example7.java) do not define any other Exception parameters.
But these two are only thrown and caught when something with communication went completely wrong, e.g. RFC not found.
But when RFC can be reached and the JCO Server is executing the Java method, an AbapException could be thrown on error. How to react on this?
In my implementation based on the examples I always get a ABAP dump. The dump says:
Exception named without message text. Why that name?
How to handle this type of exception in order to avoid the dump?
Can anyone post an example please?
Thanks,
Carsten
Edited by: Carsten Schön on Apr 15, 2008 4:22 PM
Edited by: Carsten Schön on Apr 15, 2008 4:24 PM

Hi Micky,
thanks for your quick response.
If so, to throw JCO.AbapException on JCO Server side is not correct?
What I do is throwing the JCO.AbapException (like in the JCO Example 7).
At the RFC call in APAB I handle both exceptions SYSTEM_FAILURE and COMMUNICATION_FAILURE like
CALL FUNCTION 'MY_JCO_FUNCTION_MODULE'
 DESTINATION JCO_DEST
 <...>
 EXCEPTIONS
 SYSTEM_FAILURE = 1 MESSAGE RFC_MESS
 COMMUNICATION_FAILURE = 2 MESSAGE RFC_MESS.
This works as far something with RFC is wrong, e.g. Server can not find the function or Server not reachable.
But the AbapException thrown by the JCO Server (Java) is not handled that way. Why?
Sorry if this is the wrong forum but I tried posting in Netweaver integration and got no answer for 1 week and because it's ABAP related I thought the topic suites here.
Carsten
Edited by: Carsten Schön on Apr 15, 2008 5:10 PM

Failed to transform XML-RFC to RFC:com.sap.mw.jco.JCO$Exception: (130)

Hi All,
I am working on Rfc-SOAP scenario.
I am getting error in SAP, there is no error in SXMB_MONI, responce is successfull and correct from SOAP.
In SAP Dump is saying following
Runtime Error CALL_FUNCTION_REMOTE_ERROR
Date and Time 08/07/2007 09:14:14
"failed to transform XML-RFC to RFC:com.sap.mw.jco.JCO$Exception: (130)
Please guide
Regards

Hi Rohan !!
Check this threads:
- /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
- CALL_FUNCTION_REMOTE_ERROR
to see if you have correctly configured the RFC Sender, and the possible cause of error.
Regards,
Matias.

Jco.webas.ignore_jdsr_error=1 in the sender side RFC adapter of RFC to SOAP scenario

Hello Team,
I am doing RFC to SOAP scenario after configuring the scenario i have checked the sender side communication channel it is not throughing any errors and it shows the status as green but it is displaying a short message
it is the short log displayed while checking the sender side RFC communication channel it shows that "jco.webas.ignore_jdsr_error=1" can please any one suggest me how we can solve the issue.
Regards,
Avinash.

Hi Avinash - I don't think that is an error instead it just displays your system configuration.
your RFC adapter should work i believe..
Are you facing any issues?
(I think the parameter is nothing but the value @ nwa/java system properties/XPI Adapter:RFC -> ignoreJrfcJdsrError(true/false))

Problem Executing RFC to File Scenario

Hi,
I am currently working on RFC to File Scenario which is Asynchronous in Nature i.e. The RFC will send some data to XI and then it'll be dumped in an XML File on the shared drive.
Following are the steps which were performed by me :
1. i created an RFC Destination in R/3 using SM59 and entered the Required values as mentioned in the blog
The specified item was not found.
2. Then i entered the same values in the communication channel of the sender RFC adapter.
I tested it from R/3 and the connection was successful.
3. i created an RFC in SE37 in the R/3 and just added an existing table under the "tables" tab. No further code was written in it. I saved it and activated it.
4. All the IR and ID objects were made and activated and then the scenario was run by sending a single data row by pressing F8. The RFC showed a message of "System Failure" and while looking into the XI Server (SXMB_MONI) the message gave absurd values with a error symbol(it a Red Light symbol and there was no Red Flag).
Initially, the XML file was getting posted in the shared drive but after further execution it stopped.
I am unable to figure out the problem. Kindly let me know where i am going wrong and what needs to be done to correct it ?

Hi,
For Sending RFC asynchronously check for these points:
For RFC creation and importing please follow this discussion. Very useful:
Re: RFC to FILE
Specially reply by Udo Martens.
Also for sender RFC, check two things.
1) First step is Register your ProgramId using activiating the communication channel(XI). You should be able to see it in smgw(R/3)
smgw->Goto->Looged on Clients(Check it here)
2) Then use this registered programid in your RFC Destination,in R/3 (it is Case-Sensitive).
These are just common errors i have encountered sometimes.

RFC to SOAP Scenario -- Delivery Exception

Hi All,
I am working on RFC to SOAP scenario.
On executing a program in the SAP system, the system is throwing a dump stating "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML".
I feel that the error is because of the response not being sent back by the webservice. On executing the webservice independently, it is working fine i.e. sending back the response.
Can anyone suggest the possible reasons for this error and what needs to be done to rectify this?
Thanks,
Ravi Kiran

the return from the Web service must have been an HTML(may be an error page or something)...What kind of authorization does this WS look for ?
Pls check these threads...
SOAP Receiver Adapter Proxy Settings
Receiver SOAP Adapter Error: invalid content type for SOAP: TEXT/HTML

Problem with RFC parameters in repository(RFC to File Scenario)

Hi,
I importted RFC from R/3 to XI. When I see the parametrs in the imported object I can not see all the variable of parameters defined in R/3. Because of that I am not able to do the mapping of variable of target structure.
Can anybody help me who exactly the parametrs will be dispayed in imported and objects and how we can map sorce to target.
Thanks in advance.
Regards,
Siva

Hi siva,
go to r/3 .check ur FM.Check import and export parameters.
save and activate it properly.Reimport it in XI.
Also check here more discussion on that..
Re: ** Not able to Import RFC - RFC to RFC scenario
Regards
Biplab

Third party system (JCO) ---RFC--- PI ---RFC--- ECC

Hello all,
We are trying to implement the following scenario:
Third party system (JCO) -RFC-> PI -RFC-> SAP ECC
The third party system connect to PI via Java Connector API with a know user id in PI. After that third party system tries to obtain the RFC that is already implemented and remote enabled in SAP ECC environment. But at this step there is something wrong in third party system software because we are not able to obtain the RFC interface and metadata from PI repository.
1. This step is working correctly. Connection is OK.
            JCO.Client mConnectionPI = JCO.createClient("100", // SAP client
                                                                                "user_id", // userid
                                                                                "********", // password
                                                                                "pt", // language
                                                                                "10.x.x.x", // application server host name
                                                                                "01"); // system number
            mConnectionPI.connect();
2. This step is not working correctly:
            JCO.Repository repository = new JCO.Repository("TestRep", mConnectionPI);
            IFunctionTemplate ftemplate = repository.getFunctionTemplate("Z_RFC_XXX"); - not found exception
We would like to know if there is something missing in any environment that we have to configure or implement in order to fix this issue. Thanks a lot.

Hi Primini,
couple of stupid-but-necessary questions:
1) have you imported the RFC model in PI Repository?
You don't need to have the RFC metadata in PI ABAP stack (there is no point in doing that), but rather in the PI Repository/ESR, within the SWCV you've created.
Check the "Activities" session of this link for more details:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
2) if you have done 1), have you configured the RFC Sender scenario properly?
I mean, have you ran the configuration wizard to create the agreements & determinations, setting the RFC interface as both the sender and the receiver interface? Of course, the systems would be different: as the sender system, you'll have a Business Service representing the legacy/JCo system; as the receiver, you'll have the ERP Business System.
This should make your scenario work.
If it doesn't, try one more thing: in the JCo code, just for the metadata repository connection, use a connection to the ERP system. But for the actual call, use the PI system.
Let us know the results.
Best regards,
Henrique.

** JCO$Exception Problem in RFC to RFC scenario

Similar Messages

Maybe you are looking for