FileZilla Forums

I'm using Filezilla to download a backup of files from an online server.
Works fine for majority of files, but some have error "Failed to open <filename> for writing".
Any clues anyone?

Could you post the filename of a file that is failing? Maybe there are characters in the filename not allowed on your target system, like <|>:/\?*, just to name a few. A further possibility would be executable files that will be blocked by Vista's UAC in some directories.

Thanks for the response boco.
The image below shows a snapshot of some of the failed transfers...
Gez

Well that rules out the filename theory, perfectly standard filenames. It could be an antivirus scanner, all extensions in your picture are real-time-scanned by default.

I have still not been able to resolve this.

As a test I tried downloading to an alternative folder sitting directly under desktop:
- the remote folder was public_html/administrator
- the local folder was C:\Users\Gerard\Desktop\TemporaryFilezillaTransfer\

And this works fine - all files transfer successfully.

However, when I specify the preferred location, there are problems:
- the remote folder was public_html/administrator
- local folder was C:\Users\Gerard\Documents\2009 My Documents\Business\Wearing The Hat\Administration\Corporate Identity\New Website\Website Backups\WebsiteBackup 2009-02-21\FoldersAndFiles\

Result: some files do not transfer successfully...

For example, file named config_system.php:
- successfully transfers to C:\Users\Gerard\Desktop\TemporaryFilezillaTransfer\administrator\components\com_config\views\application\tmpl
- fails to transfer to C:\Users\Gerard\Documents\2009 My Documents\Business\Wearing The Hat\Administration\Corporate Identity\New Website\Website Backups\WebsiteBackup 2009-02-21\FoldersAndFiles\public_html\administrator\components\com_config\views\application\tmpl\

But there does not seem to be anything wrong with this folder location as config_site.php transfers successfully to both locations in the same attempted filezilla operation - i.e. the folder location appears to be legitimate as other files are successfully written to it in the same operation, while the file itself must be legitimate as it successfully transfers to an alternative folder...

I'm very confused!

Any help, comments, or advice much appreciated.

Gez

Using 3.2.2.1?

My version shows 3.2.1, build date 2009-02-06

Get 3.2.2.1 and try again.

Unfortunately got the same results with 3.2.2.1

Full path too long, Windows only supports up to 255.

Due to a limitation/bug in the Windows APIs, the max. supported path length is 260 characters. This limit applies even to Windows Explorer.

Thank you both.
Time to simplify my backup directory structure!

I am getting the same error message. I am able to grab the files to my local under one path. But as soon as I changed my local path to a different location, I get the error message.

After checking different settings, I found that there is an option under the Edit menu for Directory access permissions. That path that works is already on that list. I had to add the new path to that Directory access list, too. After doing that, the files can get transferred to the new path without any error messages.

What you wrote has nothing to do with the original issue.

The Permissions in the Edit menu need to be adjusted only for FileZilla Pro purchased from the Apple Store, in order to overcome Apple's mandatory Sandbox feature.