Skip to Content
author's profile photo Former Member
Former Member

TRfc calls are errored out

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

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 15, 2004 at 11:43 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 16, 2004 at 08:05 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.