Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: BAPI transactions are not committed when you use WCF-SAP NCo connector type in BizTalk Server


View products that this article applies to.

Symptoms

BAPI transactions are not committed when you use the .NET Connector (NCo) type in the transport properties of a WCF-SAP send port in Microsoft BizTalk Server.

↑ 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


Resolution

This problem is fixed in the following cumulative updates for BizTalk Server:

Note The fix is enabled by creating the registry value HKLM\SOFTWARE\Microsoft\BizTalk Server\3.0\Configuration\EnableBizTalkSapSessionProvider of type DWORD and setting it to '1'.

↑ Back to the top


References

For information about the service packs and cumulative update list for BizTalk Server, see the following article in the Microsoft Knowledge Base:

2555976 Service Pack and cumulative update list for BizTalk Server

For more information about BizTalk Server hotfixes, see the following article in the Microsoft Knowledge Base:

2003907 Information about BizTalk hotfixes and Cumulative Update support


Third-party information disclaimer
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


Keywords: CI98588, kbHotfixAuto, kbqfe, kbfix, kb, BAPI transactions in BizTalk Server

↑ Back to the top

Article Info
Article ID : 4491648
Revision : 12
Created on : 7/28/2020
Published on : 7/28/2020
Exists online : False
Views : 191