CIPM Incoming Auditing Fails in Windows 2000 (262280)


The information in this article applies to:

  • Microsoft Site Server 3.0 Commerce Edition
This article was previously published under Q262280

SYMPTOMS

Commerce Interchange Pipeline Manager (CIPM) Incoming Auditing fails on Microsoft Windows-2000 based computers. Incoming Auditing never writes anything to the IncomingAudit table of the CIP Receipt database. If pipeline logging is enabled, the following information indicating a success is logged on the receiving computer but nothing is ever written to the IncomingAudit table: 

PIPELINE:++ component[0x2] about to be called ProgID: Commerce.Audit.1
RootObject:	ReadValue	document_type	VT_BSTR	IncomingDocument	VT_EMPTY	__empty__	
RootObject:	ReadValue	document_source	VT_BSTR	<Qualifier>12</Qualifier><Identifier>800-555-1212</Identifier>	VT_EMPTY	__empty__	
RootObject:	ReadValue	document_destination	VT_BSTR	<Qualifier>12</Qualifier><Identifier>800-555-1213</Identifier>	VT_EMPTY	__empty__	
RootObject:	ReadValue	send_datetime	VT_BSTR	Monday, May 01, 2000 20:40:43 PM	VT_EMPTY	__empty__	
RootObject:	ReadValue	return_receipt_request	VT_BSTR	
<DIGESTALGORITHM>SHA1</DIGESTALGORITHM>
<DOCUMENTTYPE>Receipt</DOCUMENTTYPE> 	VT_EMPTY	__empty__	
RootObject:	ReadValue	msg_digest	VT_BSTR	5jqk1+pjbseuHAbStwEMC5cVOX8=	VT_EMPTY	__empty__	
RootObject:	ReadValue	txid	VT_BSTR	ihk2rjfa1fupg0n7u3pfp8idc0	VT_EMPTY	__empty__	
PIPELINE:-- component [0x2] returned hr: 0x0 in 60 milliseconds

RESOLUTION

Microsoft recommends that development efforts for Business to Business document transfer be done with BizTalk Server. The technical preview for BizTalk Server can be downloaded from the BizTalk Web site at:

http://www.microsoft.com/biztalkserver/default.htm

STATUS

Microsoft has confirmed that this is a problem in Microsoft Site Server version 3.0.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Enable Incoming Auditing for one of two trading partners.
  2. Invoke the Send method of the IMSendReceiveTx or IMSendReceive object on the sending partner.
  3. Invoke the ReceiveStandard method or the IMSendReceiveTx or IMSendReceive object on the receiving partner.
Result: The IncomingAudit table of the receiving partner contains no records. Functionality of the OutgoingAudit table and ReceiptAudit tables are not affected.

Expected Result: The Incoming Audit table of the receiving partner should contain records pertaining to incoming documents.

For additional information regarding the implementation of CIPM document auditing, please refer to the CIPM Online documentation.
Modification Type:MajorLast Reviewed:6/30/2004
Keywords:kbfix kbprb KB262280
©2004 Microsoft Corporation. All rights reserved.