DNN redirect Loop - only on admin screens

Question

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

Answer 1

You're asking a lot of questions here. I'll address the one on your subject.

1) If you are seeing redirects on the Admin pages, check the database, often times on old upgrades the "issecure" flag will be set on those admin pages, and that will cause odd redirects. If you have access to the database, just check out the TABS table.

Update 4/16/2013 You might try disabling FriendlyURLs all together and see if that helps you at least get into the admin/host pages. On the DB try updating the UseFriendlyUrl setting in hostsettings, if you don't have an ObjectQualifier in your web.config you could use this SQL

update hostsettings
set SettingValue = 'N'

where settingname like 'usefriendlyurls'

UPDATE Based on the updated question, I'm thinking that you have one of two problems. Either the Skin is having issues due to using the SolPart menu, or more likely, your MODULE Containers are having problems on the page.

I believe you said you can access the ADMIN page now, but not child pages. I would set the Skin the Admin page (through the page settings) to one of the Gravity Skins (whichever you like). Then, once you've saved those settings, try the Apply Skin to All Child Pages, see if that sets the skin on all the admin child pages correctly. If setting the Skin doesn't work, try the same for the Container on the Admin page.

If that works, then you might have to do the same for the HOST menu. Though you might need to do that one through the DB.

Answer 2

Shaun, Where is this issue currently. Last we had talked I asked about the Admin urls and TabIDs. I would recommend you find a page, under Admin, such as Site Settings, and figure out what the TabID for that page is.

Then try to go to http://somedomain.com.blah/default.aspx?tabid=## replacing ## with the number of the TabID for the page in question. Let's start there, and see what happens.

Answer 3

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.