We've run into issues with the "cannot access a closed file" error periodically and were later told by Quest that writing to a local db table was a possible solution. However, what we're wondering is if the issue is related to a process not waiting long enough for the file to be released and if we need to introduce a time-delay somewhere or restarting a process like explorer.exe.
The issue is very transient and doesn't happen for some time and then suddenly becomes a persistent issue. We're trying to avoid having to rework all the existing processes if we can figure out how to handle the file access.
Have there been any further developments by Quests as there appears to be a number of threads on this topic within the forum.