Hi,

 

I have a problem with the Silverlight uploader. When the upload gets to about 300MB i get the following error:

 

 

Silverlight : The upload task is interrupted!Unable to get web http response.System.Net.WebException: The remote server returned an error: NotFound

   at System.Net.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)

   at System.Net.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at Silverlight.FileItem._OnGetResponse(IAsyncResult ar)

Hi,

 

What browser did you get such error ?

 

Did all kinds of file size get the same error ?

 

Regards,
Terry

I get it in both Firefox 3 and IE 7.

 

If I upload a small file (less than 200MB) it works perfectly. The strange thing is that the point where it breaks is never the same - usually though it's somewhere between 300-400.

 

Additionally:

 

I get this error when I upload a file larger than 400MB.

 

<add key="CuteWebUI.AjaxUploader.RewritePath" value="False" />

out of memory

Oxa0(Object createTime=1238367274263)CuteWebU...457360000 (line 1)

Ox92(Object createTime=1238367274263)CuteWebU...457360000 (line 1)

Ox91()CuteWebU...457360000 (line 1)

DoVideoUpload()()Media.js (line 15)

onclick()()

After disabling firebug the upload worked. But I am seeing a jump of about 500MB in the RAM Firefox uses while uploading a 700MB file. This does cause me some concern, because it is likely that our clients may not have that much spare memory on their machines.

 

Also, I'm having to manually set the Uploader.TempDirectory because it is not reading it from my web.config.

Sugendran,

 

Thanks for your information.

 

We are still investigating on it.

 

Regards,
Terry

 

I continue to get this error as well. And it appears to have no relationship to file size. The only way I can consistently reproduce the error is when the page the upload control is located on is accessed from a Response.Redirect("pagewithcontrol.aspx").

 

If I ask the page through a traditional HTML link, the error is not thrown.

 

It also doesn't appear to be a caching issue of the page as I append a unique querystring to the url. Any ideas around this?