BUG: MSMQ Receive Function Is Disabled When Attempting to Process Document Beginning with Hexadecimal Code Zeros (312767)



The information in this article applies to:

  • Microsoft BizTalk Server 2000
  • Microsoft BizTalk Server 2000 SP1
  • Microsoft BizTalk Server 2000 SP1a

This article was previously published under Q312767

SYMPTOMS

One or more of the BizTalk Server Microsoft Message Queuing (MSMQ) receive functions may be disabled and the following error message may occur in the BizTalk Server Application log:
Event Type:	Error
Event Source:	BizTalk Server
Event Category:	Document Processing 
Event ID:	         324
Date:		12/7/2001
Time:		3:50:30 PM
User:		N/A
Computer:	         BIZTALKSERVER
Description:
An error occurred in BizTalk Server.
 
Details:
------------------------------
There was a serious failure in the receive function "Receive". This receive
service will be shut down, please check the event log for additional error 
messages.

Unspecified error
The receive function "Receive" has experienced problems, it will be shut 
down and disabled. Once these problems have been corrected, re-enable this 
receive function in BizTalk Server Administration.

There was a failure processing the "Receive" receive function. Check your 
receive function configuration in BizTalk Server Administration.
					

CAUSE

This error can occur if the MSMQ receive function attempts to process a document that starts with hexadecimal code zeros. Because BizTalk Server cannot process documents that begin with a hexadecimal code 0, it is expected for an error to occur; however this should not cause the MSMQ receive function to be disabled.

STATUS

Microsoft has confirmed that this is a problem in BizTalk Server 2000, 2000 SP1, 2000 SP1a.

This bug was corrected in BizTalk Server 2002.

MORE INFORMATION

BizTalk Server 2002 still generates the error when it attempts to process a document beginning with hexadecimal code zeros; however, the MSMQ receive function is not disabled.

Modification Type:MajorLast Reviewed:10/17/2003
Keywords:kbbug kbnofix KB312767