- This topic has 5 replies, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
Hi All,
Lately we have noticed a strange behavior on our BizTalk environments which we can’t get our head around.
The Background:
We get files from our partner X who sends us a number of files daily.Out of these only b number of files are configured in our database.This results in the (a-b) files to fail in BizTalk with a XLANG error stating the problem (which in this case is a dot.net db retrtieval error).The corresponding instances are suspended (resumable) in BizTalk and can be seen on the admin console.This error behavior has occured daily for a week now (and is an expected behavior according to us).
The Problem:
We have now noticed that the errors have stopped completely since the last couple fo days.There is no change in the data from the partner X, nor have we configured the extra files (a-b) into our database.There has been no change to any orchestration or helper assemblies.This behavior is inexplainable (if there is a word like that)
The Question:
Taking a long shot (and I am sure it sounds stupid),but does BizTalk have any built in intelligence to suppress such recurring errors?Something similar to the receive locations that get disabled after the number of retrial attempts are exhausted.
Any help on this will be appreciated.
Many thanks in advance,
Farooq
-
-
There is no built in suppression of errors. Are you sure the orchestration and its host instance are still started?
-
Thanks for the reply thiago .. yes it would be strange if biztalk does suppress the recurring errors
The orchestrations and the host instances are started,as some messages are processed where as the others simply dissappear.
Another failure point that we identified (the code isn’t ours)is that there is a custom pipeline that brings the messages into BizTalk message box.For the messages that don’t have errors we cannot find orchestration instances in the HAT too..thereby making us wonder whether the messages reached the messagebox from the pipeline (though there are no pipeline errors too).
The lack of logs is killing the investigation 🙁
-
maybe it’s not biztalk supressing those messages but the machine itself….
( i remember reading this somewhere )
maybe this can help : http://www.flicks.com/technicalsupport/suppress_duplicate_event_log_entries.asp
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.