Script freezes during file copy

[grittyminder]

I can't figure out what's going on here. I'm using the FSO to copyFile a file from a remote server to a local machine. The destination file exists (there is error checking to ensure that this is true) as does the destination directory. The weird part is that the CopyFile function hangs freezing the script. I have error checking on after the function call but no error is ever thrown. Here is the script snippet:

FSO.CopyFile sourcePath, tempPath, true
If err.number <> 0 Then
str = "Failed to copy " & sourcePath & " to temporary directory!"
WScript.Echo(str)
WshShell.LogEvent 1, str
Err.Clear
exit function
end If
WScript.Echo("Finished.")

Of course "Finished" is never printed out either. I also tried using the file.Copy function to no avail. Any suggestions?

 

[mrmovie]

hmm, ok, where have you got, On Error Resume Next?
If it is at the top of your script and code you ahve posted is in a sub and you dont have On Error Resume Next in the sub as well then you as soon as your sub with the CopyFile method runs into an error it will exit out of the sub and never run the rest of the code...so, you will need to put on error resume next into your Sub as well..

i take it it hangs on particular file?
have you tried to copy the file in the GUI? what happens then?
have you tried to copy the file in DOS? copy command or xcopy etc?

 

[grittyminder]

Thanks for the reply. Okay, I guess that I had On Error Resume Next OFF (a detail that I probably shouldn't have left out). So I guess that if there was some sort of error thrown then the script would have halted execution immediately. I followed your suggestions and tried copying the file in the GUI and in DOS. Both of these attempts were successful. I'm going to try using WshShell.Run w/ a copy command (instead of the vbscript copy) to see if that works right now...

 

[grittyminder]

xcopy seems to work. So I'm wondering why the vbscript CopyFile function didn't work...?

 

[mrmovie]

its a funny one then grittyminder, if you had On Error Resume Next OFF then the

If Err.Number <>

code should never have been run. instead (providing you didnt have On error resume next further up the script) you should have seen a popup on the screen.

how is your script being executed?

 

[grittyminder]

Yes, you are right. The code in the if Err.Number was never run (because on error resume next was off). However, the code following the (unneccessary) error checking was never run either (i.e. WScript.Echo("Finished.")) Essentially, the script was hanging on the FSO.CopyFile command. I tried substituting FSO.CopyFile with:

WshShell.Run "xcopy " & sourcePath & fileName & " "&tempPath, 0, true

...and every thing copied fine. So my question is, why didn't the vbscript CopyFile command work? I think that a separate application may have been intermittedly writting to the file that my script wastrying to copy. Also, the length of the file was very, very, very long.

 

[tsuji]

>[tt]FSO.CopyFile sourcePath, tempPath, true[/tt]
>[tt]WshShell.Run "xcopy " & sourcePath & fileName & " "&tempPath, 0, true[/tt]
why is sourcepath in the copyfile without filename?