I've just installed DNN for the fourth time and something is happening that never happened before. I've tried both 5.4 and 5.5 and it doesn't matter. The installation goes smoothly, no problems at all. But when I use the portal all hell breaks loose.

First I add a page using the common task pannel and I'm greeted by the following page:

Server Error in '/' Application.

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly. 

Requested URL: /PaginaPrincipal.aspx

So then I create another page and BOTH the new and the "failed" one appear! So I go into the Pages administrator to delete the wrong one but BOTH dissapear. And even when I manage to delete them, if I add another one with the same name it says it already exists as if I didn't delete it.

If that's not bizzare enough, if I keep refreshing the portal the pages appear and dissapear randomly.

And now onto changing skins. I choose another of the default skins (MinimalExtropy full) and DDN tells me this:

-          An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. ---> System.Web.HttpException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Page.LoadAllState() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

What's going on? I have no idea. Help, please :S

please check and make sure the application pool is not set up as a webgarden i.e. it's not using more than 1 worker process. As asp.net is not webgarden ready each individual process does not share cache/session (we don't use session in dotnetnuke though some 3rd party modules may), so this can cause issues e.g. if you add a page the first worker process does that and updates the cache, and then the page loads and the 2nd worker process sees if it's valid and as it has an "old" version of the cache shows a 404. Further F5's result in this repeating (though somewhat randomly as other users will be causing thread changes)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

I still get the error. I reinstalled using and independent App Pool but when I changed the skin from "default" to "full screen" I still get different versions of the same page if you press F5.


I've tried to remove modules from the "fullscreen" one but I was recieving this error:


An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. ---> System.Web.HttpException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Page.LoadAllState() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

But the module was removed... Of course if you press F5 at http://derechoeinnovacion.unican.es you will get 2 versions: The "default page" you are greeted when you finish your DNN installation or the one with my modifications (no modules, fullscreen skin)

Any other ideas of why is it happening? A wrong version of ASP.NET? (I've heard it's 2.0.50.72 and 3.5sp1 is required)