Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Delivery Notification
- This topic has 1 reply, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
February 29, 2008 at 3:34 AM #19006
Hi,
I have created a orch with one recv shape and a scopr with exception handling along 2 send ports – one for success and one for failure.
send port for success is dynamic and follwing is the code used
DeliverySuccessPort(Microsoft.XLANGs.BaseTypes.Address) = FILE://D://vijaykishan//SendSuccessDelivery//vijay.xml;
Delivery notification : transmitted.
Failure send port is specify later and specified a file path. In the exception block I am catching the deliveryNotificationexception and sending fail message to failureport.
I get the following message in event log. Kindly help reg this.
1.
The “FILE” adapter is suspending a message coming from Source URL:”D:\vijaykishan\RecvDelivery\*.xml”. Details:”Could not find a matching subscription for the message. “.
2.
The Messaging engine failed to process a message submitted by adapter:FILE Source URL:D:\vijaykishan\RecvDelivery\*.xml. Details:Could not find a matching subscription for the message. . This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure
3.
The Messaging Engine encountered an error publishing a batch of “1” messages to the Message Box database for the transport adapter “FILE”. Please refer to Health and Activity Tracking tool for more detailed information on this failure and check the endpoint bindings are correctly configured.
-
February 29, 2008 at 9:18 PM #19007
Your error message does not appear to be related to Delivery Notification at all. It looks as though your message is not even making it into your orchestration due to a subscription problem.
Make sure you orchestration is bound to the correct receive port and make sure that the type of message that you have configured your receive shape(inside your orchestration ) is correct.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.