Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help Migrating Site to Another ServerHelp Migrating Site to Another Server
Previous
 
Next
New Post
5/30/2009 8:15 AM
 

Hello...

I'm trying to transfer my site to WebHost4Life.  I had it up and running on my local WHS server fine.  I followed all of the directions for migration exactly.  They where as follows:

When I type in my domain I just get the generic "this site is under construction" page.  It seems to be pointing to the install/underconstruction.htm  Any help is greatly AppreciatedThanks.

 

 

To transfer and migrate your exisitng DNN site, you need to:

1. moving your files

2. moving your database

3. configuring your web site.



1. moving your files

- Get a copy of your DNN files. If you were hosting your DNN from other hosting company, you can consult with the company and download them from FTP.

- Next upload your DNN files to your hosting account folder using FTP. Your FTP information can be found from your hosting control panel. The location of the files you should upload to depends on the path your domain point to. eg. If your site is http://mydnn.domain.com and you have created this subdomain from your hosting control panel and pointed to path c:\....\member\yourmemberID\DNN, then you should upload to DNN folder from FTP. This is because your ftp root is pointing to c:\....\member\yourmemberID. For help on using ftp, please refer to this article.

 2. moving your database

- make a database backup of your database. Note, this is backup file generated from the database server, not a raw database file and log file ending with mdf and ldf

- create a database with the same name and same login id from your hosting control panel

- from the mssql database menu in hosting control panel, click on "restore db" next to the new database you recreated. You will find a "Click here to create FTP access to the Database server, if you haven't do this already." link to create your ftp account to upload your database backup file. Follow the instruction to create the ftp account

- Now upload your database file through the new ftp account. When it is done, go back to the mssql admin page in hosting control panel. Click on "restore db", enter the information and click restore.

- Now you have your database migrated.


3. configuring your web site

- you need to configure file permission, edit your connection string, and configure your asp.net application to fit your DNN

- go to hosting control panel -> security -> file permission. Find the folder that contain your DNN files. Click the the "EDIT" button, give "NETWORK SERVICE" "Full Permissions".

- control panel -> File Manager, go into the folder that contains your DNN files. Find within the folder there's a file named "web.config". Your connection string is located in this file. You can edit the file from the file manager. Update the connection string to use your new database. Note, DNN 3.22 and later has two connection strings, please make sure you update both.

- If your DNN site is in a folder under your domain, eg. http://domain.com/mydnn, go to hosting control panel -> site admin -> .NET Application. Click "GO" next to your domain, click on "set application' icon next to the folder your DNN site is at. Now you have the folder set to a seperated asp.net applicatoin and it is displayed on top of the screen.

- If you are using DNN 4 and later version, you also need to click on "change .net version" to asp.net 2.0 from the same screen.

- If your DNN site is at the domain root, eg. http://mydnn.domain.com or http://domain.com, and, is DNN 4 or later, go to hosting control panel -> site admin. Click on "change root's .net version" next to the domain for your DNN, change it to asp.net 2.0.

 
New Post
6/1/2009 4:11 PM
 

noah white wrote
 

When I type in my domain I just get the generic "this site is under construction" page.  It seems to be pointing to the install/underconstruction.htm  Any help is greatly Appreciated.  Thanks.

You need to make sure that Default.aspx is your default document.  See WH4L's support if you don't know how to do this.  If you installed DNN in a subfolder, you need to use that subfolder in the URL, as in www.sample.com/mydnn/.

Jeff

 
New Post
12/10/2009 2:02 AM
 

 I want to migrate an existing installation of DotNetNuke from Win2003/SQL2000 to another machine Win2008/SQL2008.

Following the above quidelines I make a complete backup on the old installation getting a TRN file. When importing this file I get the error (similar to): "Error restoring the database. The database is different from the existing one."  Even if using the compatibility level for server 2003.

So i tried to manually import all tables and stored procedures and this seemed to work, I got the site running. 

But now it is no longer possible to login to the portal.

What can be done?

Thank You, Franz

 

 
New Post
12/10/2009 4:15 AM
 

Franz,

TRN files usually contain the transaction log (while BAK  hold the database).

if you backup/restore, make sure, the user account specified in your web.config connection strings has been granted dbowner permission.

Besides, you need to make sure, the machine key in your web.config has not been modified (compare with a backup).


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/10/2009 7:49 AM
 

Thank you for the ultra fast answer.

Yes, using the BAK-File solves the problem of easy transfer of database. It is no longer nesessary to transfer the tables and procedures manually.

But the problem with the login still remained. 

I copied the complete installation simply to the new computer an the only thing I changed was the connection string. All other entrries were not touched.

But  I remind me of a short installation phase at the first start of the application an the new location . And during this phase the original machine keys were modified. After replacing these values with the old ones all works fine.

Thank you very much.

Franz 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help Migrating Site to Another ServerHelp Migrating Site to Another Server


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out