After a deployment of Dotnetnuke, or after a change in the overall configuration (changing connection string for instance), the navigator seems redirecting infinitely until it stops with an error indicating that there are too much redirections.
Evidences
Looking with Fiddler what's happen, you get that kind of content:
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US">
<head>
<title id="Title"> Error </ title>
<link id="StyleSheet" href="/dnn/Install/Install.css" type="text/css"
rel="stylesheet"> </ link>
</ head>
<body>
<form name = "Form" method = "post" action = "ErrorPage.aspx? status = 500 &
= Thread error was + + + being aborted." id = "Form">
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="blablabla" />
cellspacing="5" cellpadding="5" <table border="0" class="Error">
<tr>
<td> id="Image1" src="logo.gif" alt="DotNetNuke" <img border="0" /> </ td>
</ Tr>
<tr Style="height:100%;">
<td Valign="top" style="width:650px;">
<h2> DotNetNuke Error: - Version 04.08.03 </ h2>
<hr />
<p> Thread was being aborted. </ p>
</ td>
</ Tr>
<tr>
<td align="right"> <a id="hypReturn" class="WizardButton"
href="Default.aspx"> <img border="0" /> src="/dnn/images/lt.gif"
Return to Site </ a> </ td>
</ Tr>
<tr> <td Height="10px"> </ td> </ tr>
</ table>
</ form>
</ body>
</ html>
Explanations
There is an Error somewhere in the Dotnetnuke startup process, therefore Dotnetnuke redirects to its error page, BUT the error page can't complete because of the Error. And so on...
Reasons
There is an error in the initialization process of Dotnetnuke. Here are some suspects:
- web.config with an invalid value in the connection string for instance -> no database -> error
- PortalAlias table has an invalid value (i.e. localhost)
- .Net Trust Level is not set to Full Trust, or it seems that sometime setting successively Medium then Full forces the refresh of the virtual folder config (?!? I read that somewhere, I tried, and it worked)
The redirection is probably not due to any redirection rule (check anyway), but is due to the fact that there is an error in the configuration and the Dotnetnuke Error page is unable to complete.
Redirection to an error page that raises an error is nightmare, check with special attention all your configurations, and you'll find the origin of the error