samba - May 2003 - Problems with Word 200 and Samba 2.2.6 - RESOLVED

Found this issue in the list archives, with no resolution. I think I found
one.

We were having this exact problem, and we resolved it by removing
\*.doc\*.DOC\ from our smb.conf "veto oplocks" list, and adding
\*.tmp\*.TMP\. Leaving the *.tmp files out of the veto list was causing Word
2000 to say that a file was currently locked by 'another user', even
when
the file was just created!

Unix permissions were not the problem in our case.

The problem was intermittent, in that it would only happen if Samba was
running for awhile (in use by ~400 clients), and when it was happening, it
would only occur within apparently random subdirectories of apparently
random shares. 

It would happen to everyone who tried to save or create files in those
specific subdirectories. The problem would progressively get worse until we
rebooted the server at which point it would go away, but eventually start
again as the day progressed (in different subdirectories of different
shares). 

The problem happened using both Windows 98 and 2000 clients, OS' fully
updated, using Word 97, and Word 2000, both patched to the lastest service
pack and not. The problem did not seem to occur, ever, using other Office
2000 software such as Excel and Powerpoint.

The server was running Samba 2.2.5 and Redhat 7.2.

I know that's not much of a diagnosis, but it worked.

Hope this helps someone,
Brad



-----Original Message-----
From: Ed Stoner [mailto:ed@whsd.k12.pa.us]
Sent: Thursday, November 21, 2002 9:07 AM
To: Marian Mlcoch, Ing
Cc: samba@samba.org
Subject: Re: [Samba] Problems with Word 200 and Samba 2.2.6


Thanks.  I looked at the vetofiles settings and they appear allright.  
Actually, the problem disappeared when I restarted the samba server (which
is a little unnerving).  While I'm glad the problem is gone (and now am
convinced that it is a bug in samba somewhere, since nothing else
changed), I don't have any means to investigate it any further (since it
isn't happening anymore).

On Thu, 21 Nov 2002, Marian Mlcoch, Ing wrote:
> Hi
> i read your problem and i suggest you to verify user , owner and group
chmod
> on directory with docs and on user that modified this word file.
> When you create new file word saves ~.tmp on your local harddisk temp
> directory and saves it to share with save command and new name.
> Afther when you edit then ~... file is created on share but samba can
> vetoing ~ char in name by settings veto or bad codepage.
> Check your vetofiles settings on samba.
> Bye.
> 
> ----- Original Message -----
> From: "John H Terpstra" <jht@samba.org>
> To: "Ed Stoner" <ed@whsd.k12.pa.us>
> Cc: <samba@samba.org>
> Sent: Wednesday, November 20, 2002 3:05 AM
> Subject: Re: [Samba] Problems with Word 200 and Samba 2.2.6
> 
> 
> > On Wed, 6 Nov 2002, Ed Stoner wrote:
> >
> > > I'm hoping someone has some insight into a problem I'm
currenty
having,
> > > which is:
> > >
> > > No one is able to edit (in place) documents with Word 2000 on a
samba
> > > (2.2.6) disk share.  A user can open word and save a document to
the
> > > share, but when they go to edit the document Word says "Word
cannot
> > > complete the save due to a file permission error".  From
Microsoft KB
> > > Q211632 it appears that Word 2000 performs the following steps to
Save
> an
> > > Edited File:
> > >
> > > 1.) Create a temp file (Create ~wrdxxxx.tmp)
> > > 2.) Write temp file (Save example data to ~wrdxxxx.tmp)
> > > 3.) Delete original file (Delete EXAMPLE.DOC)
> > > 4.) Move temp to target name (Move ~wrdxxxx.tmp to EXAMPLE.DOC)
> > >
> > > >From examining the samba debug log (attached) it does appear
that
this
> > > happens.  It also appears that somewhere in steps 1 and 2 above
Word
> sends
> > > a request to turn off the read,write,and execute bits for the
owner of
> the
> > > file.  When you look at this filesystem after the attempted save
the
> > > original file does indeed have these bits cleared (i.e. the user
has
no
> > > read,write,or execute permissions on the file), and that I think
is
why
> > > the error is being generated.
> >
> > What update level (service pack) have you installed on your Word 2000
> > system? Please tell us what is the exact version information from
clicking
> > on Help/About in Word.
> >
> > Please check that your Word is up to date with all service updates
from
> > the MS Web site.
> >
> > Also, what is the client OS and it's update level?
> >
> > Also, please send your smb.conf to jht@samba.org and I'll check it
over.
> >
> > - John T.
> >
> > > I've tried setting the 'create mask', 'security
mask', 'force create
> > > mode', and 'force security mode' parameters to no
avail (I assumed
that
> > > setting 'force security mode' to 0700 would prevent a
file from
getting
> > > rwx removed from the owner).  I've also tried turning 'nt
acl support'
> on
> > > and off.  I've attached my config file also.
> > >
> > > My questions are:
> > > 1.) has anyone else seen this error?
> > > 2.) if so is there a fix?
> > > 3.) why does smbd/posix_acls.c:set_nt_acl allow chmod to 000?
> > >
> > > P.S.
> > > This does not happen with the same client config connecting to
either
an
> > > NT Share or a 2000 Share, in case anyone is curious (i.e. I
don't
think
> it
> > > is a client thing)
> > >
> > > thanks
> > >
> > > -----------------
> > > Ed Stoner
> > > Network Administrator
> > > Woodland Hills School District
> > > (412) 731-1300 x0109
> > >
> >
> > --
> > John H Terpstra
> > Email: jht@samba.org
> >
> 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba