Failed to determine a receiver agreement for the given message at runtime.

[Former Member]

Hi,

I'm trying to run a HTTP to RFC Scenario. Previously this Interface was running but after we made some changes to the XI System the Interface is giving the followong error

<!-- Call Adapter

-->

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

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=***********;TS=DEV;AN=***********;ANS=http://*****;</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

</SAP:Error>

We made a full refresh of the CPA Cache, and checked access to SLD using 'sldcheck'. Additionally we also reconfigured the Integration scenarios and activated it, to be doubly sure.

We also detected that all Interfaces other than the ones using proxy adapter are also giving the same error.

Could anyone please provide any help on this problem?

Thanks in advance,

Avishek

[Former Member]

Please refrain fromchanging passwords of Service users without knowing their dependency.

[Former Member]

Cool:)

Thanks for your nice input that is visible to all.

Thanks

Farooq.

[Former Member]

Just refresh the Adapter Engine cache...or better to restart the J2EE Engine it will sove this problem.

Thanks

Farooq.

[Former Member]

Hi Farooq,

We did a CPA Cache refresh as well as server restart, didnt solve the problem. Can there be any user authorization problem while acessing the Directory from the Adapter Engine? We inadvartantly changed the pwd of XIAPPLUSER but restored the old one later can that create any problems?

Regards,

Avishek.

[Former Member]

The problem was solved by restoring the XIAPPLUSER password, and refreshing the Runtime and AE Caches.

Tahnks for your help.