I'm running DNN 5.1.4 Community Edition, unmodified, on my dedicated Windows 2003 64-bit server with SS2005EE 64-bit. I've been running a stable DNN production environment for over 6 years with no major issues. Today, I created a new page and accidently gave it the same name as an existing page. After it generated an error, I changed the page name of a unique value and it created the new page (the new page copied several modules from an existing page).

After it created the new page, whenever I try to navigate to it, DNN redirects me back the login page (standard DNN login with no mods). Anytime I try to navigate to the new page, it just sends me through an infinite loop to the login page. I've since deleted this page, emptied the recycling bin, and created several more with numerous variations of characteristics and no matter what I try, I can no longer create a new page and navigate to it without getting into a infinite loop through the login page. I've gone through all the Tabs tables at a cursory level looking for abnormalities and cannot find anything obvious. I've flushed all cache, restarted the app, recycled IIS, and bounced my server, all to no avail.

The duplicate page number produced an expected error mesage: System.ArgumentException: An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value) at Bring2mind.DNN.Modules.DMX.Services.Logging.LoggingController.LogMessage(Int32 PortalId, String Application, Exception exc, Level messageLevel, String message). But, no errors are generated in the infinite login loop problem.

As is, my DNN installation is trashed because I can no longer create a new page on any of my portals and navigate to it (irrespective of view permissions).

Any recommendations would be greatly appreciated! Should this be submitted as a potential bug?

Thanks,

John

Sebastian,

Thanks for the response. Actually, my settings were fine in the Tabs table.

After much research, I discovered that the problem was caused by a module I had installed from DNNMasters entitled SEO URLProvider. There's evidently a bug in this module that's responsible for redirecting URLs. When the DNN page creation event failed (in my case due to a non-unique name), it caused a problem in this module's data integrity that prevented it from making additional entries in its tables. So, as new pages were created, this module couldn't create new SEO-friendly redirects for those pages and so they went no where and defaulted back to the login page.

I disabled this module and then had it rebuild it's data and now it's working fine.

Hope this helps anyone else who encounters this issue. I'll report the issue to the module vendor.

Thanks everyone,

John