BizTalk Server Orchestration - 'bout ready to give up on consuming web services

Author

'bout ready to give up on consuming web services

Dan Tharp

2005-05-26, 5:54 pm

I've been "beating my head against the wall" with this one problem for the
past week and I'm at a loss for how to move forward.
I have a very simplistic process setup in BizTalk 2004 with an orchestration
that picks up an XML file from a file directory and then submits it to a web
service (basically, passing it along to the web service so it can do the
business logic).
The orchestration has an inbound port with "specify later" port binding.
(Later, in BizTalk explorer, this is set to a FILE transport type.)
The first receive shape (activate=True) picks up the file into a message
typed as System.String.
I then have a Construct Message shape which constructs a message typed to my
web service's request, which was set per the web reference.
Inside the Construct Message is a Message Assignment with an expression of:
WebServiceRequest.astrDocument = InboundDocument;
(...where WebServiceRequest is my web service request message and
astrDocument is the string parameter to be passed in and InboundDocument is
the message tied to the first Receive shape.)
Then, a Send shape sends the WebServiceRequest message out to my web service
port's Request operation.
Lastly, a second Receive shape returns a message (WebServiceResponse) which
is typed to the web service's response (set per the web reference)--an
integer return code.
The web service port is also set to "specify later" and in BizTalk Explorer
I've tried this set to SOAP and WSE with no success.

When set to SOAP, the event log messages I get are:
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5754
Date: 5/26/2005
Time: 2:34:37 PM
User: N/A
Computer: ECOMMERCE1
Description:
The "SOAP" adapter is suspending an outbound message going to destination
URL:"http://ecommerce1/WebServices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
Details:"AssemblyName context property was not valid.".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5752
Date: 5/26/2005
Time: 2:34:37 PM
User: N/A
Computer: ECOMMERCE1
Description:
The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due to
failures in message processing. Please refer to Health and Activity Tracking
tool for more detailed information on this failure.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

When set to WSE, the event log messages are:
Event Type: Error
Event Source: WSE Adapter
Event Category: None
Event ID: 0
Date: 5/26/2005
Time: 2:31:10 PM
User: N/A
Computer: ECOMMERCE1
Description:
Failed to transmit message. Exception : System.ArgumentNullException: Value
cannot be null.
Parameter name: methodname
at
Microsoft.Web.Services2.Messaging.SoapClient.SendRequestResponse(String
methodname, SoapEnvelope envelope)
at
Microsoft.BizTalk.Adapter.WseTransmitter.WseTransmitter.SendRequest(RequestObject
requestObject)
at
Microsoft.BizTalk.Adapter.WseTransmitter.WseTransmitter.ProcessMessage(RequestObject
request)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5743
Date: 5/26/2005
Time: 2:31:10 PM
User: N/A
Computer: ECOMMERCE1
Description:
The adapter failed to transmit message going to send port
"wse://http://ecommerce1/WebServices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
It will be retransmitted after the retry interval specified for this Send
Port. Details:"Value cannot be null.
Parameter name: methodname".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I would guess the problem is with the web service port within the
Orchestration(?)

Does having it set to "specify later" cause problems?

I've tried changing the authentication type, I've tried changing the proxy
from "Use handler's default..." to "Do not use" but no matter what, I can't
get this to work.
I've undeployed and recompiled and redeployed, unregistered and
re-registered into the GAC on both my development machine and the server.
And I get these same errors no matter whether my development machine's host
is running and picks it up or the server does.

Anyone got any ideas what I'm missing?

Thanks,
Dan

Dan Tharp

2005-05-26, 5:54 pm

One thing to add that I just noticed from the samples that came with Biztalk
(C:\Program Files\Microsoft BizTalk Server
2004\SDK\Samples\Orchestrations\ConsumeW
ebService):
In their example, adding the web reference created a sub-directory which
contained these files: a .MAP file, an .ODX file, a .DISCO file, a .WSDL
file, and a REFERENCE.XSD file.
My project has the same directory and it has .MAP/.ODX/.DISCO/.WSDL files,
but no REFERENCE.XSD file.

Is this reference.xsd file supposed to be created automatically when you add
a web reference to a BizTalk project?
If so, why wouldn't mine have done this?

