Word file save issue (11.0.5002.333)
Updated: 08 Jul 2010 | 11 comments
Word file deletes the file when we try to save existing Word documents on a server share.
XP Pro desktop.
Office 2003
Servers are MS Server2003
Documents all exist on server shares, various shares, various users.
When user attempts to do the following (after 1/1/2010, before that is OK):
Open existing Word 2003 documents from server share, edit said document, then SAVE document, Word pops up an error that it's unable to save due to a permissions error.
FURTHER and much worse is the fact that the document is DELETED or disappears in this transaction! It literally DISAPPEARS before your eyes when the error pops up.
I need your help:
Discussion Filed Under:
Comments
Do you have problem only with
Do you have problem only with Office 2003 only or other versions like Office 2007 having problem?
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
You need to further isolate
You need to further isolate and be able to reproduce this on a client WITHOUT SEP installed to rule out if it is or is not SEP.
Also making sure to remove SEP from the server hosting the file too just in case and test.
There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."
Check this discussion Word
Check this discussion
Word Cannot Complete the Save due to a file permission error
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
Also try by installing only
Also try by installing only av/as and try.
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
This also may be useful (It
This also may be useful (It is meant for MR4 but still u can give a try)
Failed to save Word files onto network share folder in MR4 clients
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
WOW - it would appear that We
WOW - it would appear that We aren't the only ones
The solution - turn off OPLOCKS at the file server.
Try it - bet is solves the issue................
I've spent OVER a year on this, and no one seems to believe it happens. (excpet a couple of folks at Symantec who can't explain it)
AND, we have the EXACT same configuration you are listing - same software, same SEP versions (although it's happened from December **2008** (that's an EIGHT, not a NINE) to now and all version of SEP in between)
If I turn oplocking back on, we lose documents by the dozens, turn it off, all is well except some speed issues
We turned off oplocking in January 2009 to "get by" since no matter what we did with SEP it didn't help until we did this.
This reg file turns it off:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"EnableOplocks"=dword:00000000
And NO, none of the KB docs helped, nothing Symantec has ever published has helped. I even had a tech on the phone for an afternoon one day, he was as baffled as we were. He even had us try some very little known things to change the was SEP worked - no change. Even with only the AV installed, same issue. Remove SEP, however, issue goes away.
My sites - http://theamcpages.com & http://antique-engines.com
Toy:
Shadow:
thank so much
thank so much
If you are on a Win2k8 server
If you are on a Win2k8 server with Vista and Win 7 clients, you CANNOT turn off opportunistic file locking. More of an FYI than anything... Perhaps the issue is resolved with newer flavors of Windows, but only time will tell.
There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."
I know - but he and we are
I know - but he and we are both on Server 2003.
With no file server sitting at 2008, I can't comment on any of them having issues.
I have to assume this is an issue only a few of us have to this date, and it's specific to XP clients and 2003 file servers.................................
To this day, there is no solution.
AND, it started mid-December, 2008 for us. All of a sudden.
Was it a SEP upgrade, or the MS patch for IE that did it?
My sites - http://theamcpages.com & http://antique-engines.com
Toy:
Shadow:
My post was more of an fyi
My post was more of an fyi not a solution...
but back to your point... Oct '08 was MR3 and Jan'09 was MR4... Dec '08, i have no clue?
There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."
Same issue, but not on 2008 Server
In my organization, we have also seen this same issue with oplocks on our 2003 servers, but luckily it has not affected our 2008 servers. But, another difference, we run Vista and 7 clients, which default to SMB v2 when connecting to a 2008 server. XP clients still use SMB v1, which would probably still have the oplock issue. This was one of the reasons we accelerated our upgrade off of XP and 2003 server.
Would you like to reply?
Login or Register to post your comment.