samba - Dec 2003 - Outlook pst errors on samba share

A user has recently moved his .pst file onto a samba shared
folder for testing, but he is seeing the following error message
on a samba 2.2.8a installation (linux/s390 SuSE SLES8):

"Can't open this item.  The file z:\Personal Folders.pst could
not be accessed because another workstation has modified it.
Close and then restart all mail-enabled applications."

Has anyone else seen this?

Periodically, I see 4 lines like this in his machine log
(domain and user sanitized):

[2003/12/05 11:59:53, 2] smbd/open.c:open_file(247)
  {USER} opened file Personal Folders.pst read=Yes write=No (numopen=2)
[2003/12/05 11:59:53, 2] smbd/close.c:close_normal_file(229)
  {DOMAIN}\{USER} closed file Personal Folders.pst (numopen=1)
[2003/12/05 11:59:53, 2] smbd/open.c:open_file(247)
  {USER} opened file Personal Folders.pst read=Yes write=No (numopen=2)
[2003/12/05 11:59:53, 2] smbd/close.c:close_normal_file(229)
  {DOMAIN}\{USER} closed file Personal Folders.pst (numopen=1)

This is on an ext3 filesystem mounted (rw,acl,quota).

This user is the only one that has opened this file according
to the level 2 logs.

Smbstatus for that file shows:
DenyMode: DENY_WRITE
Access: 0x2019f
R/W: RDWR
Oplock: None

I have the following global options in my smb.conf because in the past I
heard of problems without them.  Is it likely that one of these is the
root of the errors?
# grep lock /etc/samba/smb.conf
        kernel oplocks = No
        blocking locks = No
        locking = No
        oplocks = No
        level2 oplocks = No

Thanks for any help,
~ Daniel






-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

first check if there is no other process ( outlook )
to the pst file,
catching pst files is an exclusiv act.
If you have any open connect relate to that pst, any other client will fail
to open.
----- Original Message ----- 
From: <daniel.jarboe@custserv.com>
To: <samba@lists.samba.org>
Sent: Friday, December 05, 2003 6:40 PM
Subject: [Samba] Outlook pst errors on samba share

> A user has recently moved his .pst file onto a samba shared
> folder for testing, but he is seeing the following error message
> on a samba 2.2.8a installation (linux/s390 SuSE SLES8):
>
> "Can't open this item.  The file z:\Personal Folders.pst could
> not be accessed because another workstation has modified it.
> Close and then restart all mail-enabled applications."
>
> Has anyone else seen this?
>
> Periodically, I see 4 lines like this in his machine log
> (domain and user sanitized):
>
> [2003/12/05 11:59:53, 2] smbd/open.c:open_file(247)
>   {USER} opened file Personal Folders.pst read=Yes write=No (numopen=2)
> [2003/12/05 11:59:53, 2] smbd/close.c:close_normal_file(229)
>   {DOMAIN}\{USER} closed file Personal Folders.pst (numopen=1)
> [2003/12/05 11:59:53, 2] smbd/open.c:open_file(247)
>   {USER} opened file Personal Folders.pst read=Yes write=No (numopen=2)
> [2003/12/05 11:59:53, 2] smbd/close.c:close_normal_file(229)
>   {DOMAIN}\{USER} closed file Personal Folders.pst (numopen=1)
>
> This is on an ext3 filesystem mounted (rw,acl,quota).
>
> This user is the only one that has opened this file according
> to the level 2 logs.
>
> Smbstatus for that file shows:
> DenyMode: DENY_WRITE
> Access: 0x2019f
> R/W: RDWR
> Oplock: None
>
> I have the following global options in my smb.conf because in the past I
> heard of problems without them.  Is it likely that one of these is the
> root of the errors?
> # grep lock /etc/samba/smb.conf
>         kernel oplocks = No
>         blocking locks = No
>         locking = No
>         oplocks = No
>         level2 oplocks = No
>
> Thanks for any help,
> ~ Daniel
>
>
>
>
>
>
> -----------------------------------------------------------------------
>
> This message is the property of Time Inc. or its affiliates. It may be
> legally privileged and/or confidential and is intended only for the use
> of the addressee(s). No addressee should forward, print, copy, or
> otherwise reproduce this message in any manner that would allow it to be
> viewed by any individual not originally listed as a recipient. If the
> reader of this message is not the intended recipient, you are hereby
> notified that any unauthorized disclosure, dissemination, distribution,
> copying or the taking of any action in reliance on the information
> herein is strictly prohibited. If you have received this communication
> in error, please immediately notify the sender and delete this message.
> Thank you.
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>