Exception handling block not executed once the orchestration pushes the message on to the message box

 Issue:

  • When using orchestration, the message is sent to a message box.
  • Then, a send port is responsible for sending the message to a file location.
  • However, if the file location does not exist, the message fails with an error.

Here's the specific error message:

"A message sent to adapter 'FILE' on send port 'POCScope.SP' with URI 'D:\Developer\Vipin\POCScope\OUT%MessageID%.xml' is suspended.

Error details: The FILE send adapter cannot open the file D:\Developer\Vipin\POCScope\OUT{9463D718-72F2-4BB3-8761-E1A60F2AF7C8}.xml for writing.

Details: The system cannot find the path specified.

MessageId: {BF023C95-B69B-4A34-B124-642EF5895712}

InstanceID: {15D7188F-D9C7-48D5-9748-DCA7201948E4}"

  • Furthermore, the exception handling block written in the orchestration does not execute.



Root cause:

The issue arises because the error occurs at the send port, which is outside the scope of the orchestration code. The orchestration has already dropped the file onto the message box, and the send port subscribes to the message.



Comments

Popular posts from this blog

EDI X12 Trading partner configuration in BizTalk

How to create an EDI 850 profile in Boomi?

Basics of Correlation in BizTalk