Consider the following scenario:
You use the BizTalk ESB Toolkit.
You use the "ALL.Exceptions" send port to process and send binary messages to the ESB Exception database.
The MIME type of the messages is "application/octet-stream."
In this scenario, you notice that some of the messages get suspended and are not sent to the ESB Exception database. Additionally, the following error message is returned:
There was a failure executing the send pipeline: "Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Transform" Send Port: "ALL.Exceptions" URI: "<UriPath>"
Reason: Error 175002: An unexpected error occurred while trying to execute the map, 'Microsoft.Practices.ESB.ExceptionHandling.Maps.FaultMessage_to_ExceptionSql, Microsoft.Practices.ESB.ExceptionHandling.Maps, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem is fixed in the following cumulative update for BizTalk Server:
Cumulative Update 3 for BizTalk Server 2020
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