I also think it is an Office issue, just wanted to see whatever one else thought before I fought for a Microsoft trouble call.
One part I forgot in the original message is that all tests were done on the same file, in the same location, with the same Office 2003 load and by the same user(me) with domain admin and root rights. The only change was the system the test was done on.
Mike
-----Original Message----- From: tmac [mailto:tmacmd@gmail.com] Sent: Thursday, March 29, 2007 9:10 AM To: Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: Re: CIFS share on a Unix filesystem and Office 2003
I am not positive, but this could be an issue with OFFICE.
MS apps routinely create a temp file (a tilde file) and when you save, it deletes the original and copies the tilde file into its' place.
This wrecks havoc with a NetApp using MIXED or UNIX qtrees. Since the original file is gone, the new file is written with new permissions.
Check the UNIX perms on the file and see if they are what you expect.
Maybe....you have you user mapping setup so your account maps to root? Then your file could be written with UID 0, and then you may not be able to access from Windows.
In the NTFS side, even though the UID is root, there is also an ACE that shows you as the owner (not root).
There is a fix in ONTAP, although I do not think it was introduced until 7.2. I think the option is "cifs.preserve_unix_security"
On 3/29/07, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I don't know if anyone can help but I thought I would ask.
We host home directories and common file storage on a FAS960 running OnTap 7.0.3 with CIFS and NFS licenses. We use NTFS shares for Windows
roaming profiles but everything else is a Unix filesystem shared by CIFS and NFS.
We had a problem show up when using Office 2003 with the Document Image Writer feature that I have not been able to track down.
Using XP or 2003 systems I can print to the Document Image Writer printer, open the file it creates, modify and then save the file with no problems.
On a 2000 Pro system I can create the file but I can not modify it after that from the Office 2003 MDI application. Whenever the file is opened you can make changes but you can not save the changes and there
are no errors or warnings generated. If the file is on a NTFS filesystem (NetApp or otherwise) you can make all of the changes you want. It is also
possible to
create the file on the NFS filesystem, copy it to a NTFS filesystem,
make
and save changes and then copy it back to the NFS filesystem properly.
I have done all of the normal research and have even done packet captures. Nothing indicates what the issue might be. Any thoughts or hints?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com