FIX: Microsoft BizTalk Server WCF-SAP Adapter (NCo) cannot handle strong-typed batch of iDOCs

Applies to: BizTalk Server 2016 BranchBizTalk Server 2016 DeveloperBizTalk Server 2016 Enterprise

Symptoms


Assumethat you use Microsoft BizTalk Server WCF-SAP adapter together with .NET Connector(NCo). When you try to receive strong-typed batch of iDOCs by using thisadapter, you receive the following error:
The adapter "WCF-SAP" raised an error message. Details "System.ArgumentException: "typeName" can't be null or empty
Parameter name: typeName

Status


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

Resolution


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

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.