Have you tried adding the requestLengthDiskThreshold attribute as well?

It goes in the httpRuntime element.

Example of max values found here : https://stackoverflow.com...-of-maxrequestlength

I seem to recall having had the same issues years back - but I couldn't find it in my notes, so I had to rely on my old friend Google to help me out ;-)

# DnnBro

Hi DnnBro, thanks for the suggestion.  That attribute was already present in the web config, so I didn't have to add it.  Right now it's set to the same value as maxRequestLength, which I believe is correct - I read somewhere that it should never be larger than maxRequestLength, since that can cause problems.  I can try bumping both of those values up a bit so they're still equal though and see if that makes a difference.

Also, does the second file have the same extension as the first file? If it is different, make sure that file type is permitted in your DNN. You can edit the list of allowable files type in Security, More, More Security Settings.

If you look at the log4net logs (/portals/default/logs), you may find some additional information there.

Hi Joe,

Yes both files are mp4.  Thanks for the suggestion about the logs, I'll take a look at those and provide an update when I have a chance.

Hi Pam,

I noticed you have upped the executionTimeout - perhaps it is a timeout issue instead? If your executionTimeout is longer than your sessionTimeout upping the latter could also be a thing to try out.

How long does it take for you to upload the file(s)?

When checking the logs also take a look at the IIS logs (if you have access to them => C:\inetpub\logs\LogFiles)

#DnnBro

Hi Joe and DnnBro,

I finally had a chance to get back to this, and I'm not seeing anything in either the log4net logs (/portals/default/logs) or the IIS logs (C:\inetpub\logs\LogFiles).

I double checked the sessionTimeout on the server, which is set to 20 minutes.  If I understand correctly, the executionTimeout is in seconds, so a value of 3000 = 50 minutes.  I timed the file that's failing, and it takes just over 2 minutes to get to the end of the progress bar before the failure message, so I wouldn't think it's timing out at this point.  Any other thoughts?

Thanks again,
Pam  

Hmm.. this is a tough one.. I'm running a bit short on ideas I have to admit :-)

Any chance your F12 window gives you any indications of error in the console or network window?

#DnnBro

Can you try setting a Failed Request Tracing Rule in IIS to get more detailed info?

Open IIS Manager, select the website, select Failed Request Tracing Rules.

Click Edit Site Tracing, tick Enable, click OK.
Click Add to add a rule.
Leave the All content option selected, click Next.
Type your error status code - or type 400-999 if you're not sure.
Click Next.

Leave the default trace providers enabled.
Click Finish.

Restart IIS.

Recreate the request that produced the error then check content of the trace files in the directory shown when you enabled tracing.

Remember to disable tracing and restart IIS again afterwards to avoid unnecessary performance hits.