Event Viewer

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Event Viewer

Viewing 3 reply threads
  • Author
    Posts
    • April 6, 2009 at 3:57 AM #22090
      community-content

        Hi

        We have used Biztalk Server 2006 R2  in our project.

        Using the Event Viewer in Biztalk Administration Console, we are able to see the errors which happen during runtime. But as per

        our requirement, the same error message needs to be sent back to the client.

        Is there a way, we can get the error message during runtime? Are these error messages stored in the Biztalk Database?

        Please help.

        Thanks & Regards
        Shoba.V.R

      • April 6, 2009 at 6:39 AM #22092
        community-content

          You can use MOM. I think this is the best way to do it.

          Or 🙂

          I think you can do it, using WMI, using the search engine, i found the following article: http://www.eggheadcafe.com/articles/20010614a.asp

           

          Pedro, O Moleiro

        • April 6, 2009 at 12:41 PM #22093
          community-content

            Hello Shoba,

            You can capture all the error messages by using subscription (Messagetype=”failedMessage”) in either send port or orchestration.

            FYI:

            Please go through the SDK sample Error Handling

            Thanks

            Srini

             

            • April 8, 2009 at 9:54 PM #22107
              community-content

                Hi

                Thanks for the reply.

                I checked the SDK Samples provided for Error Handling. They use InfoPath and the example seems to be very complex. Is there a simple exception handling example provided for Biztalk?

                Thanks in Advance

                Shoba

                • May 19, 2009 at 11:56 PM #22418
                  community-content

                    You could use a scope shape in your orchestration. put all the shapes (where erros are usually occured) in the scope shape, then you can “Add New Exception handler” by right clicking the top of the scope shape. you can further define the type of Exception (for example System.Exception) you want to handle in the Exception handler shape. if all is done correctly, you should now be able to have access to the error/exception information/description. Hope this helps.

                     

              • April 6, 2009 at 2:10 PM #22094
                community-content

                  There are a number of capturing errors during the runtime.

                  If the error occurs in the message system (receive locations and send ports) then you can use the RouteFailedMessage
                  http://msdn.microsoft.com/en-us/library/aa559179.aspx
                  http://msdn.microsoft.com/en-us/library/aa578109.aspx

                  In the orchestration you can catch exceptions using a scope object
                  http://msdn.microsoft.com/en-us/library/aa578339.aspx

              • Author
                Posts
              Viewing 3 reply threads
              • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.