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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade SQL and DNNUpgrade SQL and DNN
Previous
 
Next
New Post
2/7/2011 4:54 PM
 
I've now got access to the "Host" section which I can now add a portal alias. I am moving from a production to production so can I just use the new IP address of the new host?
 
New Post
2/7/2011 4:58 PM
 
Sebastian Leupold wrote:
no, you don't need to delete portal aliases. Simply make sure, there is the correct one to reach the site in it.

Can I use an IP address for the portal alias? I am not moving from development to production, I am moving from one production server to another.

 
New Post
2/8/2011 6:03 PM
 
I've followed the directions from here and yet I still get redirected to the installation script. I get no errors when backing up from SQL Server 2000 and restore to SQL Server 2008.

I don't understand what the problem is and why the heck this is so difficult to move your installation from one server to another.

Does anyone else have any other suggestions?
 
New Post
2/9/2011 12:40 AM
 
I did a move from one production site to another once. This is not so complicated, when you have some understanding of MSSQL.

As Sebastian pointed out, when the installer pops up, DNN most likely cannot connect to the database. So the first step should be to check the user id and password you provided in web.config. Can you connect to the database using the SQL Server Management Studio? If you have administrator access to the database, you could also try using sa as user id, just to check out where the error lies. If you can connect as sa, then there is something wrong with the user id assigned your database. Did you make it dbowner?

Do check and double-check is the comment signs (<!-- etc.) (&lt;!--) have been moved correctly in web.config, so that the connection strings are the ones for SQL server, not for SQL server express.

____________________________________
The one-eyed in the land of the blind.
 
New Post
2/9/2011 11:44 AM
 
My situation is different than most thought. I am moving from SBS 2003 to SBS 2008 as well as upgrading from SQL Server 2000 to SQL Server 2008. Obviously, this is going to be a little more difficult and I understand that.

I can access the database fine through SQL Management Studio. I will do some more configuration and try some of the options you've suggested. Thanks for your comments. I wouldn't have even gotten this far without all the help thus far (for that I am appreciative).
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade SQL and DNNUpgrade SQL and DNN


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