Thanks again for a great utility Dean! I used your advice and was successfully able to setup the application utilizing NeatUpload in staging and am now working with the team to move it to production. I don't have access to the server that the application will reside on but will give as much detail as I possibly can and include an error from the IIS event viewer.
- NeatUpload 1.1.3
The application works great on staging and I'm able to upload files totaling nearly 800MB with no timeouts. As soon as the team moved the application over to production we noticed timeouts almost instantly (within 5 minutes) on files over 50MB. The IIS configurations are supposed to be similar and unfortunately I'm not able to remote in. I did request and received the following event log for this application. I'm hoping that maybe you can see something that I missed by viewing the stack trace and the configurations we are using.
The production site requires authentication and the staging does not. We did move the application to a directory on the production server that did not require authentication and the results were the same.
Event Type: Warning
It should also be worth mentioning that the application isn't in a web garden / farm and doesn't use a proxy server.
It sounds like there are 2, possibly related, issues. The first is that you can't upload files over 50MB. There is probably something between the browser and your app that is limiting the size of the upload. For example, URLScan and IIS7 request filtering have both been known to restrict the size of uploads. To ensure that it isn't a problem with NeatUpload, remove the UploadHttpModule from your Web.config and try to upload a large file again. You won't get a progress bar, but the InputFile and MultiFile controls should continue to function. If you still get the "page can not be displayed" error when uploading large files, the problem is probably with something other than NeatUpload. You could create a separate test page on the same server and user a standard FileUpload ASP.NET control (with the UploadHttpModule removed from the Web.config) if you wanted to be absolutely certain that NeatUpload wasn't the cause.
The issue with the timeout in the logs might also be firewall related if there is something that is preventing the server from connecting to itself. Since you aren't using a web garden/farm, the easiest way to workaround that issue is to use the InProcUploadStateStoreProvider by changing your <neatUpload> section to:
<add name="FilesystemUploadStorageProvider" type="Brettle.Web.NeatUpload.FilesystemUploadStorageProvider, Brettle.Web.NeatUpload"/>
<add name="InProcBasedUploadStateStoreProvider" type="Brettle.Web.NeatUpload.InProcBasedUploadStateStoreProvider, Brettle.Web.NeatUpload"/>
|Free forum by Nabble||Edit this page|