Thanks. Your response started me on the right path and I was able to resolve
 the issue. The issue was that the name of my port type was not the same as 
the name of my web service proxy. Once I selected the correct web services p
ort (the one generated by B
izTalk when you set a reference to the web services project) my issue was go
ne.

Thanks for your help.
"Allen Zhang (MSFT)" wrote:

> The AssemblyName context property contains name of the Web Proxy assembly
> for the remote SOAP service. You should double check the strong name of
> this assembly matches the context property. It is not the Biztalk assembly
> name.
>
> Hope this helps. Thank
>
> - Allen Zhang (MSFT)
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> -------------------- 
> a web service from an orchestration - " The "SOAP" adapter is suspending a
n
> outbound message going to destination AssemblyName context property was no
t
> valid.". 
> version but it doesn't say which assembly. I tried to change the version o
f
> the assembly which houses the orchestration but it didn't work. 
>
>

[ Post a follow-up to this message ]