Jump to content

Repeated hassles moving large file...?


Recommended Posts

Guest Kenneth
Posted

Howdy,

 

I run XP Pro on one machine, and Win 2000 on another.

 

On the XP system, I have a few large (8-9 gig) files that I

want to move to the 2000 box over our lan.

 

When I try to cut and paste, I see the progress bar, and the

estimate of 20 minutes or so to completion. Then, after

three or four minutes, the estimate drops to 16-17 minutes,

as we would expect.

 

But...

 

Shortly thereafter, the estimate starts to climb, eventually

to about 90 minutes, and there it remains.

 

If I simply wait, the XP machine eventually hangs with a

blank screen (right clicking to attempt to refresh does

nothing) and I then reboot.

 

All this has happened, as I have described, four times.

 

I have not seen anything like this before, so what might be

causing this sort of difficulty, and is there a better

approach to moving those files?

 

Sincere thanks,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest Shenan Stanley
Posted

Re: Repeated hassles moving large file...?

 

Kenneth wrote:

> I run XP Pro on one machine, and Win 2000 on another.

>

> On the XP system, I have a few large (8-9 gig) files that I

> want to move to the 2000 box over our lan.

>

> When I try to cut and paste, I see the progress bar, and the

> estimate of 20 minutes or so to completion. Then, after

> three or four minutes, the estimate drops to 16-17 minutes,

> as we would expect.

>

> But...

>

> Shortly thereafter, the estimate starts to climb, eventually

> to about 90 minutes, and there it remains.

>

> If I simply wait, the XP machine eventually hangs with a

> blank screen (right clicking to attempt to refresh does

> nothing) and I then reboot.

>

> All this has happened, as I have described, four times.

>

> I have not seen anything like this before, so what might be

> causing this sort of difficulty, and is there a better

> approach to moving those files?

 

Howdy!

 

What is the file system being used on the Windows 2000 system that you are

copying these 8 to 9GB individual files to? Is it NTFS or FAT32 or FAT16

or...?

 

Do you have a file that is under 4GB in size that you can test with? (Out

of the file systems I mentioned - only NTFS will handle files over that

size. Given you are copying over a network shared connection and not direct

connect - I suppose it is plausible that it is never giving you an error.

Usually - if it was a problem like this - it would give you something about

being out of space.)

 

--

Shenan Stanley

MS-MVP

--

How To Ask Questions The Smart Way

http://www.catb.org/~esr/faqs/smart-questions.html

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

You can try to copy it with Robocopy, it should improve things. Look

for Robocopy on the Microsoft.com site. An even better utility to use

would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

Exchange Server.

 

John

 

Kenneth wrote:

> Howdy,

>

> I run XP Pro on one machine, and Win 2000 on another.

>

> On the XP system, I have a few large (8-9 gig) files that I

> want to move to the 2000 box over our lan.

>

> When I try to cut and paste, I see the progress bar, and the

> estimate of 20 minutes or so to completion. Then, after

> three or four minutes, the estimate drops to 16-17 minutes,

> as we would expect.

>

> But...

>

> Shortly thereafter, the estimate starts to climb, eventually

> to about 90 minutes, and there it remains.

>

> If I simply wait, the XP machine eventually hangs with a

> blank screen (right clicking to attempt to refresh does

> nothing) and I then reboot.

>

> All this has happened, as I have described, four times.

>

> I have not seen anything like this before, so what might be

> causing this sort of difficulty, and is there a better

> approach to moving those files?

>

> Sincere thanks,

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Thu, 22 May 2008 19:47:25 -0500, "Shenan Stanley"

<newshelper@gmail.com> wrote:

>Kenneth wrote:

>> I run XP Pro on one machine, and Win 2000 on another.

>>

>> On the XP system, I have a few large (8-9 gig) files that I

>> want to move to the 2000 box over our lan.

>>

>> When I try to cut and paste, I see the progress bar, and the

>> estimate of 20 minutes or so to completion. Then, after

>> three or four minutes, the estimate drops to 16-17 minutes,

>> as we would expect.

>>

>> But...

>>

>> Shortly thereafter, the estimate starts to climb, eventually

>> to about 90 minutes, and there it remains.

>>

>> If I simply wait, the XP machine eventually hangs with a

>> blank screen (right clicking to attempt to refresh does

>> nothing) and I then reboot.

>>

>> All this has happened, as I have described, four times.

>>

>> I have not seen anything like this before, so what might be

>> causing this sort of difficulty, and is there a better

>> approach to moving those files?

>

>Howdy!

>

>What is the file system being used on the Windows 2000 system that you are

>copying these 8 to 9GB individual files to? Is it NTFS or FAT32 or FAT16

>or...?

