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 ...Copying DotNetNuke Site to new serverCopying DotNetNuke Site to new server
Previous
 
Next
New Post
9/16/2010 5:02 PM
 
Hi everyone - I have been tasked with moving a DotNetNuke website from a remote server to a new server here at our company headquarters. I am not familiar with DotNetNuke so this is a new app to me. Please keep that in mind. The server the site is to move from is running SQL2000. When I built the new server, I installed SQL2005. Here are the steps I've done so far: (note: the new server is running both IIS and SQL)

1) Copied web content folder (including dnn folder) for this site to new server.
2) Backed up SQL2000 DNN database on old server and moved backup to new server
3) Restored DNN backup to SQL2005 on new server, keeping the same database name.
4) Copied SQL users and credentials from old server to new server and restored them, thus keeping same SQL user name and password for DNN specified in web.config file
5) Created a new website on new server but changed the name of the website as the old server had it running as the default website. I pointed new website to web content folder I copied in step 1. Kept same host headers but attached them to the new ip address on the new server.

I can now hit the website but certain links after you log in will give me the "Internet Explorer cannot display the webpage"
I'm thinking I need to do something to "register" DotNetnuke on the new server or similar. We are hoping that once DotNetNuke is "running" on the new server properly, the dead links will resolve. Any help is much appreciated.
 
New Post
9/16/2010 5:31 PM
 
Make sure that your portal alias(es) is(are) correct.for the new site (find it under either Host-Portals or Admin->settings menu)

Links or Image sources  that were initially set when the site was a different URL may still retain that basic URL and need to be manually changed
 
New Post
9/17/2010 4:54 PM
 
Empulse wrote:
Make sure that your portal alias(es) is(are) correct.for the new site (find it under either Host-Portals or Admin->settings menu)

Links or Image sources  that were initially set when the site was a different URL may still retain that basic URL and need to be manually changed

 Thanks Empulse! Forgive my ignorance but I'm still not sure where exactly to find these portal aliases.

 
New Post
9/17/2010 6:02 PM
 
Hi Jess,

Please make sure Application have execute permissions for scripts and executable files.  Make sure the application pool user have full access to the DNN files and folders, and the anonymous IIS user have read permissions to the DNN files and folders.  The old domain must be part of the servers DNS and bind to the website on IIS or you have to changed Alias on the PortalAlias table on the SQL database.

To come more familar with using DNN there are a lot of documentation, and help.  Please start on this Blog where also linked to all resources http://www.dotnetnuke.com/Community/B...
 
New Post
9/19/2010 2:51 PM
 
Empulse wrote:
Make sure that your portal alias(es) is(are) correct.for the new site (find it under either Host-Portals or Admin->settings menu)

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Copying DotNetNuke Site to new serverCopying DotNetNuke Site to new 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