OK, I've had a case open with Symantec support, and was just told that no one else seems to be having this problem, and they have no further ideas except to run in unmanaged mode or upgrade to Endpoint Security (which we've tested and has some issues at the moment), so I'm hoping someone here has some productive ideas.
The scenario:
- around the end of November, 2 completely separate clients of ours starting having issues with a couple of machines each, where they would get intermittent "sharing violation" errors when updating and saving Excel spreadsheets in their "My Documents" folder, which in both sites is redirected to a share on a file server.
- one site is running 10.1.6, the other 10.0.1, both managed. The first site had just been upgraded, so originally I thought the upgrade was an issue, but shortly thereafter the site running 10.0.1 mentioned an issue, so that can't be it.
- both sites run Windows 2003 servers (one site runs Standard Edition, one runs SBS)
What I've tried to troubleshoot/resolve this:
- stopping the Symantec Antivirus service on the client PC makes this issue go away - no more sharing violations, so it definitely seems like something SAV-related
- I've tried removing network scanning from the AV client properties, no difference
- changed the user name that the local SAV service runs under to a domain admin, no difference
- run Windows and Office updates, no difference
- upgraded one of the clients to 10.1.7 *un*managed - no sharing violations
- uninstalled/reinstalled 10.1.7 on the same machine as *managed* - sharing violations came back
- there are no errors in the event logs of the client or server
At this point support told me there is nothing more to try, either go with an unmanaged client or upgrade to Endpoint Security, neither of which are great options.
The only thing I can think of is that a Windows Update released around the same time caused some sort of issue with SAV and the way it's accessing files - especially as it's happening with 2 completely different sub-versions of SAV - but I've searched and I don't see anyone else with this issue, so I'm not sure which update may have caused this. This issue looks remarkably similar to the one as described in the pre-XP-SP2 MS knowledge base article
http://support.microsoft.com/kb/328170 , but as all the clients I'm having issues with are post-SP2, and the registry key change suggested doesn't change anything, that's not it.
So, any ideas welcome at this point...
Message Edited by mabman on
01-02-2008 01:03 PM