There was a failure executing the send pipeline: "Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor, Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Transform" Send Port: "ALL.Exceptions" URI: "SQL://MYSQLSERVER/EsbExceptionDb/" 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=184.108.40.206, Culture=neutral, PublicKeyToken=38642839467826'.
I believe this has to do with there not being a resumable at the time the exception was triggered. Not positive if this is the case however.
I recently decided to do some performance monitoring for my BizTalk servers. While adding performance counters, I notices that one of my systems did not have the BizTalk performance counters listed. All of the BizTalk:*counters were missing.
I am using BizTalk360version 8.9.5112.2201 in a BizTalk2016 environment. In setting up reports, I came across an interesting issue. If you have looked at the CPU usage reports, you may have noticed that the graphs do not match actual performance.
Consider the following SQL Servers Performance graph.
You will notice that the left-side legend is displaying 0-100%. I make the assumption that this is Total CPU and the right-side legend is memory usage.
I had the need to test multiple ports on multiple servers and didn't want to do each one manually. Typing telnet multiple times get old real quick not to mention the potential for fat fingering the keyboard.