neilm_3.21

Hi,

I've just started working with the BizTalk Server 2006 R2 trial recently, and seem to be having a little problem. Embarrassingly enough, I'm stuck on the first tutorial. After working through it I tried to test it out, and don't seem to be getting any output. The XML input file disappears, so I'm assuming the receive port/receive location are working correctly, but beyond that I'm not sure what could be happening. No errors have appeared in the event log. Any ideas on what could be causing this would be greatly appreciated.

Thanks,

Neil


Re: BizTalk R2 General New to BizTalk, working through tutorials.

Kent Weare

Neil,

What do you see in the BizTalk Group Hub The Group hub is found within the BizTalk Administration Console. Within your tree in the console, expand "BizTalk Server 2006 Administration" - > "BizTalk Group[ServerName]". Within the group hub page, hit refresh(F5) and you will see the various states in which your message is in. It could still be running, or suspended in a resumable or non-resumable state. Once you drill down into the message you should be able to get an idea of what happened.

The other place you can check is HAT (Health and Activity Tracking) click on "Queries" -> "Most recent 100 service instances" and you should see the various stages of your process i.e Receive, Orchestration, Send. If you right mouse click on the send/receive function and select "Message Flow" it will be able to tell you if/where the message was sent.

Kent





Re: BizTalk R2 General New to BizTalk, working through tutorials.

neilm_3.21

Thanks for the help so far, I managed to find some more information on the error:

Error Code: 0xc0c01680 (Routing Failure)

Error Description: 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.

The orchestration has been enlisted and started, so I guess that leaves the problem of message properties not being promoted. Any insight as to what this means, or how I can start to fix it





Re: BizTalk R2 General New to BizTalk, working through tutorials.

Kent Weare

On your receive location are you using Pass Thru or XML Receive Also ensure that your orchestration is configured(bound) to the receive location that you have enabled.





Re: BizTalk R2 General New to BizTalk, working through tutorials.

neilm_3.21

The receive location is using XML receive, but I tried Pass Thru after you mentioned it here and am getting the same problem. I bound the orchestration to the receive location and send ports by right-clicking the application in BizTalk Administration Console and clicking "Configure...". From this menu I just added the proper ports from the drop down menus, is this correct

Not sure if this will help, but I've been playing around with BizTalk a bit by creating a schema in Visual Studio, and a sample XML file to go with it, then simply pasing it through BizTalk by configuring a receive port/location and a send port connected through a filter. All of these tests seemed to work well, the problems arise when I use an orchestration in my BizTalk application as in the first tutorial.




Re: BizTalk R2 General New to BizTalk, working through tutorials.

willjr20

Hi,

To correct the aforementioned error ensure the the send port have a Filter defined. (subscription) The most common ones are BTS.ReceivePortName (name of the ReceivePort) or BTS.MessageType defined as namespace#<rootNodeName> (http://some.namespace#s<some_RootNodeName>)

willjr20





Re: BizTalk R2 General New to BizTalk, working through tutorials.

Kent Weare

You would want to use the XML receive. I thought you may have been using Pass Thru. In your receive shape within the orchestration, what is the message type that you are trying to receive Do you have a message type defined based upon your schema Or is it System.XML.XMLdocument If you have a schema, then make sure that your message type is the same type as your schema.




Re: BizTalk R2 General New to BizTalk, working through tutorials.

neilm_3.21

I have defined message types according to the appropriate schema for both incoming and outgoing data.




Re: BizTalk R2 General New to BizTalk, working through tutorials.

Nicolae Daian - MSFT

If the message is suspended because there is no subscription, you should check the following things:

1. Receive Location uses XML Receive pipeline

2. The orchestration is bound to this Receive Port

3. The messages you drop in the folder uses the same schema as specified in the orchestration. To get a good message: in your BizTalk project (in VS) right click on the schema and choose "Generate instance". In the VS's Output window you will find the path to the generated file.

4. The orchestration is at least Enlisted, but you should have it started.

If all of these are ok, the message should be picked up by the orchestration.