cancel
Showing results for 
Search instead for 
Did you mean: 

Error on File Adapter - com.sap.engine.interfaces.messaging.api.exception.RetryControlException: HTTP call to IS unsupported in AEX case

AntonioSanz
Active Participant
0 Kudos

Hi all,

     I am using a File sender adapter. I can read the file, but I get this error:

08.10.2012 12:31:55.784ErrorTransmitting the message to endpoint http://pipci:50000/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: HTTP call to IS unsupported in AEX case.
08.10.2012 12:31:55.806ErrorMessage status set to NDLV

I have no idea what can be happening? Can you help me?

Thanks.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

        Are you using only the single stack (dual) or dual stack version. From the error description, seems the AEX is trying to send the message to the IS and is failing there. This call happens via HTTP when ur on the dual stack. Are the other scenarios in your landscape working?

Regards

AntonioSanz
Active Participant
0 Kudos

We are using dual stack.

Any futher suggestions??

Former Member
0 Kudos

Assuming that you are unable to see the message in sxmb_moni in the IS, can u check the connectivity between the AEX and IS.

Check the JCO RFC destinations in SM59 and also do an SLDCHECK to test the connectivity.

AntonioSanz
Active Participant
0 Kudos

Many Many thanks to all.

Finally I've found what was grong in my system. Although we did a dual stack installation, there was a missconfiguration on AEX (we dont know why, but

it was).

The property “com.sap.aii.ibrep.core.usage_type” was be set to “AEX”

(http://<server>:<port>/nwa > “Configuration” > “Infrastructure” > “Java System

Properties”

Select the service “XPI Service: AII Config Service” )

We have changed it to "" and now all is working fine.

Thanks again