I am new to BizTalk, have done a fair amount of research, and have been
attempting to walk through some simple development examples.  One of my
research sites, "the Bloggers Guide to BizTalk" provided such a tutorial
titled "The QuickStart Guide to Building Your First BizTalk Server 2004
Application". I built the app according to instructions but everytime I drop
a file in the "IN" directory it is picked up but not processed. I receive th
e
following error: "The Messaging Engine has suspended "1" message(s) due to
outbound processing errors. Please use Health and Activity Tracking to
determine the cause of this failure." Upon further inspection in HAT I see n
o
additional information after selecting the View Message option. What was
interesting is the HAT detail revealed no Application name and I was
expecting to see the example app BTSQuickStart referenced. I'm certain it's
probably an installation/service issue and probably not an application
problem. Any assistance or tips for debugging would be greatly appreciated.
Thank you!

[ Post a follow-up to this message ]

>I am new to BizTalk, have done a fair amount of research, and have been
> attempting to walk through some simple development examples.  One of my
> research sites, "the Bloggers Guide to BizTalk" provided such a tutorial
> titled "The QuickStart Guide to Building Your First BizTalk Server 2004
> Application". I built the app according to instructions but everytime I
> drop
> a file in the "IN" directory it is picked up but not processed. I receive
> the
> following error: "The Messaging Engine has suspended "1" message(s) due to
> outbound processing errors. Please use Health and Activity Tracking to
> determine the cause of this failure."

Chances are alongside that particular entry, you would have a second entry
with more detailed information as to what happened.


> Upon further inspection in HAT I see no
> additional information after selecting the View Message option. What was
> interesting is the HAT detail revealed no Application name and I was
> expecting to see the example app BTSQuickStart referenced. I'm certain
> it's
> probably an installation/service issue and probably not an application
> problem. Any assistance or tips for debugging would be greatly
> appreciated.

The message content is probably not useful here, but the message CONTEXT
should have the error description. Also, if an exception happened while
processing the message, using viewing the message flow (right click->
message flow) should have the error information as well.

It's hard to say what the problem is with so little information, though.

A few things to watch out for:
- You might have not enlisted and started the orchestration, in which case
you'll see an entry in the event log saying that no subscriptions where
found.
- If you're using the XMLReceive pipeline, it might be complaining about the
message format/schema, so check that as well (in this case, the message will
not have been fully parsed, likely, and the orchestration won't have been
started, either).

Also, check in HAT under Queries->Recent Service Instances

--
Tomas Restrepo
tomasr@mvps.org

[ Post a follow-up to this message ]

Tom - thanks so much for the reply.  Unfortunately no other entries next to
this one.  The message content unfortunately provides no additional
information nor doe s the Message Flow (checked both again).  I am using the
Microsoft.BizTalk.DefaultPipelines.XMLReceive pipeline as per the examples
instructions.  Please refer to
http://blogs.msdn.com/luke/archive/.../01/250876.aspx for the one page
quick start I am trying to follow.  This particular example is referenced by
most all of the Microsoft BizTalk MVPs.

In this simple example there is no true "Orchestration" to enlist but I did
enlist the the BTSQuickStartSendPort as instructed.  I also enabled the
BTSQuickStartReceiveLocation as evidenced by the fact that the simple
instance file, Instance.xml (built from the source schema) gets picked up
from the Input directory (but unfortunately just never processed).  I checke
d
also the HAT Queries, Recent Service Instances and the Receive succeeded but
no mention of the send process.

Finally, i get no errors on compiliation of the BTSQuickStart application
itself and both source and destination schemas are well-formed and valid as
well as the instance doc, Instance.xml.

I was hoping this simple example would be a great proof of concept for me to
use in displaying a brown-bag to my CTO RE: BizTalk and incorporating into
our Enterprise.  Thanks in advance for any additional help you can provide.

"Tomas Restrepo (MVP)" wrote:
 
>
> Chances are alongside that particular entry, you would have a second entry
> with more detailed information as to what happened.
>
> 
>
> The message content is probably not useful here, but the message CONTEXT
> should have the error description. Also, if an exception happened while
> processing the message, using viewing the message flow (right click->
> message flow) should have the error information as well.
>
> It's hard to say what the problem is with so little information, though.
>
> A few things to watch out for:
> - You might have not enlisted and started the orchestration, in which case
> you'll see an entry in the event log saying that no subscriptions where
> found.
> - If you're using the XMLReceive pipeline, it might be complaining about t
he
> message format/schema, so check that as well (in this case, the message wi
ll
> not have been fully parsed, likely, and the orchestration won't have been
> started, either).
>
> Also, check in HAT under Queries->Recent Service Instances
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
>

