SOAP Sender Adapter

[Former Member]

i work with some sender SOAP adapter in my xi project.

After installing SP19 all Communication channell gets error when i send message:

the error (in adapter monitoring) is following :

2006-12-15 15:29:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: INBOUND_BINDING_ERROR:

2006-12-15 15:29:01 Error SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: INBOUND_BINDING_ERROR:

2006-12-15 15:29:01 Error SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: INBOUND_BINDING_ERROR:

Any suggestion?

Alessandro p.

Message was edited by:

Alessandro Pederiva

[Former Member]

Hi Team

You have to run a report from SE38 RSXMB_ACTIVATE_ICF_SERVICES

At least I had to do that to reactivate all ICF used by XI.

Then our errormessage was solved

/tobbe

PS:credit points is appreaciated

[manuel_bassani]

Hi Torbjörn,

your solution solved my problem (file adapter error after upgrading to SP19).

If you reply to my I will be glad to reward you with 10 points.

Thank you

Manuel

[Former Member]

Hi Allesandro,

I'm having the same problem with a file adapters after upgrading to SP19.

Did Morothy's suggestions fix your problem? I restarted the caches but now my message is stuck in a 'to be delivered' status.

[moorthy]

Hi,

1) Check out the XI pipeline url in the SLD>Business System><your integration server> and it should be http://<XI server>:8xxx/sap/xi/engine/?type=entry

Here port should be http port.

2) Also make sure that, all the Sender Agreement, Receiver Agreement are active.. otherwise change it and activate

3) Check put that XIISUSER is not locked ...

4) Refresh the cache- Go to XI homepage(Intgertaion Builder)>Administration>Cache Overview and refresh the all caches.. Also do the CPACache Refresh..

5) Restrating the Adapter engine from the visual admin may help u.

Hope this helps,

Regards,

Moorthy

[Former Member]

Hi Alessandro,

sound strange, but it could be, that the name of your message interface is to long (max. 60 chars)

Regards mario

[Former Member]

the message interface name's 'MI_MXSP_USER_REQ'

[Former Member]

Sorry, we had a similar error.

I hope you solve it soon!

Regards Mario