SOAP Failed: Receiver Determination did not find any receivers at all

[markbernabe]

Hi Experts,

I'm getting this error in one of our sender SOAP channels. It's Web Service (SOAP) - PI - Proxy (SOAP) scenario using ICO. Have you come across this problem before? What should I check?

Thanks in advance.

BR Mark

[markbernabe · Accepted solution]

Hi All,

The error has been fixed. The inbound message sent from the web service to PI is incorrect (wrong message type/structure). This has been corrected and the SOAP error in the sender channel is no longer existing.

Your inputs were greatly appreciated.

BR Mark

[former_member690959]

Hi Mark.

I'm currently facing the same issue.

What exactly do you mean by "corrected message type/structure"? How does the correction work?

Did you go back to using ICO or kept the classical configuration?

Thanks in advance.

[former_member690959]

Forget it.

It was a problem with the operation name and namespace.

Thanks anyway.

[markbernabe]

Hi,

Since I couldn't progress much, I decided to switch back to classical configuration instead of ICO. Now, there's no error in the soap channel but the message being processed is totally different. But then again, if we test the service using soapUI, it's working properly and the message is processed by the channel without any issue. Do you know why we get this payload instead of the actual message structure?

Thanks

Mark

[markbernabe]

Hi All,

I've tested the service by pushing soap requests using soapUI and WSNAVIGATOR. All test requests are OK. The messages are posted and processed successfully by PI. I also didn't get the receiver determination error in the sender SOAP channel. But still, when the request is triggered from Portal, the error persists. Will it help if I delete and recreate the ICO? I would like to try this but I fear that it may just cause negative impact to the interface.Appreciate any insight or idea that you may be able to provide.

Thanks!

Mark

[Former Member]

Hello,

First of all enable message logging for your scenario. Secondly, i hope Portal system is having updated WSDL file the same which you are using in SOAP UI?

Also, can you check if the message coming from Portal system is having some junk/special characters or not?

Thanks

Amit Srivastava

[markbernabe]

Hi!

Actually this interface is not entirely new and it's running fine until we have enhanced the data type being used by the service and made some changes to the service in CAF. After that change only we started getting this error. Btw, I've already activated the ICO after applying the data type change and also provided the WSDL URL (Integrated Configuration -> Display WSDL).

Mark

[abhradeepbasu]

Hi Mark,

Try to test this from SOAP-UI first and check your new structure is showing there or not.

Check your cache status as well.

/AB

[markbernabe]

Hi AB,

I tried to test the service in SOAP UI but I got this ERROR:org.apache.http.conn.HttpHostConnectException: Connection to https://host:port refused  org.apache.http.conn.HttpHostConnectException: Connection to https://host:port refused. Any idea about this?

BR Mark

[abhradeepbasu]

Hi Mark,

Please check the AUT Tab from your SOAP UI tool

Username / Password – specifying these will use them for standard Basic Authentication (remember to set the global HTTP Preference for preemptive authentication if your server expects the credentials without an authentication challenge).

/AB

[Former Member]

Hello,

I guess you are trying to ping ur server using https endpoint URL as a result above error is coming.

In your soap UI select http (http://host:port...) endpoint URL.

Thanks

Amit Srivastava

[vishnu_pallamreddy]

Hi Mark.

Please go to transactions RZ10 and SMICM and check the HTTP Port address and remaining connection parameters and also check the SXMB_ADM transaction.

This may help you.

Thanks In Advance,

Vishnu Pallamreddy.

[naveen_chichili]

Hi Mark,

Cross check your configuration steps in Integration Directory.

Seems like you have made mistake in configuring receiver determination and receiver agreement.

Thanks and Regards,

Naveen

[MichalKrawczyk]

Hi Mark,

did you configure the scenario in PI ?

have you generate the WSDL from ICO object which you're using now to post the message ?

did you activate the flow in PI ?

Regards,

Michal Krawczyk