Hello,

I have read other threads on here regarding moving your site from Test -> Prod and having to update the PortalAlias table to match your new fully qualified domain name. But I think the issue I'm seeing is different, let me list the steps I've taken and then describe what I'm seeing;

1. Copied database and website to production servers
2. Configured web.config to point to new database server
3. Entered new publicly accessible domain name in alias table
   1. Verified I could access a standard html file through this FQDN
   2. Attempted to access DNN site and got a redirect to the first entry in the PortalAlias table
   3. Changed the initial entry in table to point to www.msn.com
   4. Rinse and repeat and get directed to www.msn.com
4. Entered internally accessible IP address of production server
   1. Verified I could access a standard html file thorugh this IP address
   2. Entered internal IP addres into PortalAlias table
   3. Attempted to access DNN site and succesfully browsed site

Bottom line is, I know the new FQDN is working because I can view entries in the IIS log file that show that default.aspx is being served. However, I am getting an entry that shows my FQDN with an HTTP_ERROR code of 302 (temporary redirect).

Any help? I'm stuck and have to release by Wednesday.

Thanks Everyone!

Hi Michael,

It would help identify the issue you're having if you could determine where DNN is attempting to 302 redirect you to.  If I were in your shoes, I would use a http proxy like Fiddler to see where Default.aspx is trying to redirect.  Usually the problem would become immediately apparent after this information was identified, but if you are unable to proceed, post the 302 details here and I'll try to assist further.

Brandon

Hi Michael,

Well, that doesn't really clarify much.  DNN is trying to send you off to the installer, which could mean several things (one of which is a bad database connection). 

Do you have any exceptions logged in your event viewer?  Are there any relevant exceptions logged in your DNN database (in the EventLog table, look in the LogProperties column)? Are there any other redirects in Fiddler prior to that final 302 status?

Brandon