Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What could be causing a windows 2003 file server to no longer release file locks? The locks are being created and not released by

  • Legacy vendor code (C++ I assume)
  • Legacy code, VB
  • Newer C# code

All with separate logging code (all locks are happening in logs so far). The problem has been steadily getting worse for the past month, and now is occurring multiple times a day. The only system wide change we've made recently (patches are staggered across affected and un-affected servers) is a storage change on the file server to CLARiiON. What could be causing the locks to not release as they are no longer used?

Related: Windows File Sharing Orphaned File Locks

share|improve this question

Please us unlocker assistance to check which process is locking the files. You can download it from

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.