Student Tip: Stopping WinSCP filepart errors
Last week a student on my course gave me a tip. Personally, I perfer to use Veeam’s FastSCP for ESX Server when transferring files from my Windows Desktop to ESX 3. However, occasionally in the lab environments I work in I have to use WinSCP which is slower. One thing I have observed is if I copy a file such as an ISO to a VMFS volume, then WinSCP gives me an error. Basically, what happens is though the files get copied to the VMFS volume – and error occours when renaming the file from say – w2k3sp2.iso.filepart to w2k3sp2.iso. This is caused by the “Resume” feature in WinSCP which is intended to pickup an upload when it fails from where it failed, rather than starting the upload from the beginning. It appears as VMFS doesn’t support this functionality.
The solution to this problem is a work-around. To disable the “Resume” feature in the WinSCP software. I don’t mind doing this. Everything is gigabit in the lab environments I work in and very reliable so I don’t really need the resume feature. To disable the WinSCP “Resume” feature do the following:
In the menu choose, Options and Preferrences
Under Transfer, select Resume
Under “Enable transfer resume for”, select Disable
Under “Automatic Reconnect“, disable “Automatic reconnect session, if it breaks during transfer“
RSS
iTunes
October 1st, 2007 at 2:37 pm
[...] dr.scott.mcleod@gmail.com (Scott McLeod) wrote an interesting post today on Student Tip: Stopping WinSCP filepart errorsHere’s a quick excerpt [...]
October 4th, 2007 at 2:32 am
[...] Student Tip: Stopping WinSCP filepart errors mikelaverick Mon, 01 Oct 2007 12:09:50 GMT [?] Share This Popularity: 1% [?]Tags: VMWARE, Technology [...]
June 4th, 2008 at 7:36 pm
[...] Running the latest version of ESX3.5 enables a lot of usability enhancements in the VI Client. Many of the administrative tasks and configurations previously performed on the Service Console or by third party tools are now accessible as new options directly from the GUI. For example, you previously could not use the Datastore Browser to upload files such as ISOs to the ESX hosts, but instead had to use a tool such as WinSCP or other similar methods. With the ESX3.5 VI Client you can now transfer files right from the client. What makes this native ability even cooler is the fact that you no longer have to enable remote root access or create a special user. If you connect the VI Client to VirtualCenter as a local administrator, or if you connect to the ESX host as root you can use the VI Client to upload files without any other configurations. [...]