Click to See Complete Forum and Search --> : Can't delete a file....


Mike Burdick
10-23-2005, 03:59 AM
Okay..I was testing a perl script I wrote and have set up debug for the module SOAP::Lite such that it writes the output to a file. Well somehow it wrote this file named: ".pureftpd-rename.62036.8609d620". Well... I can't delete the darn thing! When I try to rename it, or delete it, or whatever, I get the message "550 Prohibited filename. Well...Duh! The

The file is in my directory at my web host. Any suggestions on how to get rid of this file? I'm using WS_FTP LE.

David Harrison
10-23-2005, 09:00 AM
Try renating an empty .txt file (including the file extension) to the same name as the file that won't be deleted, then try uploading it over the top of the old one. Sometimes if I've got a file that can't be deleted in Windows that what I do, not sure if it'll work over FTP but maybe.

Mattew79ITA
11-19-2005, 07:02 PM
If you have an account with a good hosting provider you'll have cpanel.
Log IN and USE your FTP File Manager. Delete the file or directory. It will function. i had the same problem. Now it works

Matteo www.italiasw.com

Mike Burdick
11-19-2005, 11:09 PM
Thanks!

That's how I eventually did it.

Mike

VinceC
06-04-2009, 11:13 PM
What do you do when it doesn't show up in your cPanel?

JunkMale
07-04-2009, 06:20 AM
What do you do when it doesn't show up in your cPanel?

You contact the web host and ask why and how you can remove it.

You may get a standard "Rubberwall" treatment, it is pretty normal to do this and I get fed up of it, I had to point out that a webalizer script was not of my concotion and that it was they who wrote it, this was after going to the webalizer user group and asking for help.

Even on the webalizer help I got the rubberwall treatment instead of the "Owner and Author" saying that the script is nothing to do with them, I spent 3 days of emails that needent have been, if you catch my drift.

This is why CS is so shabby all over the net, too many companys and people rubberwall your querys without giving you the reason. Eventually I got back to my host, pointed out the facts and then got the issue resolved within an hour. 3 days and 1 hour too much IMHO but it eventually got sorted.

So do not give up at the first hurdle.