Microsoft KB Archive Search

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.

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

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

View products that this article applies to.

Symptoms

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.

↑ Back to the top

Resolution

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.

↑ 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

References

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

Learn about BizTalk Server 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: kbqfe, kbsurveynew, kbexpertiseadvanced, kbfix, kbbts, kb

↑ Back to the top

Article Info
Article ID : 3164730
Revision : 1
Created on : 1/7/2017
Published on : 10/10/2016
Exists online : False
Views : 304