CrossOver Support - Community Forums

Important Information These are community forums and not official technical support. If you need official support: Contact Us

CrossOver Linux
Discussion about CrossOver Linux

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

can't save changes in MS-Office 2010-files on a mounted Server2008R2-share

Since I've installed a new Leap Suse 15.0 and CXOffice 17.5 I can't save the changes in edited MS-Office2010-files on a mounted share from a MS Server 2008 R2.
The mount-options are the same as before and the native linux-to-smb-share-access works fine. There I can overwrite files on the mounted share, create new and delete files.. But if I use CXOffice and the MS Office 2010 I can not save the edited files - only if I use a new name.
I think the issue with the missing recent-folders can help, but it doesn't help.
Any other ideas?

I have had the same issue for ages, it seems related to the 2008R2 server using SMB2 shares. For me the problem existed with an EMC Isilon share that at some point got switched to SMB2, from that point i couldn't save over the existing file anymore.

And this only happens with apps running in a crossover bottle (any bottle). So libreoffice can overwrite the file just fine.

I'm on Ubuntu 18.04.

=> Same problem here. For both Office 2010 and Office 365. I could same on network share on to new file (from office). Cannot override existing file, even if I just created it (with the previous save).

I've tried setting cifs with different combinations of following mount options (no success):

I tried to finding something else on some forums, with no success.

I'm having a very similar problem. Essentially, I get an error as described in this article when trying to save an Excel workbook using an Ubuntu 18.04 workstation running Crossover Office 18.5.0 connected to a Samba file server:

However, I do have the correct modify and delete file permissions. The error goes away when I force the SMB1 connection while mounting. Clearly, there is a problem with Crossover or Wine and Ubuntu's implementation of SMB2, but I'm not sure what the issue is.

I have the same problem. Tested with crossover 18.5 and 19.0 beta, multiple bottles, tested with Office 2013 and Office 2016. The same behavior. When the opened file is on Samba share >SMB1 the file cannot be saved. The only way is to save to the new file and then copy over. Any other SW can access the files just fine, LibreOffice can open edit and save the same file the same as any other text editor, the only problem is with the crossover. I have checked WINWORD.EXE process and it runs under correct user, even if the user is the same (not group match but exact user match) the process cannot save its own file. This really happens only on SMB >1, seems to work with SMB1 share.

I know I'm resurrecting a somewhat old thread, but I'm still having this problem. I tried creating a new bottle and installing Microsoft Office 2016, getting the same results. Files can be read just fine, but when trying to save an existing file, getting the same errors as others reported in this thread. There is another thread on this forum that reports a very similar issue:;forumcurPos=200;msg=195184

Some info:

Ubuntu 18.04 x64
4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Crossover Office 19.0.1
File server: Samba 4.7.6, running on Ubuntu
Tried both:
Bottle: Windows XP, Microsoft Office 2007
Bottle: Windows 7, Microsoft Office 2016

Has anyone found out what the cause of this is?

EDIT: Updated broken link

Please Note: This Forum is for non-application specific questions relating to installation/configuration of CrossOver. All application-specific posts to this Forum will be moved to their appropriate Compatibility Center Forum.

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...