The problem with re-saving the file in MS Excel using cifs

[mikemm]

Problem. There is MS Excel 2010 installed using PlayOnLinux (wine 1.8 and 4.3 - tested these versions), lubuntu 18.04.2. There is a network drive. Create a new file on a network drive - saved. When you try to make changes to this file, after saving there is an error: unable to save changes to 'Book2.xlsx' due to access conflict. Try saving the data in another file. Similar issue with MS Excel 2013. At the same time from another computer on Windows there is no such problem. Also, there is no such problem if the file is resaved on the local disk. What to do, where to dig?

Environment and settings:
1. Smb config.conf on the file server:

Code: Select all

[global]
workgroup = FAETON
netbios name = faetonfs
server string = %h server (Samba, Ubuntu)
dns proxy = yes
log file = /var/log/samba/log.%m
max log size = 1000
map to guest = bad user
usershare allow guests = yes

[documents]
comment = documents on faetonfs
path = /home/sambafolders/documents
guest ok = yes
browsable = yes
writable = yes
read only = no
create mask = 0777
directory mask = 0777

2. On the client machine connects as follows in fstab:

Code: Select all

//192.168.88.5/documents /home/documents\040on\040faetonfs cifs guest,rw,nofail,x-gvfs-show,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=<userxxx>,gid=<groupxxx>,vers=2.0

3. The folder on the client machine on which it is mounted:

Code: Select all

drwxrwxrwx  2 <userxxx> <groupxxx>      0 мар  3 23:13 documents on faetonfs/

I read about the algorithm of resaving in the office:
In the destination folder specified in the Save as dialog box, Excel creates a temporary file with a random name (for example, Cedd4100@@@ [,] without a file name extension). The entire workbook is written to this temporary file. If you save changes to an existing file, Excel deletes the original file. Excel changes the name of the temporary file to the name specified in the Save as dialog box (for example, Book1.xlsx).

It has been suggested that somehow the office process does not have permissions to delete the file. But it was not confirmed: I wrote a macros to delete the file, run - the file was deleted.