![]() This seems to affect files in all directories (i.e., 100% of the several folders which I tried) and affects. DOC file in the same directory, everything works and I can see that the lock file is created (and then removed correctly when I close the file). There are no visible lock files (i.e., not visible in Windows 7 and not visible in an ls -a on the server.) When I try to open a. Open document read-only or open a copy of the document for editing” “Document file ‘xxxxxxxxxx.odt’ is locked for editing by: ODT file using Writer/LO, I get a message like this: This set-up has been stable for a couple years on several different computers and as far as I know, nothing has changed about the CentOS server or ExpanDrive but I am experiencing this problem on a new computer and a new installation of ExpanDrive and a fresh install of LO (4.1.0.4). These errors occur moving data from an internal hard drive, so it’s clearly writing to the destination that is a problem and not reading from the source. ExpanDrive transfer failed because some data can’t be read or written. ![]() ![]() ExpanDrive exposes my server’s files (using sftp) as a virtual drive in Windows. In the case of multiple files, it fails because one or more required items can’t be found. I am trying to edit them using Windows 7 and a product called ExpanDrive (v2.4.0). I see several questions about unlocking files but none seems to match my circumstances.
0 Comments
Leave a Reply. |