FIX: Messages become stuck in SM58 when you use a WCF-based SAP Adapter in BizTalk Server 2010

View products that this article applies to.

This article applies to the following products:

Microsoft BizTalk Adapter Pack 2010
Microsoft BizTalk Adapter Pack 2013

Symptoms

Assume that you use a Microsoft Windows Communication Foundation (WCF)-based SAP adapter from Microsoft BizTalk Adapter Pack 2010 to connect to an SAP system on a Microsoft BizTalk Server-based computer. You encounter some errors when the WCF-based SAP adapter receives intermediate document (IDOC) messages from the SAP system. In this situation, the IDOC messages may become stuck in the Transaction Executing state in SM58 in the SAP system. Additionally, the following error messages are logged in the Application log on the BizTalk Server:

<EventData><Data>WCF-Custom</Data><Data> System.Runtime.InteropServices.COMException (0xC0C0163C): Exception from HRESULT: 0xC0C0163C at Microsoft.BizTalk.TransportProxy.Interop.IBTTransportBatch.SubmitMessage(IBaseMessage msg) at Microsoft.BizTalk.Adapter.Wcf.Runtime.Batch2.SubmitMessage(IBaseMessage message, Object userData) at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkExecutionQueue.DequeueTaskCore() </Data></EventData>
<EventData><Data>WCF-Custom</Data><Data> Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_INVALID_HANDLE. AdapterErrorMessage=An exception has occurred on the listener while executing RfcWaitForRequest.. at Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& requestContext) at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1.System.ServiceModel.Channels.IReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& context) at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) </Data></EventData>

Note This issue also occurs when the WCF-based SAP adapter host shuts down or intermittent network issues occur.

↑ Back to the top

Cause

This issue occurs because the BizTalk adapter sends error messages to the SAP system. However, the SAP system cannot handle the error messages.

↑ Back to the top

Resolution

After you apply the fix, a different kind of error message is passed on to the SAP system.

Cumulative update package information

For BizTalk Adapter Pack 2013

The hotfix that resolves this issue is included in cumulative update package 1 for BizTalk Adapter Pack 2013.

For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2892600 Cumulative update package 1 for BizTalk Adapter Pack 2013

For BizTalk Adapter Pack 2010

The hotfix that resolves this issue is included in cumulative update package 3 for BizTalk Adapter Pack 2010.

For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2617150 Cumulative update package 3 for BizTalk Adapter Pack 2010

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk Server hotfixes

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top