send Message SOAP to Proxy failed - No standard agreement found for

[Former Member]

Hello to all,

we have a SOAP to Proxy scenario.

The Service Interface have 6 Operations.

When I implement 2 Operation it works fine. Now I have implemented all Operation.

When I send a request I get following Error:

I have checked the Interface determination. It is ok. I have Sender, Receiver and all Operations.

Where could be the error?

Please help us.

Thanks and regards

Martin

Edited by: Martin Weidauer on Nov 9, 2010 4:45 PM

Edited by: Martin Weidauer on Nov 9, 2010 4:47 PM

[Former Member · Accepted solution]

Martin,

Go to ID ->Tools -> test configuration. Fill up all the fields and run by clicking "test your configuration".

Here you will come to know the exact error. Also go to ID -> Environment -> cache notification...If you see any messages in red then refresh it.

I think this gonna solve your issue...

Before going to the above steps please re visit your ID components and correct if something is wrong.

Rgds

Veeru

[Former Member · Accepted solution]

Hello Veeru,

I have tested my configuration.

During the interface determination I get following error:

Error when determining the inbound interface: No interface determination found for outbound interface <NS>.GetPersonalInformations_Sync_Out: Error while determining root tag of XML: BOM / charset detection failed

What could be the error?

Thanks and regards

Martin

[Former Member · Accepted solution]

Hi Martin,

The charset of the XML cannot be determined. That is written clearly in the message.

Is your XML UTF-16 or UTF-32? Then it needs a BOM which is missing.

http://en.wikipedia.org/wiki/Byte-order_mark

Check, if there is an XML header and which charset is mentioned, if any.

[Former Member · Accepted solution]

Hi,

I have checked every Message and all start with:

<?xml version="1.0" encoding="UTF-8"?>

So I found no UTF-16 or UTF-32.

Have someone any idee?

Thanks and regards

Martin

[Former Member · Accepted solution]

Martin,

Please perform the following..

1) Please go thru this link.

2) Perform a full CPACache refresh using PIDIRUSER.

http://XiHost:Port/CPACache/refresh?mode=full

3) Kindly check Note No.'s in service market place ::

1284103, 1278244, 1278273 .

Just perform and let me know...

Regards

Veeru

[Former Member · Accepted solution]

Hello,

thanks to all who have answered.

We solved the problem. I started the Test of the configuration with a well formed xml message.

After that the interface determination processed successfully but the receiver agrreement failed.

The solution for this error was the xml namespace in the webservice defintion. I had updated it before.

xmlns before was not xmlns after the change. I corrected and it works fine.

Thanks to all again.

Regards Martin

[rodrigoalejandro_pertierr]

you are facing an error in the configuration.

check that all operation are configured properly in the Interface Determination

as i can see you miss one operation configuration in the Interface Determination.

remember tjhat each opertarion requiere the proper configuration and you do it in there.

Edited by: Rodrigo Alejandro Pertierra on Nov 9, 2010 1:59 PM

[Former Member]

Hello,

I checked the Interface Determination. All Operations are configured.

Every Operation has one Operations Mapping.

what could be the error?

Thanks and regards

Martin