FIX: You receive a CIS_E_PARSER_NO_DATA 1435 error message when you try to receive a binary document by using Message Queuing receive functions in BizTalk Server 2002

When you try to receive a binary document by using Microsoft Message Queuing receive functions in Microsoft BizTalk Server 2002, the document is not processed and the following event is logged in the Application log:

Event Type: Error
Event Source: BizTalk Server
Event Category: Document Processing
Event ID: 324
Description:
An error occurred in BizTalk Server.

Details: ------------------------------
[0x1435] There is no data that can be parsed on the dictionary. Verify that either the "working_data" field or the "file_path" field contains nonempty data.

[0x80070057] The parameter is incorrect.

[0x1730] Suspended Queue ID: "{DBCB1B77-6E86-470C-9E6D-A3AF4F2F6AAE}"

[0x80070057] The parameter is incorrect.

0x80041011
[0x1731] The server cannot send a WMI event for the Suspended queue item "{DBCB1B77-6E86-470C-9E6D-A3AF4F2F6AAE}". The most likely cause is that the user configured for this submission has insufficient privileges to access WMI.

Note The CIS_E_PARSER_NO_DATA error message value is 0x1435.

This problem occurs when BizTalk Server 2002 performs the following tests to determine whether the document is valid:

�	The document is tested to determine whether the document is a VT_BSTR document type.
�	The document is tested to determine whether the first two bytes of the document are not 00 00, or null characters.

The second test is not correct. A document that is a VT_BSTR document type is valid when the first two bytes are 00 00.

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

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer 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 tool in Control Panel.

   Date         Time   Version     Size     File name
   ------------------------------------------------------
   04-Feb-2004  19:59  3.0.2515.0  553,232  Ciscore.dll
   06-Jan-2005  00:27  3.0.2539.0  758,032  Cisparser.dll    

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

This hotfix introduces a new registry entry that controls whether null characters (00) are permitted in messages. Therefore, after you apply this hotfix, you must add the following DWORD registry entry to enable the hotfix:If the AllowNullCharsInMsg DWORD value is set to 0 (zero), BizTalk Server 2002 will not process documents when the first two bytes are 00 00. If the AllowNullCharsInMsg value is set to any other value than 0 (zero), BizTalk Server 2002 will process documents when the first two bytes are 00 00.

To add the new registry entry, follow these steps.

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.

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\BTSSvc{GUID}
3.	On the Edit menu, click New, and then click DWORD Value.
4.	Type AllowNullCharsInMsg, and then press ENTER.
5.	Right-click AllowNullCharsInMsg, and then click Modify.
6.	In the Edit DWORD Value dialog box, type a value of 0 or 1 depending on the behavior that you want to occur, and the click OK. Note Enter a 0 (zero) value when you do not want to process documents when the first two bytes are 00 00. Enter a 1 value when you want to process documents when the first two bytes are 00 00.
7.	On the File menu, click Exit.

Additionally, if you are using the RosettaNet Implementation Framework (RNIF) for document interchange, you may require an additional hotfix. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: For additional information, click the following article number to view the article in the Microsoft Knowledge Base: