skip to main |
skip to sidebar
The following instructions are recommended for overcoming out of box limitations related to uploading documents. These configurations are done once per web application and are not global changes. 1. Central Administration > Application Management > SharePoint Web Application Management > Web Application General Settings > Maximum Upload Size: Change to 2047 MB (Maximum)2. Internet Information Services Manager > Web Site > Right-Click > Properties > Connections: Change Setting (e.g. 600 seconds)3. Windows Explorer > Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Layouts\ > Web.ConfigReplace This:
httpRuntime maxRequestLength="2097151"
With This:
httpRuntime executionTimeout="999999" maxRequestLength="2097151"
4. Web.Config Continued...Replace This:httpRuntime maxRequestLength="51200"
With This:
httpRuntime executionTimeout="999999" maxRequestLength="51200"
5. Windows Explorer > INET PUB\WWWRoot\VirtualDirectories\WebApplication\ > Web.Config
Add the snipet from http://support.microsoft.com/kb/944981%20BconfigSections between the "configSections" closing tag and the "SharePoint" opening tag (like Shane suggests in his post).
References:
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
http://support.microsoft.com/kb/944981
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"
http://support.microsoft.com/kb/925083
Windows Server 2008 WFE will not allow large file uploads
http://msmvps.com/blogs/shane/archive/2008/12/17/windows-server-2008-wfe-will-not-allow-large-file-uploads.aspx
Over the past few months, I have been upgrading numerous SharePoint environments to SQL Server 2008 and I have wrestled with system performance. Unless adjustments are made, SQL Server will attempt to consume more than its share of processor. I've seen this cause SharePoint web applications to freeze and become unusable. A resource management measure for SQL Server 2008 which I consider to be crucial for SharePoint environments, is outlined below. These steps will limit SQL Server Management Studio and Query Analyzer to 25% processor utilization, and possibly preserve the usability of the SharePoint farm. I strongly recommend these steps for SharePoint environments using SQL Server 2008.SQL Server 2008 Resource GovernorSteps take from TechNet article: Integration of SQL Server 2008 and Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc990273.aspx1. Create a resource pool to limit CPU usage to 25 percent
CREATE RESOURCE POOL poolAdhocWITH (MAX_CPU_PERCENT = 25);
2. Create a workload group for ad hoc queries and register it with the new resource pool
CREATE WORKLOAD GROUP groupAdhocUSING poolAdhoc;
3. Create a function that classifies Management Studio and Query Analyzer as members of the ad hoc group
CREATE FUNCTION adhocQueryClassifier() RETURNS SYSNAMEWITH SCHEMABINDINGASBEGIN DECLARE @grp_name AS SYSNAME IF (APP_NAME() LIKE '%MANAGEMENT STUDIO%') OR (APP_NAME() LIKE '%QUERY ANALYZER%') SET @grp_name = 'groupAdhoc' RETURN @grp_nameENDGO4. Register the new function with Resource Governor
ALTER RESOURCE GOVERNORWITH (CLASSIFIER_FUNCTION= dbo.adhocQueryClassifier);
5. Restart Resource GovernorALTER RESOURCE GOVERNOR RECONFIGURE;
Want to view a demonstration of current and future capabilities of FAST ESP? Here are a couple YouTube videos that provide a great overview. Fast ESP for SharePoint - 1 of 2http://www.youtube.com/watch?v=kTbcCNby8xEFast ESP for SharePoint - 2 of 2http://www.youtube.com/watch?v=WjW6ZjX8Pyk
By default, MOSS will not crawl URLs which are case sensitive. However, Microsoft Help and Support Article ID 932619 provides instructions for making a registry modification to the Index server which allows case sensitive URLs to be crawled.Microsoft Help and Support Article ID 932619: You cannot crawl case-sensitive Web content in SharePoint Server 2007http://support.microsoft.com/kb/932619It is important to note that a content index reset is required. For this reason, this modification may require a maintenance window for production environments, especially large environments with lots of items in the content index that will need to be crawled again. Like most system changes, it is a good idea to test this first in Development or QA environments, record the change, and then schedule a time to deploy it to production. The instructions are straightforward, however, the first time that I made the modification, the search service didn't start properly so I had to stop it and start it a second time. Then it was fine. Running through the steps in Development or QA first will allow you to work the kinks out.