Windows Forum

Ask something
Discussion Locked

HTTP file upload(type=file) with IIS 5.0

0 helpful
4 replies

by housedoc1800s

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

(2nd posting - incorrect attribution on first posting)

System: W2KServer SP2+Cold Fusion 5.0.

Baffled by a problem! Have two different W2K servers; same OS. On Server A, the HTTP file-upload command initiated from a client browser works perfectly. On Server B, when executing the same http file-upload code it doesn't complete the upload and the webpage "times out". In my troubleshooting I've been able to only succesfully upload small files to Server B(<45kb) using HTTP file-upload, but larger files fail with a "The page cannot be displayed" message.

I've made sure server B has NTFS write permission set on the folder where the file is intended to be uploaded to. I've made sure that IUSR_name user has permission to write to the folder. Using regedt32, I've also increased the UploadReadAhead value with no greater successful outcome.

I'm stumped as to the misconfiguration of Server B.

In order to demonstrate the problem, I've created two test pages, Server A testpage (the one that works well) is at http://www.dermconsult.com.au/tester.cfm.

The Server B test page (the one that does NOT upload, but should) is at http://www.tfcinfo.com/tester.cfm

You can go ahead and try uploading files to either test page. If the upload is successful you will see "VAR0,FILENAME,VAR1,UPLOAD". If the upload is NOT successful you will see "VAR0" only.

P.S. On these test pages, any uploaded files are not stored anywhere. They go off to never-neverland.

4 replies

by timthetoolman

Hi,

I'd go for running performance monitor with a log file on the two servers during the attempted uploads to see if you can spot any resource bottlenecks first.

The differences between the two may at least point you in the direction to begin looking...

Select all vaguely relevent counters (pretty much everything), log every 5 seconds and be sure to turn it off as soon as its done as it will chew enormous amounts of disk space with its log.

Cheers,
Tim.

by housedoc1800s

I appreciate your good idea for sleuthing the problem and valliant effort to suggest a solution. The actual solution came from increasing the IIS 5.0 cgi script timeout value. I'm closing the question.

This discussion is closed to new replies.