I used the following settings, which allow me to upload large image files and synchronise the database 400 mb of data. I just kept increasing the numbers until it worked. Hope this might work for you!

<!-- allow large file uploads -->
    <httpRuntime executionTimeout="4000" maxRequestLength="39192"
      useFullyQualifiedRedirectUrl="true" appRequestQueueLimit="2000" />

If URLScan is installed on the IIS Server, it too has a default 8MB max file upload default. So the URLScan setting would need to be coordinated with the web.config changes.

Rob Ralston

---

Rob Ralston, SilverBullet Technologies LLC, www.silverbullettech.com

John - I have run up against this problem too with trying to post podcast files that are fairly large (15mb or so) - I started on building/rebuilding the file control you see in the documents module to use neatUpload to allow for really large uploads (gigabyte range) and not bring the server to its knees - really have had mixed results with this approach but might still get it to work -

My analysis of the problem has to do with more than DNN or the web config file settings - on hosted servers there seems to be some throttling that takes place and if the thread that is running for the upload takes to long and takes too much memory it gets killed off - I dont know how but thats what it looks like after an hour on  the phone with tech support one night

I have tried the neatUpload route because it spools the file to disk so memory on the server doesnt get loaded and kill server performance - I notice this seems to interfere with some of the clientAPI stuff in dnn so not sure if this is worth persuing more but might try it again.

Anyway my 2 cents on the problem - I dont think the answer is in the web.config because I can set that to hundreds of megs but the asp.net method of handling uploaded files just really inst up to anything over a few megs.

---

Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules