Last week I had success uploading a very large file (1.7gB) on my development server, thanks to assistance I received here. Now I have another interesting problem.

I have a development and a demo server, both are Amazon cloud with essentially the same operating environment (server 2003, IIS6, ASP.NET 3.5). I checked the web.config files and app pool and as far as I can tell they have the same settings.

But, the demo server can't upload anything larger than 1mb or so. I begin the upload via the DMX new/file process. The progress bar starts to move and then at some point 10-30 seconds later it stops/stalls. Eventually the page is refreshed and a message that says "You must upload a file" is displayed.

I have checked and double-checked the web.config parameters and they look identical, so can anyone think of other things that might affect this? I have been googling and reading a lot of information but I have already done the things they suggest without success.

Thanks,
Bruce

Hi Bruce,

I don't have a specific solution idea, but I would try to isolate the problem on the demo server and take Amazon out of the mix by temporarily changing your target document repository to be a local file store to see if it then works and go from there.

Rob Ralston
SilverBullet Technologies LLC

To clarify, the servers are just AWS (Amazon). I am not using s3 for storage, so the document reside on the server where the app does.

Also, the httperr log is reporting "Connection_Abandoned_By_AppPool DefaultAppPool" around the time the failure occurs. Since that is the only thing happening on the server at the time of the error I am assuming it could be related.

Another note, I am using the RAD upload method.

"You must upload a file" is displayed if, after the page has skipped to the next step, the file upload control comes up empty handed or if the file has disappeared from its temporary location (portals\[id]\DMX\Upload). The most common cause for the first is that the stream for uploading has been caught by another component. The common cause of this is the introduction in DNN 5.x (can't remember exactly which version) of a rad upload handler that had the exact same path info as the Bring2mind handler. So the DNN handler began accepting the file and DMX ends up empty handed. This was resolved in a recent update of DMX by renaming the handler for DMX such that it doesn't collide any longer.

Peter

Still no luck. Thinking that perhaps my DNN install might not have been perfect, I restored and re-installed DNN 5.6.3 and DMX 5.3.8. No change. I still get somewhere between 15-30 seconds into the download when it stalls, then perhaps 10 seconds later the page re-displays with the message "You must upload a file". Peter's note about a conflict in naming seems not to apply here, as I am at the latest version of DNN and DMX as far as I can tell.

I have also tried a separate application pool for the site but that has made no difference.

I have tried the file upload from DNN's File Manager and that produces an error in the WebUpload.ascx.vb at line 310, object reference not set to an object.

Two servers, configured as near to identical as I can tell, yet one can load 1.7gb files and one can't get through a 3mb file. I'd take any help I can get.

Bruce

The "You must upload a file" error is an indication that the upload control did not receive the file. The most common cause is that the Ajax calls to the server sending the file are captured by another component than DMX's upload control. This is tricky to debug but it can be done by a skilled technician. Basically you'll need to trace the call.

You start by finding what call it is. For this you can use Fiddler. It shows what is happening between your browser and the server. You'll easily spot the ajax calls uploading the file to the "progress handler" of DMX's RadUpload control. Now the difficult part begins: looking for hints as to which component is picking up the call. Start to look very carefully through the handlers section in the web.config. These define which component picks up various calls. If the two web.configs are identical in this respect then the call is being captured before it even reaches the website. Is it going to the right website? Check the call.

Peter