Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Sharing violation / MS Office

  • Please log in to reply
No replies to this topic

#1 molecul3


  • Members
  • 16 posts
  • Local time:04:28 PM

Posted 27 October 2009 - 09:14 PM

Hi guys,

I am really hoping someone can help me on this...

Background - three users constantly receive the "Your changes could not be saved to 'file name.xls' because of a sharing violation. Try saving to a different file". It then changes the file name to a random alphanumeric name.

These normally happen to MS Office files (particularly Excel) sitting on a network file server and have been left opened overnight.

When this happens, we can see that the user will have multiple sessions open on the file server under Computer Management > Shared Folders > Sessions and one of those sessions will have an "Idle time" of almost the same amount of time when the next session starts. For example, if they have two sessions, one session will be have an Idle time of 9.04 hours and the second session would have a connected time of 9.04 hours. Both sessions have files open and normally when we see this "Idle time", it will lead to sharing violation errors.

Things we have done:
1. Turn off autodisconnect in the registry on the File server
2. Disable AV (Kaspersky AV 6.0) scanning on the folder where the file resides on the File Server
3. Disable AV on the client PC
4. Added KeepConn registry setting on the client PC
5. Updated NIC drivers on the client PC
6. Set NIC settings to never power off to save power

1. Could our backups be causing it? - we are running Veritas Backup Exec 9.1 with AOFO set to Microsoft VSS for backup on the file server
2. Could Volume Shadow Copy be causing it? - we run a Volume Shadow Copy of all shared drives on the file server twice a day
3. Could the AV be causing it? - I have heard of Symantec causing this problem but we are not using it on both client and server and it even happens when AV is disabled.

Any advice or help is very much appreciated.


Edited by garmanma, 28 October 2009 - 01:42 PM.
Added to title description

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users