>

>Do you have a file that is under 4GB in size that you can test with? (Out

>of the file systems I mentioned - only NTFS will handle files over that

>size. Given you are copying over a network shared connection and not direct

>connect - I suppose it is plausible that it is never giving you an error.

>Usually - if it was a problem like this - it would give you something about

>being out of space.)

>

>--

>Shenan Stanley

> MS-MVP

 

Hi Shenan,

 

Both systems are NTFS...

 

When you suggest that I try with a file "under 4GB" I assume

that you are not asking that I try some tiny file. Am I

correct that you were asking me to try a file that is

"slightly" under 4GB?

 

Also, I know that there is lots of free space on the

receiving partition.

 

Thanks for any further thoughts...

 

All the best,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Thu, 22 May 2008 22:14:56 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

>

>Kenneth wrote:

>

>> Howdy,

>>

>> I run XP Pro on one machine, and Win 2000 on another.

>>

>> On the XP system, I have a few large (8-9 gig) files that I

>> want to move to the 2000 box over our lan.

>>

>> When I try to cut and paste, I see the progress bar, and the

>> estimate of 20 minutes or so to completion. Then, after

>> three or four minutes, the estimate drops to 16-17 minutes,

>> as we would expect.

>>

>> But...

>>

>> Shortly thereafter, the estimate starts to climb, eventually

>> to about 90 minutes, and there it remains.

>>

>> If I simply wait, the XP machine eventually hangs with a

>> blank screen (right clicking to attempt to refresh does

>> nothing) and I then reboot.

>>

>> All this has happened, as I have described, four times.

>>

>> I have not seen anything like this before, so what might be

>> causing this sort of difficulty, and is there a better

>> approach to moving those files?

>>

>> Sincere thanks,

>You can try to copy it with Robocopy, it should improve things. Look

>for Robocopy on the Microsoft.com site. An even better utility to use

>would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

>Exchange Server.

>

>John

 

Hi John,

 

Thanks for your suggestions...

 

I will try Robocopy tomorrow, but unfortunately don't have

access to an Exchange Server.

 

Might you know of another source?

 

All the best,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Thu, 22 May 2008 22:14:56 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

>

>Kenneth wrote:

>

>> Howdy,

>>

>> I run XP Pro on one machine, and Win 2000 on another.

>>

>> On the XP system, I have a few large (8-9 gig) files that I

>> want to move to the 2000 box over our lan.

>>

>> When I try to cut and paste, I see the progress bar, and the

>> estimate of 20 minutes or so to completion. Then, after

>> three or four minutes, the estimate drops to 16-17 minutes,

>> as we would expect.

>>

>> But...

>>

>> Shortly thereafter, the estimate starts to climb, eventually

>> to about 90 minutes, and there it remains.

>>

>> If I simply wait, the XP machine eventually hangs with a

>> blank screen (right clicking to attempt to refresh does

>> nothing) and I then reboot.

>>

>> All this has happened, as I have described, four times.

>>

>> I have not seen anything like this before, so what might be

>> causing this sort of difficulty, and is there a better

>> approach to moving those files?

>>

>> Sincere thanks,

 

>You can try to copy it with Robocopy, it should improve things. Look

>for Robocopy on the Microsoft.com site. An even better utility to use

>would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

>Exchange Server.

>

>John

 

 

Hi again John,

 

I just tried Robocopy, but can't seem to make it happy...

 

Because (full path) name of the file is rather long, I used

cut and paste to create the command entry. It looked fine to

me, but when I touched Enter, the command failed.

 

Might that be because I was using long filenames (with

spaces)?

 

Thanks for any further tips,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Thu, 22 May 2008 22:00:54 -0400, Kenneth

<usenet@soleSPAMLESSassociates.com> wrote:

>On Thu, 22 May 2008 22:14:56 -0300, "John John (MVP)"

><audetweld@nbnet.nb.ca> wrote:

>>

>>Kenneth wrote:

>>

>>> Howdy,

>>>

>>> I run XP Pro on one machine, and Win 2000 on another.

>>>

>>> On the XP system, I have a few large (8-9 gig) files that I

>>> want to move to the 2000 box over our lan.

>>>

>>> When I try to cut and paste, I see the progress bar, and the

>>> estimate of 20 minutes or so to completion. Then, after

>>> three or four minutes, the estimate drops to 16-17 minutes,

>>> as we would expect.

>>>

>>> But...

>>>

>>> Shortly thereafter, the estimate starts to climb, eventually

>>> to about 90 minutes, and there it remains.

>>>

>>> If I simply wait, the XP machine eventually hangs with a

>>> blank screen (right clicking to attempt to refresh does

>>> nothing) and I then reboot.

>>>

