I wrote a mock-up web service which takes a string and return a string. It
all went well while calling in .NET client code, the result returned
successfully as a string. But when I pointing the orchestration to it,
BizTalk always complains as below

"
Uncaught exception terminated service
ISL.BizTalk.Orchestrations.Tx301.ProducerSearch(11967595-abda-30f2-757c-a2af
81ca4317), instance 9991cb84-cf0a-456c-9b07-d527ce306022

The XLANG/s message has no part at index '0'.  The total number of parts
found in the message is '0'. If you expect a multipart message, check that
the pipeline supports multipart messages such as MIME.

Exception type: MissingPartException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void ReadMessageState(Microsoft.XLANGs.Core.Envelope,
Microsoft.XLANGs.BaseTypes.XLANGMessage)
Help Link:
Additional error information:
"

[ Post a follow-up to this message ]

Since you are passing a string back make sure you are not using the Xml
Pipeline – that might cause a problem but I wouldn’t think you’d get t
hat
error.  I think Xml is the default when setting up web ports.

Just a thought.

Stephen W. Thomas
http://www.biztalkgurus.com
http://geekswithblogs.net/sthomas/

"Tommy" wrote:

> I wrote a mock-up web service which takes a string and return a string. It
> all went well while calling in .NET client code, the result returned
> successfully as a string. But when I pointing the orchestration to it,
> BizTalk always complains as below
>
> "
> Uncaught exception terminated service
> ISL.BizTalk.Orchestrations.Tx301.ProducerSearch(11967595-abda-30f2-757c-a2
af81ca4317), instance 9991cb84-cf0a-456c-9b07-d527ce306022
>
> The XLANG/s message has no part at index '0'.  The total number of parts
> found in the message is '0'. If you expect a multipart message, check that
> the pipeline supports multipart messages such as MIME.
>
> Exception type: MissingPartException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Void ReadMessageState(Microsoft.XLANGs.Core.Envelope,
> Microsoft.XLANGs.BaseTypes.XLANGMessage)
> Help Link:
> Additional error information:
> "

[ Post a follow-up to this message ]