Error in Proxy

[Former Member]

HI All,

I am doing a FILE2Proxy interface it was wroking fine. But suddenly I am getting this error in XI MONI

*XI MONI Error*

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Call Adapter

-->

- <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="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>

<SAP:P1>500</SAP:P1>

<SAP:P2>Timeout</SAP:P2>

<SAP:P3>(See attachment HTMLError for details)</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Timeout) (See attachment HTMLError for details)</SAP:Stack>

<SAP:Retry>A</SAP:Retry>

</SAP:Error>

*R/3 Error*

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Call Inbound Proxy

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIProxy</SAP:Category>

<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>

<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>

<SAP:P2>YFICL_MI_FIITCHD001_II_REVENUE</SAP:P2>

<SAP:P3>MI_FIITCHD001_II_REVENUE_SETTL</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error during proxy processing An exception with the type CX_SY_RANGE_OUT_OF_BOUNDS occurred, but was neither handled locally, nor declared in a RAISING clause Part-field access (offset = 0, length = 1) to a data object of the size 0 exceeds valid boundaries.</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

and in R/3 it is going to DUMP...

Please suggest the solution

Thanks In advance

REgards,

Prasad.

[Former Member · Accepted solution]

Hi,

are you testing the interface in the same system were it was working fine or have you transported to another system and testing there facing this issue.......... if you are getting in another system after transportation then please check your transports are moved correctly.

thanks,

chinna

[Former Member · Accepted solution]

I am testing in the same system

[Former Member · Accepted solution]

Hi Stefen,

I put External Break Point in begining of program. The Data is not stoping the code it is going to dump.

In ST22 it is saying SYSTEM_CORE_DUMPED

[Former Member · Accepted solution]

issue with your proxy code.......check it by debugging the code.

thanks,

chinna

[stefan_grube · Accepted solution]

Have you checked the dump?

[Former Member · Accepted solution]

Hi Stefen,

This is the dump I got in R/3.

"The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.

The current ABAP program "SAPMSSY1" had to be terminated because the ABAP

processor discovered an invalid system state.

-

---

Last error logged in SAP kernel

-

---

Component............ "Taskhandler"

Place................ "SAP-Server prd3_PRD_13 on host prd3 (wp 0)"

Version.............. 1

Error code........... 11

Error text........... "ThSigHandler: signal"

Description.......... " "

System call.......... " "

Module............... "thxxhead.c"

Line................. 9806

User, transaction...

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Program............. "SAPMSSY1"

Screen.............. "SAPMSSY1 3004"

Row of screen....... 2

Information about program making the Remote Function Call (RFC):

System.............. "PRD"

Database Release.... 620

Kernel Release...... 640

Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)

Call type: "asynchron without reply (imode 0)" (S = Synchronous, a/A =

Asynchronous, T = Transaction)

Client.............. 000

User................ "DDIC"

Transaction......... " (Program: RSSTAT83)"

Function module..... "SAPWL_WORKL_PARALLEL_COLLECTOR"

Call destination.... "prd3_PRD_13"

Source server....... "prd3_PRD_13"

Source IP address... "172.22.2.17"

Additional RFC logon information:

Trusted Relation....." "

Logon return code....0

Note: Prior to Release 4.0, there was less information available on RFC

calling programs.

Information on where terminated

The termination occurred in the ABAP program "SAPMSSY1" in

"REMOTE_FUNCTION_CALL".

The main program was "SAPMSSY1 ".

The termination occurred in line 68 of the source code of the (Include)

program "SAPMSSY1"

of the source code of program "SAPMSSY1" (when calling the editor 680)."

[stefan_grube]

This is a program error of your inbound proxy ABAP code.

This is why it is an ApplicationFaultMessage.

Check the dump for details.