>>> All this has happened, as I have described, four times.

>>>

>>> I have not seen anything like this before, so what might be

>>> causing this sort of difficulty, and is there a better

>>> approach to moving those files?

>>>

>>> Sincere thanks,

>

>

>>You can try to copy it with Robocopy, it should improve things. Look

>>for Robocopy on the Microsoft.com site. An even better utility to use

>>would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

>>Exchange Server.

>>

>>John

>

>

>Hi again John,

>

>I just tried Robocopy, but can't seem to make it happy...

>

>Because (full path) name of the file is rather long, I used

>cut and paste to create the command entry. It looked fine to

>me, but when I touched Enter, the command failed.

>

>Might that be because I was using long filenames (with

>spaces)?

>

>Thanks for any further tips,

 

Hi again John,

 

I looked into this further and see that I need to enclose

the full path filenames in quotes.

 

'too tired now, but will try it tomorrow.

 

Thanks, as before,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Thu, 22 May 2008 21:35:53 -0400, Kenneth

<usenet@soleSPAMLESSassociates.com> wrote:

>On Thu, 22 May 2008 22:14:56 -0300, "John John (MVP)"

><audetweld@nbnet.nb.ca> wrote:

>

>>

>>Kenneth wrote:

>>

>>> Howdy,

>>>

>>> I run XP Pro on one machine, and Win 2000 on another.

>>>

>>> On the XP system, I have a few large (8-9 gig) files that I

>>> want to move to the 2000 box over our lan.

>>>

>>> When I try to cut and paste, I see the progress bar, and the

>>> estimate of 20 minutes or so to completion. Then, after

>>> three or four minutes, the estimate drops to 16-17 minutes,

>>> as we would expect.

>>>

>>> But...

>>>

>>> Shortly thereafter, the estimate starts to climb, eventually

>>> to about 90 minutes, and there it remains.

>>>

>>> If I simply wait, the XP machine eventually hangs with a

>>> blank screen (right clicking to attempt to refresh does

>>> nothing) and I then reboot.

>>>

>>> All this has happened, as I have described, four times.

>>>

>>> I have not seen anything like this before, so what might be

>>> causing this sort of difficulty, and is there a better

>>> approach to moving those files?

>>>

>>> Sincere thanks,

>

>>You can try to copy it with Robocopy, it should improve things. Look

>>for Robocopy on the Microsoft.com site. An even better utility to use

>>would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

>>Exchange Server.

>>

>>John

>

>Hi John,

>

>Thanks for your suggestions...

>

>I will try Robocopy tomorrow, but unfortunately don't have

>access to an Exchange Server.

>

>Might you know of another source?

>

>All the best,

 

Hi again John,

 

I have been experimenting with Robocopy, but right now, am

stuck...

 

I've learned about the need for double quotes to surround

long full path filenames, but then I try this command:

 

Robocopy "G:\Note05\Note05 Hold

BASE\3-5-08-Note05-APPS-7.tib" "\\Store\Store images

d\Note05\Note05 Hold Base\3-5-08-Note05-APPS-7.tib"

 

I get an error 123 "Accessing Source Directory

G:\Note05\Note05 Hold BASE\3-5-08-Note05-APPS-7.tib\

The filename, directory name, or volume label syntax is

incorrect."

 

The last thing I will mention is that I am using cut & paste

to enter those long filenames.

 

Might you have any suggestions to unknot this?

 

Sincere thanks, as before,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

Kenneth wrote:

> On Thu, 22 May 2008 21:35:53 -0400, Kenneth

> <usenet@soleSPAMLESSassociates.com> wrote:

>

>

>>On Thu, 22 May 2008 22:14:56 -0300, "John John (MVP)"

>><audetweld@nbnet.nb.ca> wrote:

>>

>>

>>>Kenneth wrote:

>>>

>>>

>>>>Howdy,

>>>>

>>>>I run XP Pro on one machine, and Win 2000 on another.

>>>>

>>>>On the XP system, I have a few large (8-9 gig) files that I

>>>>want to move to the 2000 box over our lan.

>>>>

>>>>When I try to cut and paste, I see the progress bar, and the

>>>>estimate of 20 minutes or so to completion. Then, after

>>>>three or four minutes, the estimate drops to 16-17 minutes,

>>>>as we would expect.

>>>>

>>>>But...

>>>>

>>>>Shortly thereafter, the estimate starts to climb, eventually

>>>>to about 90 minutes, and there it remains.

>>>>

>>>>If I simply wait, the XP machine eventually hangs with a

>>>>blank screen (right clicking to attempt to refresh does

>>>>nothing) and I then reboot.

>>>>

>>>>All this has happened, as I have described, four times.

>>>>

