See and this is what I mean.. the only thing that is different here is that I tried it again from another computer (3rd computer) and this time it installed :)

I really don't get it... such a wierd problem.. Thanks again..

-Chris

Hi.. here's an update... And some strange results...

2 computers: 1 - Desktop (IE, FireFox), 2 - Laptop (IE)

I should also note that this install problem affects skin, and container uploads as well as modules.. (Same behavior where I'm sent back to the calling page with no errors, and no log entries about the installation request.. it's as if it never happened)..

For the sake of clarity, I will refer to this behavior (click "upload new file", no install runs, no log entries made, get sent back to the calling page where the upload new "whatever" was initiated, etc.)...  as

    "Strange Upload Behavior (SU Behavior)"

Ok, from the laptop using IE.. I successfully uploaded and installed a skin and then  tried to install another one and I got the SU Behavior... So I went to my desktop and tried to install the same skin with IE and got the SU Behavior again.. So on a whim I decided to test FireFox and the skin uploaded fine... Then, later I tried uploading (with FireFox) a new custom skin (that I've been working on) and I got the SU Behavior again... I'm confused at this point so I tried it again from IE and I think it worked...

I made more updates to the skin and tried to upload again using IE and then FireFox and both were triggering the SU Behavior so I went back to IE and logged out and tried again, same behavior.. Then I cleared the logs and tried again with IE and it worked...

Also there was one time I couldn't get a skin to upload until I went to the "Host Settings" page and tried to upload the skin from there.. Same browser, same session... Just clicked a different "upload skin" link and it worked...

Maybe tonight I'll do some hard core testing to see exactly what's going on here.. But maybe this has something to do with the cache in the browser?  It seems after a time, the installs work on the same computer with the same browser where it failed only a day or two earilier.

Any other thoughts on this? This is becoming a major problem for me since I've been working on customizing a skin for my site... Thanks in advance for all the support guys :)

-Chris

I've seen the probem on DNN 4x from day one.  Subsequent versions made no improvements.  In the log, you should be able to see that it has captured some errors (as a matter of  fact a lot of errors).

There is a bug somewhere between DNN and ASP.net that thinks you ran out of memory at the server.  Your DNN log could be showing the application startup/shutdown in the middle of your session.

I was able to demonstrate this but am unable to arrive at a solution yet.   I found that if you increase the RAM in you server (increase ALOT not just a little) then the problem would appear to go away; however, if at the server, you increase it's memory usage by running increasing more applications simulatneously, you will see this SU Behavior appear again.