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 ...Transfer DNN site to new hostingTransfer DNN site to new hosting
Previous
 
Next
New Post
8/21/2011 6:33 PM
 

Hello,

I'm in the process of moving a DotNetNuke website from PowerDNN hosting to GoDaddy.  The site resides in the httpdocs folder on PowerDNN so I installed the Dot Net Nuke software in a subfolder called httpdocs on GoDaddy.  Once the install was complete, I uploaded the files from PowerDNN to this subfolder on GoDaddy's hosting.  I then downloaded the database from PowerDNN as a .bak file, used SQL Server Management Studio to restore the database and then upload it using the Database Publishing Wizard.  I grabbed the web.config file from PowerDNN and updated the connection string information.  When I go to test the site, I receive the below error:

The namespace 'Resources' already contains a definition for 'GlobalResources'

I renamed the GlobalResources.Portal-0.resx to GlobalResources.Portal-0.old but this didn't resolve the issue.  I didn't add a portal alias on the live site before starting the migration, could this be the reason I'm receiving the above error?  Any help is appreciated.  Thanks in advance.

 
New Post
8/21/2011 9:33 PM
 
I would have to say - really . . . ???  Godaddy is up there with one of the worst possible places to host a dnn web site.

But seriously . . . - first off there is no reason to put dnn in a subfolder on the godaddy site.

PowerDNN uses the httpdocs folder as the ROOT folder for your hosting ... so any files in the httpdocs would be copied across into the ROOT folder of a godaddy hosting.

As for the error - get the files into the right place and then see what other errors you get.

Westa

 
New Post
8/22/2011 3:09 PM
 
i agree, i'm not a fan of godaddy for a dnn site, but i'm transferring the site there for a client... dnn requires read/write access doesn't? i thought i had read somewhere that godaddy's ROOT folder only allows read access
 
New Post
8/22/2011 4:34 PM
 
i agree, godaddy isn't the best setup for dnn, but this is a client's site i'm working with... i believe i read that godaddy doesn't have read/write access on the ROOT and that's something that dnn requires? if i need to place the dnn files from powerdnn in godaddy's ROOT, i didn't see a way to enable read/write access.
 
New Post
8/22/2011 9:06 PM
 
Not sure this is it but check to make sure you only have one web.config file anywhere in your folder structure.

Good luck!


Josh
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Transfer DNN site to new hostingTransfer DNN site to new hosting


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