I am having a problem that I have been having since build 1317. I just downloaded the current version and installed over the previous version and the issues are still happening.
I am trying to upload to a Linux server over SSH:
Resolving "67.15.64.5"
Connecting to 67.15.64.5 port 22
Connected socket #2084 to 67.15.64.5 port 22
Server version: SSH-1.99-OpenSSH_3.6.1p2
version: SSH-2.0-SSH-Local: Sep 23 2004 18:47:58
Using SSH protocol version 2
processing group exchange
processing key exchange
Host key fingerprint is:
ssh-rsa 1024 da:bd:e2:aa:a1:4f:b3:ea:56:c1:2b:98:d9:64:71:7e
Initialized AES-256 client->server encryption
Initialized AES-256 server->client encryption
Keyboard-interactive authentication refused
Sent password
Access granted
Opened channel for session
Started shell session
Sometimes when I try to upload a file I get this message:
STOR /home/choice/www/user/index.php
WARNING: Zero length file...
Transfer time: 00:00:00
STOR /home/choice/www/user/_NavCClt.Log
WARNING: Zero length file...
Transfer time: 00:00:00
STOR /home/choice/www/user/VPSCAN.INI
WARNING: Zero length file...
Transfer time: 00:00:00
The files are not empty. Normally I transfer files that are stored on a networked machine through a mapped drive but the above examples were local files.
Attempting the transfer twice usually results in a run-time exception, where the masochistic Core FTP 'requests the Runtime to terminate it in an unusual way'. Sounds kinky. This error doesn't always wait for the second time, currently I can open the program, connect to the server, transfer a single file and get the crash. No information is displayed in CoreFTP before the error occurs, and a replace dialog box is not displayed. Most of what I transfer are PHP files that give me the repetitive errors. This happens after a reboot as well.
I can see no information in the event viewer about this and I cannot see any log files for CoreFTP.
Any assistance would be appreciated, obviously I can't really get any use out of the program with this behavior. Thanks.
SFTP file upload errors
Those three local files I showed were not open by anything, just random files in C: I tested with.
The PHP files I mostly attempt to transfer are open with a text editor only which I know does not open anything exclusively. The text editor in question is ConTEXT from context.cx. Closing ConTEXT altogether has no effect.
I am using this on a Win 2000 pro machine and the files are across the network on NT4 SP6 (don't ask).
I've also got a separate issue with choosing a folder which may or may not be related - I choose a previous folder from the dropdown which contains the files I am trying to transfer. The folder is located on a share across the network via a mapped drive and is of the form W:\wwwroot\inetpub...etc, 4 levels deep. If I click it in the list, the local view doesn't change. If I then highlight it in the box and hit enter no change. If I remove the last folder to go to it's parent, still no change. In fact hitting enter in the folder name box doesn't appear to do anything at all, it doesn't even make the tooltip disappear. I have to hit the "go to parent" button 4 times (putting the path at W:) before either the folder name displayed or the local view changes, which it then does change to show the contents of W: and the correct path. To repeat that, hitting go to parent 3 times still displays the full path 4 folders deep, hitting once more shows W: and the correct contents. The same folder is in the local startup for the site and is not selected at connection. I can browse to the folder manually in Core FTP and in other apps, and it is my working folder in ConTEXT which does not have any problems.
The PHP files I mostly attempt to transfer are open with a text editor only which I know does not open anything exclusively. The text editor in question is ConTEXT from context.cx. Closing ConTEXT altogether has no effect.
I am using this on a Win 2000 pro machine and the files are across the network on NT4 SP6 (don't ask).
I've also got a separate issue with choosing a folder which may or may not be related - I choose a previous folder from the dropdown which contains the files I am trying to transfer. The folder is located on a share across the network via a mapped drive and is of the form W:\wwwroot\inetpub...etc, 4 levels deep. If I click it in the list, the local view doesn't change. If I then highlight it in the box and hit enter no change. If I remove the last folder to go to it's parent, still no change. In fact hitting enter in the folder name box doesn't appear to do anything at all, it doesn't even make the tooltip disappear. I have to hit the "go to parent" button 4 times (putting the path at W:) before either the folder name displayed or the local view changes, which it then does change to show the contents of W: and the correct path. To repeat that, hitting go to parent 3 times still displays the full path 4 folders deep, hitting once more shows W: and the correct contents. The same folder is in the local startup for the site and is not selected at connection. I can browse to the folder manually in Core FTP and in other apps, and it is my working folder in ConTEXT which does not have any problems.
Should I be looking at filesystem performance to solve this? For example, if the app makes a request for a specific file from a networked machine, and doesn't get a response back in a certain amount of time, does it just assume it can't open the file? Is there a time limit on that sort of thing, or will the app wait for a response?
I forgot one other thing.
I realize the 0 byte message means it couldn't open the file, but what about the crashes? The way the behavior is now, I can open the app, connect to the server, browse to a specific folder, upload a specific 4kb file that has worked in the past, and get the crash before the replace dialog. I can do this all day and it will keep doing the same. I can upload files near the target one (parent folders or other subfolders of the same depth) with no problems. I can even upload another 4kb file from the same source and destination folders with no problem.. why would it have a problem with another arbitrary file? All of my file are text files created with the same editor.
I realize the 0 byte message means it couldn't open the file, but what about the crashes? The way the behavior is now, I can open the app, connect to the server, browse to a specific folder, upload a specific 4kb file that has worked in the past, and get the crash before the replace dialog. I can do this all day and it will keep doing the same. I can upload files near the target one (parent folders or other subfolders of the same depth) with no problems. I can even upload another 4kb file from the same source and destination folders with no problem.. why would it have a problem with another arbitrary file? All of my file are text files created with the same editor.
I should make a note about the zero length file error. The ansi version did indeed stop the runtime errors.
I got in to work this morning and started Core FTP and went to upload a file, and got the zero byte message. The procedure was like this:
Start app
Connect to server (loads remote start folder and shows the last local folder I was viewing)
Upload file - zero length error
The file is across the network located on a mapped drive. After the first zero error, I used the "go to parent" button to go up 4 folder levels to the root of my mapped drive, and then manually navigated back to my file. The second upload worked fine. I also verified that right-clicking the file and selecting properties the first time showed 0 bytes, and the second time showed the correct size after I manually navigated.
I'm not sure what the exact problem is, but it looks like if the files are not local Core FTP does not refresh the listing or something like that to get the file sizes, I had to do it manually. Hopefully this helps with debugging. I can provide more info if necessary.
I got in to work this morning and started Core FTP and went to upload a file, and got the zero byte message. The procedure was like this:
Start app
Connect to server (loads remote start folder and shows the last local folder I was viewing)
Upload file - zero length error
The file is across the network located on a mapped drive. After the first zero error, I used the "go to parent" button to go up 4 folder levels to the root of my mapped drive, and then manually navigated back to my file. The second upload worked fine. I also verified that right-clicking the file and selecting properties the first time showed 0 bytes, and the second time showed the correct size after I manually navigated.
I'm not sure what the exact problem is, but it looks like if the files are not local Core FTP does not refresh the listing or something like that to get the file sizes, I had to do it manually. Hopefully this helps with debugging. I can provide more info if necessary.
The mapped system:
Windows NT4 SP6 (4.00.1381)
640MB RAM
"Intel Family 6 Model 7 Stepping 3" - pretty sure that's a P-3, I think around 800-900MHz
NTFS SCSI RAID (Striped set with parity across 3 drives)
The drive I map to is locally the F drive, and contains the web root. My map points to F:\Inetpub, and is mapped on my machine as W:.
I am running on a Windows 2000 Pro machine with 900Mhz. Our network is 10/100 cat5, might be cat6 but I doubt it, most cabling is at least 5 years old. The network goes through a Cisco router and a 24-port switch, and the NT4 machine above I believe is multihomed, so it has 2 network cards, one on either side of the Cisco.
Windows NT4 SP6 (4.00.1381)
640MB RAM
"Intel Family 6 Model 7 Stepping 3" - pretty sure that's a P-3, I think around 800-900MHz
NTFS SCSI RAID (Striped set with parity across 3 drives)
The drive I map to is locally the F drive, and contains the web root. My map points to F:\Inetpub, and is mapped on my machine as W:.
I am running on a Windows 2000 Pro machine with 900Mhz. Our network is 10/100 cat5, might be cat6 but I doubt it, most cabling is at least 5 years old. The network goes through a Cisco router and a 24-port switch, and the NT4 machine above I believe is multihomed, so it has 2 network cards, one on either side of the Cisco.
Zero length file
Hi!
I also had the problem of zero length files, although the weren't opened by any other program.
After I found and read this thread, I realized that I typed the path to my local folder in the directory field instead of browsing there.
Although CoreFTP displayed the correct file sizes in the list, it couldn't find the files when i viewed the properties or tried to upload the file.
Please correct that bug!
I also had the problem of zero length files, although the weren't opened by any other program.
After I found and read this thread, I realized that I typed the path to my local folder in the directory field instead of browsing there.
Although CoreFTP displayed the correct file sizes in the list, it couldn't find the files when i viewed the properties or tried to upload the file.
Please correct that bug!