I have a problem with a programmable/scriptable off-the-shelf third party product that creates files that we need to post-process (move, zip, or whatever).
The product let's us run commands after it has finished creating its output, so everything is perfect, right?
Not so much, because the application still has the files "open" when calling our script, so Windows won't let me touch them or the directory they're in.
The only idea I have so far is
start mystuff.bat and starting mystuff.bat with a sleep, but that opens up a can of worms with respect to error handling and such, because the server program can't know when the post-processing job has finished.
Anyone know how to solve this problem?
- The files are written to local disk on the windows server (2008 R2).
- Asking the software supplier to fix their program has failed so far :-(
The software is PrintNetT, a print production system, it runs as a service/daemon, processing job requests, creating directories+files, keeping them locked for the duration of the batch creating them. It runs 24/7 on a server (headless). After the batch has finished, the files are not locked anymore.