Copying FIles Error

[Jim Heavey]

I have written a little application which copies files from one location to
another location.
Before it copies the file, it ensure the directory for both the from and to
locations is valid. It also ensures that the from file exists.

All that being successful, it attempts to copy the file, but each time I get
an exception in which the text of the message says "The process can not copy
the file XXXXXXXXX because it is being used by another process."

These files are just sitting on a shared drive and where they are being
copied to is on a shared drive. Not everyone of these files is currently
in-use and I would be surprised if any of the file are in-use by another
application/process/user.

So what is the real error here and what can I do to resolve this issue?

Thanks in advance for your assistance!!!!

[scott blood]

Jim,

How are you actually copying the files?????

Are you using the System.IO File.Copy method or are you copying the files
bit by bit after opening them internally.

I accidently once wrote a bug into an application that copied files, but
accidently left the file handles open and could not copy the files becuase
they were being accessed by another process, i.e., my application when it
was calculating the actual size of the file.

Regards

Scott Blood
C# Developer

"Jim Heavey" <Ji*******@discussions.microsoft.com> wrote in message
news:19**********************************@microsof t.com...

I have written a little application which copies files from one location to
another location.
Before it copies the file, it ensure the directory for both the from and
to
locations is valid. It also ensures that the from file exists.

All that being successful, it attempts to copy the file, but each time I
get
an exception in which the text of the message says "The process can not
copy
the file XXXXXXXXX because it is being used by another process."

These files are just sitting on a shared drive and where they are being
copied to is on a shared drive. Not everyone of these files is currently
in-use and I would be surprised if any of the file are in-use by another
application/process/user.

So what is the real error here and what can I do to resolve this issue?

Thanks in advance for your assistance!!!!

[vj]

This sure sounds like a FileHandle being not closed..

VJ

"Jim Heavey" <Ji*******@discussions.microsoft.com> wrote in message
news:19**********************************@microsof t.com...

I have written a little application which copies files from one location to
another location.
Before it copies the file, it ensure the directory for both the from and
to
locations is valid. It also ensures that the from file exists.

All that being successful, it attempts to copy the file, but each time I
get
an exception in which the text of the message says "The process can not
copy
the file XXXXXXXXX because it is being used by another process."

These files are just sitting on a shared drive and where they are being
copied to is on a shared drive. Not everyone of these files is currently
in-use and I would be surprised if any of the file are in-use by another
application/process/user.

So what is the real error here and what can I do to resolve this issue?

Thanks in advance for your assistance!!!!

[Jim Heavey]

Yes, I am using the System.IO.File.Copy to copy the files with the OverWrite
options.

[Jim Heavey]

My application does not open the files, it only performs the items which I
indicated previously. Check to see if the directory is valid on both the
from and to locations. And then it check the From File name to see if the
file exist. If all of those are true, it jus uses the System.IO.File.Copy
process to copy the file from one location to another with the "overwrite"
option of the copy method.

[vj]

Oh then... maybe the process that is writing the file is not releasing
handle properly... If your problem is intermittent as you have mentioned

VJ

"Jim Heavey" <Ji*******@discussions.microsoft.com> wrote in message
news:D0**********************************@microsof t.com...

My application does not open the files, it only performs the items which I
indicated previously. Check to see if the directory is valid on both the
from and to locations. And then it check the From File name to see if the
file exist. If all of those are true, it jus uses the System.IO.File.Copy
process to copy the file from one location to another with the "overwrite"
option of the copy method.

[Jim Heavey]

Turns out that I was using the same file name for both my from and to file to
copy.
Silly mistake, but atleast now I understand the error message which was
generated.