- This topic has 3 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
You can use the Specify Later option when configuring ports from within your orchestration.
You can then add, configure and bind whatever port you wish when you deploy the assembly.The error you are receiving indicates the adapter and pipeline have successfully received a message, but are unable to find a subscriber for that message. A subscriber is a send port or orchestration that subscribes to specific promoted properties from that message.
You need to check the subscription details of your orchestration:
[url]http://www.winterdom.com/weblog/2006/03/14/ViewingSubscriptionsInBizTalk2006.aspx[/url]And compare that against the context properties from the message that failed
-
The MessageType used in Biztalk is not a .NET type like string. It is a way of identifiying an Xml message.
The MessageType is made from the root node and target namespace of the incoming message and must match a schema deployed in Biztalk.
The MessageType is determined by one of the pipeline components like the Xml disassembler or FF disassembler.Because your message is a string it will have no MessageType.
The only way to receive untyped messages into an orchestration is to declare the message as an XmlDocument.
This applies to all untyped messages, you can receive a binary image file by declaring the MessageType as XmlDocument.-
One of my ports need to be accessing a BizTalk queue.
When I add a port in my orchestration and selec the dropdown for Transport. I only have the following options:
FILE
HTTP
SOAP
MSMQTDo you know what I need to do to have MQSeries as an option?
I am able to dummy it up w/ MSMQT, deploy the solution then change the ports from BizTalk Admin console but then it bombs after receiving the message w/
\”The Messaging engine failed to process a message submitted by adapter:MQSeries Source URL:MQS://cbtnt283/CBTNT283/QL.CBTNT.CNR.MACROCELL. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure. \”
BizTalk is picking up the message because I find the complete body of the message via HAT.
Any advice?!?!
-
[quote:198f3cabdb=\”greg.forsythe\”]You can use the Specify Later option when configuring ports from within your orchestration.
You can then add, configure and bind whatever port you wish when you deploy the assembly.The error you are receiving indicates the adapter and pipeline have successfully received a message, but are unable to find a subscriber for that message. A subscriber is a send port or orchestration that subscribes to specific promoted properties from that message.
You need to check the subscription details of your orchestration:
[url]http://www.winterdom.com/weblog/2006/03/14/ViewingSubscriptionsInBizTalk2006.aspx[/url]And compare that against the context properties from the message that failed[/quote:198f3cabdb]
Thanks Greg.
I was able to get it to \”kind of\” work by changing the message type coming in to an XMLDocument. For some reason, when I change the message type to STRING, which is what I need passed in, I get that error.
Any thing else you think I should try?
Thanks again!
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.