FIX: BizTalk Server May Lose Data When It Processes Binary Data with the Receive Function Preprocessor (311251)

MORE INFORMATION

Steps to Reproduce Behavior

1. Create a Message Queuing receive function. Set the Pass-through property.
2. Use the following Microsoft Visual Basic 6.0 code to create a preprocessor for the Message Queuing receive function:
   
   NOTE: You must include a reference to the "Microsoft BizTalk Server Application Interface Components 1.0 Type Library" (Btscomplib.tlb) in the project for this code.

   Implements IBTSCustomProcess
   Sub IBTSCustomProcess_SetContext(ByVal pCtx As IBTSCustomProcessContext)
   'This subroutine is required but is not used.
   End Sub
   
   Sub IBTSCustomProcess_Execute(ByVal vDataIn, ByVal nCodePageIn As Long, _
                                 ByVal bIsFilePath As Boolean, ByRef nCodePageOut, _
                                 ByRef vDataOut)
       nCodePageOut = nCodePageIn
       vDataOut = vDataIn
       debug.print typename(vDataOut) 'Data type of byte() is a SAFEARRAY.
       debug.print LenB(vDataOut) 
   End Sub
   					

3. Configure a channel to a port to an Application Integration Component (AIC), which has the following code:
   
   NOTE: You must include a reference to the "Microsoft BizTalk Server Application Interface Components 1.0 Type Library" (Btscomplib.tlb) in the project for this code.

   Implements IBTSAppIntegration
   Private Function IBTSAppIntegration_ProcessMessage(ByVal bstrDocument As String) _
                   As String
       
       Dim strDocument As String
       debug.print LenB(bstrDocument) 'This loses a byte if you submit document as binary.
       ' Convert the document that is passed in to Unicode.
       strDocument = StrConv(bstrDocument, vbUnicode)
           
       ' Write out the document.
       Open "c:\AICOutput.txt" For Binary Access Write As #1
       Put #1, , strDocument
       Close #1
   End Function
   					

4. Submit binary data to the Message Queuing queue that the Message Queuing receive function monitors.

If binary data is written to the incoming Message Queuing queue, the resultant Visual Basic SAFEARRAY output is the correct size in the preprocessor. However, a byte of data is missing from the SAFEARRAY output when the output reaches the Application Integration Component.

If non-binary data is written to the incoming Message Queuing queue, this problem does not occur because the preprocessor output is not a SAFEARRAY. This problem only occurs if the preprocessor output is a Visual Basic SAFEARRAY.