Your best friend for file transfer.

Fetch application logoFetch

Exceeded your storage allocation message (4 posts)

  • Started 18 years ago by Katya
  • Latest reply 18 years ago from Jim Matthews
  • Katya Member


    I've had a number of cases where I've gotten the following error message in my Fetch interface when dragging and dropping a folder of images:

    Error: you have exceeded your storage allocation on the server

    However, this message is wrong, as my storage limit had never been exceeded. And when I used a different FTP client, I didn't have any issues.

    Any idea why this could be happening?

    Posted 18 years ago #

  • Scott McGuire Administrator

    The next time you get this error, dismiss the error, then choose "Fetch Transcript" from the Window menu, copy the contents, and post them here.

    We will take a look at the transcript and try to figure out what the problem is.


    Scott McGuire
    Fetch Softworks

    Posted 18 years ago #

  • Katya Member

    Hello Scott.

    Thank you for your reply. Here is an example transcript:

    PORT 62,23,94,93,82,252 200 command successful STOR cm.bush.6.27.05.U3130.jpg 552 transfer failed ftp_store_setup: -30007 (state == RPUT_SETTING_UP) ABOR 226 abort successful TYPE A 200 Type set to ASCII. PORT 62,23,94,93,40,176 200 command successful LIST 150 Opening ASCII data connection for directory listing 226 transfer complete

    As you can see, there is no message from the server saying that there is a storage allocation issue. This appears to be an issue with Fetch, where Fetch aborts the upload. Please advise. Thank you.

    Posted 18 years ago #

  • Jim Matthews Administrator

    When Fetch gives the command to start the upload (STOR, short for "store"), the server replies:

    552 transfer failed

    The 552 reply code is defined to mean:

    Requested file action aborted.
    Exceeded storage allocation (for current directory or dataset).

    So Fetch shows you a message about your storage allocation. At this point the transfer has been aborted by the server.

    It could be that the server is giving the wrong reply code for the actual problem that it is encountering (resulting in the inaccurate error message in Fetch). But there is definitely some problem on the server side that is resulting in this 552 message.

    So the curious thing is that you aren't seeing a problem with a different FTP client. Have you tried uploading this same file with a different FTP client? If so I would be interested in seeing the transcript from that client to see what the differences are.

    Another thing you could try is uploading the same file with a different name, to see if the problem is related to the name.


    Jim Matthews
    Fetch Softworks

    [This message has been edited by JimMatthews (edited 09-08-2005).]

    [This message has been edited by JimMatthews (edited 09-08-2005).]

    Posted 18 years ago #


  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.