Member Avatar for fayola

running IIS6 on server 2003.
wrote a classic asp app for uploading flash videos, I have a couple of videos about 2MB each that upload no problem, but the client now has files that are 25MB and 30MB each and IIS times out when trying to upload these.

I have tried Enabling Direct Metabase Edit and changing the following to:
AspBufferingLimit="50000000"
AspMaxRequestEntityAllowed="50000000"
AspScriptTimeout="360"

But still timing out, I'm going to try extending AspScriptTimeout some more but is there anything else I can do to upload these files without timing out?

:cool:

  • 2 Contributors
  • 2 Replies
  • 124 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by sknake

Dani AI

Generated

Related to ’s report and ’s suggestion: larger uploads that work in small sizes but fail at ~25–30MB usually point at a layer other than the classic-ASP parser (which already had its limits adjusted). Useful checks and remedies are listed below.

Verify server- and site-level timeouts and recycles. The Web Site “Connection time-out” (IIS Manager → site → Properties → Performance) can kill long POSTs; increase it for testing. Application pool recycling (scheduled or memory-based) can interrupt long uploads — suspend recycling while diagnosing. After metabase edits, restart the service to ensure changes take effect (iisreset).

Inspect logs to find which layer aborts the transfer. Review Event Viewer (Application and System), the HTTP error log at C:\Windows\System32\LogFiles\HTTPERR, and the IIS W3SVC logs under C:\Windows\System32\LogFiles\W3SVC*. Look for connection aborts or sc-status codes such as 408/413/503; those point to timeouts, request-size rejections, or service interruptions and will narrow whether IIS, http.sys, a proxy/ISA box, or a firewall is dropping the request.

If timeouts persist, avoid buffering the entire POST in classic ASP. Use a streaming upload solution (a well-tested third-party ASP upload component or an ASP.NET handler that supports streaming) or implement chunked uploads so each request stays small. Also check intermediate devices (load balancers, proxies), antivirus scanning on temp/upload directories, and free disk space on the system drive. Back up the metabase/registry before edits and apply changes during low-traffic windows.

Recommended Answers

All 2 Replies

Member Avatar for fayola

wow, no suggestions? still timing out :(

Member Avatar for sknake

Have you checked the event logs of your server? Is the client receiving an error message?

I think the event logs would be the best place to start. Let me know what you find

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.