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: Microsoft BizTalk Server WCF-SAP Adapter (NCo) cannot handle strong-typed batch of iDOCs


View products that this article applies to.

Symptoms

Assume that 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 this adapter, 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

↑ 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:

↑ 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: CI112141, kbHotfixAuto, kbqfe, kbfix, kb, sap adapter with nco in biztalk

↑ Back to the top

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