Prasad Bolla's SharePoint Blog

Click Here to go through the Interesting posts within my Blog.

Click Here to go through the new posts in my blog.

Friday, February 24, 2012

SharePoint site Quota Limit Exceeded Error in SharePoint 2007


I have had several clients call me regarding issues they are having with uploading large files in SharePoint. Although the upload multiple files options seems to help with some of these issues, there are still other settings you may have to configure to reach optimal performance for your uploads.  Here are some suggestions I found regarding this issue:
·       Increase the paging file size for the server to at least 1 gigabyte (GB).
·        Increase the IIS timeout settings to 65,000
·        Check whether a quota is defined on the site collection, and if the quota has been exceeded. If so, increase the quota limit. ·        Check the maximum file upload size limit. The default maximum file size for uploads to SharePoint is set at 50MB. Try increasing this value if you are uploading large files.
·        Add the executionTimeout value in the Web.config file.<httpRuntime executionTimeout=”999999″ maxRequestLength=”2097151″ />
  • Add the following settings under the <configuration> section of the Web.config file: <system.webServer><security><requestFiltering><requestLimits maxAllowedContentLength=”52428800″/></requestFiltering></security></system.webServer>
  • I also read about Increase the default chunk size for large files but this seemed to focus on previous versions of SPS. The large-file-chunk-size property sets the amount of data that can be read from server running SQL Server at one time. If you have a file that is greater than your chunk size (such as 70 MB when the chunk size is set to 5 MB), the file would be read in 14 chunks (70 / 5). The chunk size is not related to the maximum upload file size. The chunk size simply specifies the amount of data that can be read from a file at one time. By default, the large-file-chunk-size property is set to 5 MB. If you notice performance or scale problems on the client or server, then you may need to tune this setting to get the performance you are targeting. Note that if you raise the chunk size too high, the files might use up too much front-end memory and you may need to lower this setting.
The large-file-chunk-size property must be set from the command line, use the following syntax:Stsadm.exe –o setproperty –pn large-file-chunk-size –pv <size in bytes> Restart IIS
  • Finally I came across this blog that says the issue has to do with a default setting in Internet Explorer 6.0 and earlier. This limits the data rate that the browser sends information. This becomes particularly noticeable with larger files (e.g. greater than 2 MB). The resolution is to make an update to the registry on the user’s computer. http://support.microsoft.com/default.aspx/kb/329781

No comments:

Post a Comment