Hello,
We are using the method described in the below link to upload files programmatically.
http://www.telerik.com/support/kb/silverlight/upload/how-to-use-the-radupload-programatically.aspx
Our Silverlight application, provides a page with a save button, onto which any number of files can be dragged from windows explorer.
Once files are dragged to the silverlight page, clicking on save button will start uploading the dragged files to IIS server.
Currently the code is written to create a separate "RadUpload" control for each file. That means if user drags 100 files on to the application page, 100 "RadUpload" controls are created dynamically each of which will handle single file upload.
Though it is working on our systems upto 70/80 files at a time, on some customer systems the "upload" is failing when user drags more than 12 files and starts upload.
My question is, whether creating as many "RadUpload" controls as the "file to be uploaded" is causing upload to fail. Is there any such limitation on the number of "RadUpload" controls to create dynamically, that may result in upload failures. Each file is of size 2 KB
[The RadUpload.MaxFileCount is set to 100 which is more than what customer is trying to upload(around 12 files).]
The errors are as below.
Handler not found or execution of the handler failed!
[HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
Check RadUpload's BufferSize property remarks.
[HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer,Log Time: 7/21/2013 11:57:42 PM,
Thank You,
Rakesh
We are using the method described in the below link to upload files programmatically.
http://www.telerik.com/support/kb/silverlight/upload/how-to-use-the-radupload-programatically.aspx
Our Silverlight application, provides a page with a save button, onto which any number of files can be dragged from windows explorer.
Once files are dragged to the silverlight page, clicking on save button will start uploading the dragged files to IIS server.
Currently the code is written to create a separate "RadUpload" control for each file. That means if user drags 100 files on to the application page, 100 "RadUpload" controls are created dynamically each of which will handle single file upload.
Though it is working on our systems upto 70/80 files at a time, on some customer systems the "upload" is failing when user drags more than 12 files and starts upload.
My question is, whether creating as many "RadUpload" controls as the "file to be uploaded" is causing upload to fail. Is there any such limitation on the number of "RadUpload" controls to create dynamically, that may result in upload failures. Each file is of size 2 KB
[The RadUpload.MaxFileCount is set to 100 which is more than what customer is trying to upload(around 12 files).]
The errors are as below.
Handler not found or execution of the handler failed!
[HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer
Check RadUpload's BufferSize property remarks.
[HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer,Log Time: 7/21/2013 11:57:42 PM,
Rakesh
1 Answer, 1 is accepted
0
Hi Rakesh,
I've posted a reply in the support thread you sent. However, I will post the same suggestions here so that they can be available to the community:
The described errors are usually raised either because the client application cannot access or find the upload handler or because the buffer size is too small and can't process the files for upload. This is why I recommended checking the values of the BufferSize, MaxFileSize or MaxUploadSize properties of the RadUpload. It might be best to leave this properties with their default values by not setting them at all.
As I noted in your support thread, if these suggestions don't help the best way to proceed would be to either send a sample solution we can examine or to modify the solution I attached in your support thread.
Regards,
Tina Stancheva
Telerik
I've posted a reply in the support thread you sent. However, I will post the same suggestions here so that they can be available to the community:
The described errors are usually raised either because the client application cannot access or find the upload handler or because the buffer size is too small and can't process the files for upload. This is why I recommended checking the values of the BufferSize, MaxFileSize or MaxUploadSize properties of the RadUpload. It might be best to leave this properties with their default values by not setting them at all.
As I noted in your support thread, if these suggestions don't help the best way to proceed would be to either send a sample solution we can examine or to modify the solution I attached in your support thread.
Regards,
Tina Stancheva
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for SILVERLIGHT.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>