2

We are using the ESBExceptionDb in BizTalk 2020 to log error information. Recently, we have started go get the following error being suspended on application Microsoft.Practises.ESB on send port ALL.Exceptions:

Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The input data for the field/parameter Name is larger than that allowed on the SQL Server. Maximum length allowed is 256, length found was 340.

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)

Problem is, I can't find the reason for this error. It says that the name of the field/parameter is called 'Name', but I can't see this field being used anywhere in the Fault table in ESBExceptionDb.

Have anyone encountered the same problem before, and if so - how did you solve it?

onmi
  • 87
  • 1
  • 9

1 Answers1

0

I think this is due to the name of a "Distinguished" property which is in fact the XPATH used to identify it, it is part of the context properties that are integrated to the message but XPath are often longer than 256 chars... you need to either update the ESB procedure and the table or use direct xpath in your orchestrations instead of distinguished in a schema...

Neoark
  • 1
  • 3
  • I dont think I understand your explanation. I'm not using a distinguished field, I'm just trying to add a message to the EsbExceptionDb and receive the error described in my question. – onmi Jun 14 '22 at 16:19