Files Locked for editing - who is at fault?

[meBrian]

We are running Netware 6 with all versions of windows since 98 connecting for file services. We are regularly seeing files which remain locked after they have been closed and the user has logged off. Some of these files have been locked for several months and through multiple restarts of the server. When attempting to open the file the message states 'Filename is locked for editing' by user Username. Also, there are no temp files in the directory where the locked file resides. This problem is occuring with MS Office files.

Is this a Novell problem or Microsoft, or both?
I've read about disabling File Caching. Is this a worthwhile attempt at correcting this? Any known fixes?
Suggestions welcome.

 

[Ghostalker623]

Im sure you have tried this, but under the monitor.nlm program you can view who has files open. Its called File Open Lock Activity.

Are these MS Database files? We get this routinely and had to tweak some settings. Are you talking about record locking errors that you see on the console screen?

 

[hmjones]

Did you ever resolve this problem? If so, can you please tell me what you did to resolve it? I am running into the same situation. Thanks, Heath.

 

[meBrian]

hmjones -
we have seen a moderate level of success while in the process of upgrading desktops to XP. We have less than 3% of PCs below windows 2k. Additionally, we have completed a migration from office 97 to office xp. Which change fixed it, I can't be sure as these things happened at the same time. We still have locking problems but not nearly as often. The locked file is being passed off to the next person using the same connection # on the novell box. By clearly that connection manually (2000/XP will reconnect automatically, generally without error) the problem is solved. Good luck. Let me know if you have more questions.