>>>>I have not seen anything like this before, so what might be

>>>>causing this sort of difficulty, and is there a better

>>>>approach to moving those files?

>>>>

>>>>Sincere thanks,

>>

>>>You can try to copy it with Robocopy, it should improve things. Look

>>>for Robocopy on the Microsoft.com site. An even better utility to use

>>>would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

>>>Exchange Server.

>>>

>>>John

>>

>>Hi John,

>>

>>Thanks for your suggestions...

>>

>>I will try Robocopy tomorrow, but unfortunately don't have

>>access to an Exchange Server.

>>

>>Might you know of another source?

>>

>>All the best,

>

>

> Hi again John,

>

> I have been experimenting with Robocopy, but right now, am

> stuck...

>

> I've learned about the need for double quotes to surround

> long full path filenames, but then I try this command:

>

> Robocopy "G:\Note05\Note05 Hold

> BASE\3-5-08-Note05-APPS-7.tib" "\\Store\Store images

> d\Note05\Note05 Hold Base\3-5-08-Note05-APPS-7.tib"

>

> I get an error 123 "Accessing Source Directory

> G:\Note05\Note05 Hold BASE\3-5-08-Note05-APPS-7.tib\

> The filename, directory name, or volume label syntax is

> incorrect."

>

> The last thing I will mention is that I am using cut & paste

> to enter those long filenames.

>

> Might you have any suggestions to unknot this?

 

Robocopy syntax can be a bit tricky. Robocopy is designed to copy whole

folders (many files), it doesn't accept single file names in the path,

for single files place the filename at the end, like so:

 

Robocopy "G:\Note05\Note05 Hold BASE" "\\Store\Store images

d\Note05\Note05 Hold Base" 3-5-08-Note05-APPS-7.tib

 

or

 

robocopy "x:\Folder Name" "\\Server Name\Share Name" "File Name.ext"

 

To copy all files by extension:

 

robocopy "x:\Folder Name" "\\Server Name\Share Name" *.ext

 

Don't leave hanging backslashes at the end of the paths:

 

robocopy "x:\Folder Name\" is incorrect and will error out.

 

> Sincere thanks, as before,

 

You're welcome.

 

John

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Fri, 23 May 2008 19:44:03 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

 

 

Hi John,

 

Please see my comments inline below...

>

>Robocopy syntax can be a bit tricky. Robocopy is designed to copy whole

>folders (many files), it doesn't accept single file names in the path,

>for single files place the filename at the end, like so:

>

>Robocopy "G:\Note05\Note05 Hold BASE" "\\Store\Store images

>d\Note05\Note05 Hold Base" 3-5-08-Note05-APPS-7.tib

 

When I tried the above as soon as I entered the string, it

started running. That is, it started to copy before I

entered the destination.

 

I get the idea of the quotes surrounding the path with the

individual file following, but might you provide the syntax

that would allow me to specify the destination?

 

I assume it would look something like this:

 

Robocopy "sourcePathHere" fileNameHere "destinationPathHere"

fileNameHere

 

but I can't get that far before it launches.

>

>or

>

>robocopy "x:\Folder Name" "\\Server Name\Share Name" "File Name.ext"

>

>To copy all files by extension:

>

>robocopy "x:\Folder Name" "\\Server Name\Share Name" *.ext

>

>Don't leave hanging backslashes at the end of the paths:

>

>robocopy "x:\Folder Name\" is incorrect and will error out.

>

 

I had not included the backslash. It did appear in the error

text however.

 

>

>> Sincere thanks, as before,

>

>You're welcome.

>

 

As before, many thanks,

 

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

Kenneth wrote:

> Hi John,

>

> Please see my comments inline below...

>

>>Robocopy syntax can be a bit tricky. Robocopy is designed to copy whole

>>folders (many files), it doesn't accept single file names in the path,

>>for single files place the filename at the end, like so:

>>

>>Robocopy "G:\Note05\Note05 Hold BASE" "\\Store\Store images

>>d\Note05\Note05 Hold Base" 3-5-08-Note05-APPS-7.tib

>

>

> When I tried the above as soon as I entered the string, it

> started running. That is, it started to copy before I

> entered the destination.

>

> I get the idea of the quotes surrounding the path with the

> individual file following, but might you provide the syntax

> that would allow me to specify the destination?

>

> I assume it would look something like this:

>

> Robocopy "sourcePathHere" fileNameHere "destinationPathHere"

> fileNameHere

 

 

No, this way:

 

ROBOCOPY source destination [file [file]...] [options]

 

Don't put the file name after the source, only put it after the

destination. Do ROBOCOPY /? for more help.

 

> but I can't get that far before it launches.

 

