How and in what cases Property demotion works in BizTalk. And the adapter leaves the message context to. When you drop the incoming file, properties of the.

Author: Sandro Pereira Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc.

He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Biztalk 2010 cu4, win2k8 server, no anti virus I'm having an issue where the biztalk file adapter is picking up the exact same file twice intermittently. This happens to both receive locations that are either unc remote or local across 2 different receive locations in 2 different applications. The receive location has all default settings.

I've tried setting rename files ticked and unticked with no resolution to the issue. The file masks are of H3OR*.txt. The time of pickup being the 'unparsed interchanges' between the duplicates is never greater than 1 second.

2 ms is common. Looking at the unparsed interchanges of the duplicates, the context properties 'receivedfilename' is exactly the same. The occurrence of the duplication is roughly 1 in 8 files being received. The receive location does have credentials to the unc path and it does delete files after it's done with them.

Restarting both the receive location and the biztalk host has no effect. Let me know if you need any more info. I don't think so. The process which drops the files off has been running for years including before biztalk was implemented. This problem only started occurring when biztalk was turned on.

I've checked a recent sample of the problem and the message id is different. Still with a few milliseconds difference between creation time. Unfortunately I've given up on this problem for now and use an orchestration to block duplicate files. I'll keep watching this thread in case someone has an interesting idea. – Nov 29 '12 at 5:16 •.