I have picked up and moved a complete dnn installation from one box to another.

I have reinstated the db and all appears good permissions, etc. - wise in SQL Server.

I have change the various login strings in web.config to match up with this new host and I have ensured the PortalAlias for the new host dns exists in the db.

But when I load the site now, I get a login dialog and it doesn't matter which creds I try, it doesn't seem to want to load.

Can anyone tell me what is happening pls?

I would expect not as I used the same web.config and db. I detached the db and copied the files, then moved the copies. And I copied and moved the entire dnn directory. Have I done somthing wrong in this process?

So it is on a 3rd party module that used AJAX ?  Could it then be that the server have not the AJAX Framework installed ?

And your question before:
The best way to move a DNN instance from one server to a other is to backup the database using SSMS and restore it on the new sql server. Some Hosting applications (like PLESK) could also be used to backup and restore the database, if you have also other domainname modify the Portal table.  Then copy all the files of DNN to the new server and make your changes on the web.config file and make sure you have set the physical folder permissions and the IIS configuration.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN