PRB: No Receipt When You Use the Loopback Transport (295591)


The information in this article applies to:

  • Microsoft BizTalk Server 2000
This article was previously published under Q295591

SYMPTOMS

When you use the Loopback transport on your BizTalk Messaging port, BizTalk Server may not generate a receipt even though your channel is configured to generate receipts.

CAUSE

When you use the Loopback transport, you must submit documents by using the synchronous method call SubmitSync. The SubmitSync method provides no mechanism for invoking a receipt channel within the same thread.

RESOLUTION

To receive receipts, you must use the asynchronous method call Submit().

STATUS

This behavior is by design.

MORE INFORMATION

The issue discussed in this article is not specific to the Loopback transport, and applies with any transport when SubmitSync is used. The Loopback transport requires that the document be submitted through the SubmitSync call. Therefore, it is most evident in this scenario. Use the Loopback transport when you want to have the response document returned to your application that called the SubmitSync method.

REFERENCES

For more information about using receipts with Microsoft BizTalk Server, refer to the online documentation.
Modification Type:MajorLast Reviewed:9/30/2003
Keywords:kbprb KB295591
©2003 Microsoft Corporation. All rights reserved.