File Manager -

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
10/13/2011 4:28:36 PM
Gravatar
Total Posts 23

File Manager -

Hi,

mojoPortal Version 2.3.7.0 MSSQL
Operating System Microsoft Windows NT 6.0.6002 Service Pack 2
ASP.NET Info v4.0.30319 Running in Full Trust

When I try to upload a 4MB .pdf using the file manager, I get the following error. I can upload other files successfully.

2011-10-13 11:27:25,998 ERROR 192.168.20.101 - en-US - /Services/FileService.ashx?cmd=upload&t=80b20e54-90fb-41a0-8853-dd859a73ad34 - mojoPortal.Web.Services.FileService - System.Web.HttpException (0x80004005): Maximum request length exceeded.
   at System.Web.HttpRequest.GetEntireRawContent()
   at System.Web.HttpRequest.GetMultipartContent()
   at System.Web.HttpRequest.FillInFormCollection()
   at System.Web.HttpRequest.get_Form()
   at System.Web.HttpRequest.FillInParamsCollection()
   at System.Web.HttpRequest.GetParams()
   at System.Web.HttpRequest.get_Params()
   at mojoPortal.Web.Services.FileService.LoadSettings(HttpContext context)
   at mojoPortal.Web.Services.FileService.ProcessRequest(HttpContext context)

 

 

When I tried uploading a 5MB .pptx file, I got this error:

2011-10-13 11:33:57,815 ERROR 192.168.20.101 - en-US - /Services/FileService.ashx?cmd=upload&t=80b20e54-90fb-41a0-8853-dd859a73ad34 - mojoPortal.Web.Services.FileService - System.Web.HttpException (0x80004005): Maximum request length exceeded.
   at System.Web.HttpRequest.GetEntireRawContent()
   at System.Web.HttpRequest.GetMultipartContent()
   at System.Web.HttpRequest.FillInFormCollection()
   at System.Web.HttpRequest.get_Form()
   at System.Web.HttpRequest.FillInParamsCollection()
   at System.Web.HttpRequest.GetParams()
   at System.Web.HttpRequest.get_Params()
   at mojoPortal.Web.Services.FileService.LoadSettings(HttpContext context)
   at mojoPortal.Web.Services.FileService.ProcessRequest(HttpContext context)

 

Again, smaller files work. I have not changed anything in the web.config, because these files seem to be well under the maxRequestLength of 2097151, or am I not understanding this correctly?

10/13/2011 5:03:27 PM
Gravatar
Total Posts 115
mojoPortal Community Expert

Re: File Manager -

If you are running in Full Trust you should be using NeatUpload to handle file uploads. You need to refer to this document for configuration. NeatUpload uses a different config section.

10/13/2011 5:13:10 PM
Gravatar
Total Posts 23

Re: File Manager -

I saw that, and I thought that this section of the web.config:

<neatUpload useHttpModule="true" maxNormalRequestLength="4096" maxRequestLength="2097151" multiRequestUploadHandlerUrl="~/NeatUpload/MultiRequestUploadHandler.ashx" maxUploadRate="300" xmlns="http://www.brettle.com/neatupload/config/2008">
  </neatUpload>

 

shows that the maxRequestLength is still 2097151KB, which should be more than adequate for handling 4-6 MB files.

10/14/2011 6:41:40 AM
Gravatar
Total Posts 18439

Re: File Manager -

If you don't see a progress bar when uploading files then you are not using NeatUpload and adjusting the NeatUpload settings won't have any effect, in that case the <httpRuntime element has the relevant settings. If you do see the progress bar when uploading then the NeatUpload settings are important, you might also try increasing the maxNormalRequestLength. Even when using NeatUpload the executionTimeout on the <httpRuntime element is a factor.

Hope that helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.