<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx</link><description>Scenario: You create a business process that receives a message and send it to multiple target systems. For whatever reason the send from the business process fails ie. the message exists the business process and a later pipeline or adapter fails. This</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#80147</link><pubDate>Thu, 26 Feb 2004 01:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:80147</guid><dc:creator>Jody</dc:creator><description>Is there any way to get more detail about the reason for the exception?  We can see DeliveryFailureException, but we would like to know why.</description></item><item><title>re: BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#80210</link><pubDate>Thu, 26 Feb 2004 04:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:80210</guid><dc:creator>Mike</dc:creator><description>If you have two send ports and let's say both of them use the SQL Adapter, can you have both act as one transaction?  If one SQL Insert fails, I want both of the sends to roll back.</description></item><item><title>re: BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#80952</link><pubDate>Fri, 27 Feb 2004 08:37:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:80952</guid><dc:creator>Joris</dc:creator><description>Scott, Which build do you use? We use build 4712, but can't seem to find the property you are talking about.</description></item><item><title>re: BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#80990</link><pubDate>Fri, 27 Feb 2004 10:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:80990</guid><dc:creator>Joris</dc:creator><description>Let me refrase my question: Which build do you use, because in build 4712 it doesn't seem to work. I tried your example and added a send after the exception (in a decide shape), but it won't work.</description></item><item><title>re: BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#88814</link><pubDate>Fri, 12 Mar 2004 22:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:88814</guid><dc:creator>Brian Loesgen</dc:creator><description>Yes, VERY cool Scott. I'm using this approach in a solution that sends files by FTP. If the site goes down, now I can handle it intelligently.&lt;br&gt;&lt;br&gt;So, what about in the other direction? Ie: if I have a receive location that's an FTP site, (and that receive location goes to an activating receive shape) and the site goes down, I want to handle it. Presumably the same approach won't work as the orchestration has not been instantiated. Is there any way I trap and handle this condition?</description></item><item><title>re: BTS2004 Delivery Notifications</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#122236</link><pubDate>Wed, 28 Apr 2004 18:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:122236</guid><dc:creator>Amadeu Campanelli</dc:creator><description>Joris,&lt;br&gt;did you find the delivery notification property? I'm new to BizTalk and I didn't this property too.&lt;br&gt;&amp;lt;br&amp;gt;&lt;br&gt;Could you help me?&lt;br&gt;</description></item><item><title>re: FILE </title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#165521</link><pubDate>Fri, 25 Jun 2004 10:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:165521</guid><dc:creator>Christof Claessens' WebLog</dc:creator><description /></item><item><title>Exception handling with MSMQT.</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#200587</link><pubDate>Thu, 29 Jul 2004 12:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:200587</guid><dc:creator>Amit Sawant</dc:creator><description>Hi&lt;br&gt;&lt;br&gt;&lt;br&gt;	We have some doubt in Exception handling with MSMQT.&lt;br&gt;	&lt;br&gt;	we have a scenario wherein we receive a flat file from a MSMQT port,transform it by using  map &lt;br&gt;	and transmit it to MSMQ of another m/c.&lt;br&gt;	&lt;br&gt;	While transmiting we initialize a correlation set inorder to correlate the response of this transmit.&lt;br&gt;&lt;br&gt;	The send shape and receive shape for sending the message and receiving the response message are in same scope shape.&lt;br&gt;	&lt;br&gt;	We have added a exception handler to this scope shape which handles  System.Exception and which transmit the original message to temporary folder.&lt;br&gt;&lt;br&gt;	Orchestration works fine and we get desired output.&lt;br&gt;&lt;br&gt;	BUt if we remove the network code from the m/c(so that it cannot access the MSMQ of another m/c) the send should fail and &lt;br&gt;	message should be transmited to temp folder.&lt;br&gt;&lt;br&gt;	The orchestration consumes the input file but doesn't raise an exception.No error are seen in event log also.&lt;br&gt;&lt;br&gt;	we also tried DeliveryFailure Exception,general exception in the exception object type.&lt;br&gt;	&lt;br&gt;	Send port as delivery notification property =Trasmitted.&lt;br&gt;	Number of retry=0&lt;br&gt;	&lt;br&gt;	Why there are no error's in eventlog ???&lt;br&gt;	why this exception is not handled ??&lt;br&gt;	&lt;br&gt;Regards&lt;br&gt;Amit</description></item><item><title>Handling errors in Orchestrations from invoked WebServices</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#403551</link><pubDate>Wed, 30 Mar 2005 04:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:403551</guid><dc:creator>Commonality</dc:creator><description>When you are invoking WebServices from your BizTalk Server 2004 orchestrations, you might need to ensure that two things happen...</description></item><item><title>Send Port Acknowledgement | keyongtech</title><link>http://blogs.msdn.com/scottwoo/archive/2004/02/25/80037.aspx#9365638</link><pubDate>Thu, 22 Jan 2009 12:44:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9365638</guid><dc:creator>Send Port Acknowledgement | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/324143-send-port-acknowledgement"&gt;http://www.keyongtech.com/324143-send-port-acknowledgement&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>