Hi,
Do you see this error when issuing a "Save" action on an existing document from within Word, as opposed to a "Save As…" action that you would (implicitly) use on a new document?
I remeber seeing an error that might have the same origin. Note, it may as well be something entirely differrent, but you never know if it may help you into the right dirtection.
In my case it was FCP 7 throwing the error, when saving (to) an existing document. Saving (to) a new document worked fine.
It wouldn't surprise me if both application use the same (older) API for saving their documents.
I eventually found that the problem was caused by the application attempting to execute the exchange command on the existing document and a newly created temporary document, in order to perform a sort of atomic save action.
I asume exchange normally implicitly deletes the existing document, but somehow fails at doing that. As my filesystem lacked this function, so it would use the default implementation, which failed.
My solution was not to try fix it by implementing a proper exchange function, but rather implementing an exchange function that simply returns -ENOTSUP instead of the default implementation, forcing FCP7 to use an alternate method for saving the file.
This worked great.
Hope this helps,