"Toni Fontenele" <(E-Mail Removed)> wrote in message
news:eC%(E-Mail Removed)...
> Paul,
>
> Mark,
>
> I post a lot of messages here, in the past, about a problem like yours and
> until now
> I did not fin any solution. Here, is my discovers about it:
>
> We have two Windows 2000 Servers with SP3. One of them are presenting a
> well-known message, when we try to delete a folder: "Error Deleting File
or
> Folder. Cannot delete "folder": There has been a sharing violation. The
> source or destination file may be in use."
>
> I made a research through Newsgroups around the Internet and I found that
> explorer.exe is locking that folder. People outhere tell us to restart
> Windows and delete the folder, after logon. It works but it is very boring
> to restart the computer every time we have a locked file or folder.
>
> As an workaround to prevent a restart, I found a great free utility called
> WhoLockMe (http://www.dr-hoiby.com/WhoLockMe/) for Win2K. WhoLockMe is a
> little extension for your Microsoft Explorer. It permeets you to list all
> the process locking your selected file. So I started to use it to unlock
any
> folder handled by explorer.exe, just killing its process.
If you really just want to kill explorer, you can use task manager.
However, you don't really need to kill explorer.
http://www.SysInternals.com has a nifty program called Process Explorer.
You can search it for a specific handle, then force the handle closed. Do
this only with files, and only if you have to. I've found that if I have an
open handle due to having opened a folder, if I navigate to someplace else,
explorer will often close the handle, and I don't need to force it closed.
Phil
--
Philip D. Barila Windows DDK MVP
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.
E-mail address is pointed at a domain squatter. Use reply-to instead.