Hi,
I am trying to move a site I have created from one hosting company to another. I have copied all the files from the exsisting hosting and uploaded them to the root of my new hosting. I have exported the database using sql server manager to a local database. I have then setup my new database with the same db name user name and same password. I have then imported the database to my new hosting. I have changed the webconfig file to show the new server value. Usr name and pass etc are still the same. I have setup prepopergation support on my new hosting as i dont want to redirect the domain name until I know its all working. So far that is all I have done. When I try to access the site on the new hosting I get nothing, no error message and no site!! any ideas what I am missing. Or am i doing this in completely the wrong way?

Regards

Roger Goodwin

Take a look at the techniques outlined in these tutorials:

• How to backup a live hosted DotNetNuke website and restore it to a localhost installation
• How to transfer a localhost DotNetNuke installation to a live website

You should be able to use them to transfer a site from one host to another one.


My guess would be that you haven't changed the PortalAlias table in the new database to point to the new server.

I have had a look at the videos and I have done most of what you recomend. The only differances are that I didnt backup the database i just created the database and then exported the local database. The other issue I might have is that the origional DNN site used an sql 2000 database where my new hosting uses an sql 2005. Would this cause a problem?
I did go into the existing site and add the portal alias. I then re ran the export of the database again.

the error i am getting is as follows.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

Roger,

I think that it definitely would be worthwhile to modify web.config so that you can see the full error messages.

One thing that you could test is can you login to your newly restored 2005 database and view the tables and data?