When uploading, and yes even downloading, you can run into the 50 mb filesize limiter. There are some different ways to fix the issue. I tried to collect them all. This is regarding the MOSS enviroment and WSS 3.0 version.
You should start adjusting the maximum filesize setting from your central administration. “Central Administration” > “Application Management” > “Web Application General Settings” (Located under SharePoint web Application Management). Here you can change the default value to the preffered new one.
Then there are 2 web.config files that should be changed in order to set the connection timeout. You can localize those to in
- C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\web.config , Global config
- C:\inetpub\wwwroot\wss\VirtualDirectories\SITENAME\web.config, web application config
1. For the global configuration, localize the following node in the web.config file
<location path="upload.aspx"> <system.web> <httpRuntime maxRequestLength="51200" /> </system.web> </location>
Add the attribute “executionTimeout” with a value of 999999 to the “httpRuntime” node.
<location path="upload.aspx"> <system.web> <httpRuntime executionTimeout="999999" maxRequestLength="51200" /> </system.web> </location>
2. For the local configuration, find the “location” node in the web.config where the “path” attribute is set to upload.aspx
<httpRuntime maxRequestLength="51200" />
<httpRuntime maxRequestLength="51200" executionTimeout="999999" />
It should not be nececerly to change the maxRequestLength, cause this should come from your maximum Upload Size set in Central Administration.
IIS 7.0 and “Exporer view”
When uploading content with the explorer view, you also need to add the following nodes to the end of the web.config file. Here you must set the file size in bytes. In this case its set to 1 gb
<system.webServer> <security> <requestFiltering> <requestLimits maxAllowedContentLength="1048576000" /> </requestFiltering> </security> </system.webServer>
IIS 6.0 / 7.0
Something i did not experience self but have read about it, is to change the timeout settings for the Site in your IIS.