cannot delete aspnet_client folder

Discussion in 'FTP' started by Wingate, Feb 4, 2011.

  1. Hello,

    I can't seem to delete the aspnet_client folder. I get a 550 Access Denied error.
    I went in as far as I could in the folder structure and deleted some contents, but it seems the server really likes the aspnet_client-->system_web--->4_0_30319 folder.

    I checked permissions all are 777.

    How can I delete this folder?

    Thank you.
     
  2. Ray

    Ray

    It sounds like you are not inside your root folder. If you go outside of your root folder you may see a systems folder called asp_client. That is automatically created by the system when updates or patches to the server are installed. This has nothing to do with your application and it will not affect you or your root. But because you are outside of your root, you will not have permission to delete it. Make sure you are inside your root folder. You can only delete/read/write what is inside your root folder.
     
  3. The root folder is named after my account domain, correct? (first 8 letters)

    I have 3 subfolders in the root for websites and a web.config using rewrite to redirect to the folders. The aspnet_client folder is at the same level as those folders. So I am at the root... correct?

    I admin another account with Winhost (great!) and there is no aspnet_client folder anywhere.

    Where am I screwed up? (please keep it related to this problem!)
     
  4. Ray

    Ray

    Give us a full copy of your FTP log from beginning to end.
     
  5. First. Thank you for the quick response. You guys have a great reputation.

    Here's the log from Filezilla, from login to delete attempt.

    Status: Resolving address of ftp.builders.w02.Winhost.com
    Status: Connecting to 96.31.35.21:21...
    Status: Connection established, waiting for welcome message...
    Response: 220-Microsoft FTP Service
    Response: 220 Winhost.com FTP
    Command: USER builders
    Response: 331 Password required for builders.
    Command: PASS ********
    Response: 230-Welcome
    Response: 230 User logged in.
    Command: OPTS UTF8 ON
    Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.
    Status: Connected
    Status: Retrieving directory listing...
    Command: PWD
    Response: 257 "/builders" is current directory.
    Command: TYPE I
    Response: 200 Type set to I.
    Command: PASV
    Response: 227 Entering Passive Mode (96,31,35,21,19,229).
    Command: LIST
    Response: 150 Opening BINARY mode data connection.
    Response: 226 Transfer complete.
    Status: Directory listing successful
    Status: Retrieving directory listing...
    Command: CWD aspnet_client
    Response: 250 CWD command successful.
    Command: PWD
    Response: 257 "/builders/aspnet_client" is current directory.
    Command: PASV
    Response: 227 Entering Passive Mode (96,31,35,21,19,232).
    Command: LIST
    Response: 150 Opening BINARY mode data connection.
    Response: 226 Transfer complete.
    Status: Directory listing successful
    Status: Retrieving directory listing...
    Command: CWD system_web
    Response: 250 CWD command successful.
    Command: PWD
    Response: 257 "/builders/aspnet_client/system_web" is current directory.
    Command: PASV
    Response: 227 Entering Passive Mode (96,31,35,21,19,229).
    Command: LIST
    Response: 150 Opening BINARY mode data connection.
    Response: 226 Transfer complete.
    Status: Directory listing successful
    Status: Retrieving directory listing...
    Command: CWD 4_0_30319
    Response: 250 CWD command successful.
    Command: PWD
    Response: 257 "/builders/aspnet_client/system_web/4_0_30319" is current directory.
    Command: PASV
    Response: 227 Entering Passive Mode (96,31,35,21,19,237).
    Command: LIST
    Response: 150 Opening BINARY mode data connection.
    Response: 226 Transfer complete.
    Status: Directory listing successful
    Command: CWD /builders/aspnet_client/system_web
    Response: 250 CWD command successful.
    Command: PWD
    Response: 257 "/builders/aspnet_client/system_web" is current directory.
    Command: RMD 4_0_30319
    Response: 550 Access is denied.
    Command: CWD /builders/aspnet_client
    Response: 250 CWD command successful.
    Command: PWD
    Response: 257 "/builders/aspnet_client" is current directory.
    Command: RMD system_web
    Response: 550 Access is denied.
    Command: CWD /builders
    Response: 250 CWD command successful.
    Command: RMD aspnet_client
    Response: 550 Access is denied.
    Status: Retrieving directory listing...
    Command: PASV
    Response: 227 Entering Passive Mode (96,31,35,21,19,213).
    Command: LIST
    Response: 150 Opening BINARY mode data connection.
    Response: 226 Transfer complete.
    Status: Directory listing successful
     
    Last edited by a moderator: Oct 14, 2015
  6. Ray

    Ray

    Passive mode is fairly temper mental and unpredictable. But it is often needed if you are behind a firewall. For now as a test because I suspect the issue is caused by Passive Mode, try bypassing your firewall and router all together and connect directly to the internet. Also make sure you update the connection mode from Passive Mode to Active Port mode. Send us a new FTP log to view if you continue to have FTP problems.
     
  7. OK. That makes sense. But there is a problem.

    I'm out in the boonies. My ISP is my neighbor who has a T1 line going to his house for business. He then broadcasts it wireless to our little subdivision. He has a Fortigate Firewall and by the time it gets to my place it has gone through several routers (repeaters).

    So how can I do this?

    Or... can you just delete that sucker off for me!?

    Thanks again.
     
  8. Ray

    Ray

    Try this link. Its a 3rd party web site (not affiliated with us) that will connect via FTP. Since it is web base, it should be able to go through the firewall for you.

    http://www.net2ftp.com
     
  9. Well I gave that a try. Cool site. But...
    Failure... and the folders are empty except for the subfolders...

    * Processing directory /builders/aspnet_client
    o Processing directory /builders/aspnet_client/system_web
    + Processing directory /builders/aspnet_client/system_web/4_0_30319
    # Unable to delete the subdirectory /builders/aspnet_client/system_web/4_0_30319 - it may not be empty
    # Processing of directory /builders/aspnet_client/system_web/4_0_30319 completed
    + Unable to delete the subdirectory /builders/aspnet_client/system_web - it may not be empty
    + Processing of directory /builders/aspnet_client/system_web completed
    o Unable to delete the subdirectory /builders/aspnet_client - it may not be empty
    o Processing of directory /builders/aspnet_client completed

    # All the selected directories and files have been processed.


    It may not be important for that folder to be deleted, except that I don't need it and don't want any conflicts.

    What I'm doing is an install of DotNetNuke in the root folder and portal to my sites. So I'll have the subfolders for each site (for now) until I build the dnn sites, at which time I'll delete those folders.

    I just don't know why the server is so attached to those folders.

    Thanks for all your time on this.
     
  10. Ray

    Ray

    OK, try opening a ticket to our support department and ask them to manually delete that specific folder for you. Make sure you open the ticket from within your control panel since they'll need to authenticate the request and tell them the exact name of the folder and the path to the folder. The last thing you want is for them to accidentally delete the wrong folder for you.
     
  11. Will do.

    Thank you.
     
  12. Last edited by a moderator: Oct 14, 2015

Share This Page