J
JW
Background: I recently upgraded my server's motherboard and thus had to do a
repair install of Win2000 Server. Prior to this I have kept the OS up to the
latest Microsoft updates. I have installed all available updates from
Microsoft via the "Windows Update" site.
I also have SQL 2000 and IIS running on this machine. It is behind a
firewall and is running Computer Associates My-Etrust virus scanner - also
up to date.
Since the repair install, once I write a file via a server shared folder,
that file is no longer writable. I get a file sharing violation (File is in
use). Using handle.exe from www.sysinternals.com, it appears that the System
process keeps the file open. I have closed every window that could be
accessing the folder/file and re-run System and the file is still listed as
open under System. This only appears to happen after a write using the
share. After that the file is unavailable via share or via direct.
If I reboot the system I can again write the file. But not after I again
write it via share!
Not sure what to look at next.
Wes
repair install of Win2000 Server. Prior to this I have kept the OS up to the
latest Microsoft updates. I have installed all available updates from
Microsoft via the "Windows Update" site.
I also have SQL 2000 and IIS running on this machine. It is behind a
firewall and is running Computer Associates My-Etrust virus scanner - also
up to date.
Since the repair install, once I write a file via a server shared folder,
that file is no longer writable. I get a file sharing violation (File is in
use). Using handle.exe from www.sysinternals.com, it appears that the System
process keeps the file open. I have closed every window that could be
accessing the folder/file and re-run System and the file is still listed as
open under System. This only appears to happen after a write using the
share. After that the file is unavailable via share or via direct.
If I reboot the system I can again write the file. But not after I again
write it via share!
Not sure what to look at next.
Wes