Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: You receive parsing and validation errors in some Category 0 message types when you use Microsoft BizTalk Accelerator for SWIFT


View products that this article applies to.

Symptoms

When you use Microsoft BizTalk Accelerator for SWIFT 2.1, Microsoft BizTalk Accelerator for SWIFT 2.3, or Microsoft BizTalk Accelerator for SWIFT 3.0, you receive parsing and validation errors in some Category 0 message types. For example, you receive an event error message that resembles the following:

Event Type: Error
Event Source: BizTalk Accelerator for SWIFT
Event Category: None
Event ID: 4096
Description:
Publishing failed message to MessageBox. Details: The single message of type 012, whose Interchange ID is {FF87C404-5EDC-4E98-A931-242D810F8C43}, has been marked as A4SWIFT_Failed=True in the MessageBox database by the SWIFT Disassembler. This message failed with 1 parse errors, 1 XML validation errors, and 0 BRE validation errors. Error details can be extracted from the failed message in the MessageBox database by subscribing to messages where A4SWIFT_Failed=True.

↑ Back to the top


Cause

This problem occurs after you install and configure BizTalk Accelerator for SWIFT Message Pack 2008. Some of the Category 0 messages that are included in Message Pack 2008 do not fully comply with the Worldwide Interbank Financial Telecommunication (SWIFT) 2008 Standards Release Guide specification.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft BizTalk Accelerator for SWIFT 2008 Message Pack installed and configured to apply this hotfix. To install this hotfix, follow the instructions in the Readme.txt file that the hotfix package contains.

Restart requirement

You must restart the BizTalk services after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Microsoft.solutions.financialservices.swift.commonfunctions.dll4.1.1016.3293,81631-Oct-200811:52x86
Mt010.xsdNot applicable133,88620-Oct-200807:46Not applicable
Mt011.xsdNot applicable132,01425-Oct-200805:53Not applicable
Mt012.xsdNot applicable136,16417-Oct-200812:08Not applicable
Mt012.xsnNot applicable83,79816-Oct-200817:50Not applicable
Mt015.xsdNot applicable126,16820-Oct-200807:48Not applicable
Mt019.xsdNot applicable136,98015-Oct-200823:05Not applicable
Mt019.xsnNot applicable87,2676-Oct-200814:58Not applicable
Mt020.xsdNot applicable242,95631-Oct-200811:23Not applicable
Mt022.xsdNot applicable240,17020-Oct-200807:49Not applicable
Mt022.xsnNot applicable90,65620-Oct-200814:53Not applicable
Mt023.xsdNot applicable277,71620-Oct-200807:50Not applicable
Mt023.xsnNot applicable108,79820-Oct-200814:53Not applicable
Mt028.xsdNot applicable134,63820-Oct-200807:51Not applicable
Mt028.xsnNot applicable83,33820-Oct-200814:53Not applicable
Mt029.xsdNot applicable153,59020-Oct-200807:51Not applicable
Mt029.xsnNot applicable84,98320-Oct-200814:53Not applicable
Mt031.xsdNot applicable132,14820-Oct-200807:52Not applicable
Mt031.xsnNot applicable83,10520-Oct-200814:53Not applicable
Mt032.xsdNot applicable125,39420-Oct-200807:53Not applicable
Mt032.xsnNot applicable82,30920-Oct-200814:53Not applicable
Mt037.xsdNot applicable123,93020-Oct-200807:53Not applicable
Mt037.xsnNot applicable82,34120-Oct-200814:53Not applicable
Mt041.xsdNot applicable125,39220-Oct-200807:54Not applicable
Mt041.xsnNot applicable82,31020-Oct-200814:53Not applicable
Mt044.xsdNot applicable130,49220-Oct-200807:55Not applicable
Mt044.xsnNot applicable83,24120-Oct-200814:53Not applicable
Mt045.xsdNot applicable125,29620-Oct-200807:55Not applicable
Mt045.xsnNot applicable82,29620-Oct-200814:53Not applicable
Mt046.xsdNot applicable127,90220-Oct-200807:56Not applicable
Mt046.xsnNot applicable82,31220-Oct-200814:53Not applicable
Mt051.xsdNot applicable149,93820-Oct-200820:04Not applicable
Mt051.xsnNot applicable92,56320-Oct-200814:53Not applicable
Mt052.xsdNot applicable132,28820-Oct-200820:05Not applicable
Mt052.xsnNot applicable83,52220-Oct-200814:53Not applicable
Mt055.xsdNot applicable172,90420-Oct-200820:05Not applicable
Mt055.xsnNot applicable87,47320-Oct-200814:53Not applicable
Mt056.xsdNot applicable378,97620-Oct-200820:20Not applicable
Mt056.xsnNot applicable98,14820-Oct-200814:53Not applicable
Mt057.xsdNot applicable131,12820-Oct-200820:23Not applicable
Mt057.xsnNot applicable83,43420-Oct-200814:53Not applicable
Mt061.xsdNot applicable146,58220-Oct-200820:24Not applicable
Mt061.xsnNot applicable87,48520-Oct-200814:53Not applicable
Mt062.xsdNot applicable131,35020-Oct-200820:24Not applicable
Mt062.xsnNot applicable83,47520-Oct-200814:53Not applicable
Mt063.xsdNot applicable145,90620-Oct-200820:25Not applicable
Mt063.xsnNot applicable85,16720-Oct-200814:53Not applicable
Mt064.xsdNot applicable130,85620-Oct-200820:25Not applicable
Mt064.xsnNot applicable83,27120-Oct-200814:53Not applicable
Mt065.xsdNot applicable125,28620-Oct-200820:26Not applicable
Mt065.xsnNot applicable82,30220-Oct-200814:54Not applicable
Mt066.xsdNot applicable167,07420-Oct-200820:26Not applicable
Mt066.xsnNot applicable86,35720-Oct-200814:54Not applicable
Mt067.xsdNot applicable148,08620-Oct-200820:27Not applicable
Mt067.xsnNot applicable85,61620-Oct-200814:54Not applicable
Mt068.xsdNot applicable130,82820-Oct-200820:27Not applicable
Mt068.xsnNot applicable83,25620-Oct-200814:54Not applicable
Mt069.xsdNot applicable125,26420-Oct-200820:28Not applicable
Mt069.xsnNot applicable82,30220-Oct-200814:54Not applicable
Mt073.xsdNot applicable160,93620-Oct-200814:38Not applicable
Mt073.xsnNot applicable84,48720-Oct-200814:54Not applicable
Mt074.xsdNot applicable168,27616-Oct-200814:12Not applicable
Mt074.xsnNot applicable85,96620-Oct-200814:54Not applicable
Mt075.xsdNot applicable155,10031-Oct-200811:25Not applicable
Mt076.xsdNot applicable146,79820-Oct-200811:25Not applicable
Mt076.xsnNot applicable83,74720-Oct-200814:54Not applicable
Mt081.xsdNot applicable149,91016-Oct-200819:43Not applicable
Mt081.xsnNot applicable92,62320-Oct-200814:54Not applicable
Mt083.xsdNot applicable167,52620-Oct-200820:33Not applicable
Mt083.xsnNot applicable86,46220-Oct-200814:54Not applicable
Mt087.xsdNot applicable149,02815-Oct-200814:14Not applicable
Mt087.xsnNot applicable83,59020-Oct-200814:54Not applicable
Mt090.xsdNot applicable126,03015-Oct-200814:15Not applicable
Mt090.xsnNot applicable82,21420-Oct-200814:54Not applicable
Mt092.xsdNot applicable134,84220-Oct-200807:49Not applicable
Mt092.xsnNot applicable83,42620-Oct-200814:54Not applicable
Mt094.xsdNot applicable179,62220-Oct-200806:53Not applicable
Mt094.xsnNot applicable86,48520-Oct-200814:54Not applicable
Mt361.xsdNot applicable950,32016-Oct-200807:43Not applicable
Mt361.xsnNot applicable153,64017-Oct-200813:25Not applicable
Mt564_validation_policy.xmlNot applicable627,97921-Oct-200813:20Not applicable
Mt566_validation_policy.xmlNot applicable351,98721-Oct-200813:26Not applicable
Mt750.xsdNot applicable299,45016-Oct-200819:43Not applicable
Mt750.xsnNot applicable98,4976-Oct-200814:32Not applicable
Swiftbasetypes.xsdNot applicable824,52822-Oct-200806:24Not applicable
Swift_networkrule282_policy.xmlNot applicable8,78822-Oct-200806:29Not applicable
This hotfix addresses problems with Category 0 parsing and validation. After you install this hotfix, you can use the SWIFT standard that was established in November 2008. You must install this hotfix after you install and configure Message Pack 2008.

This hotfix also includes the following fixes:
  • The hotfix includes a fix for a problem that occurs when you try to parse or validate the MT012 SWIFT message or the MT019 SWIFT message. You receive the following error message:
    Stray data was found at the end of the message
  • The MT030 SWIFT message and the MT039 SWIFT message are removed. These messagse are no longer necessary.
  • The MT051 SWIFT message and the MT081 SWIFT message are modified to remove tag 209.
  • The hotfix includes a fix for a problem with the MT009 SWIFT message. This message contains incorrect encoding.
  • The hotfix includes corrects .xsn files for some of the MT message types. For more information, see the list in the "File information" section.
  • The MT081 SWIFT message and the MT620 SWIFT message are modified to resolve a parsing error.
  • The MT535 SWIFT message is modified to resolve a validation error.
  • This hotfix includes hotfix 958737. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    958737 FIX: The SWIFT disassembler misses the message trailer part or a parsing error occurs when you run the SWIFT disassembler in Microsoft BizTalk Accelerator for SWIFT Message Pack 2008
  • This hotfix includes hotfix 959143. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    959143 FIX: Message types MT535, MT564, and MT566 fail the BRE validation when you use Microsoft BizTalk Accelerator for SWIFT Message Pack 2008
  • This hotfix modifies other message types to comply with the SWIFT Guidelines. For example, this hotfix upgrades the SRG version from 2007 to 2008.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbbtsaccelerators, kbsurveynew, kbautohotfix, kbexpertiseinter, kbhotfixserver, kbqfe, KB959067

↑ Back to the top

Article Info
Article ID : 959067
Revision : 1
Created on : 1/7/2009
Published on : 1/7/2009
Exists online : False
Views : 528