Failed to open <filename> for writing

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
GPRyan
504 Command not implemented
Posts: 6
Joined: 2009-02-12 16:00
First name: Gerard
Last name: Ryan

Failed to open <filename> for writing

#1 Post by GPRyan » 2009-02-12 16:04

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?

User avatar
boco
Contributor
Posts: 25501
Joined: 2006-05-01 03:28
Location: Germany

Re: Failed to open <filename> for writing

#2 Post by boco » 2009-02-12 20:58

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.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

GPRyan
504 Command not implemented
Posts: 6
Joined: 2009-02-12 16:00
First name: Gerard
Last name: Ryan

Re: Failed to open <filename> for writing

#3 Post by GPRyan » 2009-02-12 22:01

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

Image

User avatar
boco
Contributor
Posts: 25501
Joined: 2006-05-01 03:28
Location: Germany

Re: Failed to open <filename> for writing

#4 Post by boco » 2009-02-12 22:13

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.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

GPRyan
504 Command not implemented
Posts: 6
Joined: 2009-02-12 16:00
First name: Gerard
Last name: Ryan

Re: Failed to open <filename> for writing

#5 Post by GPRyan » 2009-02-22 18:42

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

User avatar
botg
Site Admin
Posts: 33425
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Failed to open <filename> for writing

#6 Post by botg » 2009-02-22 23:59

Using 3.2.2.1?

GPRyan
504 Command not implemented
Posts: 6
Joined: 2009-02-12 16:00
First name: Gerard
Last name: Ryan

Re: Failed to open <filename> for writing

#7 Post by GPRyan » 2009-02-23 11:36

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

User avatar
botg
Site Admin
Posts: 33425
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Failed to open <filename> for writing

#8 Post by botg » 2009-02-23 12:00

Get 3.2.2.1 and try again.

GPRyan
504 Command not implemented
Posts: 6
Joined: 2009-02-12 16:00
First name: Gerard
Last name: Ryan

Re: Failed to open <filename> for writing

#9 Post by GPRyan » 2009-02-23 12:15

Unfortunately got the same results with 3.2.2.1

User avatar
botg
Site Admin
Posts: 33425
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Failed to open <filename> for writing

#10 Post by botg » 2009-02-23 18:30

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

User avatar
boco
Contributor
Posts: 25501
Joined: 2006-05-01 03:28
Location: Germany

Re: Failed to open <filename> for writing

#11 Post by boco » 2009-02-24 08:39

Due to a limitation/bug in the Windows APIs, the max. supported path length is 260 characters. This limit applies even to Windows Explorer.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

GPRyan
504 Command not implemented
Posts: 6
Joined: 2009-02-12 16:00
First name: Gerard
Last name: Ryan

Re: Failed to open <filename> for writing

#12 Post by GPRyan » 2009-02-25 23:29

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

knittingguy
500 Command not understood
Posts: 1
Joined: 2021-04-02 23:41

Re: Failed to open <filename> for writing

#13 Post by knittingguy » 2021-04-02 23:59

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.

User avatar
boco
Contributor
Posts: 25501
Joined: 2006-05-01 03:28
Location: Germany

Re: Failed to open <filename> for writing

#14 Post by boco » 2021-04-06 13:44

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.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

Post Reply