Hi Paul,
We run into this occasionally as well. And we don't have any idea
what's going on, either.
Our best guess is that Arbortext thinks that the original file is locked
elsewhere and cannot be written over. That doesn't make any sense,
because Arbortext itself locks the file when opening it the first time.
And we're pretty confident that no one else had the file open
simultaneously. Might there be something buggy about how Arbortext
locks / releases the lock on files?
Does the problem occur when editing a file on a Windows network share?
(That's true for us, but then again we edit every file over a network
share.)
We're using 5.3 m040.
-James