Skip to content

Latest commit

 

History

History
42 lines (27 loc) · 2.68 KB

lesson-2-submitting-an-mt103-message-that-is-not-valid.md

File metadata and controls

42 lines (27 loc) · 2.68 KB
Raw
description title ms.custom ms.date ms.service ms.reviewer ms.suite ms.topic
Learn more about: Lesson 2: Submitting an MT103 Message That Is Not Valid
Lesson 2: Submitting an MT103 Message That Is Not Valid
06/08/2017
biztalk-server
article

Lesson 2: Submitting an MT103 Message That Is Not Valid

In this lesson, you submit an MT103 message that is not valid and then you troubleshoot the resulting error using your System Tools.

To submit an MT103 message that is not valid

  1. Copy the file MT103_Invalid_Sample.txt from <drive:>\Program Files\Microsoft BizTalk Accelerator for SWIFT\SDK\Tutorial to <drive>:\Labs\Inbound\FlatFile folder. Note the time that you drop the file into the folder.

  2. Open <drive:>\Labs\Outbound to verify that no XML file corresponding to MT103_Invalid_Sample.txt is in the folder. (The XML file corresponding to the valid MT103_Sample.txt message should still be in that folder.)

  3. In Notepad, open the file MT103_Invalid_Sample.txt in <drive:>\Program Files\Microsoft BizTalk Accelerator for SWIFT\SDK\Tutorial.

  4. Start BizTalk Server Administration.

  5. In the BizTalk Server Administration Console, expand Event Viewer (Local), and then click Application.

  6. Look for an error entry that has a source of BizTalk Accelerator for SWIFT and a time that corresponds to when you dropped the invalid message into the <drive>:\Labs\Inbound\FlatFile folder. Double-click that error entry.

  7. In the Event Properties dialog box for the error, verify in the Description pane that the failed message was published to the MessageBox and that the SWIFT Disassembler marked A4SWIFT_Failed as True. Close the Event Properties dialog box.

  8. In the BizTalk Server Administration Console, expand BizTalk Server Administration, and then expand BizTalk Group. In the View menu, click Group Hub Page.

  9. In the Group Overview pane, in the Grouped Suspended Service Instances pane, click Grouped by Application.

  10. In the Preview for the selected query result pane, double-click the entry for MT103_FlatFile_ReceivePort.

  11. In the Service Details dialog box, click the Messages tab. Double-click the entry for which the Service Name is MT103_FlatFile_ReceivePort.

  12. In the Message Details dialog box, click Body in the left pane.

  13. Verify that the message displayed in the body pane of the Message Details dialog box corresponds to MT103_Invalid_Sample.txt that you opened in Notepad.

    Proceed to Lesson 3: Testing an XML Instance.