A DotNetNuke(DNN) Website Errors Saying the Page Isn't Redirecting Properly
Issue
When you go to your DotNetNuke website, the page either continually flashes (in IE) or you receive a "The page isn't redirecting properly" (in FireFox) error message.
Cause
While there are many causes for this error, the two most common are:
- Incorrect page permissions in the DotNetNuke website.
- An invalid portal alias
Resolutions
Verify Page Permissions Are Set Correctly in the DotNetNuke Website.
Note: This fix's test requires use of the Control Suite. Shared hosting clients do not have access to this program.
- Use the Control Suite to log into the website as the HOST user.
- If you are not able to log into the website using the Control Suite, the issue is not caused by invalid page permissions.
- Verify that the Home Page and the Login Page are set to allow All Users to have View permissions. Please keep in mind that the home page and login page may be changed from their defaults under Admin > Site Settings. Just because a page has a name of Home does not mean that it is set as the home page.
Determine if it is a Portal Alias Problem:
These steps require you to have Microsoft SQL Server Management Studio installed on your computer. If you do not have this installed Microsoft SQL Server Mangement Studio Express 2008 is available for free from Microsoft, and can be downloaded through this link: http://www.microsoft.com/download/en/details.aspx?id=22985
- Open SQL Server Management Studio and connect to the server.
- Go to Databases > [Database] > Tables. Right-Click on PortalAlias and select Edit Top 200 Rows or Open Table (depending on SQL version)
- Carefully verify that all portal aliases are spelled correct and contain no special characters. A common issue is for a portal alias to contain a leading or trailing slash or space.
- If an invalid portal alias is found, correct it by editing the database directly and then Recycle the Application Pool.
Article ID: 201, Created: April 6, 2012 at 10:37 AM, Modified: August 25, 2014 at 2:37 PM