TRfc calls are errored out

[Former Member]

I am able to successfully process the XML messages from a fileadapter thru to routing and mapping. The XI monitor does not give any error messages. But since i am using asynchrounous calls, i find that the error log of the transactional RFC calls to an external R3 from XI are accumulated in SM58. I get the following error. Pls help me resolve this.

Table-ARFCSTATE

-

---

Status Text: Exception in handleRequest of server Xmb2RfcService

java.lang.Exception : <XIhostname>_<SID>_00

How can i debug the above error?

Regards,

Chandhan

[Former Member]

Hi

Finally i managed to resolve the problem. It turned out to be a mistake in the RFC adapter configuration file. I picked up the sample of the working RFC configuration posted by one of the SDN members and managed to make the asynchronous scenario work. The problem is that the error message is no way related to the actual problem and i went in the wrong direction looking for the solution. Hope other members take note of this and hope SAP will give the relevant error message in future releases (probably they have handled it already in XI 3.0).

Cheers.

[Former Member]

Hi

Inspite of all the efforts to resolve the below error, i am finding it really difficult to debug this error. I realize that this error is familiar to some of SDN members and has been resolved earlier. Pls help me resolve this error when i access the Xmb2RfcService server program (RFC Outbound adapter). The XML has been processed successfully in the integration server but encounters an error at this final step of sending to the receiver system. I dont think this is a connectivity related issue. Greatly appreciate your help.

The error message is:

Exception in handleRequest of server Xmb2RfcService: java.lang.exception: Bean n

Thanks.

[Former Member]

Chandhan,

I have the exact same error here. Please refer to my post earlier. At least it will tell you how to better isolate the problem but I have not resolved the issue yet and I have had no responses to my post. And yes someone else has had the problem and posted that they had resolved the issue, I wish they would tell us how. I do know that if you restart the RFC adapter it will work n number of times or if you change it to async you can send it transactions all day long. Maybe you will have better luck than I with getting a response. If you do figure this one out please post the resolution. We have spent several days trying to resolve this here at Bose.

Jeff V. vansky@bose.com

[Former Member]

Oh one more hing the rest of the error message is Bean not Found...

[Former Member]

Hi Jeff,

My scenario is an asynchronous outbound scenario using RFC adapter in the outbound channel. But still i am getting the Xmb2RfcService handle request error: bean n. You have mentioned that it is possible to send RFC calls in case of asynchronous scenario without any problem. Do we have to make any setting in the RFC adapter to tell it that it is asynchronous (or) the settings in the interface builder (asynchronous-outbound)during design will suffice. If we have to make any special settings in the RFC adapter for asynchronous scenario pls let me know asap. Greatly appreciate your help.

Thanks.

[Former Member]

Chandhan,

Sounds like we may have a different problem our senerio is synchronous File Adapter outbound to RFC inbound to SAP and back. Whish I could be more help.

Jeff V.