Search code examples
dotnetnuke

DNN redirect Loop - only on admin screens


I do not undrstand this problem.

The other issues mentioning this redirect problem is related to portal aliases and full/med trust levels, etc.

I have a .net 4 Classic pool pointing to the recently upgraded DNN install.

Previous version was 5.xxxx, and now I have upgraded to 7.0.5

All the current cms pages work. When I go to the admin section, and in there choose page management, or host setting in the host section, then I get this problem.

I know dnn is slowly going down the MVC path, although I still see .apx extention floating around, meaning they have not fully cashed into the seo thing, but they are 80% there I guess.

I do not understand where the problem is.

It is almost like half of the site is still on the tabid=x idea, but some of the admin screens is on the more friendly url concept of "/host/HostSettings//tabid/16/portalid/0/Default.aspx" kind of firendly url / MVC conept.

Is there an entry that I can edit to either have everything in friendly urls, or every thing using the tabid concept and then move forward from there?

Or does the redirect problem have nothing to do with friendly urls?

I am a bit lost here, even after developing in DNN for many years...

Thanks in advance!

As per Chris's advice I went through all the tabs in the table and made sure nothing is set to isSecure=True.

Still get: Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects. IS there a way to turn redirect off in the tables?

I have gone through the entire hostSettings and PosrtalSettings tables and compared it with another working system, but could not find anything obvious...

EDITED

Now with a few things turned off and debug mode set to true, I get the following:

Server Error in '/cms' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

[No relevant source lines]

Source File: c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\cms\3fbf2a3e\66b53196\App_Web_xepmxekk.1.cs Line: 0

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.UI.Containers.ActionBase.get_ModuleContext() +7 DotNetNuke.UI.Containers.ActionBase.get_ActionRoot() +30 DotNetNuke.UI.Containers.ActionBase.OnLoad(EventArgs e) +35

[ModuleLoadException: An error has occurred.] DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +397

[PageLoadException: An error has occurred.] DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +417 DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc) +96 DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +548 DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(Control ctrl, Exception exc, Boolean DisplayErrorMessage) +188 DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(Control ctrl, Exception exc) +40 DotNetNuke.UI.Containers.ActionBase.OnLoad(EventArgs e) +71 DotNetNuke.UI.WebControls.SolPartActions.OnLoad(EventArgs e) +13 System.Web.UI.Control.LoadRecursive() +54 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Control.LoadRecursive() +145 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +772

[PageLoadException: An error has occurred.] DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +417 DotNetNuke.Framework.PageBase.OnError(EventArgs e) +629 System.Web.UI.Page.HandleError(Exception e) +79 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6695 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +245 System.Web.UI.Page.ProcessRequest() +72 System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21 System.Web.UI.Page.ProcessRequest(HttpContext context) +58 ASP.default_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\cms\3fbf2a3e\66b53196\App_Web_xepmxekk.1.cs:0 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +341 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929


Solution

  • I can get to the site settings page, after upgrading to the latest dnn 7.0.6.

    I am not sure why it stopped working after the last upgrade, and the started to work on the next upgrade.

    But some pages became non editable..

    You edit the content, hit save, and then the old content came back.

    That is another annoying issue.

    I decided to rebuild the CMS from scratch, and have a clean slate, as I think the old CMS has gone through too many upgrades.