[ Post a follow-up to this message ]

I forgot to mention also that I tested SchemaMap.btm within .NET IDE with
both Test Map and Validate Map successfully.  Test Map built the correct
output XML with XSLT transformations in place.


"Tomas Restrepo (MVP)" wrote:
 
>
> Chances are alongside that particular entry, you would have a second entry
> with more detailed information as to what happened.
>
> 
>
> The message content is probably not useful here, but the message CONTEXT
> should have the error description. Also, if an exception happened while
> processing the message, using viewing the message flow (right click->
> message flow) should have the error information as well.
>
> It's hard to say what the problem is with so little information, though.
>
> A few things to watch out for:
> - You might have not enlisted and started the orchestration, in which case
> you'll see an entry in the event log saying that no subscriptions where
> found.
> - If you're using the XMLReceive pipeline, it might be complaining about t
he
> message format/schema, so check that as well (in this case, the message wi
ll
> not have been fully parsed, likely, and the orchestration won't have been
> started, either).
>
> Also, check in HAT under Queries->Recent Service Instances
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
>

[ Post a follow-up to this message ]

Well from within the BTSQuickSendPort, Outbound Maps node, I removed my
reference to BTSQuickStart.SchemaMap in an attempt to reset all values from
scratch.  When I did so it would NOT let me reselect a map - the bad news.
The good news is the end to end process now works!  I am a bit frustrated
that I don't understand "the why".  And I am still unable to select a map fo
r
the Outbound Maps node.  Any ideas?

"Tomas Restrepo (MVP)" wrote:
 
>
> Chances are alongside that particular entry, you would have a second entry
> with more detailed information as to what happened.
>
> 
>
> The message content is probably not useful here, but the message CONTEXT
> should have the error description. Also, if an exception happened while
> processing the message, using viewing the message flow (right click->
> message flow) should have the error information as well.
>
> It's hard to say what the problem is with so little information, though.
>
> A few things to watch out for:
> - You might have not enlisted and started the orchestration, in which case
> you'll see an entry in the event log saying that no subscriptions where
> found.
> - If you're using the XMLReceive pipeline, it might be complaining about t
he
> message format/schema, so check that as well (in this case, the message wi
ll
> not have been fully parsed, likely, and the orchestration won't have been
> started, either).
>
> Also, check in HAT under Queries->Recent Service Instances
>
> --
> Tomas Restrepo
> tomasr@mvps.org
>
>
>

[ Post a follow-up to this message ]

Hi again,
> Tom - thanks so much for the reply.  Unfortunately no other entries next
> to
> this one.  The message content unfortunately provides no additional
> information nor doe s the Message Flow (checked both again).  I am using
> the
> Microsoft.BizTalk.DefaultPipelines.XMLReceive pipeline as per the examples
> instructions.  Please refer to
> http://blogs.msdn.com/luke/archive/.../01/250876.aspx for the one page
> quick start I am trying to follow.  This particular example is referenced
> by
> most all of the Microsoft BizTalk MVPs.
>
> In this simple example there is no true "Orchestration" to enlist but I
> did
> enlist the the BTSQuickStartSendPort as instructed.  I also enabled the
> BTSQuickStartReceiveLocation as evidenced by the fact that the simple
> instance file, Instance.xml (built from the source schema) gets picked up
> from the Input directory (but unfortunately just never processed).  I
> checked
> also the HAT Queries, Recent Service Instances and the Receive succeeded
> but
> no mention of the send process.
>
> Finally, i get no errors on compiliation of the BTSQuickStart application
> itself and both source and destination schemas are well-formed and valid
> as
> well as the instance doc, Instance.xml.

Were you able to deploy the solution succesfully?

Here's something I'd check to ensure the problem is not related to schemas:
modify both the receive location and send port to use the PassThru pipelines
instead of the XML ones and remove any maps from the ports. Now restart your
biztalk host and try again. does it work? if so, then something is
definitely amiss with all of this.

Also, check again the send port configuration regarding the filters: your
message might be getting into biztalk, but perhaps it is not being routed
correctly (a friend of mine has a tendency to misspell the receive port name
when setting up filters, for example  )

--
Tomas Restrepo
tomasr@mvps.org

[ Post a follow-up to this message ]