FIX: NullReferenceException is thrown when you change ConnectorType on WCF-SAP send port in BizTalk Server

Applies to: Microsoft BizTalk Adapter Pack 2013BizTalk Server 2013 R2 BranchBizTalk Server 2013 R2 Developer


When you change the ConnectorType property on a WCF-SAP send port in BizTalk Server, the port fails at runtime and you may receive an error message that resembles the following:
A message sent to adapter "WCF-SAP" on send port "SAPSP" with URI "sap://CLIENT=###;LANG=EN;@a/sapserver/##?RfcSdkTrace=False&AbapDebug=False" is suspended.
Error details: System.NullReferenceException: Object reference not set to an instance of an object.
Server stack trace:
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)

Additionally, the ConnectorType change does not take effect even after the configured cache refresh interval.


Cumulative update information

The fix that resolves this issue is included in the following cumulative update for BizTalk Server:Note After you apply this hotfix, the host instance for the send port must be restarted for the change to take effect and resolve this error.


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