cffileupload - 2 GB and up issue

[Haikiba]

I'm running a new install of CF9, on IIS 6 on Windows Server 2003.

I need cffileupload to be able to upload large files, in the neighboorhood of 5 GB. However, I'm running into this problem even after I copied the CFIDE scripts to a "publically" available directory. Trying to set upload limits greater than 2 GB throws an error a la CF8. If I set the max allowable file size in the administrator and the tag to 4096 MB, it will always show a "File size cannot exceed 0 MB" error. If I set the size in both places to 2000 MB, it works. At 2048 MB it will always show a "File size cannot exceed -2048 MB" error. In the urlscan.ini file, I have the MaxAllowedContentLength attribute at 5 billion bytes.

[chrisbowyer]

I just tried maxuploadsize="1000000" and got no error running the page. Just in case, note that size is in MB not bytes. Also, I don't think there is a maxallowedcontentlength attribute in cffileupload.

[Haikiba]

Setting maxuploadsize to 1000000 yields a "File size cannot exceed 576 MB" error. It's strange in that at 2048 MB it loops around to the negatives. At a maxuploadsize of 2049,the error says "File size cannot exceed -2047 MB." Where I reference maxuploadcontength is in the urlscan.ini file, which governs the largest size file IIS will accept.

[tclaremont]

I believe IIS has a customizable max upload limit setting, so even if the CF setting were adequate it may still fail when hitting the web server limit.

It has been quite a while since I faced this issue, so don't quote me on it, though.

[chrisbowyer]

I ran the page with ColdFusion's built in web server, so maybe that's why I didn't get an error. I can't help you with IIS.

[Haikiba]

In IIS 6, the urlscan.ini file controls its upload limit with maxAllowedContentLength in bytes. Right now I have it set to 5 billion bytes.

[tclaremont]

Going way out on a limb here, but are you sure you have enough free space to upload the file? Again, it has been a while, but I dont think the file gets uploaded to the destination directory immediately. I think it goes to a temp location during the upload, and THEN it gets moved to the desired location. Naturally you will need plenty of free space in the temp location.

What is your timeout setting? Is there a chance you are running up against that?

[Haikiba]

I have 10 GB available on our virtual server, and the files get transferred to a server with TB of space available. Our connection timeouts set on IIS and on the upload handler page is 7200 seconds with a cfsetting tag.

The error is in the flash interface itself, so any file over 2 GB that I select regardless of settings will get rejected by it. If I ramp the maxUploadSize up past 2047, it won't let anything through, no matter what the size, and the error message goes to the negatives - maxUploadSize of 2048 shows -2048, 2049 shows -2047, etc.

[tclaremont]

Using the flash interface for a file upload is new terrotory for me, so please forgive the questions. When you use this process, does any part of the file EVER get to the server, or is it being stopped on the client side completely?

[Haikiba]

That's OK. Well, if I have the maxUploadSize set below 2 GB, say 2000 MB, it functions normally. If I take it to 2048 and above, nothing, not even a 1 KB text file, can get to the server, because according to the error message the file size is greater than -2048 MB. I have my maximum allowable file size in the administrator currently at 2500 MB, and I'm testing with a 2.2 GB file.