We believe it might be Commander that is causing the issue since we do have tags that are printing multiple tags correctly so it might not be a Windows patch. Where do we set the Delay in Bartender or Commander?
We verified that with Commander disabled, it works correctly but with Commander disabled not all the tags are printing. We do have a picture in the tag so I’m not sure if is the memory size of the tag file that is causing the issue within Commander. Any thoughts as to why Commander is not able to rename the files correctly with the correct file size when enabled?
I’ve generally found BarTender support to be very good, what did they say about it?
Did you ever get this resolved?
If it’s a large bartender trigger file being written (a ton of kb’s for an image) - could this be happening?:
TriggerFile.txt created
TriggerFile starts to get written with lots of bytes
Bartender notices TriggerFile, attempts to access\rename it while OS is still writing
Looks like under task properties in commander you can try some changes:
You could set the scan to polling and set a time for that to occur, or you could try increasing the locked-file timeout
Yes this issue did get resolved. We believe it was due to a latency in the network when retrieving the picture and the file getting written. When we tested with changing the polling interval, it resolved it in both our test and production environments but left it as immediate detection in production and it is working fine so far.