Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Large File Issues

  Asked By: Mackenzie    Date: Jun 15    Category: Sharepoint    Views: 6232

I should probably search the site for a while before my first post, but
going out on a limb anyway.

I have a document library being used for a picture repository. The
pictures range from 1 to 350 MB. Also, the files are in many
different formats, Tif, JPG, etc.

The issue that I have is that when someone is in detail view, checks
the boxes for a selection of pictures, including one picture that is
large, and then clicks download; the download fails. The users get as
far as the download pictures popup window and it fails after this.

We have not applied any service packs as of yet, because we are still
in an evaluation environment.

Share: 

 

12 Answers Found

 
Answer #1    Answered By: Deonte Stein     Answered On: Jun 15

either:
-increase your page timeout in the web server.
-install SP1 at a bare minimum for WSS (www.microsoft.com/.../stsd05_SP01121517.mspx)

even evaluation's are patchable so i dont see why you wouldnt want to?

 
Answer #2    Answered By: Stephon Valentine     Answered On: Jun 15

I set up a test server and patched it to WSS SP2 and I am still
having the issue. Which time out are you speaking of? I have
increased, on my test server, just about every timeout that I could
find. I even attempted to see if the Office Picture Manager had a
timeout that I was missing.

 
Answer #3    Answered By: Leif Cardenas     Answered On: Jun 15

I am going to hazard a guess and say that he is speaking about the timeout in ISS, and this is where it would be:

Please don’t hesitate to correct me if I’m wrong..

 
Answer #4    Answered By: Jasper Hatfield     Answered On: Jun 15

sorry, i dont think my whole url made it but heres what it says:

Configuring large  File Support
The biggest change included in Windows SharePoint Services 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 Windows SharePoint Services.

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 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.

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 Windows SharePoint Services, 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).

(www.microsoft.com/.../stsd05_SP01121517.mspx)

 
Answer #5    Answered By: Rashawn Hopper     Answered On: Jun 15

I am going to hazard another guess since I have no pictures that large  to test
against.
We use the system's temp directory during the upload of large files after SP1.
Is it possible that we are using it for downloads too? If so, the everyone (or
authenticated users) group needs read/write permissions on the temp directory
AND it should be moved off the system drive to one where there is space and no
I/O conflict.
Are your users having any problems with uploads or is it just downloads?

 
Answer #6    Answered By: Horace Coffey     Answered On: Jun 15

The issue only happens with downloads. I believe that the uploads
work just fine. I remember from the class that I took two weeks ago
with you in Boston about the file  rights. I do not remember how to
move the location, but this is an informality because I created a
script that cleans up this location nightly, prior to the backup.

 
Answer #7    Answered By: Rigoberto Beard     Answered On: Jun 15

The issue only happens with downloads. I believe that the uploads
work just fine. I remember from the class that I took two weeks ago
with you in Boston about the file  rights. I do not remember how to
move the location, but this is an informality because I created a
script that cleans up this location nightly, prior to the backup.

 
Answer #8    Answered By: Alphonso Mckay     Answered On: Jun 15

When a file  is larger than 50 MB my users are not able to download
them when selecting to download multiple files. The large  files all
seem to be tiff format, but I have tested large PDF files and they do
the same thing.

I know there is a location to set the maximum file size upload, but
there seems to be a limitation on the download size as well.

What is an LOB and what backwards thing? There is an isue with NTFS
permissions on the c:\windows\temp\frontpagetempdir location if the
inet_user can not read, write, or delete files. This is the
temporary location used to cache up the file before the download
occurs.

 
Answer #9    Answered By: Daron Oneill     Answered On: Jun 15

i was re-reading this again and noticed that..

(www.microsoft.com/.../stsd05_SP01121517.mspx)
Large file  support limitation
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).


so that may explain the symptoms if you are having issues  with picture  libraries.

if you are still having the issues, perhaps you can check the section entitled "Configuring large  File Support" for the 3-4 things you can do in addition to changing settings in SP central admin pages.

>What is an LOB and what backwards thing?
Dont worry about the backwards thing.. if you dont know what it is, you shouldnt need to (its for people who never completed thier sps2001 upgrades).
As for the (B)LOB - www.windowsitpro.com/.../20460.html - its basically your file stored inside a database as opposed to being on the filesystem.

>c:\windows\temp\frontpagetempdir location if the inet_user can not read, write, or delete files. This is the temporary >location used to cache up the file before the download occurs.
I've never seen files left there, in fact im not sure files are ever put there (ill enable folder auditing to see just to make sure) even for caching purposes.. sql server likely handles all file caching from the database and ASP.net for the display (which is cached somewhere else). i'm not sure however!!

 
Answer #10    Answered By: M Juarez     Answered On: Jun 15

It is my understanding that prior to Sharepoint SP1, files being uploaded were loaded into RAM until the upload was complete and then sent to SQL.

After SP1, every 400k of the file  is placed in the system temp directory until the upload is complete, then the file is re-assembled and sent to SQL. Hence, after SP1 the 50MB limit was removed. (But left in the GUI.)

 
Answer #11    Answered By: Marty Mcdowell     Answered On: Jun 15

On the subject of the c:\windows\temp\frontpagetempdir I can see the
file being cached at this location during a download/upload. I know
this because I was working with one of my team members and discovered
it. I have noticed that not all files get deleted from this location.

On the subject of SP1, I have installed SP2 on a test server and
fully patched the Windows OS. I am still experiencing the same
issues with the Temp directory and fle downloads.

 
Answer #12    Answered By: Brandon Gross     Answered On: Nov 19

My company Attunix specializes in developing Digital Asset Management solutions. We have a solution that allows for managing any size files with SharePoint. If you are interested in learning more about the solution, feel free to reach to me at brandong@attunix.com. Thanks, Brandon.

 
Didn't find what you were looking for? Find more on Large File Issues Or get search suggestion and latest updates.




Tagged: