The remote server returned an error: (550) ...

Question

0.00/5 (No votes)

See more:

I am doing FTP upload and download in ASP.NET. When I try to download the file immediately after uploading, it is throwing the following error:

"The remote server returned an error: (550) File unavailable (e.g., file not found, no access)."

If I wait for a minute and then try to download it, it's working fine. Can somebody suggest a way to get out of this.

P.S.: As soon as uploading finishes, I am showing the files in a grid to download them, hence assuming that the file upload is complete.

Posted 4-Jun-10 4:42am

M123SD

Updated 6-Jun-10 9:44am

Deeksha Shenoy

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dr.Walt Fair, PE · Answer 1 · 2010-06-06T06:47:00

I've run into that problem before and it appears that (in my case) it involved a cache either on the server or client somewhere. The client had finished sending the data, but the server had not finished receiving and saving it yet.

I solved it by adding a delay on the client side after sending the data. I didn't like that solution, but I couldn't find any other way to easily work around it.