I don't know what you mean by that, you are doing this at the Command

Prompt? It only launches when you press <Enter>. If you are using the

GUI version you will have to experiment with it, I have little

experience with the GUI version.

> As before, many thanks,

 

Once again, you're welcome.

 

John

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Thu, 22 May 2008 22:05:25 -0400, Kenneth

<usenet@soleSPAMLESSassociates.com> wrote:

>On Thu, 22 May 2008 22:00:54 -0400, Kenneth

><usenet@soleSPAMLESSassociates.com> wrote:

>

>>On Thu, 22 May 2008 22:14:56 -0300, "John John (MVP)"

>><audetweld@nbnet.nb.ca> wrote:

>>>

>>>Kenneth wrote:

>>>

>>>> Howdy,

>>>>

>>>> I run XP Pro on one machine, and Win 2000 on another.

>>>>

>>>> On the XP system, I have a few large (8-9 gig) files that I

>>>> want to move to the 2000 box over our lan.

>>>>

>>>> When I try to cut and paste, I see the progress bar, and the

>>>> estimate of 20 minutes or so to completion. Then, after

>>>> three or four minutes, the estimate drops to 16-17 minutes,

>>>> as we would expect.

>>>>

>>>> But...

>>>>

>>>> Shortly thereafter, the estimate starts to climb, eventually

>>>> to about 90 minutes, and there it remains.

>>>>

>>>> If I simply wait, the XP machine eventually hangs with a

>>>> blank screen (right clicking to attempt to refresh does

>>>> nothing) and I then reboot.

>>>>

>>>> All this has happened, as I have described, four times.

>>>>

>>>> I have not seen anything like this before, so what might be

>>>> causing this sort of difficulty, and is there a better

>>>> approach to moving those files?

>>>>

>>>> Sincere thanks,

>>

>>

>>>You can try to copy it with Robocopy, it should improve things. Look

>>>for Robocopy on the Microsoft.com site. An even better utility to use

>>>would be ESEUTIL.EXE but you would have to get it (and ESE.DLL) from an

>>>Exchange Server.

>>>

>>>John

>>

>>

>>Hi again John,

>>

>>I just tried Robocopy, but can't seem to make it happy...

>>

>>Because (full path) name of the file is rather long, I used

>>cut and paste to create the command entry. It looked fine to

>>me, but when I touched Enter, the command failed.

>>

>>Might that be because I was using long filenames (with

>>spaces)?

>>

>>Thanks for any further tips,

>

>Hi again John,

>

>I looked into this further and see that I need to enclose

>the full path filenames in quotes.

>

>'too tired now, but will try it tomorrow.

>

>Thanks, as before,

 

Hi John,

 

Well, I finally succeeded, but with a wrinkle that I don't

understand:

 

On the source machine I have:

 

folder1 > folder2 > files 1-5

 

On the destination machine I had

 

folder1 > folder2(empty)

 

At a command prompt on the source box, I entered:

 

robocopy "sourcebox > folder1 > folder2" "destinationbox >

folder 1 > folder2"

 

and touched enter.

 

Robocopy started to do the deed.

 

When it finished, I looked over the result on the

destination box, and was surprised to see:

 

destinationbox > folder1 > files 1-5 > folder2 > files 1-5

 

so the five files I was trying to copy were, indeed, copied

to the intended folder (folder2) on the destination machine,

but the files were also put in folder1 which is above that

folder in the tree.

 

This is certainly no disaster... (I just deleted the extra

files), but I sure am curious.

 

Might you explain this to me?

 

Sincere thanks as before,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

Kenneth wrote:

> Hi John,

>

> Well, I finally succeeded, but with a wrinkle that I don't

> understand:

>

> On the source machine I have:

>

> folder1 > folder2 > files 1-5

>

> On the destination machine I had

>

> folder1 > folder2(empty)

>

> At a command prompt on the source box, I entered:

>

> robocopy "sourcebox > folder1 > folder2" "destinationbox >

> folder 1 > folder2"

>

> and touched enter.

>

> Robocopy started to do the deed.

>

> When it finished, I looked over the result on the

> destination box, and was surprised to see:

>

> destinationbox > folder1 > files 1-5 > folder2 > files 1-5

>

> so the five files I was trying to copy were, indeed, copied

> to the intended folder (folder2) on the destination machine,

> but the files were also put in folder1 which is above that

> folder in the tree.

>

> This is certainly no disaster... (I just deleted the extra

> files), but I sure am curious.

>

> Might you explain this to me?

 

Sorry for the delay, I missed the post amongst the others in the group.

 

I tried to replicate your "experiment" but couldn't with the syntax that

you suggested.

 

I create the following folder structure on my C:\ drive only:

 

Test\Test1

