Forum Replies Created
-
AuthorPosts
-
September 3, 2008 at 12:12 PM in reply to: Exception while sending message thru WCF-BasicHTTP adapter #20565
Looks like you have WCF tracing turned on the error has to do with the tracing. Do you have WCF tracing on? If so, maybe try turning it off. WCF tracing is configured using the SvcConfig tool, and needs to be configured in the BizTalk config file.
Thanks Russell
Sorry, I haven’t seen that error before, but do you really need a custom functoid? They make the install process for your solution miserable. Seriously, I have seen very few custom functoids that were useful enough to justify the extra pain and suffering of installing them. You can solve many of the same problems using a scripting functoid and an external assembly. It is not as elegant of a solution, but is much easier to install.
Did you receive any errors in the event log?
And by “not supported”, I didn’t mean “can’t configure”. I meant if you need to open a support ticket with MSFT they will make you rebuild your system on SQL 2005 before they will help you.
Yeah, you need to wait for R3. The last release date I heard was early 2009. It’s not just the BAM DB, none of the BizTalk DBs are supported on SQL 2008.
September 2, 2008 at 7:11 AM in reply to: Call a webservice with an “object” parameter from orchestration #20555I read on in an another forum thread that when BtsActionMapping is used the WCF adapter tries to match the operation name with an action defined in the BtsActionMapping, and if it can’t find the Operation context property in the BTS message, it sets the whole BtsActionMapping as the action on the outgoing WCF message.
And since no orchestrations are used the Operation context property (that comes with the default binding file) is not set.
The solution is to set the action of the send port directly to http://Microsoft.Samples.BizTalk.WCF.BasicHttpSendAdapter.BasicHttpWcfServiceConsuming/IOrderProcess/Submit
//Ershad
Hi
I experienced something similar. The message was terminated. The receive pipeline was incorrect.
September 1, 2008 at 11:46 PM in reply to: Call a webservice with an “object” parameter from orchestration #20551Hi Russell,
I’ve set up the walkthrough but I receive the following error on the call to the WS
<faultcode xmlns:a=”http://schemas.microsoft.com/ws/2005/05/addressing/none“>a:ActionNotSupported</faultcode><faultstring xml:lang=”sv-SE“>The message with Action ‘<BtsActionMapping xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”> <Operation Name=”Submit” Action=”http://Microsoft.Samples.BizTalk.WCF.BasicHttpSendAdapter.BasicHttpWcfServiceConsuming/IOrderProcess/Submit” /> </BtsActionMapping>’ cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).</faultstring></s:Fault>My Soap action header in the send port is set to this
<BtsActionMapping xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema“>
<Operation Name=”Submit” Action=”http://Microsoft.Samples.BizTalk.WCF.BasicHttpSendAdapter.BasicHttpWcfServiceConsuming/IOrderProcess/Submit” />
</BtsActionMapping>Any ideas on hos I can troubleshoot this?
//Ershad
You need to retrieve the ReceivedFileName context property from the incoming message. The code would be something like this:
fileName = IncomingMessage(FILE.ReceivedFileName);
Then just add the file name into the XML you need to send to the queue.
I can’t configure it at the send port, but I can configure it in the Adapter handler properties (which is applied to all adapters because it is a handler property).
September 1, 2008 at 12:05 AM in reply to: Call a webservice with an “object” parameter from orchestration #20548Hi Russell,
I’m still working on this issue. My primarily intention is to get WCF to work. If not I’ll somehow will work for trying to change the Webservice interface. Anyway I’ll return with an update!
// Ershad
I did restart the host instance but not the admin console and Visual Studio. It is good to know that this might be needed.
Hmmmm, not sure about that one. It’s hard to predict what will happen when you muck around in the DB. Can you configure the adater batch size on the send port properties?
-
AuthorPosts