Re: Downloads Fail With IIS 6.0
From: Jason at CDS (JasonatCDS_at_discussions.microsoft.com)
Date: Fri, 13 Aug 2004 07:49:01 -0700
Unfortunately, the FTP idea isn't an option. We have an FTP server, but it
isn't very secure. Plus, we would have to rewrite many pages of our web
application, create a more secure FTP site, with different users/privileges,
rewrite our web administration client so the support people creating these
files can upload them to a different location...an awful lot of work and zero
time to do it in the next three years.
I was on the phone for a long time with an IIS specialist from Microsoft
Support yesterday, but the issue still isn't resolved. She is having some
network specialists look at some things. So it still remains problematic.
Interestingly, she, one of her colleagues, and one of my colleagues, were
all able to successfully download the same test file off our old W2K IIS 5.0
machine all at the same time...so it's not a firewall issue, not a network
issue, and not a client issue.
I'll post any updates as they come available.
"Andrey P" wrote:
> Well, I could say that it's something may be related to network latency,
> server connectivity or anything else. I don't have an idea at the
> moment. We have a lot of servers with mostly default timeout settings
> and I never heard about such a problem (T3/OC3 connectivity).
> If the downloading of an appropriate file is a crucial task for you, I
> would recommend to set up a FTP server and put that file (files) on it.
> Jason at CDS wrote:
> > I have an httperr.log file that has 1774 entries in the past 9 days, and 1504
> > of them say "Timer_MinBytesPerSecond".
> > What that means to me is that very few files are being downloaded
> > successfully. We're in the midst of a global website project, whereby our
> > downloadable files will all be hosted from this location. But if local people
> > can't even get them, I don't see how someone halfway around the world could
> > possibly get them.
> > As for different locations, I tried from home, my colleague tried from his
> > home outside his VNC, I tried from a machine located here but outside our
> > firewall, and I even had the wife try from her place of employment. Small
> > files aren't a problem, but large ones always time out.
> > There are no problems I could see in the connection logs - just a whole lot
> > of code 200's (successful page requests). The system and application event
> > logs don't mention anying to do with IIS either. So it would appear that this
> > is strictly a connection/download issue.
> > And as for anything inside the network, it "usually" isn't a problem with
> > the files that are sitting on the web server's hard drive. But dynamically
> > generated PDF's tend to take a long time, and sometimes don't ever get
> > completely created and/or sent to the client browser.
> > We've been having other issues that might be related: smaller PDF files will
> > appear to download, and show the correct number of pages, but have all blank
> > content inside the IE window using the Adobe PDF plugin. We went so far as to
> > put some quick-fix ideas right on our site - like right-clicking the link and
> > saving the target file to the user's hard drive, or changing Adobe so that it
> > opens in its own window instead of inside IE. But I have a feeling, now that
> > we've discovered this download/timeout issue, that the download/timeout issue
> > is more likely the problem rather than a possible Adobe/IE problem.
> > Thanks for any suggestions you can make.
> > "Andrey P" wrote:
> >>Jason at CDS wrote:
> >>>Is there any other way to keep connections open long enough to download a
> >>>large file (say a 10MB pdf file)?
> >>>I have the Connection timeout set at 3,600 seconds on both the Web Sites
> >>>Properties and the Default Web Site Properties. I have tried adding this
> >>>registry key:
> >>>I have dropped the MinFileBytesPerSec property in Metabase.xml down to 10.
> >>>Nothing seems to work. If you try to get a small (<1MB) file it works great.
> >>>But larger files timeout 99% of the time, for 99% of the people access the
> >>>I have spent the entire day researching forums and newsgroups and websites
> >>>for an answer, but none of the suggestions I found have worked. I think it
> >>>has to do with the http.sys api waiting for receipt verification of packets,
> >>>but I'm not completely sure.
> >>>At this point, any and all suggestions are welcome. The "powers that be" are
> >>>ready to make me move everything back to a W2K box with IIS 5.0. I don't like
> >>>the sound of that!
> >>I don't see any reason for that. Did you give it a try from different
> >>locations? What if you download pdf file on the same server?
> >>Any messages in IIS log ? In IIS error log
> >>(c:\windows\system32\logfiles\httperr\) ?
> >>Any events in event log ?