Microsoft KB Archive/320635

= FIX: Supporting Multiple MBCS Document Submissions in One Interchange::Submit =

Article ID: 320635

Article Last Modified on 10/6/2005

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-



This article was previously published under Q320635



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
If you interchange a multi-byte character set (MBCS) flat file between BizTalk and other applications (such as a SAP application), the document may be corrupted. If you apply hotfix 312616 to correct this problem and you then submit the data of multiple MBCS documents in the flat file as a string directly (for example, if you submit the data through a Message Queuing receive function, an HTTP receive function, or an IInterchange.Submit call in SAP or the MQSeries adapter), you will not receive multiple documents in the interchange.



CAUSE
This problem occurs because the stream that the core interchange parser is holding on to is different from the one that the MBCS parser is working with in the new MBCS parser design.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

815781 How to Obtain the Latest BizTalk Server 2002 Service Pack

Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) 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 tool in Control Panel.   Date         Time   Version          Size   File name ---  31-May-2002  06:44  3.0.1520.0     57,616   Bizedit1.exe 31-May-2002 06:44  3.0.1520.0     57,616   Bizmap1.exe 31-May-2002 06:44  3.0.1520.0    266,512   Cannedfunctoids.dll 31-May-2002 06:31  3.0.1520.0    172,304   Cismsg.dll 31-May-2002 06:34  3.0.1520.0    712,976   Cisparser.dll 31-May-2002 07:03  3.0.1520.0    200,976   Cispositionalmbcsparser.dll 31-May-2002 07:03  3.0.1520.0    188,688   Cispositionalmbcsserializer.dll 31-May-2002 06:44  3.0.1520.0     82,192   Codelistproj.dll 31-May-2002 06:44  3.0.1520.0    213,264   Extensionmod.dll 31-May-2002 06:44  3.0.1520.0  1,605,904   Mapedit.ocx 31-May-2002 06:44  3.0.1520.0     74,000   Scriptparser.dll 31-May-2002 06:44  3.0.1520.0    499,984   Treedatasvr.dll

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To install this hotfix:  Run Hotfixsetup.exe. Copy the CISPositionalMBCSParser.dll and CISPositionalMBCSSerializer.dll files to the BizTalk server root. Register the two files with regsvr32.exe. To do this, type the following from the command line:

regsvr32 c:\program files\Microsoft Biztalk Server CISPositionalMBCSParser.dll



This fix adds a new function in the core interchange parser and the MBCS parser. If you enable the new function, the interchange parser and the MBCS parser work on the same new data stream, and the multiple document submission problem is fixed. To enable the new function, set the following registry value to 1:



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft BizTalk Server 2002 Service Pack 1.



MORE INFORMATION
This new function applies to the CISPositionalMBCSParser.dll file, but it only applies to the flat file parser. If you want to test this new function, you must have the MBCS positional parser and the MBCS positional serializer registered and set to the top of the parser order in the BizTalk group properties. Additionally, you must change the document schema and set reserver_prop2 to PositionMBCSByByte or PositionMBCSByByte-bstrNotUnicode, depending on whether the data is submitted as a Unicode BSTR or is submitted directly from a file. To do this, follow these steps:
 * 1) Open the document schema with BizTalk Editor.
 * 2) Select the root node in the left pane, and then click the Parser tab in the right pane.
 * 3) Locate the Count Positions In Bytes property, and then set the value to Yes (Data in BSTR is Unicode) or Yes (Data in BSTR is MBCS).
 * 4) Save the change, and then exit BizTalk Editor.

Keywords: kbbug kbfix kbbiztalk2002sp1fix KB320635

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.