Installing and Using Service Packs for Windows SharePoint Services

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Service packs are intended to help you keep your installation up to date with the latest security enhancements, product feature enhancements, and fixes for common problems. The following service packs have been released for Microsoft :

  • Service Pack 1 (SP1) - September 2004

Installing and Using Service Pack 1

SP1 includes fixes for several issues, including the following:

  • Formatted text moved after plain text after relinking form.When you relink a form in your Windows SharePoint Services Web site that contains rich text, all formatted text is moved from its original position to after the plain text.

  • Cannot search past or future events in your Windows SharePoint Services Web site.When you try search for events in your Windows SharePoint Services Web site, past and future events are not found. The search results include only the next event.

  • Cannot add a Web Part to your online Web Part gallery.When you try to add a Web Part to your online Web Part gallery, the Web Part is not added. This issue may occur when the file name of the Web Part contains international or language-specific characters.

  • Error 403.1 when creating Web site in Windows Server 2003.When you try to create a new Windows SharePoint Services Web site on a computer running Microsoft Windows Server 2003, you receive the following error message:HTTP Error 403.1 - Forbidden: Execute access is denied. Internet Information Services (IIS).

  • Oldest item always listed first in discussion board.When you try to sort items in Threaded view in a discussion board, the oldest item is always listed first.

  • Links at root of Web site are broken after restoring Microsoft SQL Server database.When you restore your SQL Server database to your Windows SharePoint Services Web site, links contained at the root of your Web site are broken.

  • Language of template pack does not appear in Select Language list.After you install a language-specific Windows SharePoint Services template pack, the language of the pack does not appear in the Select Language list of the Sites and Workplaces page.

  • Cannot upload large files to your Windows SharePoint Services Web site.When you try to upload a large file to your Windows SharePoint Services Web site, you may receive an error message.

Note: Windows SharePoint Services SP1 also includes several security updates that are not included in this list.

For a complete list of fixes included in Windows SharePoint Services SP1, see the Microsoft Knowledge Base article number 841876 .

Install Service Pack 1

Caution: Before you apply the service pack, you should back up your Windows SharePoint Services environment. For more information about creating a backup, see Backup and Restore Options for Windows SharePoint Services .

If you already have Windows SharePoint Services installed, do one of the following:

If you do not yet have Windows SharePoint Services installed, download the current version of Windows SharePoint Services from the Microsoft Download Center Web site , which includes the updates from Service Pack 1.

Configuring Large File Support

The biggest change included in SP1 is the support for uploading large files. By default, the maximum size for uploading files is set to 50 MB. If you need to be able to upload larger files (such as when you use smigrate.exe to migrate a site between servers), you can change this setting to any value up to 2 GB (2047 MB).

To configure large file support you must increase the default upload size in SharePoint Central Administration. You may also need to perform the following additional actions (depending on your hardware configuration):

  • Tune the Microsoft Internet Information Services (IIS) connection timeout setting.

    The default timeout for connections in IIS is 120 seconds (2 minutes). Depending on your maximum file size and how long it takes for the file to be uploaded, you may not need to change this setting. If, however, IIS is timing out when you upload large files, you can change this property to ensure that larger files can be uploaded successfully.

  • Increase the default chunk size for large files.

    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.

  • Increase the maximum size limit for Web Parts.

    By default, the maximum size limit for a Web Part is 1 MB. If you need to accomodate large Web Parts, you can change this setting in the web.config file for your server or servers running .

Increase the maximum upload size

  1. Click Start , point to All Programs , point to Administrative Tools , and then click SharePoint Central Administration .

  2. Under Virtual Server Configuration , click Configure virtual server settings .

  3. On the Virtual Server List page, click the virtual server you want to change.

  4. On the Virtual Server Settings page, under Virtual Server Management , click Virtual server general settings .

  5. Under Maximum upload size , type the maximum file size (in MB) that you want to allow to be uploaded.

  6. Click OK .

If IIS is timing out when you upload large files, you can configure the Connection timeout setting in IIS to allow more than the default 120 seconds (2 minutes).

Tune the IIS connection timeout

  1. Click Start , point to All Programs , point to Administrative Tools , and then click Internet Information Services (IIS) Manager .

  2. Right-click the virtual server you want to configure, and then click Properties .

  3. Click the Web Site tab.

  4. In the Connections section, in the Connection timeout box, type the number of seconds you want IIS to wait before timing out.

  5. Click OK .

Increase the default chunk size for large files

The largefilechunksize property must be set from the command line. This property is configured for a server or server farm, and cannot be configured for an individual virtual server. To set this property, use the following syntax:

Stsadm.exe o setproperty pn largefilechunksize pv <size in bytes>.

After making a change to this property, you must restart IIS. You can restart IIS by typing iisreset on the command line.

Increase the maximum limit for Web Parts

This change is required only when working with large Web Parts.The maximum limit for Web Parts is set to 1048576 bytes by default.

  1. On your server computer running , open Notepad .

  2. In Notepad, navigate to the %HomeDrive%\Inetpub\wwwroot folder and open the web.config file.

  3. Locate the PropertySize attribute in the configuration\SharePoint\WebPartLimits element.

  4. Change the PropertySize attribute to the maximum size you need.

  5. Save and close the web.config file.

Large file support limitations

The following features do not support files larger than 50 MB:

  • Virus checking.

  • Picture libraries.

  • Streaming files.

  • Client-side restoration of smigrate backup files (limited to 2 GB). The manifest files for an smigrate backup cannot be larger than 2 GB.

  • Site templates (limit of 10 MB per site template, including content).