I also caught wind of this idea in BizTalk Server 2004 Unleashed
(http://www.bookpool.com/sm/0672325985) page 290: "...locate the schema
created by the Web Reference...".

I've deleted the reference and added it back again, but still no
REFERENCE.XSD.
Is this supposed to be created or do I have to create it?

Thanks,
Dan

"Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
news:O%23nls5iYFHA.3320@TK2MSFTNGP12.phx.gbl...
> I've been "beating my head against the wall" with this one problem for the
> past week and I'm at a loss for how to move forward.
> I have a very simplistic process setup in BizTalk 2004 with an
> orchestration that picks up an XML file from a file directory and then
> submits it to a web service (basically, passing it along to the web
> service so it can do the business logic).
> The orchestration has an inbound port with "specify later" port binding.
> (Later, in BizTalk explorer, this is set to a FILE transport type.)
> The first receive shape (activate=True) picks up the file into a message
> typed as System.String.
> I then have a Construct Message shape which constructs a message typed to
> my web service's request, which was set per the web reference.
> Inside the Construct Message is a Message Assignment with an expression
> of:
> WebServiceRequest.astrDocument = InboundDocument;
> (...where WebServiceRequest is my web service request message and
> astrDocument is the string parameter to be passed in and InboundDocument
> is the message tied to the first Receive shape.)
> Then, a Send shape sends the WebServiceRequest message out to my web
> service port's Request operation.
> Lastly, a second Receive shape returns a message (WebServiceResponse)
> which is typed to the web service's response (set per the web
> reference)--an integer return code.
> The web service port is also set to "specify later" and in BizTalk
> Explorer I've tried this set to SOAP and WSE with no success.
>
> When set to SOAP, the event log messages I get are:
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5754
> Date: 5/26/2005
> Time: 2:34:37 PM
> User: N/A
> Computer: ECOMMERCE1
> Description:
> The "SOAP" adapter is suspending an outbound message going to destination
> URL:"http://ecommerce1/WebServices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
> Details:"AssemblyName context property was not valid.".
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5752
> Date: 5/26/2005
> Time: 2:34:37 PM
> User: N/A
> Computer: ECOMMERCE1
> Description:
> The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due
> to failures in message processing. Please refer to Health and Activity
> Tracking tool for more detailed information on this failure.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> When set to WSE, the event log messages are:
> Event Type: Error
> Event Source: WSE Adapter
> Event Category: None
> Event ID: 0
> Date: 5/26/2005
> Time: 2:31:10 PM
> User: N/A
> Computer: ECOMMERCE1
> Description:
> Failed to transmit message. Exception : System.ArgumentNullException:
> Value cannot be null.
> Parameter name: methodname
> at
> Microsoft.Web.Services2.Messaging.SoapClient.SendRequestResponse(String
> methodname, SoapEnvelope envelope)
> at
> Microsoft.BizTalk.Adapter.WseTransmitter.WseTransmitter.SendRequest(RequestObject
> requestObject)
> at
> Microsoft.BizTalk.Adapter.WseTransmitter.WseTransmitter.ProcessMessage(RequestObject
> request)
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type: Warning
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5743
> Date: 5/26/2005
> Time: 2:31:10 PM
> User: N/A
> Computer: ECOMMERCE1
> Description:
> The adapter failed to transmit message going to send port
> "wse://http://ecommerce1/WebServices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
> It will be retransmitted after the retry interval specified for this Send
> Port. Details:"Value cannot be null.
> Parameter name: methodname".
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> I would guess the problem is with the web service port within the
> Orchestration(?)
>
> Does having it set to "specify later" cause problems?
>
> I've tried changing the authentication type, I've tried changing the proxy
> from "Use handler's default..." to "Do not use" but no matter what, I
> can't get this to work.
> I've undeployed and recompiled and redeployed, unregistered and
> re-registered into the GAC on both my development machine and the server.
> And I get these same errors no matter whether my development machine's
> host is running and picks it up or the server does.
>
> Anyone got any ideas what I'm missing?
>
> Thanks,
> Dan
>
>
>
>
>
>
>
>
>
>
>

Matt Milner

2005-05-27, 2:47 am

It is created if you have complex types in your web service, which you do
not. So it is not a problem that it is not there.

I assume that you are using the web port created when you added the web
reference, correct? I'd try leaving it as specify now with the address
included in the dialog and making sure to use the passthrough pipeline on
the send and receive side.

Matt

"Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
news:%23ZgO4GjYFHA.4036@tk2msftngp13.phx.gbl...
> One thing to add that I just noticed from the samples that came with
> Biztalk (C:\Program Files\Microsoft BizTalk Server
> 2004\SDK\Samples\Orchestrations\ConsumeW
ebService):
> In their example, adding the web reference created a sub-directory which
> contained these files: a .MAP file, an .ODX file, a .DISCO file, a .WSDL
> file, and a REFERENCE.XSD file.
> My project has the same directory and it has .MAP/.ODX/.DISCO/.WSDL files,
> but no REFERENCE.XSD file.
>
> Is this reference.xsd file supposed to be created automatically when you
> add a web reference to a BizTalk project?
> If so, why wouldn't mine have done this?
>
> I also caught wind of this idea in BizTalk Server 2004 Unleashed
> (http://www.bookpool.com/sm/0672325985) page 290: "...locate the schema
> created by the Web Reference...".
>
> I've deleted the reference and added it back again, but still no
> REFERENCE.XSD.
> Is this supposed to be created or do I have to create it?
>
> Thanks,
> Dan
>
> "Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
> news:O%23nls5iYFHA.3320@TK2MSFTNGP12.phx.gbl...
>
>

Dan Tharp

2005-05-27, 5:50 pm

Matt,
Thanks for the info....so the missing Reference.xsd doesn't seem to be the
problem.
I changed the orchestration port to "specify now" and, when reconfiguring
the port, the URI, transport, and receive/send pipeline items were greyed
out (since they were pulled in from the reference created port type). The
send/receive pipelines were both default pipeline passthrough.
But I still get the following errors regardless if the processes are run on
my (development) machine or the server, regardless if the web service being
called is localhost or remote:

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5754
Date: 5/27/2005
Time: 7:57:35 AM
User: N/A
Computer: ECOMMERCE1
Description:
The "SOAP" adapter is suspending an outbound message going to destination
URL:"http://ecommerce1/webservices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
Details:"AssemblyName context property was not valid.".
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5752
Date: 5/27/2005
Time: 7:57:35 AM
User: N/A
Computer: ECOMMERCE1
Description:
The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due to
failures in message processing. Please refer to Health and Activity Tracking
tool for more detailed information on this failure.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Got any ideas on this "AssemblyName context property was not valid" issue?
Most things I've seen on this error are other people asking the same
question, but I haven't found any solutions.

Thanks!
Dan

"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:eByGHmmYFHA.3840@tk2msftngp13.phx.gbl...
> It is created if you have complex types in your web service, which you do
> not. So it is not a problem that it is not there.
>
> I assume that you are using the web port created when you added the web
> reference, correct? I'd try leaving it as specify now with the address
> included in the dialog and making sure to use the passthrough pipeline on
> the send and receive side.
>
> Matt
>
>
> "Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
> news:%23ZgO4GjYFHA.4036@tk2msftngp13.phx.gbl...
>
>

Phua Chiu Kiang

2005-05-31, 7:47 am

Dan,

The "AssemblyName context property was not valid" error message you get when
calling a SOAP send port is usually caused by a lack of some properties in
the SOAP request message, in your case it's probably the method (operation)
name. Make sure that you are using the New Configured Port Type and choose
the correct Web Port Type when you create your send port in the
orchestration. Do not create a new Port Type by yourself, as it will not
include the method information.

Regards,
ck.
http://www.pckconsulting.com

"Dan Tharp" wrote:
> Matt,
> Thanks for the info....so the missing Reference.xsd doesn't seem to be the
> problem.
> I changed the orchestration port to "specify now" and, when reconfiguring
> the port, the URI, transport, and receive/send pipeline items were greyed
> out (since they were pulled in from the reference created port type). The
> send/receive pipelines were both default pipeline passthrough.
> But I still get the following errors regardless if the processes are run on
> my (development) machine or the server, regardless if the web service being
> called is localhost or remote:
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5754
> Date: 5/27/2005
> Time: 7:57:35 AM
> User: N/A
> Computer: ECOMMERCE1
> Description:
> The "SOAP" adapter is suspending an outbound message going to destination
> URL:"http://ecommerce1/webservices/wsCDOWarehousePricingImport/wsCDOWarehousePricingImport.asmx".
> Details:"AssemblyName context property was not valid.".
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5752
> Date: 5/27/2005
> Time: 7:57:35 AM
> User: N/A
> Computer: ECOMMERCE1
> Description:
> The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due to
> failures in message processing. Please refer to Health and Activity Tracking
> tool for more detailed information on this failure.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Got any ideas on this "AssemblyName context property was not valid" issue?
> Most things I've seen on this error are other people asking the same
> question, but I haven't found any solutions.
>
> Thanks!
> Dan
>
>
> "Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
> news:eByGHmmYFHA.3840@tk2msftngp13.phx.gbl...
>
>
>

mis_gdtransportation

2005-06-29, 5:51 pm

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

"Phua Chiu Kiang" <ckphua@pc.jaring.my.(donotspam)> wrote in message
news:A60ECACE-C046-4C02-9BCE-67BDA7385F77@microsoft.com...[vbcol=seagreen]
> Dan,
>
> The "AssemblyName context property was not valid" error message you get
> when
> calling a SOAP send port is usually caused by a lack of some properties in
> the SOAP request message, in your case it's probably the method
> (operation)
> name. Make sure that you are using the New Configured Port Type and
> choose
> the correct Web Port Type when you create your send port in the
> orchestration. Do not create a new Port Type by yourself, as it will not
> include the method information.
>
> Regards,
> ck.
> http://www.pckconsulting.com
>
> "Dan Tharp" wrote: