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

Bring2mind Forums

Maximum Request Length Exceeded
Last Post 08/17/2010 5:54 PM by Jason Scott. 5 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Chris Lietz
New Member
New Member
Posts:6


--
08/13/2010 3:33 PM

I'm attempting to upload a 57.2mb PDF file to my DMX installation; there's only one other file i've uploaded to my fresh DMX install thus far.

According to your documentation I can upload files up to 2gb; yet when I attempt to upload the pdf I get the following error

Server Error in '/' Application. -------------------------------------------------------------------------------- Maximum request length exceeded. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Maximum request length exceeded. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Maximum request length exceeded.] Bring2mind.Telerik.WebControls.RadUploadHttpModule.ThrowMaximumRequestLengthExceeded(HttpResponse response) +64 Bring2mind.Telerik.WebControls.RadUploadHttpModule.Context_BeginRequest(Object sender, EventArgs e) +242 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Can someone please explain why I'm receiving this error; and if I need to increase storage, how to do so? Thanks!
Chris Lietz
New Member
New Member
Posts:6


--
08/16/2010 3:32 PM
Any and All help would be appreciated (bump)
Jason Scott
New Member
New Member
Posts:46


--
08/16/2010 11:03 PM
You might want to make sure your web.config file is set to allow large file uploads. It could be .NET itself that is blocking the file. Search your web.config file for "maxrequestlength", and the number you see is the file size in KB that can be uploaded. For instance, if it's just around 4000, that's only about 4 megs. Bump that up and increase the timeout limit (in seconds) as well. Hope this helps.

Jason
Chris Lietz
New Member
New Member
Posts:6


--
08/17/2010 3:43 PM
Jason, That was it! I thank you for your assistance!
Additionally, when you mention Timeout Limit; do you mean the cookieTimeout? or the Form Timeout?

I also increased the requestLengthDiskThreshold as well.
Jason Scott
New Member
New Member
Posts:46


--
08/17/2010 5:50 PM
Glad that worked for you, Chris! In the same httpruntime section of your web.config file, you can specify a parameter called maxRequestLength, where the length is listed in seconds. By default, this is not in your web.config file, and it will use the default value of 110 seconds. Depending on how large of a file you want to allow, you might have to increase this dramatically. For instance, you could add the following:

maxRequestLength="600"

and it would give users up to 10 minutes to upload their file. You could add this directly after the "requestLengthDiskThreshold" value.
Jason Scott
New Member
New Member
Posts:46


--
08/17/2010 5:54 PM
I clearly haven't had enough coffee this morning! Obviously, we already covered "maxRequestLength", and so my post above makes no sense. The parameter that DOES set the timeout value in seconds (and defaults to 110) is:

executionTimeout="600"

I'm sorry for the confusion. Adding the executionTimeout of 600 will give you 10 minutes to upload a file.
You are not authorized to post a reply.