I am having a problem moving my website from the live server to my local box. I backed up the web files, and did a SQL Server backup. I am using DNN 4.3.5

I made sure before the move that "localhost/funeralin" and "MACHINENAME/funeralin" was in the PortalAlias table. I even deleted the virual directory "localhost/funeralin" and recreated it, because I heard DDN caches this.

All I get in IE is a flashing status bar. Then "Page cannot be displayed".

In firefox I get the error: "The page isn't redirecting properly" (Cookies are enabled for both browsers)

Why does DNN do this? Where else is this cached, or stored to cause this behavior.

As an experiment, I have tried the following:

1. Live Server files + Live DB version = Error
2. Live Files + Test DB version (originally installed on local machine) = Works!

So this must have something to do with something in the database which for the life of me I cannot figure out.

Can anyone help me with this? Thank you in advance.

Hi Mitchel,

I have one one entry in my portalAlias, "localhost/funeralin" which is what I have in IIS as a virtual directory.

I know it has to be something in my DB that is not the PortalAlias, because they are identical for my test version, and my live version (I removed the www.funeralin.com entry). The test version works and the live just keeps hitting the stored proc "getPortalByAliasID(@portalid)" over and over.

I even put a break in the page_init on default.aspx, and it never even gets that far.

I am wondering why no one else has had this problem. It seems to happen to me all the time with DNN.

Any other suggestions?

Thanks!