Hi,

Just need some information around BizTalk logs that logs both the successful and failed file transfers if there is any ? If so how can I access this?

Thanks

Bhanu

successful transfer -  No error

failed transfer -  error/warning in Application log event viewer and eventually written to ESB portal which sends alerts to people. If you dont have ESB you can point your monitoring tool like SCOM/SPLUnk to look for errors on any event viewer and send alerts.

Delivery failre excepion : You can catch these type of exceptions in orchestration by using deviveryfailure exception handler attached to scope.

Cheers

Hi Bhanu,

Are you able to give some information on the scenario as that may give a better view on what any solution would be?

One thing to definitely not do is enable message tracking which would be the BizTalk out of the box way of doing this. However, using this can adversely impact performance of the system and should only ever be used in anger for incident diagnosis.

There are many examples of logging approaches for BizTalk solutions around things like log4net or the BizTalk CAT Instrumentation Framework for tracing when logging continuously is not the requirement.

The former is really more about logging generally whilst you can use the latter to instrument your code so you can turn it on when required for diagnosing issues.

https://gihansampathliyanage.wordpress.com/2014/07/07/write-log-file-for-biztalk-logging-with-log4net-sample/

http://blogs.msdn.com/b/appfabriccat/archive/2010/05/11/best-practices-for-instrumenting-high-performance-biztalk-solutions.aspx

https://btscatifcontroller.codeplex.com/

You can use either of these tools to write information out and then use something like Splunk to display on a dashboard.

Another alternative would be BAM which you could use to provide logging at endpoints. You can use Continuation to tie endpoints together and then once again use something like Splunk to read the data from the tables in the BizTalk database. You can also use the BAM API and BAM Interceptors to provide additional programmatic functionality that allows you to extend this.

Cheers,

Martin

hi Martin & Janardhan,

Thanks for your inputs. After observing the event log I found out that there is some issue with the file transfer and I can see the error messages like so

Is any one of you familiar with this error? I just happened for one day and it got fixed automatically next day

Also wondering why the files in the receive location got deleted when there are errors. I have set the ftp polling properties Delete after download to YES. So I expect it only to delete the files after they have been downloaded and transferred across to Send Location.

Thanks

Bhanu

Hi Bhanu,

Error says there are some logon issue, could you please check you have proper access (read/write) on send port URL, or is there any connect issue during transmit the message to send port.

'why the files in the receive location got deleted when there are errors'

Seems you are getting error on send port not in receive location, so when FTP receive location picks the file as per your define property its delete the file from RL.

Hi Bhanu,

This looks like an authentication/authorisation issue, without knowing the mechanics involved it could be that the Service Account was locked for some reason, or some other infrastructural issue played a part.

In terms of why the message goes, this is just an artifact of the way the messaging engine in BizTalk works. The message is picked up from the Receive Location, and is moved to the MsgBox. This process "consumes" the inbound file so it no longer remains. The Delete option is there only for if there is an issue in reading the whole file in to BizTalk on the initial read, it doesn't impact any ongoing transactional control. So in this case, the file was fully downloaded and so was deleted, but routing of that message to the FILE adapter failed, but of course by this time there was no ability to feedback to the receive location.

Hope that helps,

Martin

Your error is much more about authentication issue of the user which is trying to poll the file location . May be the user running the host instance  does not have read/write privilege at the specific time  .

Now coming to your main question , you  need to have some logging mechanism build around CAT or enterprise logging to read /write the flow of message in and out of BizTalk .

Or other way is to read the DTA DB for the transaction details .

Thanks

Abhishek 

Hi Bhanu,

As others said i also guess it is logon issue re the host account user for writing the file. For me it looks like the account got disabled in AD so please check the acount status in active directory.

Since the question you have asked is about the default logging for all file transfers i mentioned the error/warning in event log. Here is more about logging if you are interested

Message only scenario ( No orchestrations or components) : Errors/warning will be written to event viewer OR ESB portal and then you can use SCOM/SPLUNK to alert the users based on these.

Orchestration/Pipeline components : Log4NET or CAT framework.

Delivery failure : Negative ACKs using deliveryfailure exception handler attached to scope in Orchestration

Irrespective of the success/failure at the send port, if the receive port works without any issues then the file will be delete automatically.