Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

CAupload and RADupload
Last Post 07/14/2011 2:58 PM by Peter Donker. 4 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
primeripe
New Member
New Member
Posts:3


--
07/06/2011 8:34 PM
We've been struggling with getting an upload with a progress bar to work. We've tried both CAupload and RADupload, and read posts on this forum as well as CA and Teleriks websites.

Some of the information was helpful and enabled some functionality but still neither work properly. CAUpload appeared to be working, single files around 50mb worked as did a couple files of that size. We tried it with 6 30mb files and it failed. Once the upload completes you can see the page submit but it processes for at least 5 minutes as if its uploading the files again. Instead of being directed to the permissions page, the uploader simply refreshes as if you didn't upload anything.

RADUpload works as well, but without a progress bar. We're open to using either uploader but a progress bar is a requirement.

DMX_RadUploadModule/RadUploadModule/ComponentArtUploadModule are registered as modules and Bring2mind Telerik Upload/Bring2mind CA Upload are registered as handlers under system.webserver in the web.config.

maxAllowedContentLength is set to 2097152000 under security.requestFiltering, maxRequestLength/requestLenghtDiskThreshold are set to 2000000 and executionTimeout set to 6000 in httpRuntime.

We've tried IIS in both integrated pipeline and classic mode.

This is clean install of DNN and DMX, no other modules installed and we're not using a URL rewriter.

Windows Server 2008 R2 Standard
IIS 7.5
DNN 05.06.02
DMX 5.3.7

Any help would be appreciated.
Rob Ralston
Basic Member
Basic Member
Posts:164


--
07/07/2011 6:45 PM
Hello,

I'm not going to suggest this will fix your problem, but I believe you may not be helping with your large "requestLengthDiskThreshold" value.

This value determines when IIS starts to write the data stream buffer to disk, it does not control how large the file can be, which is what "maxRequestLength" controls for IIS.

I don't use either of those controls as I had trouble with them (but don't remember the specifics right now). Not sure how they interact with these IIS settings.

I use the standard upload control and have the following values in my web.config which allowed me to upload a file close to 400MB in size:

maxRequestLength="409600" requestLengthDiskThreshold="8192" executionTimeout="10800"

So you see the the requestLengthDiskThreshold="8192" is still just 8KB, so as each 8KB gets uploaded, it is written to a temporary buffer on disk rather than consuming huge amounts of RAM.

Hope this helps you a bit.

Rob
Rob Ralston
Basic Member
Basic Member
Posts:164


--
07/07/2011 7:10 PM
Correction. Actually, that was a mistake to say I wasn't using either of them. I am using the RADUpload Control.

Sorry for the confusion.

Rob
Rob Ralston
Basic Member
Basic Member
Posts:164


--
07/07/2011 8:09 PM
No I had it right the first time. Not using RadUpload because of Medium Trust issues. I just verified this.

Unfortunately, I have just discoverd a transient problem when attempting to upload a file, which I will contact Peter about separately.

I appologize, but want to provide accurate information.

Rob
Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
07/14/2011 2:58 PM
In these cases it is really helpful to fire up Fiddler to see what the server responds to the progresshandler calls that happen in the background. That way you know whether it is a server issue (i.e. handlers) or a client side issue (i.e. displaying).

Peter
You are not authorized to post a reply.