Skip to main content

You cannot upload files that are larger than 28 MB on a Windows Server 2008-based computer that is running Windows SharePoint Services 3.0

When you run Windows SharePoint Services on a Window Server 2008-based computer that is also running Internet Information Services 7.0, you cannot upload files that are larger than 28 megabytes (MB). You experience this problem even though you have configured the large file upload settings according to Microsoft Knowledge Base article 925083.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
925083 (http://support.microsoft.com/kb/925083/ ) Error message when you try to upload a large file to a document library on a Windows SharePoint Services 3.0 site: "Request timed out"



To work around this problem, follow these steps:
1. Use Notepad to open the Web application Web.config file. By default, this file is in the following folder:
Microsoft Windows SharePoint Services 3.0
C:\Inetpub\Wwwroot\Wss\VirtualDirectories\ VirtualDirectoryFolder

Windows Small Business Server 2008
C:\Program Files\Windows Small Business Server\Bin\webapp\InternalWebSite

2. Add the following code to the section of the Web.config file:

<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="52428800">
</requestFiltering>
</security>
</system.webServer>


Note This code sets the value of the maxAllowedContentLength property to 52428800. Therefore, the maximum file size of an uploaded file is 52428800 bytes. However, set the value of this property so that it is larger than the file that you are trying to upload. Also, set the value of this property so that it is larger than the maximum file upload size that you have configured in SharePoint. If you do not, users will not receive an error message that they are exceeding the size limit if they try to upload a file that is larger than the maximum file upload size that you have configured in SharePoint.

Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.