Here is the senerio:

DNN 5.0.01  working fine until I tried to go from edit mode while logged into host account to layout mode.

Now I get this:

DotNetNuke.Services.Exceptions.PageLoadException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). ---> System.Web.HttpException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). at System.Web.UI.ControlCollection.AddAt(Int32 index, Control child) at DotNetNuke.UI.Skins.Pane.ProcessPane() at DotNetNuke.UI.Skins.Skin.ProcessPanes() at DotNetNuke.UI.Skins.Skin.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

not a pretty sight to behold concidering I have a major meeting /presentation Monday am.  Has anyone ran into this before?  Oh and one other small issue I have noticed is that I am unable to login to the site in IE either 7 or 8, however FireFox works fine (well did) now nothing works.

 

Thanks for any suggestions in advance

---

Russ

Trying to work through this I found the javascript error and it no longer occures.  The other issue if I clear the cache I can get back to the site, however if I try to log in as host it blows up again, I can clear the cache and go back but logging into host still creates the same issue.  That being said is there a data file (table) that holds the last known view mode selected? 

Oh one more thing clearing the cache for FireFox works IE 7 no dice.  :(  anyone have some suggestions?

---

Russ

Have you tried 1) clearing your browser cookies and then 2) restarting/recycling the website's application pool before trying to log in again as host? If you don't have access to the server, the easiest way to restart the site is to make a minor change to the site's web.config (add a space etc.) then re-save the web.config file.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner