Large Uploads

[scaiferw]

I've been trying to enable large uploads as indicated in the thread below, but am running into a snag.

It seems the the server, SQL2005, maxes out at 2gb for individual files, so that's the maximum I'm aiming for. (Our developers occasionally need to store .iso files over 1GB.)

I changed the vault web.config file to maxRequestLength="2048576" as indicated in the thread referenced below, ran IISRESET on the server to spin the services, and I see the web admin panel now shows an IIS File Upload Limit of 2048576.

However, when I try to upload a test file of around 1.3GB, I get

[01/10/2012 8:43:50 AM] File C:\Temp\VaultLargeFilesUploadTest\TestFile.iso (1383530496 bytes) is larger than the server's configured upload limit of 1073741824 bytes.
[01/10/2012 8:43:50 AM] Transaction failed

http://support.sourcegear.com/viewtopic.php?f=5&t=18885

Any ideas where I've gone wrong?

[lbauer]

Did you restart IIS after changing the web.config file?

[scaiferw]

I ran IISRESET, which I presume is the same thing.

Perhaps I'm wrong, is there something different I need to do?

Thanks,

Rob

[lbauer]

Running IISRESET is correct.

I'd like to see your system information.

Log into the Vault Server with the Vault Client and provide the information under Help->Technical Support.

I was able to upload a 1.48 GB file with Client and Server on the same Windows 7 machine when I changed the maxRequestLength to "2048576".

Are you using Chunked Encoding? This setting is in the Vault Client under Tools->Options->Network Settings.

[scaiferw]

Here you are.

I'm using chunked encoding, also "Do not use a proxy". We've found those two settings solve most of our upload problems.

Not sure why it says "License information unavailable.", we are properly licensed.

Code: Select all

Client Information
    Vault Standard Client Version: 5.1.1.19215
    .NET Framework Version: 2.0.50727.3620
    Operating System: Microsoft Windows XP Professional
    Service Pack: 3.0
    OS Version: 5.1.2600
    Total Physical Memory: 3.24 GB
    Time Zone: (GMT-05:00) Eastern Time (US & Canada)
    
Server Information
     Server Version: 
    .NET Framework Version: 
    Operating System: 
    Service Pack: 
    OS Version: 
    Timezone: 
    
License Information
        License information unavailable.

[lbauer]

Not sure why it says "License information unavailable.", we are properly licensed.

It probably because you're not logged in to the Vault Server.

What OS is the Vault Server running on? Is it 64 or 32-bit?

How much memory on the Vault Server machine?

[scaiferw]

OK, maybe this is more useful;

Client Information
Vault Standard Client Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.3620
Operating System: Microsoft Windows XP Professional
Service Pack: 3.0
OS Version: 5.1.2600
Total Physical Memory: 3.24 GB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Server Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.4971
Operating System:
Service Pack:
OS Version:
Timezone:
SQL Version: Microsoft SQL Server 2005 - 9.00.5266.00 (Intel X86)




License Information
1 serial number(s):
1 of 1: 100 full users, permanent

[lbauer]

Thanks. For some reason it's still not giving me the Server OS.

What OS is the server using? I need to know your IIS version.

[scaiferw]

Hi Linda;

I'm running IIS 7.5.7600.16385 on Server 2008 R2.

Rob

[lbauer]

I'm not sure why the change in the Vault web.config didn't work for you, or why you're getting this value in the upload error:

server's configured upload limit of 1073741824 bytes.

There may be a setting in IIS that's over-riding what you have in the Vault web.config file.

Also, from some Internet searches, it looks like you may need to set the maxAllowedContentLength as well as the maxRequestLength. However maxAllowedContentLength is an IIS setting, and there's no configuration for this in the Vault web.config file.

http://forums.iis.net/t/1169846.aspx

It's possible it could be added to the Vault web.config, or modified in an IIS config file.

[scaiferw]

The maximum allowed content length is 30000000, or 28mb, so since we're already going way over this anyway it doesn't seem like that would be the culprit.

[lbauer]

Try changing 30000000 to something larger.

More details here:
http://social.msdn.microsoft.com/forums ... 923B099907

[scaiferw]

I've upped that value to 2gb, but since we were already uploading files far larger than 28mb I'm not sure that's the bottleneck.

Is there a way to make these changes stick without the big hammer method of resetting all the services? I can't just boot all my users offline mid-day by running iisreset, and I'd rather not boot them at all if not necessary.

As it is I've set a scheduled task to run iisreset at 3:00am, but I'd rather not wait a day between troubleshooting attempts.

Thanks,

Rob

[lbauer]

I couldn't find specific information on changing file upload size, but this link has some general information about when to restart IIS:

http://mvolo.com/when-to-restart-iis-wh ... pplication