Hi Joe, I've run into a strange issue with uploading files, and I'm not sure how to resolve it or if it's possibly a bug in mojoPortal, or even .NET. Let me give you the shortened story. Last week a user who is in a non-admin role that has been granted "Roles that can browse and upload files," reported she was unable to upload a 42 MB file (using the file browser within an HTML instance).

I confirmed that I could not upload the file either, so I read through your updated Supporting Large File Uploads document, and changed our web.config settings to support uploads up to 250 MB. It turned out that maxAllowedContentLength was the setting that needed to be changed. 

I tested and was able to upload files up to 250 MB, so I pronounced the problem fixed. But she came back to me yesterday and said it still wasn't working. Sure enough, when I log in as her and try to upload a large file, I get the dreaded "Oops" message, regardless of the browser I use. Using her account I can upload small files without a problem.

No errors are logged anywhere, so it is definitely still behaving as though the maxAllowedContentLength setting isn't set (i.e. defaulting to 30000000).

In troubleshooting, I made sure I was using the latest code line. Is there a setting I could be missing somewhere? Are you able to reproduce this yourself?

Thanks,
Jamie

Thanks Joe, that was it. I didn't even consider quotas since we're not limiting users to their own folders. I added this to my user.config, touched web.config, and it's working as expected now.

<add key="MediaFolderMaxSizePerFileInMegaBytes" value="250" />

I know you're limited on the error trapping/reporting in the uploader, but do you think it would be possible to give a more meaningful error message, or log an error when one of the quotas is exceeded? That could be helpful to others in the future. 

Thanks!

Jamie