Skip Ribbon Commands
Skip to main content

Quick Launch

Todd Klindt's home page > Todd Klindt's Office 365 Admin Blog > Posts > How to troubleshoot file upload problems in SharePoint
July 30
How to troubleshoot file upload problems in SharePoint

Time for me to wax nostalgically. I remember the good old days when the only thing that really kept users from uploading files was the "Max Upload Size" setting in Central Administration. But alas, times change and things get more complicated. Now when files won't upload there's a whole laundry list of things to look at. And if you're like me, laundry lists are not your forté. Just ask my wife.

This came up this week as I was trying to upload my netcasts to my shiny new hosted web space. The rock stars at Rackspace have graciously agreed to host my media files. While I'm sure it's because they're great people, part of me thinks it's self serving so they don't have to suffer through the slow downloads of getting the files from my current setup. J

Once we got the site provisioned I started the task of uploading all of my previous netcasts to the new spot. That's when the hilarity began. I won't take you through every single foible, but here is a list of things to check if you're having problems uploading files to SharePoint:

  1. Web App upload setting: This is the most obvious thing, and the one you should check first. Go to Central Admin > Application Management > Web App General Settings (/_admin/vsgeneralsettings.aspx). You should always start there.
  2. While we're in the Web App general settings, take a look at your Web Page Security Validation settings. If you're uploading large documents across a slow connection, the page security could time out before the file gets up there. Increase that value as needed from its default of 30 minutes.
  3. While we're in Central Administration, let's make sure your file type isn't blocked. Go to Operations > Blocked File Types (/_admin/BlockedFileType.aspx) and make sure your extension isn't listed. This is a web app specific setting, so make sure you're changing the setting for the correct web app.
  4. Now we're going to hit some obscure settings. By now you should be using Windows 2008 (and it better be 64 bit, too!). With Windows 2008 came many improvements, including IIS 7. While IIS 7 includes all kinds of great improvements, it also quietly brought with it an upload limit. Regardless of what you do in SharePoint, IIS 7 out of the box limits you to around 30 MB uploads. KB 944981 covers how to increase this. However, the instructions aren't completely correct. Make sure you backup your web.config before changing it. My experience has been that you need to make the recommended additions between the </configSections> and <SharePoint> tag. Otherwise it'll break your web app. Also keep in mind this is a web app specific setting, so make sure you're editing the correct web.config.
  5. You can also change the IIS connection time out for your web app. In IIS 7 find your web app's site in the IIS Manager and click the "Limits" link on the right in the "Actions" pane. The default is 120 seconds. Feel free to make that much longer.
  6. Finally, since upload.aspx is an application page it has its own web.config settings. You can read how to increase its timeout settings in KB 925083. This is one I've had to do a lot.

That's about it. That last KB article has some other guidance on how to troubleshoot upload errors. This blog post is better, of course. J If you've had to do other stuff to fix file uploads, leave me some comments. I will cover this in more detail in next week's netcast. Thanks again to the fine folks at Rackspace for putting up with me.



There are other settings

Hey Todd

Keep working on Opeth and Amorphis :-)

On an on topic note, don't forget that in a corporate env if you use the Webdav mini-redirector it has a 50MB limit. I think its all Webdav clients (Vista/200x) but I've never checked

You may receive an error message when you try to download a file that is larger than 50000000 bytes from a Web folder on a computer that is running Windows XP with Service Pack 1 or with Service Pack 2

This issue occurs because a security change in Windows XP SP2 affects the Web Distributed Authoring and Versioning (WebDAV) redirector. This security change makes sure that an unauthorized server cannot force a client computer into a denial of service attack. If you try to download a file that is larger than 50000000 bytes, the client computer interprets this download as a denial of service attack. Therefore, the download process stops

• Click Start, click Run, type regedit, and then click OK. 
• Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters 
• In the right pane, right-click the FileSizeLimitInBytes value, and then click Modify.
• If you cannot see the FileSizeLimitInBytes value, right-click the blank space in the right pane, click New, click DWORD Value, type FileSizeLimitInBytes, and then click OK.
• In the Edit DWORD Value box, click to select the imal option. In the box under Value data, type a value that is larger than the size of the file that you want to download. Click OK.
• Note The default value for the file size limit is 50000000 bytes.
• Quit Registry Editor. Restart the computer. 
 on 7/30/2009 7:59 PM

A couple more...

You can also get file upload problems for the following 2 more reasons:

1.  The filename has strange characters in it.  If you're uploading one file at a time, you'll get a nice descriptive error, but if it's a multiple file upload, you won't really know what's wrong.

2.  There have been so many folders deep created in the document library, that the URL path has exceeded a certain number of characters.  SharePoint simply won't let you upload a new file when this happens, and I don't remember what the obscure error is that it returns... but it's happened in our environment before.
My response:  Don't use folders, people!  Use metadata and views.  They just don't get it.  ;-)
 on 8/6/2009 1:52 PM

Re: A couple more...

Forgot to sign that last one...

Signed, your biggest fan!

Laura Rogers
 on 8/6/2009 1:57 PM

IIS 7.0 File Upload Limit

My situation was as described above. 30 MB upload was the best we could do. Followed the KB article you mention did an iisreset and the problem was solved.

Thanks, Bill Burke
 on 10/6/2009 9:07 AM

WSS3 large file download problems: not upload. Can you help?

Read a lot of different posts. Our prob is not large file uploading (changed the limit to 1GB in Central Admin), it's downloading a 200MB file from a Sharepoint library/list. Would it be relevant to make the registry change to FileSizeLimitInBytes on the Windows 2003 server? 
Or is this just for the client computer? Our clients won't know or want to change the registry on their own pc. Keep getting the Server is Out of Memory Sharepoint errors when downloading large files over the 50MB limit. Large file uploading is fine. Any ideas how to fix download issues with large files in WSS3? Thanks
 on 1/30/2010 7:53 PM

Re: WSS3 large file download problems: not upload. Can you help?

Did you make the change in that KB article to see if it worked? I've never seen the problem you're having, but it sounds very similar to what the KB article described.

Todd O. KlindtNo presence information on 1/31/2010 5:04 PM

unable to complete the operation

i  can  not  upload    any  kind  of  file  on  my  Sharepont  portal  even  a   1kb,what  could  be  the  problem ???

Awadhi  Njovu

Dar es salaam
 on 5/11/2010 12:34 AM

Re: unable to complete the operation

Could be a lot of stuff. I would look on the SQL side. Are your drives full? Can your data files (MDF) or log files (LDF) grow?

Todd O. KlindtNo presence information on 5/11/2010 9:51 AM

Webclient Cache

Hi all

I have a problem with webclient.
I'll explain:
doing a massive upload via webdav on SP2007 server, the folder "C:\Documents and Settings\LocalService\Impostazioni locali\Temporary Internet Files\Content.IE5" fills up to saturate the disc.

For file < 50Mb the client manages the cache, but for larger no.

Someone knows how to solve this problem or how to move the cache folder?

Tnx a lot
Sergio Luppo
 on 6/8/2010 4:15 AM

Webclient Cache

Hi all,

I'm replying to myself: it seems that was an unresolved bug in xp webclient that uses WinINet protocol, instead of WinHTTP (as in > Vista)..

 on 6/10/2010 5:00 AM
1 - 10Next

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.


Body *

Today's date *

Select a date from the calendar.
Please enter today's date so I know you are a real person


Want a message when I reply to your comment? Put your Twitter handle here.