Very strange FTP error

[codoherty]

I consistently receiving this error during FTP transfer, I cannot understand why? This path exists, the user has rights to the folder and I have 50GB free space available.

"Error copying xxx: Cannot open file "C:\WINDOWS\TEMP", The system cannot find the path specified."

[chrroe]

Hi Levelsoft!

This is a classic case for using the great tool Process Monitor from (ex-) Sysinternals. Download it at http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/processmonitor.mspx

Using it you can easily investigate any problems in the filesystem when running BC.


Bye
Christoph

[codoherty]

:confused: I have used this application for years now! But I don't see how this can help me in this instance, please expand :confused:

[chrroe]

Well, obviously BC has difficulties while accessing C:\WINDOWS\TEMP\...
Use the Process Monitor to watch BC's system-calls on the file-system. Let it highlight all entries which contain "C:\WINDOWS\TEMP\" and then you should be able to see the reason why BC cannot access this directory (Does not exist, permission denied, not enough space and so on).



Bye
Christoph

[codoherty]

This is the strange thing as per my first post, the folder does exist, it has admin rights and has 50GB available. I believe there is something else going a miss. Also I can see previous BC temporary files existing already in this folder.

I have a feeling this is something internal to BC, also I trying to sync anywhere between 3000 to 4000 files.

I should also mention that BC could be transferring files without problems, then all of a sudden strart thowing this message.

[chrroe]

Hmm, if the operating system gives a returncode to BC signalizing a failure, using Process Monitor is the best way to check, if BC probably doesn't handle the returncode right.

What results are shown by Process Monitor?
Which Windows version are you using?
What kind of filesystem is partition C: (NTFS, FAT32, ... )?


Bye
Christoph

[codoherty]

This is an automated sync process controlled by VisualBuild (www.kinook.com), running on a Win2003 SP1 with all NTFS drives. The BC sync process is being called from the command line.

It seem BC throws this error indiscriminately, so I have to wait until this error is thrown again to check with Process Monitor. Either way I can't see why the OS would throw such a strange error, it happens half way through the list of transfer files, with an abundance of disk space.

PS. Meant to mention before thanks for you help Christoph!

[WardXmodem]

1. I have to believe sysinternal's FILEMON was wanted, not PROCMON.

2. Is it possible an antivirus is intercepting file transfers, throwing stuff in temp, virus scanning, then moving them to their final destination? and that there is something wrong THERE, not with BC?

I guess I'll throw a semi-off-topic question here - when I had 1.2G free on my disk and downloaded a 700M ISO, it failed because "something" (blame Windows!) downloaded it to some "goofy place", not to where I wanted it, then in copying it from "goofy place" (I know where, I just feel like saying that) to my ultimate destination, it ran out of disk space (700x2 > 1.2G). Might that have been an antvirus? Or just some wack-o idea Windows has to slow down your system and waste time / space copying from "temp"?

(I'm a big XP fan, but there are certainly some things that bug me, like this)

[Craig]

Sorry Ward, that's BC wonkiness. It currently always downloads the file to a temp location and then copies it to the final destination. We're considering changing this in BC3.

[Chris]

Process Monitor is the correct tool. Filemon still works, but Process Monitor is a newer tool that combines the features of FILEMON and REGMON.