Uploading large files fails (2003 and 2008)

Perfil de BradSharePoint BlogFotosBlogListas

Herramientas

Ayuda

< Anterior Siguiente >

17 julio

Uploading large files fails (2003 and 2008)

When you attempt to upload a large file in Sharepoint, you may receive errors relating to timeouts, 404s etc.

To resolve this, make the following changes:

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 (Web Application properties). You may also need to perform the following additional actions (depending on your hardware configuration):

Increase the maximum upload size
Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
Under Virtual Server Configuration, click Configure virtual server settings.
On the Virtual Server List page, click the virtual server you want to change.
On the Virtual Server Settings page, under Virtual Server Management, click Virtual server general settings.
Under Maximum upload size, type the maximum file size (in MB) that you want to allow to be uploaded.
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
Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
Right-click the virtual server you want to configure, and then click Properties.
Click the Web Site tab.
In the Connections section, in the Connection timeout box, type the number of seconds you want IIS to wait before timing out.
Click OK.
Increase the default chunk size for large files
The large–file–chunk–size 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 large–file–chunk–size –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.

If you want to 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.

On your server computer running Windows SharePoint Services, open Notepad.
In Notepad, navigate to the %HomeDrive%\Inetpub\wwwroot folder and open the web.config file.
Locate the PropertySize attribute in the configuration\SharePoint\WebPartLimits element.
Change the PropertySize attribute to the maximum size you need.
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).

Additional changes in 2008 server:

In 2008 server, there's a second change you need to make as well -

In either the WSS3 / MOSS site's Web.config, add / update the following line -

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

If you wish to apply it across all sites, make the change in the Application.config file in %windir%\system32\inetsrv\config\applicationhost.config

Other Notes:

You may find these hints useful as well

In the web.config file for the farm (Program Files\Common Files\Microsoft Shared\Web server extensions\12\TEMPLATE\LAYOUTS), update the executionTimeout value in this line:

You may also have to do something similar if the property is declared in the Web Application -

13:35 | Agregar al blog

Comentarios (2)

Para agregar un comentario, inicia sesión con tu cuenta de Windows Live ID (si utilizas Hotmail, Messenger o Xbox LIVE, ya tienes una cuenta de Windows Live ID). Iniciar sesión

¿No tienes una cuenta de Windows Live ID? Regístrate

Brad Saideescribió:

Well Said Yaohan.

Make sure that you have Quota profiles set up and in force across all sites - this way you can "manage" the MP3 collection that someone tries to upload while at the same time allowing the saving and storage of larger site templates (because Site Collection Administrators are not affected by quotas).

27 Julio

Yaohan Yaohanescribió:

I would be careful before doing this. One of the reasons is because your site may suddenly explode and use a lot of storage, which may make your DR strategy a lot harder to meet the SLA.

The other is that with any file in SharePoint, user will need to download the file locally before being able to open it. It does not support streaming. Thus, depending on the file size and network, your user may have a sluggish user experience in working on files, thus may turn user off from sharepoint.

Of course, there will be xception and you will need to upload a large file at times, but make sure you keep an eye on it and do not let it out of control.

18 Julio

Vínculos de referencia

La dirección URL del vínculo de referencia de esta entrada es:

http://sharepointblog.spaces.live.com/blog/cns!74C8FB1191265567!531.trak

Weblogs que hacen referencia a esta entrada

Ninguno