Home Page › Forums › BizTalk 2004 – BizTalk 2010 › What is a failed message in biztalk 2006
- This topic has 1 reply, 1 voice, and was last updated 9 years, 3 months ago by
community-content.
-
AuthorPosts
-
-
August 13, 2008 at 11:51 AM #20409
I created a simple schema with the name Employee.xsd in a project names TestSendPortDelivRec
<ns0:Employee xmlns:ns0=”http://TestSendPortDelivRec.Employee“>
<FNAME>Srinivas</FNAME>
<LNAME>Kandha</LNAME>
<PLACE>HP EC1</PLACE>
</ns0:Employee>I also created a simple orchestration, which gets a file from a receive file location and move the same message to a different file location.
I tried using “Enable routing for failed messages” on file receive port. But when the recieve port expects a different message type other than what it is configured to, it fails. It always expects to receive a message type which is already deployed, if not it fails. When you copy a file of different message type which is already deployed to this location it treats as error message and does its job. And if there is any error in the expected message type (say “<” or ” is missing) also it fails. I just want to know what exactly is a failed message or fault message in biztalk.
Say for example, instead of sending the above message type, if I copy the .xml file with the following data (where the root node is changed to Employeess)
<ns0:Employeess xmlns:ns0=”http://TestSendPortDelivRec.Employee“>
<FNAME>Srinivas</FNAME>
<LNAME>Kandha</LNAME>
<PLACE>HP EC1</PLACE>
</ns0:Employeess>it fails by writing the following errors to the event log given below
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5719
Date: 8/14/2008
Time: 12:08:35 AM
User: N/A
Computer: VAASU
Description:
There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML disassembler” Receive Port: “TestSendPortDelivRec_1.0.0.0_TestSendPortDelivRec.Test_Port_1_dcd0a51ed911e477” URI: “C:\VASUData\Testand Delete\TestSendPortDelivRec\IN\*.xml” Reason: Finding the document specification by message type “http://TestSendPortDelivRec.Employee#Employeess” failed. Verify the schema deployed properly.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
AND
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5720
Date: 8/14/2008
Time: 12:08:35 AM
User: N/A
Computer: VAASU
Description:
There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML assembler” Send Port: “SendPort1” URI: “C:\VASUData\Testand Delete\TestSendPortDelivRec\Failed\%MessageID%.xml” Reason: This Assembler cannot retrieve a document specification using this type: “http://TestSendPortDelivRec.Employee#Employeess“.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
AND
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754
Date: 8/14/2008
Time: 12:08:35 AM
User: N/A
Computer: VAASU
Description:
A message sent to adapter “FILE” on send port “SendPort1” with URI “C:\VASUData\Testand Delete\TestSendPortDelivRec\Failed\%MessageID%.xml” is suspended.
Error details: There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML assembler” Send Port: “SendPort1” URI: “C:\VASUData\Testand Delete\TestSendPortDelivRec\Failed\%MessageID%.xml” Reason: This Assembler cannot retrieve a document specification using this type: “http://TestSendPortDelivRec.Employee#Employeess“.
MessageId: {EC2CAA90-8C28-4007-A430-0924EE4703B0}
InstanceID: {146284E2-C1C8-455A-A098-7B001AF2EACC}For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Please let me know if you have any idea about this. I thank you in advance.
Vaasu
-
August 22, 2008 at 5:07 AM #20478
It looks like you are using the XML Receive/Send pipelines. These pipelines have the property “Allow unrecognized messages”, which is false by default. If you were to set this property to true, then BizTalk would receive your messages, and you could use failed message routing. When you enable failed message routing on a receive port, BizTalk will attach some specal context properties to the message when an exception occurs. Then you could create another process, an SMTP send port for example, to filter on these failed messages and deliver them to someone who cares. Example filter: ErrorReport.FailureCode Exists. Keep in mind that failed message routing only works messaging exceptions, not orchestration exceptions.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.