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...Administration ...Administration ...Restoring DotNetNuke To Local Server...Restoring DotNetNuke To Local Server...
Previous
 
Next
New Post
8/10/2007 12:05 PM
 

Hi everyone,

I have been running a DotNetNuke site at GoDaddy for several months now.  Yesterday, I attempted to upgrade it, and ran into a number of problems.  Before I did the upgrade, I backed up the database into a .bak file and copied the entire DNN directory to my computer.  When I restored the database using GoDaddy's tools, something went wrong, and I wasn't able to log in to their database manager.  I called them for support, and the guy basically said that he was escalating the issue.  Apparently, they just added the backup/restore feature a few weeks ago, so it probably hasn't been throughly tested.  So, the site is down.

Since I have a copy of the database and the DNN directory locally, this morning I attempted to recreate the site locally.  I was able to load all of the database information into an SQL 2000 server (which is the GoDaddy server uses), and it appears that all of the data is intact.  I ran into some problems initially with the connection string, but I eventually got a connection string to work in my web.config file.  When I got that to work, the site began to refer me to the domain URL (i.e. it redirected me to my production dot net nuke that is currently down).  I searched in a couple tables, notably dbo_PortalAlias and dbo_HostSettings, and tried to change the HostURL or alises to the local IP address, or 127.0.0.1, or localhost, but now the problem is that firefox will give this error:

The page isn't redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

- This problem can somtimes be caused by disabling or refusing to accept cookies.

Anyway, now that I have explained my situation, does anyone have any advice or suggestions regarding this situation?  Specifically, has anyone attempted something similar with GoDaddy and DNN, or does anyone know what the problem is when I try to recreate the system on my local machine?

Any help would be greatly appreciated!

Jason Pell

 

 
New Post
8/13/2007 3:08 PM
 

Any insight at all?  :-/

 
New Post
8/13/2007 5:23 PM
 

After you change the portal alias table you might need to restart the application (Save your web.config file with an extra space to do this)


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
8/14/2007 10:20 AM
 

Thanks for the reply.  I got past that error using either your suggestion or one that I tried.  I had the directory saved on the hard drive in all lowercase, but the virtual directory was in uppercase.  Previously, it was in lowercase in the database, so I changed it to uppercase.  I have another problem, but I will be making an additional posting for that.  Thanks again for the help!

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Restoring DotNetNuke To Local Server...Restoring DotNetNuke To Local 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