Red Hat Bugzilla – Bug 204611
Excel "share workbook" feature broken by -excel patch in 3.0.9-1.3E.6 and later
Last modified: 2007-11-30 17:07:10 EST
Description of problem:
MS Excel has a feature which allows several users to work on the same excel file
concurrently ("Arbeitsmappe freigeben" in German, probably "share workbook" in
This feature doesn't work if the -excel patch introduced in 3.0.9-1.3E.6 is
applied. Even worse, if a user tries to use this feature, other users always get
a warning that the file is locked, even if they are currently the only one who
are accessing it. So, not only doesn't concurrent access work any more, even
serial access doesn't work.
The same user (on two different clients) can open the file. So it's probably
some kind of permission problem, and since my file is writable for all, my
guess is that Excel is trying to change some metadata (probably the timestamp).
If I rebuild the 3.0.9-1.3E.10 rpm without the -excel patch (patch24), sharing
workbooks works (but then Excel files change mtime if opened).
Version-Release number of selected component (if applicable):
3.0.9-1.3E.6 to 3.0.9-1.3E.10 (inclusive)
Steps to Reproduce:
1. Create an Excel file on a Samba share. Make sure it is writable by other users
2. Open the file with excel and select "share workbook" from the menu. The title
bar should now indicate that the file is shared.
3. Log in as a different user and open the excel file.
You get an error message that the file is locked. You can still open it, and the
title bar indicates that the file is shared, but when you try to save it you get
an error message "you aren't connected to the file any more" (my translation
from German). You can only save it with a different file name.
The file should be opened without an error. Saving the file should be possible.
Excel is from Office XP (2002) but Excel 97 was also shortly tested. File system
is ext3 with ACLs and quotas enabled.
I cannot reproduce the problem with the current version (3.0.23b) from samba.org.
The changelog indicates possibly relevant changes in 3.0.12 and 3.0.14.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.