none
How to retrieve errors such as SFTP folder issue

    Question

  • Hi,

    I would like to create a BizTalk application that retrieves errors from BizTalk Admin Console such as the following

    folder issue "No such file or directory". The error message will be sent as as email (I have codes to send email.).

    My only concern is on  how to retrieve the error message from the  BizTalk Admin Console..

    The adapter failed to transmit message going to send port "MasterProductSFTPSendPort" with URL "sftp://mo234ww1:22//app/dev/media/hybris/data/import/fe/master/products111/%SourceFileName%". It will be retransmitted after the retry interval specified for this Send Port. Details:"WinSCP.SessionRemoteException: Cannot create remote file '/app/dev/media/hybris/data/import/fe/master/products111/feMasterProduct_20170221125544257.csv'.
    No such file or directory.

    Please advise.

    Thanks.

    Friday, March 3, 2017 8:17 PM

Answers

  • Hi,

    You can use this: http://mitchvanhelden.blogspot.in/2011/03/biztalk-monitoring-part-2-bts-suspended.html


    Rachit Sikroria (Microsoft Azure MVP)

    Saturday, March 4, 2017 1:58 AM
    Moderator
  • Hi,

    First of all I think it is not a good idea to create a BT application for error management.

    But you can try these options which would be decoupled from Biztalk side.

    1. Out of box BizTalk errors: These will be written to the eventviewer by BizTalk so you can monitor eventlogs using tools like Splunk or powershell script and send the emails. If you have ESB portal set-up these can be alerted using notifications.

    2. Custom errors from BizTalk projects: If you use logging frameworks like Log4net you can use eventlog/Email appendars that sends the error messages.


    JB


    Monday, March 6, 2017 3:11 AM
  • You can create a subscribing orch and have routing enabled for failed messages on desired send ports.

    Your orch can consume these failed messages and you can operate on them to take any action.


    Pi_xel_xar

    Blog: My Blog

    BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/

    Monday, March 6, 2017 7:26 AM
    Answerer
  • Hi

    Ideally, you should be using Failed Message routing which can be leveraged to send notifications(note that this also cleans up the suspended instance, so if you intend to resume the suspended instance later from Admin Console, this is not the approach you can use. Refer this.

    If you want to retain the suspended instance in Admin Console and send out alerts, you can use something like-

    http://rajasekharcbe-biztalk.blogspot.in/2012/08/biztalk-suspended-messages-email.html


    Thanks Arindam

    Wednesday, March 8, 2017 5:00 AM
    Moderator
  • Hi,

    You can use three approaches to do this

    1. Failure Message routing and send an email using esb exception handling-->prefer if you dont need the suspended messages any more. Once its sent to the exception db, no messages will exist in the Suspended messages. You may resubmit the message but it takes more efforts.

    2. Query the Suspended message tables in an optimized way to send the notification on Description-->Prefer if you need a resumption capability and notification. optimize query/caching mechanism/Temp tables to avoid performance issues.

    3. Event-Viewer based Alerts(SCOM) to filter and send SFTP/BizTalk specific alerts -->Prefer if concerned on the Option 2,its isolated from the biztalk impacts



    Regards, Vignesh S

    Wednesday, March 8, 2017 12:26 PM
  • Hi Vignesh,

    2. Query the Suspended message tables in an optimized way to send the notification on Description-->Prefer if you need a resumption capability and notification. optimize query/caching mechanism/Temp tables to avoid performance issues.

    --What is the name of the tables that store the suspended messages?

    Thanks.

    Wednesday, March 8, 2017 1:59 PM

All replies

  • Hi,

    You can use this: http://mitchvanhelden.blogspot.in/2011/03/biztalk-monitoring-part-2-bts-suspended.html


    Rachit Sikroria (Microsoft Azure MVP)

    Saturday, March 4, 2017 1:58 AM
    Moderator
  • Hi,

    First of all I think it is not a good idea to create a BT application for error management.

    But you can try these options which would be decoupled from Biztalk side.

    1. Out of box BizTalk errors: These will be written to the eventviewer by BizTalk so you can monitor eventlogs using tools like Splunk or powershell script and send the emails. If you have ESB portal set-up these can be alerted using notifications.

    2. Custom errors from BizTalk projects: If you use logging frameworks like Log4net you can use eventlog/Email appendars that sends the error messages.


    JB


    Monday, March 6, 2017 3:11 AM
  • You can create a subscribing orch and have routing enabled for failed messages on desired send ports.

    Your orch can consume these failed messages and you can operate on them to take any action.


    Pi_xel_xar

    Blog: My Blog

    BizTalkApplicationDeploymentTool: BizTalk Application Deployment Tool/

    Monday, March 6, 2017 7:26 AM
    Answerer
  • Hi

    Ideally, you should be using Failed Message routing which can be leveraged to send notifications(note that this also cleans up the suspended instance, so if you intend to resume the suspended instance later from Admin Console, this is not the approach you can use. Refer this.

    If you want to retain the suspended instance in Admin Console and send out alerts, you can use something like-

    http://rajasekharcbe-biztalk.blogspot.in/2012/08/biztalk-suspended-messages-email.html


    Thanks Arindam

    Wednesday, March 8, 2017 5:00 AM
    Moderator
  • Hi,

    You can use three approaches to do this

    1. Failure Message routing and send an email using esb exception handling-->prefer if you dont need the suspended messages any more. Once its sent to the exception db, no messages will exist in the Suspended messages. You may resubmit the message but it takes more efforts.

    2. Query the Suspended message tables in an optimized way to send the notification on Description-->Prefer if you need a resumption capability and notification. optimize query/caching mechanism/Temp tables to avoid performance issues.

    3. Event-Viewer based Alerts(SCOM) to filter and send SFTP/BizTalk specific alerts -->Prefer if concerned on the Option 2,its isolated from the biztalk impacts



    Regards, Vignesh S

    Wednesday, March 8, 2017 12:26 PM
  • Hi Vignesh,

    2. Query the Suspended message tables in an optimized way to send the notification on Description-->Prefer if you need a resumption capability and notification. optimize query/caching mechanism/Temp tables to avoid performance issues.

    --What is the name of the tables that store the suspended messages?

    Thanks.

    Wednesday, March 8, 2017 1:59 PM