none
SAP send adapter and does not send a large response back RRS feed

  • Question

  • Can anyone suggest how to stop large response messages from SAP  failing on a SAP send port?

    We send a request using a BizTalk 2013 SAP adapter and can get a 5Mb response back successfully.

    We send another request to the same adapter and expect a response to be about 15Mb. We never get this response back. Eventually after a long time we get the following failure message.

    System.Transactions.TransactionException: The operation is not valid for the state of the transaction. at System.Transactions.TransactionState.EnlistVolatile(InternalTransaction tx, IEnlistmentNotification enlistmentNotification, EnlistmentOptions enlistmentOptions, Transaction atomicTransaction) at System.Transactions.Transaction.EnlistVolatile(IEnlistmentNotification enlistmentNotification, EnlistmentOptions enlistmentOptions) at Microsoft.BizTalk.Adapter.Wcf.Runtime.TransmitTxnBatch..ctor(IBTTransportProxy transportProxy, ControlledTermination control, Transaction transaction) at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkDeleteTxn.Execute(BizTalkExecutionContext executionContext)

    We also collected a WCF trace which shows that the response is never closed.

    We have tried adjusting he time out on the SAP adapter but believe that the SAP adapter does not use these time outs. We have also changed the pipeline to passthrough and discarded the maps to remove any other complications and still see the same error with large SAP response on the SAP adapter.

    Can anyone suggest how to stop large response messages from SAP failing on  a SAP send port?

    Thursday, May 1, 2014 3:55 AM

Answers

  • Hi Mark, We faced same issue on Oracle Adapter a while ago and here is the article I posted about the solution. It should work for you.

    If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    • Marked as answer by Mark Brimble Friday, May 2, 2014 6:19 PM
    Thursday, May 1, 2014 5:42 AM