| mis_gdtransportation 2005-06-29, 5:51 pm |
| Originally, I posted my problem submitting documents to a web service
through orchestration under a thread entitled "'bout ready to give up on
consuming web services", dated May 31st, 2005, but I thought it might help
someone else if I posted this seperately, so here goes:
....
FYI - I ended up having to open a call with Microsoft to solve this problem.
The "AssemblyName context property was not valid" errors I got when trying
to submit a document to a web service via an orchestration were caused by my
having first set up the project with a "messaging only" approach, meaning
there was no orchestration in place.
When this was done, I had a filter on the send port (for example:
BTS.ReceivePortName == rptWebService) which tied the receive port and the
send port so a document being picked up by the receive port would be passed
through to the send port.
This is what you're SUPPOSED to do when you have a "messaging only"
scenerio.
However, once you introduce an orchestration, the process of "binding" the
internal ports (on the port surface of the orchestration) to the ports in
BizTalk Explorer serves the same purpose...so there's no need to have a
filter on the send port.
Apparently, if you have a filter on a send port that's bound to an
orchestration, it causes problems (and/or by-passes the orchestration).
As soon as I removed the filter on the send port in BizTalk Explorer, the
"AssemblyName context property was not valid" problem went away and I was
able to submit my document to the web service via the orchestration.
And, I'm able to re-produce/correct this issue across several different
projects:
When a filter exists on the send port, an "AssemblyName context property was
not valid" error occurs.
When a filter is NOT on the send port, everything works fine.
You'd think the message would say something like, "Hey, stupid: You've bound
this port in an orchestration so you don't need to set a filter on it.", but
for whatever reason, someone at Microsoft thought "AssemblyName context
property was not valid" explained it better.
:O)
Anyways, if you're having any problems with "AssemblyName context property
was not valid", a filter on the send port might be your problem.
MUCH THANKS to Maria Quian at Microsoft for this solution!
Dan
|