|
Home > Archive > BizTalk Server Applications Integration > January 2005 > SOAP Port does not support solicit-response ??
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SOAP Port does not support solicit-response ??
|
|
| Spaceman Spiff 2004-11-18, 7:46 am |
| I am calling an external partner's Web Service from an Orchestration using a
Dyamic SOAP Port. The Web Service is syncronous, so I have to get a message
back from it after sending the request message. This is why the Orchestration
Port is Request-Response. I succesfully "Web-Referenced" the partner's Web
Service from BizTalk project and I setted it as "dynamic" since the Web
Service URI is dynamically set during the Orchestration. The physical
"solicit-response" dynamic port is automatically created when deplying the
Orchestration. When debugging the Orchestration goes just fine until sending
the message through the SOAP port. This is when I get this odd messaage:
"Microsoft.XLANGs.Core.SendFailedException: Failed while attempting to send
message 'MessageOut'. ---> System.Runtime.InteropServices.COMException
(0xC0C01661): The Messaging Engine failed to send the message to the two-way
dynamic send port for the following URL
"http://localhost/FakeWSG4PWM/wsg.asmx". The chosen transport "SOAP" does not
support solicit-response protocol."
Is this an unbelievable contradiction?
Regards
Spaceman Spiff
| |
| Marco Ganio Vecchiolino 2004-11-19, 7:46 am |
| Sorry for my intrused posting: please, how you debug your Orchestration? I'm
trying to do it since a while... without success.
Can you tell me just a path to address proper documentation?
Thanks,
M.G.V.
"Spaceman Spiff" wrote:
> I am calling an external partner's Web Service from an Orchestration using a
> Dyamic SOAP Port. The Web Service is syncronous, so I have to get a message
> back from it after sending the request message. This is why the Orchestration
> Port is Request-Response. I succesfully "Web-Referenced" the partner's Web
> Service from BizTalk project and I setted it as "dynamic" since the Web
> Service URI is dynamically set during the Orchestration. The physical
> "solicit-response" dynamic port is automatically created when deplying the
> Orchestration. When debugging the Orchestration goes just fine until sending
> the message through the SOAP port. This is when I get this odd messaage:
>
> "Microsoft.XLANGs.Core.SendFailedException: Failed while attempting to send
> message 'MessageOut'. ---> System.Runtime.InteropServices.COMException
> (0xC0C01661): The Messaging Engine failed to send the message to the two-way
> dynamic send port for the following URL
> "http://localhost/FakeWSG4PWM/wsg.asmx". The chosen transport "SOAP" does not
> support solicit-response protocol."
>
> Is this an unbelievable contradiction?
>
> Regards
>
> Spaceman Spiff
| |
| Spaceman Spiff 2004-11-19, 7:46 am |
|
Using HAT you can select the message to debug, right-click and select
"Orchestration Debugger".
"Marco Ganio Vecchiolino" wrote:
[vbcol=seagreen]
> Sorry for my intrused posting: please, how you debug your Orchestration? I'm
> trying to do it since a while... without success.
>
> Can you tell me just a path to address proper documentation?
>
> Thanks,
> M.G.V.
>
> "Spaceman Spiff" wrote:
>
| |
| Spaceman Spiff 2004-11-21, 5:48 pm |
| I am still waiting for a Microsoft representative to reply to this issue. I
red somewhere that they should answer in no more than 48 hours...
Regards
Tom
| |
| Nkishi 2005-01-11, 5:53 pm |
| Hello Spaceman,
I don't know if you have already solved your problem, but since I ran into
the same problem and waisted enough time so solve it, here is what I figured
out.
It seems the SOAP send Handler must use the same host as your orchestration.
I had a setup similar to yours with a dynamically called webservice from an
orchestration that worked fine until I changed my hosts assignments. After
several trials, I got it to work as long as the Orchestration ran on the same
host as the SOAP Send Handler.
cheers,
N.K.
PS: It's funny how there can only be one send hanler per transport type, but
the label "Send Handlers" in the BizTalk Administration Console is plural...
"Spaceman Spiff" wrote:
> I am calling an external partner's Web Service from an Orchestration using a
> Dyamic SOAP Port. The Web Service is syncronous, so I have to get a message
> back from it after sending the request message. This is why the Orchestration
> Port is Request-Response. I succesfully "Web-Referenced" the partner's Web
> Service from BizTalk project and I setted it as "dynamic" since the Web
> Service URI is dynamically set during the Orchestration. The physical
> "solicit-response" dynamic port is automatically created when deplying the
> Orchestration. When debugging the Orchestration goes just fine until sending
> the message through the SOAP port. This is when I get this odd messaage:
>
> "Microsoft.XLANGs.Core.SendFailedException: Failed while attempting to send
> message 'MessageOut'. ---> System.Runtime.InteropServices.COMException
> (0xC0C01661): The Messaging Engine failed to send the message to the two-way
> dynamic send port for the following URL
> "http://localhost/FakeWSG4PWM/wsg.asmx". The chosen transport "SOAP" does not
> support solicit-response protocol."
>
> Is this an unbelievable contradiction?
>
> Regards
>
> Spaceman Spiff
| |
| Spaceman Spiff 2005-01-11, 8:46 pm |
| Hi Nkishi,
You are right, the SOAP send Handler must use the same host as your
orchestration.
This problem should be solved by the upcoming BTS2004 Service Pack 1 which
will be released soon.
Regards
Spaceman Spiff
"Nkishi" wrote:
[vbcol=seagreen]
> Hello Spaceman,
>
> I don't know if you have already solved your problem, but since I ran into
> the same problem and waisted enough time so solve it, here is what I figured
> out.
>
> It seems the SOAP send Handler must use the same host as your orchestration.
> I had a setup similar to yours with a dynamically called webservice from an
> orchestration that worked fine until I changed my hosts assignments. After
> several trials, I got it to work as long as the Orchestration ran on the same
> host as the SOAP Send Handler.
>
> cheers,
>
> N.K.
>
> PS: It's funny how there can only be one send hanler per transport type, but
> the label "Send Handlers" in the BizTalk Administration Console is plural...
>
> "Spaceman Spiff" wrote:
>
|
|
|
|
|