Hi

This problem occurs on both the built in asp.net HtmlInputFile control and the mediachase control, so its likely to be an IIS/OS problem, but you guys can hopefully help.

We recently converted an asp.net 1.1 into an asp.net 2.0 one. Locally, as all our developers are, we run 32-bit XP and the conversion appears fine - no problems at all with file uploads.

However when we release to testing, which is 64-bit, any files uploaded by either control get saved with 0kb.

Its not the maxRequestLength setting, tried that with 1million, anyway we're testing with 30k files. Code hasnt changed so its an environment thing somewhere.

Any ideas appreciated.

Al

p.s. i wanted to make this not relevant, but we have a web farm that handles the requests, and the web farm posts a byte stream (read from the file upload control) to a remoting layer to do the save to file server. pretty sure the web layer is posting 0kb, so im guessing web/iis/windows/acls or something, or 64-bit shenegans

Open your upload page and check htlm source, your form tag should include
- enctype attribute with "multipart/form-data" value
- method attribute with "post" value.
, like line below
<form method="post" enctype="multipart/form-data" ...>

If enctype is not equal to multipart/form-data, browser does not send file stream.

Did you receive correct file name (HttpPostedFile.FileName)?

I can recommend you to create simple form (with HtmlInputFile) and check that browser send correct post form with file to server.
For example, install Wireshark and capture outgoing post.

If post is ok, so you should analyze IIS settings, than ASP.NET.