Ignoring Unc Paths Follow
I have configured a task in Commander to detect *.csv files and print them.
If I pick the "Folder to Scan:" to be D:\IncomingData\ it works fine. But my live data folder is \\db2\labels (a linux box). As soon as I change my "Folder to Scan:" to this, Commander just ignores files landing here. I've tried restarting Commander, changing the detection method from immediate to polling, changing file encoding and the detection response from rename to delete. But none of these changes have any effect.
If I enable message logging to file, I can see messages for Commander restarting but nothing is logged when I drop my CSV files into \\db2\labels. It's as though BarTender Commander just doesn't like UNC paths and actively refuses to monitor them.
Please can someone offer some help or advice.
We're using the latest Automation Enterprise release by the way.
Please sign in to leave a comment.