File1

File2

File3

File4

File5

 

I run the following command:

 

robocopy c:\test\test1 d:\test\test1

 

and the folder structure is copied to D:\ exactly as it is on C:\ with

files 1 to 5 in the test1 folder only.

 

Then I create an empty folder structure on D:\

 

D:\Folder\folder1

 

and I run the following:

 

robocopy c:\test\test1 d:\Folder\folder1

 

and the files 1 to 5 are copied to the folder1 only, so I can't see what

you did wrong.

 

By the way, was Robocopy faster at copying the large files?

 

John

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Wed, 28 May 2008 22:14:04 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

>and the files 1 to 5 are copied to the folder1 only, so I can't see what

>you did wrong.

>

>By the way, was Robocopy faster at copying the large files?

>

>John

 

Hi John,

 

There is certainly no need for any apology... I really

appreciate your help.

 

I can't see what I did wrong either, and can't replicate the

odd result I described.

 

And about speed:

 

I am not sure. Certainly there was no dramatic difference

that I noted.

 

But, when I tried to copy the files from the XP GUI the

results were failing to verify too frequently.

 

With Robocopy, the MD5 checksum always verified.

 

As before, thanks for the kind help,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

Kenneth wrote:

> On Wed, 28 May 2008 22:14:04 -0300, "John John (MVP)"

>>By the way, was Robocopy faster at copying the large files?

> I am not sure. Certainly there was no dramatic difference

> that I noted.

>

> But, when I tried to copy the files from the XP GUI the

> results were failing to verify too frequently.

>

> With Robocopy, the MD5 checksum always verified.

>

> As before, thanks for the kind help,

 

You're welcome.

 

John

  • 2 weeks later...
Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Wed, 28 May 2008 22:58:36 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

>>

>> As before, thanks for the kind help,

>

>You're welcome.

>

>John

 

Hi John,

 

As you will remember, you had pointed me in the direction of

ROBOCOPY as a tool for moving a bunch of large files (8-12

gig.)

 

I used it successfully, but am now having trouble that I is

confusing, to say the least.

 

Let's describe three of my systems as "X", "Y", and "Z."

 

I want to move files from "X" to "Z", but when I try to do

that using ROBOCOPY, at some point in the process, I get

Error 64 "The specified network name is no longer

available." (It does not offer the network name that has

"vanished.")

 

This occurred many times...

 

It seemed to me that I had a flaky NIC on either "X" or "Z."

(I will add that both of these systems are in use all

through the work day, and have displayed no problem whatever

prior to this.)

 

To narrow it down, I tried the same ROBOCOPY command but

with "Y" as the destination instead of "Z."

 

That worked perfectly, many times.

 

That seemed to indicate the problem is on "Z" and since I

had a spare NIC, I installed it on "Z" and hoped for the

best.

 

That did NOT correct the problem...

 

What might you suggest as next steps to sort this out?

 

Many thanks, as before,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

Kenneth wrote:

> Hi John,

>

> As you will remember, you had pointed me in the direction of

> ROBOCOPY as a tool for moving a bunch of large files (8-12

> gig.)

>

> I used it successfully, but am now having trouble that I is

> confusing, to say the least.

>

> Let's describe three of my systems as "X", "Y", and "Z."

>

> I want to move files from "X" to "Z", but when I try to do

> that using ROBOCOPY, at some point in the process, I get

> Error 64 "The specified network name is no longer

> available." (It does not offer the network name that has

> "vanished.")

>

> This occurred many times...

>

> It seemed to me that I had a flaky NIC on either "X" or "Z."

> (I will add that both of these systems are in use all

> through the work day, and have displayed no problem whatever

> prior to this.)

>

> To narrow it down, I tried the same ROBOCOPY command but

> with "Y" as the destination instead of "Z."

>

> That worked perfectly, many times.

>

> That seemed to indicate the problem is on "Z" and since I

> had a spare NIC, I installed it on "Z" and hoped for the

> best.

>

> That did NOT correct the problem...

>

> What might you suggest as next steps to sort this out?

>

> Many thanks, as before,

 

While this error may happen when you copy large files it is not caused

by Robocopy as such. Take a look in the Event Log to see if any errors

are logged around the same time as the network error 64.

 

John

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Fri, 06 Jun 2008 15:57:28 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

>Kenneth wrote:

>

>> Hi John,

>>

>> As you will remember, you had pointed me in the direction of

>> ROBOCOPY as a tool for moving a bunch of large files (8-12

>> gig.)

>>

>> I used it successfully, but am now having trouble that I is

>> confusing, to say the least.

>>

>> Let's describe three of my systems as "X", "Y", and "Z."

>>

>> I want to move files from "X" to "Z", but when I try to do

>> that using ROBOCOPY, at some point in the process, I get

>> Error 64 "The specified network name is no longer

>> available." (It does not offer the network name that has

>> "vanished.")

>>

>> This occurred many times...

>>

>> It seemed to me that I had a flaky NIC on either "X" or "Z."

>> (I will add that both of these systems are in use all

>> through the work day, and have displayed no problem whatever

>> prior to this.)

>>

>> To narrow it down, I tried the same ROBOCOPY command but

>> with "Y" as the destination instead of "Z."

>>

>> That worked perfectly, many times.

>>

>> That seemed to indicate the problem is on "Z" and since I

>> had a spare NIC, I installed it on "Z" and hoped for the

>> best.

>>

>> That did NOT correct the problem...

>>

>> What might you suggest as next steps to sort this out?

>>

>> Many thanks, as before,

>

>While this error may happen when you copy large files it is not caused

>by Robocopy as such. Take a look in the Event Log to see if any errors

>are logged around the same time as the network error 64.

>

>John

 

Hi John,

 

Thanks for your comments...

 

I was not suggesting that ROBOCOPY was causing the problems

at all. I assume that there is something else causing the

problem, and then choking ROBOCOPY.

 

That said, here's the status:

 

I tried the copy again, and after about 15% completion, it

stopped, but this time, with a different error:

 

"The semaphore timeout period has expired."

 

Next, I checked Event Viewer on the "source" system, and it

was clean.

 

Then, I went to the "destination" machine, but was surprised

to see it completely locked up. Even CNTL-ALT-DEL did

nothing.

 

I powered it down, then re-booted it, expecting to see

something interesting in its Event Viewer, but it, too, was

clean.

 

Then, I tried yet again...

 

This time, I tried copying a folder that held 5 files, each

of about 10 gig.

 

It took perhaps five minutes to get to 9.7% completion. At

that point, it appeared to have stopped.

 

I watched, and it took about 5 minutes to get to 9.8%, and

another five minutes to get to 9.9.

 

Unfortunately, at that point, I had to leave my office. I

left the copy effort running, and I assume that eventually

it will throw an error.

 

Thanks for any further thoughts,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest John John (MVP)
Posted

Re: Repeated hassles moving large file...?

 

 

 

Kenneth wrote:

> On Fri, 06 Jun 2008 15:57:28 -0300, "John John (MVP)"

> <audetweld@nbnet.nb.ca> wrote:

>

>

>>Kenneth wrote:

>>

>>

>>>Hi John,

>>>

>>>As you will remember, you had pointed me in the direction of

>>>ROBOCOPY as a tool for moving a bunch of large files (8-12

>>>gig.)

>>>

>>>I used it successfully, but am now having trouble that I is

>>>confusing, to say the least.

>>>

>>>Let's describe three of my systems as "X", "Y", and "Z."

>>>

>>>I want to move files from "X" to "Z", but when I try to do

>>>that using ROBOCOPY, at some point in the process, I get

>>>Error 64 "The specified network name is no longer

>>>available." (It does not offer the network name that has

>>>"vanished.")

>>>

>>>This occurred many times...

>>>

>>>It seemed to me that I had a flaky NIC on either "X" or "Z."

>>>(I will add that both of these systems are in use all

>>>through the work day, and have displayed no problem whatever

>>>prior to this.)

>>>

>>>To narrow it down, I tried the same ROBOCOPY command but

>>>with "Y" as the destination instead of "Z."

>>>

>>>That worked perfectly, many times.

>>>

>>>That seemed to indicate the problem is on "Z" and since I

>>>had a spare NIC, I installed it on "Z" and hoped for the

>>>best.

>>>

>>>That did NOT correct the problem...

>>>

>>>What might you suggest as next steps to sort this out?

>>>

>>>Many thanks, as before,

>>

>>While this error may happen when you copy large files it is not caused

>>by Robocopy as such. Take a look in the Event Log to see if any errors

>>are logged around the same time as the network error 64.

>>

>>John

>

>

> Hi John,

>

> Thanks for your comments...

>

> I was not suggesting that ROBOCOPY was causing the problems

> at all. I assume that there is something else causing the

> problem, and then choking ROBOCOPY.

>

> That said, here's the status:

>

> I tried the copy again, and after about 15% completion, it

> stopped, but this time, with a different error:

>

> "The semaphore timeout period has expired."

>

> Next, I checked Event Viewer on the "source" system, and it

> was clean.

>

> Then, I went to the "destination" machine, but was surprised

> to see it completely locked up. Even CNTL-ALT-DEL did

> nothing.

>

> I powered it down, then re-booted it, expecting to see

> something interesting in its Event Viewer, but it, too, was

