Problem Uploading Large Documents - Bring2mind

Bring2mind Forums

Prev Go to previous topic

Go to next topic

Last Post 08/11/2006 11:19 PM by Peter Donker

Problem Uploading Large Documents

7 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

Ken Simpson

New Member
Posts:11

04/12/2006 9:46 PM
I have read the few discussions in this forum about uploading/downloading large documents. However, I have made numerous attempts to modify my web.config settings for timeout and file size. Both of the web.config values have been set to allow for large files but I still consistently get failures for any file over about 40 MB. Can anyone help me out with this? I have a site where we need to be able to upload large numbers of documents, many of them over 40 MB. Can this module handle this? Thanks, Ken

Peter Donker

Veteran Member
Posts:4536

04/13/2006 12:54 PM
Ken, DMX does not do anything with the file size. It doesn't even ask DNN whether the 'portal quota' are being violated. It merely takes what .net gives it and writes it to disk. File size problems are at the level of ASP.NET/IIS/Server. Note that a file gets streamed to memory by ASP.NET during the upload process. Peter

Ken Simpson

New Member
Posts:11

04/13/2006 5:46 PM
I guess I am looking for a little guidance from the developers and/or the forum members about how to get this configured correctly. It seems that others have solved this issues as I hear people talking about files over 50 MB in DMX. Can someone provide some step by steps or things to check on? Questions: Do I need to allow for a multiple of the largest file size I expect to upload? (i.e. If my max file size will be 100MB do I need to configure my web.config to allow for 200MB or 300MB due to caching, temp files etc?) What are all the places I need to configure my time out settings and what should this setting be for 100MB files? web.config machine.config? IIS? (is there more than one place in IIS that needs to be configured? Anything else I missed to make this work for 100MB file upload and download? Any guidance I ca get to make this work would be greatly appreciated. Anyone else out there using this module for large document repositories? Thanks, Ken

Matthias Kühnle

New Member
Posts:9

07/06/2006 4:07 PM
Ken, still having this problem? Enabling a Webgarden on IIS 6 with ASP.NET 1. machine.config ... webGarden="true" ... 2. check if AspNet State Server Service is running if not - console: net start aspnet_state (Set from manual to automatic in Services when started) 3. Edit web.config, paste the whole section in the mode="StateServer" stateConnectionString="tcpip=localhost:42424" /> 4. Registry check for matching the default port (Optional): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\Port 5. IIS: Create an app pool only for "your website" and set the website to this pool. 6. Increase / configure the workerprocesses / performance options for your needs. Your done! (If you have question to sessionstate... have a look at this: http://msdn2.microsoft.co...brary/h6bb9cz9.aspx) I'm interested in your testing results.

Ken Simpson

New Member
Posts:11

07/06/2006 5:45 PM
I haven't tested this again recently but as far as I know I still have issues with uploading larger files in DMX. Not sure I understand the rest of your post. Is this information related to uploading large documents?

Peter Donker

Veteran Member
Posts:4536

07/06/2006 11:09 PM
It all revolves around this line in your web.config: <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192"/> Note the maxRequestLength. It is set to around 8 Mb. This means IIS will cut off the request if the amount of bytes received is larger than that. What you don't see in the standard web.config included with DNN is the parameter executionTimeout. This parameter is specified in seconds and defaults I believe to 90. It tells you after how many seconds IIS thinks it's enough. Add this parameter as well to the web.config. Test this setting by progressively trying the upload from "further away" (i.e. start maybe locally on the server, then from your LAN, finally from a remote place). Thanks a bunch for the manual by supermatze who explains how to tune the configs so that it all works in a web farm. Thanks.

Matthias Kühnle

New Member
Posts:9

07/07/2006 10:08 AM
Peter, this property "executionTimeOut" seems to be new in .Net Framework version 2.0 it won't help on 1.1 machines. see: http://msdn2.microsoft.co...xecutiontimeout.aspx Ken, I've successfully tested uploading in DMX for up to 184 MB Zip-Files with running a "IIS 6 webgarden" with the above configs without changing the maxRequestLength or adding params like executionTimeout. Please note the difference between webgarden and webfarm: webgarden: one server runs one website with multiple workerprocesses to increase performance on heavy loads (I.e. above scenarios, since we don't believe that only one users will upload a large document at A time =:-). webfarm: multiple servers run one website to give redundancy...

Peter Donker

Veteran Member
Posts:4536

08/11/2006 11:19 PM
executionTimeout is IIS specific, not framework version specific. Check out the following: Production Debugging for .NET Framework Applications http://msdn.microsoft.com...bda/html/dbgch01.asp

You are not authorized to post a reply.