Symptoms

After you change the ConnectorType property for an SAP solicit response Send port from ClassicRfc to NCo in Microsoft BizTalk Server, the WCF-SAP adapter crashes. Additionally, you may receive the following error message:

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP:Body><SOAP:Fault><faultcode>Microsoft BizTalk Server Negative Acknowledgment </faultcode><faultstring>An error occurred while processing the message, refer to the details section for more information </faultstring><faultactor>sap://CLIENT=XXX;LANG=EN;@a/XXXXXXX.XXXXX.net/20?RfcSdkTrace=True&AbapDebug=False</faultactor><detail><ns0:NACK Type="NACK" xmlns:ns0="http://schema.microsoft.com/BizTalk/2003/NACKMessage.xsd"><NAckID>{ID}</NAckID><ErrorCode>0xc0c0167a</ErrorCode><ErrorCategory>0</ErrorCategory><ErrorDescription>System.NullReferenceException: Object reference not set to an instance of an object.

Resolution

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

Cumulative Update 2 for BizTalk Server 2016

Cumulative Update 5 for BizTalk Adapter Pack 2013

Cumulative Update 6 for BizTalk Server 2013 R2

Status

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

References

Learn about service pack and cumulative update list for BizTalk Server.

Learn about BizTalk Server hotfixes and cumulative update support.

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×