SEP and MS Word
I hate to bring up an old favorite, but I believe I have a new twist on an old dog. I have searched and read quite a bit on the web, Symantec's Platinum Site, this forum and have logged a case with Symantec about this item; "Clients cannot save Word documents to Local Storage". My SEP version, my issue and my environment differ from any entries I have yet read in all the above named sources. The particulars;
Issue at Hand - Users open Word, create a document, save it to local storage. Later, open the same document, make changes and save once again to local storage. Word app.notifies that; "A copy of this document is stored in a Document Workspace. Do you want to update the workspace copy with changes you make to your copy" yes or no answer irrelevant as the result is the same, this message; "Do you want to retry the save" - yes, message; "Word cannot complete the save due to a file permission error". The document is then unsaved and unrecoverable. No environmental changes to cause real permission issues and changes to permission levels would be other than our standard. This issue is hit and miss and may be just beginning to rear its ugly head. No clue how widespread it will be.
Environment
- SEP v.11.0.4000.2295
- Antivirus and Antispyware Protection - installed, active with policies in place
- Proactive Threat Protection - installed
- Network Threat protection - Installed, not enabled, simply a pass through at this time
- Application and Device Control Policy - No policy - not enabled
- Intrusion Prevention Policy - not enabled - no policy
- 1360 clients
- 6 occurrences of issue
Probably forgot something......... in a hurry, right where we all live - right? hope someone can add something to help. This could get rough!!
Comments
Case Number
I am looking into this. It would be helpful if you could post your case number as well. Thanks.
Grant-
Please don't forget to mark your thread solved with whatever answer helped you : )
I know this sounds crazy but
I know this sounds crazy but the local file system is not a FAT32 file system. I know hardly anyone uses this anymore, but I have seen people use it because they need to switch back and forth between Macs and PCs and this is the best medium to do so. I am still researching other possibilities.
Grant-
Please don't forget to mark your thread solved with whatever answer helped you : )
This may relate to PTP. Try
This may relate to PTP.
Try these two workarounds.
Workaround 1:
Check the application control policy,disable USB block or log polcy etc in SEPM.
Workaround 2:
Disable "scan for keylogger" option in SEPM or in client directly.
Thomas
SEP and MS Word
Grant - thanx for jumping in. re;
1) PTP - Picture Transport Protocol?
2) case number - do not have one - working through a Symantec TAM - case numbers never seem to enter the picture
3) workaround #1 - do not have any Application and Device control policies enabled
4) workaround #2 - where do I locate the keylogger setting?
1) PTP = Proactive Threat
1) PTP = Proactive Threat Protection - if you have it installed/enabled.
In other places, it's point-to-point among other things............... but the above is correct for SEP.
My sites - http://theamcpages.com & http://antique-engines.com
Toy:
Shadow:
yep - should of known that
yep - should of known that one - thanx
I have seen this on local USB
I have seen this on local USB drives as well as mapped network drives....never able to consistently reproduce. Only seems to impact Office though, never seen it in another app.
Anecdotally turning off "File cache" in AV policy SEEMED to help, but since I can never reproduce on demand I really don't know. Never had a case number either for the same reason, too tough to reproduce.
I have read and been advised
I have read and been advised of this issue with usb and nw drives, not getting much rhythum on local storage. Working with TAM, am now having customer complete many saves with Auto protect enabled and disabled and have been asked to send MS Process Monitor logs to TAM. My situation is like yours, I am unable to locate a machine that I can lay my hands on that will duplicate symptoms.
@thomas Here are a few
@thomas Here are a few worekarounds to try.
1. Disable application and device control policy, which has been applied onto clients.
2. Check the applied "application and device control" policy, make sure all rules of "application control" have been disabled. Meanwhile, you can enable device control.
3. Change the permession of shared folders, to "full control" for remote users.
Would you like to reply?
Login or Register to post your comment.