How to log exceptions for BizTalk Server 2020 into a database

Michael Beaupre 1 Reputation point
2022-01-20T21:33:17.987+00:00

We installed BizTalk Server 2020, Cumulative Update 3, and ESB Toolkit on our TEST Server. I’m attempting to configure the Microsoft.Practices.ESB Application so that the Exceptions will be inserted into our SQL Server 2016 database (see the attached image below).

One method for doing this that I’ve seen on the web is what I'll call the “custom development” approach. That is, to create a map between the FaultMessage schema in Microsoft.Practices.ESB.ExceptionHandling.Schemas.Reporting.dll
and the usp_insert_Fault schema (created using the Consume Adapter Service in Visual Studio, from the usp_insert_Fault SP in the EsbExceptionDb database), as the old SQL Adapter uses a different schema layout to execute a stored procedure.

Has anyone had success using other methods? Using the WCF-Custom Adapter perhaps?
Thank you.

Microsoft BizTalk Server
Microsoft BizTalk Server
A family of Microsoft server products that support large-scale implementation management of enterprise application integration processes.
365 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Michael Beaupre 1 Reputation point
    2022-01-20T21:46:12.683+00:00

    ![166868-image.png]1

    0 comments
  2. Colin Dijkgraaf 1,361 Reputation points
    2022-01-26T19:57:18.13+00:00

    The WCF-Custom adapter would require you to select the SQL binding, which would be the same as using the WCF-SQL adapter.
    There is a StackOverflow answer here that goes into the steps.

    The only other option I've seen is to install the old deprecated SQL adapter

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.