BPE_ADAPTER failure with S/A Bridge BPM

[Former Member]

Hello all,

I've got really strange problem. After two days of searching I'd like to know your opinion.

I'm testing simple BPM with S/A Bridge. Inside there is only a transformation of incoming message to response message - just for testing purposes. According to the thread [|] it's possible to do this.

And now the troubles: on one installation of XI7.0 SP14 all works fine, on other two installations (SP11 and SP13) it doesn't work with same symptoms:

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

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="BPE_ADAPTER">SYSTEM_FAILURE_INTERNAL</SAP:Code>

...

<SAP:Stack>An internal error has occurred</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

and the last information from the trace is:

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

<Trace level="1" type="T">Start Sync/Async Communication</Trace>

<Trace level="1" type="Timestamp">2008-12-01T19:27:55Z CET Starting Processing</Trace>

<Trace level="1" type="T">Pipeline Timeout: 01.12.2008 20:28:55 CET</Trace>

<Trace level="3" type="T">Calling BPE Adapter</Trace>

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

<Trace level="3" type="T">Processing mode is</Trace>

<Trace level="3" type="T">set corresponding asynchron interface IF_IPSAB_DATA_ABST</Trace>

<Trace level="3" type="T">created BPE proxy for message 26E10930BFDE11DD8A62005056AD7BF9</Trace>

<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>

<Trace level="3" type="T">reset to synchron interface IF_IPSAB_SYNC_ABS http://xxx.zz</Trace>;

<Trace level="1" type="T">Destination not found:</Trace>

</Trace>

</Trace>

All was triple checked, triple generated, checked against working system, SXI_CACHE-BPMs have got sy-subrc 0 .. all seems fine.

One thing to be mentioned - there is no records in SXMB_MONI_BPE, so it seems to me that the BPM is not activated at all.

Do you have any the slightiest idea what might be wrong ?

Thank you in advance.

Best regards

Tomas

[SudhirT · Accepted solution]

Hi Tomas,

Please check the thread

this might help you.

Thanks!

[Former Member · Accepted solution]

Thanks to Sudhir,

this is exactly the thread I was looking for ... pity that SDN search engine does not return it with key word "BPE_ADAPTER SYSTEM_FAILURE_INTERNAL", which I used many times.

The problem was in WF-BATCH user and the WF customizing.

Thank you

Tom

[Former Member]

Tomas,

check whether any BPM scenario is working on that server.if all the scenarios are throwing the same error.Please check you WFBATCH user might be locked.unlock it and test it once again.

Regards

prabhakar

[Former Member]

check your receiver determination. the msg is not even reaching BPE..

[Former Member]

Hello Anand,

all is the same as on "working system". The only difference are the names and namespaces .. but I hope that at least this is not the source of the problem.

Any other ?

Thank you

Tomas

[Former Member]

Hello again,

I did some sarching and comparing in the trace log. The trace logs from "working" and "not working" system are nearly the same. There are minor exception but I count it as a different logging as from the systems with different SP level.

Now here are the parts, which tell something about the problem. First from working system:

<Trace level="3" type="T">reset to synchron interface MI_TST_IPSAB_ABS http://dummy.max</Trace>;

<Trace level="1" type="Timestamp">2008-12-02T07:11:05Z CET qRFC raised on XBQO$PE_WS90000001</Trace>

<Trace level="3" type="T"> setting SA BPE state to wait for 62B5E270C04011DDC33D001CC0781F94</Trace>

.. now from not working system

<Trace level="3" type="T">reset to synchron interface IF_IPSAB_SYNC_ABS http://xxx.zz</Trace>;

<Trace level="1" type="T"> Destination not found: </Trace>

It still seems to me, that something is not generated correctly.

Any ideas ?

Tomas