cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

DYNAMIC_CALL_FAILURE

Go to solution
Former Member

on ‎03-02-2010 10:20 AM

0 Kudos

Hi all,

We recently had upgrade from PI7 to PI7.1.

after that we are getting error as below:

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

- <!-- Response

-->

- <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>CL_BBPX_TRADING_PARTNER_SUS_IN</SAP:P2>

<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>

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

</SAP:Error>

Could not find much information in Trace as well.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Response --> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">CL_XMS_MAIN-&gt;DETERMINE_EXT_PID: CENTRAL_BACK</Trace>

<Trace level="1" type="T">Party normalization: sender </Trace>

<Trace level="1" type="T">Party normalization: receiver </Trace>

<Trace level="1" type="T">Determining the sender agreement </Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>

<Trace level="1" type="T">User = XQ1XIAPPLUSE</Trace>

<Trace level="1" type="T">Message ID = 4B89FD2B8A5D39DDE10000000A028186</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">

<Trace level="1" type="T">CL_XMS_MAIN-&gt;DETERMINE_EXT_PID: CENTRAL_BACK</Trace>

<Trace level="1" type="T">CL_XMS_MAIN-&gt;DETERMINE_INT_PID: SAP_CENTRAL_BACK</Trace>

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">

</Trace>

<Trace level="1" type="T">system-ID = BD2</Trace>

<Trace level="1" type="T">client = 020</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XQ1XIAPPLUSE</Trace>

<Trace level="1" type="Timestamp">2010-03-02T09:15:02Z EST </Trace>

<Trace level="1" type="T">ACL Check is performed </Trace>

<Trace level="1" type="T">XML validation is executed </Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace><!-- ************************************ -->

<Trace level="1" type="T">PLNAME = CENTRAL_BACK</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">

<Trace level="1" type="T">Queue name : XBTBN0__0001</Trace>

<Trace level="1" type="T">Going to persist message </Trace>

</Trace>

<Trace level="1" type="T">Generated prefixed queue name = </Trace>

<Trace level="1" type="T">Schedule message in qRFC environment </Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->

<Trace level="1" type="T">--start determination of sender interface action </Trace>

<Trace level="1" type="T">select interface Acknowledgment </Trace>

<Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/Message/30 </Trace>

<Trace level="1" type="T">--start determination of receiver interface action </Trace>

<Trace level="1" type="T">Loop 0000000001 </Trace>

<Trace level="1" type="T">select interface Acknowledgment </Trace>

<Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/Message/30 </Trace>

<Trace level="1" type="T">--no interface action for sender or receiver found </Trace>

<Trace level="1" type="T">Hence set action to DEL </Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL_BACK</Trace>

<Trace level="1" type="T">system-ID = BD2</Trace>

<Trace level="1" type="T">client = 020</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XQ1XIAPPLUSE</Trace>

<Trace level="1" type="Timestamp">2010-03-02T09:15:02Z EST </Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">

<Trace level="1" type="T">&gt;&gt;&gt;PID delete old pid determination coding </Trace>

<Trace level="1" type="B" name="PLSRV_UPDATE_ACK_STATUS">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_UPD_ACK_STATUS-ENTER_PLSRV">

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

</Trace>

<Trace level="1" type="B" name="PLSRV_INSERT_BRANCH_ACKS">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_INSERT_BRANCH_ACKS-ENTER_PLSRV">

<Trace level="1" type="T">Switching RefToMsgId due to branch: </Trace>

<Trace level="1" type="T"> old RefToMsgId was: 80144FEAD3961DEF89BB8286CFE4D986</Trace>

<Trace level="1" type="T"> new RefToMsgId is: 80144FEAD3961DEF89BB8286CFE4D986</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

</Trace>

<Trace level="1" type="B" name="PLSRV_TECHNICAL_ROUTING_BACK">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_ROUTING_BACK-ENTER_PLSRV">

<Trace level="1" type="T">routing back with the following channel </Trace>

<Trace level="1" type="T">Channel name = GeneratedReceiverChannel_IDoc</Trace>

<Trace level="1" type="T">... receiver party = </Trace>

<Trace level="1" type="T">... receiver service = ED2_200</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

</Trace>

<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">---- Outbound IDoc-Adapter -

</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">

<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>

<Trace level="1" type="T">Get Information from IS-Header Objekt </Trace>

<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint </Trace>

<Trace level="1" type="T">Sender and Receiver after Header-Mapping </Trace>

<Trace level="1" type="T">Sender service ED2_200</Trace>

<Trace level="1" type="T">Receiver service ED2_200</Trace>

<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt </Trace>

<Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-CONVERT_SEGTYP_TO_SEGDEF"></Trace><!-- ************************************ -->

<Trace level="1" type="T">Call Outbound IDoc-Adapter </Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter </Trace>

<Trace level="1" type="B" name="IDX_OUTBOUND_XMB">

<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= ED2CLNT200</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

</Trace>

</Trace>

<Trace level="1" type="T">system-ID = BD2</Trace>

<Trace level="1" type="T">client = 020</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = XQ1XIAPPLUSE</Trace>

<Trace level="1" type="Timestamp">2010-03-02T09:15:03Z EST </Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->

</SAP:Trace>

Thanks,

Srinivasa

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎03-02-2010 12:30 PM
0 Kudos

Hi,

Check these threads will help you or not...

Regds,

Pinangshuk.

Show replies
Show replies

Answers (1)

Answers (1)

former_member206760
Active Contributor
‎03-02-2010 10:26 AM
0 Kudos

chk out this blog

/people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method

Show replies
Show replies
Former Member
‎03-02-2010 10:44 AM
0 Kudos

Please read my issue clearly,It is not related to Authorization.

Thanks,

Srinivasa

former_member206760
Active Contributor
‎03-02-2010 10:56 AM
0 Kudos

debug your receiver proxy locally maybe some exception is arising in the code and it is not caught properly

Ask a Question