How Kill Running Application Process

[Steve B.]

I think a user exited my local application incorrectly and now I can't
compile a new version of the application to the public network without
getting a "in use" error message. Also, can't rename or delete the exe
file/directory without "access denied"

How do I find out who/what is using the exe on my local network?
How can I kill the exe process because I don't see it on my machine?
How can I prevent this application error from occuring in the future?

I have a local IDE application written in Visual Studio in which I compile a
Release version of the application to the public network drive for users.

When I try to Release compile I get a the following error: Could not copy
temporary files to the output directory. The file 'assembly name' cannot be
copied to the run directory. The process cannot access the file because it is
being used by another process.

Copy Local = false is not the problem as described in
http://support.microsoft.com/default...b;en-us;313512

Steve

[Wessel Troost]

> I think a user exited my local application incorrectly and now I can't

compile a new version of the application to the public network without
getting a "in use" error message. Also, can't rename or delete the exe
file/directory without "access denied"

Use the "net file" command to see if a remote user has the file opened.
You can close the file with the same command, using the /CLOSE switch.

If that doesn't help, download
http://www.sysinternals.com/Utilities/Handle.html to check which process
has the file locked. Kill the process.

If even that doesn't help, change the security settings for the file so
that nobody has access to it, and reboot the machine. Give yourself
rights to delete the file then delete it.

Greetings,
Wessel

[Steve B.]

The net file command says "There are no entries in the list" and the handle
utility says it needs admin rights (I'm checking with IT now). In your third
point I assume you mean the server (machine)?

"Wessel Troost" wrote:

I think a user exited my local application incorrectly and now I can't
compile a new version of the application to the public network without
getting a "in use" error message. Also, can't rename or delete the exe
file/directory without "access denied"

Use the "net file" command to see if a remote user has the file opened.
You can close the file with the same command, using the /CLOSE switch.

If that doesn't help, download
http://www.sysinternals.com/Utilities/Handle.html to check which process
has the file locked. Kill the process.

If even that doesn't help, change the security settings for the file so
that nobody has access to it, and reboot the machine. Give yourself
rights to delete the file then delete it.

Greetings,
Wessel

[Wessel Troost]

> The net file command says "There are no entries in the list" and the

handle
utility says it needs admin rights (I'm checking with IT now). In your
third
point I assume you mean the server (machine)?

Yeah, all commands are for the server. The third option is really a "last
ressort" option tho. It's only required when some driver you can't stop
is locking the file.

The empty "net file" result suggests that the file is locked by a local
process, which is surprising for an executable on a file server. Perhaps
double-check from Administrative Tools -> Computer Management -> System
Tools -> Shared Folders -> Open Files.

Greetings,
Wessel

[Steve B.]

The shared folders/Opens files says "there are no items to show in this
view". I'm looking at Handle now not sure if I have permissions for usage.
Anything else?

"Wessel Troost" wrote:

The net file command says "There are no entries in the list" and the
handle
utility says it needs admin rights (I'm checking with IT now). In your
third
point I assume you mean the server (machine)?

Yeah, all commands are for the server. The third option is really a "last
ressort" option tho. It's only required when some driver you can't stop
is locking the file.

The empty "net file" result suggests that the file is locked by a local
process, which is surprising for an executable on a file server. Perhaps
double-check from Administrative Tools -> Computer Management -> System
Tools -> Shared Folders -> Open Files.

Greetings,
Wessel