> clean.

>

> Then, I tried yet again...

>

> This time, I tried copying a folder that held 5 files, each

> of about 10 gig.

>

> It took perhaps five minutes to get to 9.7% completion. At

> that point, it appeared to have stopped.

>

> I watched, and it took about 5 minutes to get to 9.8%, and

> another five minutes to get to 9.9.

>

> Unfortunately, at that point, I had to leave my office. I

> left the copy effort running, and I assume that eventually

> it will throw an error.

>

> Thanks for any further thoughts,

 

Without an Event ID error to hang this on I can only suggest basic

troubleshooting guides and possible causes to explore.

 

http://www.chicagotech.net/troubleshooting/systemerror64.htm

 

Advanced network adapter troubleshooting for Windows workstations

http://support.microsoft.com/kb/325487

 

You experience slow file server performance and delays occur when you

work with files that are located on a file server

http://support.microsoft.com/kb/822219/

 

The semaphore timeout error can also occur if the source drive is busy

being accessed by other third party applications, for example AV

software scanning or filtering can cause the error, try disabling your

AV software.

 

How to temporarily deactivate the kernel mode filter driver in Windows

http://support.microsoft.com/kb/816071/

 

John

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Sat, 07 Jun 2008 00:03:26 -0300, "John John (MVP)"

<audetweld@nbnet.nb.ca> wrote:

>

>Without an Event ID error to hang this on I can only suggest basic

>troubleshooting guides and possible causes to explore.

>

>http://www.chicagotech.net/troubleshooting/systemerror64.htm

>

>Advanced network adapter troubleshooting for Windows workstations

>http://support.microsoft.com/kb/325487

>

>You experience slow file server performance and delays occur when you

>work with files that are located on a file server

>http://support.microsoft.com/kb/822219/

>

>The semaphore timeout error can also occur if the source drive is busy

>being accessed by other third party applications, for example AV

>software scanning or filtering can cause the error, try disabling your

>AV software.

>

>How to temporarily deactivate the kernel mode filter driver in Windows

>http://support.microsoft.com/kb/816071/

>

>John

 

Hi John,

 

Many thanks, as before...

 

We shall see,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

Guest windmap
Posted

Re: Repeated hassles moving large file...?

 

If possible Connect the Y Network cable to Z then try copying the file

again.See if its works.I would also recommended to disable the Scan Network

Drives feature in target computers Antivirus protection.

 

"Kenneth" <usenet@soleSPAMLESSassociates.com> wrote in message

news:90ui44hjcrfrmfguqlj5te0u5l40hm5df1@4ax.com...

> On Wed, 28 May 2008 22:58:36 -0300, "John John (MVP)"

> <audetweld@nbnet.nb.ca> wrote:

>

>>>

>>> As before, thanks for the kind help,

>>

>>You're welcome.

>>

>>John

>

> Hi John,

>

> As you will remember, you had pointed me in the direction of

> ROBOCOPY as a tool for moving a bunch of large files (8-12

> gig.)

>

> I used it successfully, but am now having trouble that I is

> confusing, to say the least.

>

> Let's describe three of my systems as "X", "Y", and "Z."

>

> I want to move files from "X" to "Z", but when I try to do

> that using ROBOCOPY, at some point in the process, I get

> Error 64 "The specified network name is no longer

> available." (It does not offer the network name that has

> "vanished.")

>

> This occurred many times...

>

> It seemed to me that I had a flaky NIC on either "X" or "Z."

> (I will add that both of these systems are in use all

> through the work day, and have displayed no problem whatever

> prior to this.)

>

> To narrow it down, I tried the same ROBOCOPY command but

> with "Y" as the destination instead of "Z."

>

> That worked perfectly, many times.

>

> That seemed to indicate the problem is on "Z" and since I

> had a spare NIC, I installed it on "Z" and hoped for the

> best.

>

> That did NOT correct the problem...

>

> What might you suggest as next steps to sort this out?

>

> Many thanks, as before,

> --

> Kenneth

>

> If you email... Please remove the "SPAMLESS."

Guest Kenneth
Posted

Re: Repeated hassles moving large file...?

 

On Sat, 7 Jun 2008 19:12:19 +0530, "windmap"

<windmap@gmail.com> wrote:

>If possible Connect the Y Network cable to Z then try copying the file

>again.See if its works.I would also recommended to disable the Scan Network

>Drives feature in target computers Antivirus protection.

>

 

Howdy,

 

Unfortunately, I can't do the cable switch but...

 

I have experimented with using ROBOCOPY /z and with that,

things seem much better.

 

All the best,

--

Kenneth

 

If you email... Please remove the "SPAMLESS."

×
×
  • Create New...