Incoming async abap proxy messages fail after upgrade to PI 7.31

[former_member189102]

Hi all,

We're upgrading our PI systems from 7.10 SP8 to 7.31 SP 8.

On our upgraded PI system the incoming asynchronous abap proxy messages fail, where they worked before the upgrade.

All incoming SOAP tot abap proxy messages are getting this error. (several different interfaces, so not just one scenario)

The error we're getting is : Attribute ProcessingMode has the unexpected value S; A was expected

Here is the header data and the error of the incoming message:

-

<SOAP:Header>

<SAP:Main versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

  <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

  <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

  <SAP:MessageId>8050EF27-1F8C-11E3-BA7D-000020C100BF</SAP:MessageId>

  <SAP:RefToMessageId>7A4EFF55-AACC-1EE3-87F3-3AE9C7904012</SAP:RefToMessageId>

  <SAP:TimeSent>2013-09-17T11:30:06Z</SAP:TimeSent>

<SAP:Sender>

  <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Agiv</SAP:Party>

  <SAP:Service>Gipod</SAP:Service>

  <SAP:Interface namespace="urn:infrax:pi:Gipod">SI_OA_GIPOD_Responses</SAP:Interface>

  </SAP:Sender>

<SAP:Receiver>

  <SAP:Party agency="" scheme="" />

  <SAP:Service>T01CLNT400</SAP:Service>

  <SAP:Interface namespace="urn:infrax:pi:Gipod">SI_IA_GIPOD_Responses</SAP:Interface>

  </SAP:Receiver>

  <SAP:Interface namespace="urn:infrax:pi:Gipod">SI_IA_GIPOD_Responses</SAP:Interface>

  </SAP:Main>

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

  <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>

  </SAP:ReliableMessaging>

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

  <SAP:Category>XIServer</SAP:Category>

  <SAP:Code area="INTERNAL">ATTRIBUTE_UNEXPECTED_VALUE</SAP:Code>

  <SAP:P1>ProcessingMode</SAP:P1>

  <SAP:P2>S</SAP:P2>

  <SAP:P3>A</SAP:P3>

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:Stack>Attribute ProcessingMode has the unexpected value S; A was expected</SAP:Stack>

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

  </SAP:Error>

As you can see in the header it says the ProcessingMode is Asynchronous and the QoS is ExactlyOnce.

But the error says the ProcessingMode is S !!

We are getting this for all incoming async proxy soap messages, on 2 different upgraded PI systems.

The sender adapter had QoS: Exactly Once

The interfaces have mode 'Asynchronous'.

I triple checked this to be sure.

I also did a full cache refresh, no help.

Recreated the interfaces and the adapter (with SOAP metadata 7.31), no help.

This also happens with a super simple soap to abap proxy scenario without any mapping or BPM or something.

Does anybody has any idea where this error is coming from?

It has to be upgrade related since these scenarios were untouched since the upgrade and they worked before the upgrade.

I read about notes

#1702837 'XI mapping: ProcessingMode not set for split mapping'

#1703163 'XI mapping: ProcessingMode split mapping is not set II'

But these are already included in our SPS and don't really relate to our problem since we don't even have a mapping.

Does anyone encountered something similar after an upgrade?

Any idea what we can do to solve?

Thanks for any input provided.

Benjamin

[former_member189102 · Accepted solution]

Hi all,

It seem we have found a solution for this.

In case anyone encounters the same issue, in our case it was solved by implementing these notes:

Note 1609041 - XI runtime: Synchronous acknowledgements

Note 1849533 - XI runtime: synchronous acknowledgments II

Note 1857701 - XI runtime: Synchronous acknowledgements III

[former_member218864 · Accepted solution]

Thanks for sharing the answer!

I had the same issue. We have one XI Receiver CC and works fine but only with sync calls, when we used to call an async proxy the same error rise...(Note: We have the same version and SP level as you)

It was solved with the notes you mentioned!

Thanks a lot

[iaki_vila]

Hi Benjamin,

Thanks for sharing!.

Regards.