Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...Error after moving site.Error after moving site.
Previous
 
Next
New Post
10/2/2008 12:51 PM
 
Chad P. Statham


www.mymaxstore.com
Joined: 7/2/2003
Posts: 100

OK, let's see if we can help ourselves figure this out... please anyone from the community that has the answer give us your input.

On GoDaddy:

  1. I went through the Value Applications and allowed GoDaddy to do an automated "Typical Install" of 4.8.4 worked perfectly.
  2. I then upgraded DNN to 4.9 by downloading the upgrade package, comparing the release.config file with the existing web.config file created during the GoDaddy install through their hosting control panel > Value Apps.
  3. Copied over from the existing web.config to the upgrade package release.config
    1. database connection string in two places
    2. installation date (now I have a question here; I didn't find this line in the release config so I created it with the information from the web.config)
    3. machine key and decrypt key
  4. I then renamed the release.config to web.config and uploaded the upgrade package to my subdomain / subfolder that was created by GoDaddy.
  5. I then had a working updated instance of DNN 4.9.0.

Now for the big main act.  We all want our DNN installation to work on the root of our domains at GoDaddy.  So it should be as easy as moving over the files right?

  1. I verified the root had the same permissions by going through the GoDaddy hosting control center and file manager permissions
  2. copied all files from /dotnetnuke folder on GoDaddy to the Root

And it threw this error:

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.
 
New Post
10/2/2008 3:45 PM
 
Chad P. Statham


www.mymaxstore.com
Joined: 7/2/2003
Posts: 100

Chad P. Statham wrote

OK, let's see if we can help ourselves figure this out... please anyone from the community that has the answer give us your input.

On GoDaddy:

  1. I went through the Value Applications and allowed GoDaddy to do an automated "Typical Install" of 4.8.4 worked perfectly.
  2. I then upgraded DNN to 4.9 by downloading the upgrade package, comparing the release.config file with the existing web.config file created during the GoDaddy install through their hosting control panel > Value Apps.
  3. Copied over from the existing web.config to the upgrade package release.config
    1. database connection string in two places
    2. installation date (now I have a question here; I didn't find this line in the release config so I created it with the information from the web.config)
    3. machine key and decrypt key
  4. I then renamed the release.config to web.config and uploaded the upgrade package to my subdomain / subfolder that was created by GoDaddy.
  5. I then had a working updated instance of DNN 4.9.0.

Now for the big main act.  We all want our DNN installation to work on the root of our domains at GoDaddy.  So it should be as easy as moving over the files right?

  1. I verified the root had the same permissions by going through the GoDaddy hosting control center and file manager permissions
  2. copied all files from /dotnetnuke folder on GoDaddy to the Root

And it threw this error:

 

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

 

Continued...

I have deleted the orginal subdirectory that GoDaddy install DNN to.  I have verified I have all the files at the Root as they should be.

Question: Do I have to delete the application pool from IIS that is related to the subdirectory?  Assuming that the Root is by default alwasy an app pool even though I can't see it or change it's settings?

Or, is the issue in the web.config elsewhere?
 
New Post
10/2/2008 4:45 PM
 
Chad P. Statham


www.mymaxstore.com
Joined: 7/2/2003
Posts: 100

Chad P. Statham wrote

 Chad P. Statham wrote

OK, let's see if we can help ourselves figure this out... please anyone from the community that has the answer give us your input.

On GoDaddy:

  1. I went through the Value Applications and allowed GoDaddy to do an automated "Typical Install" of 4.8.4 worked perfectly.
  2. I then upgraded DNN to 4.9 by downloading the upgrade package, comparing the release.config file with the existing web.config file created during the GoDaddy install through their hosting control panel > Value Apps.
  3. Copied over from the existing web.config to the upgrade package release.config
    1. database connection string in two places
    2. installation date (now I have a question here; I didn't find this line in the release config so I created it with the information from the web.config)
    3. machine key and decrypt key
  4. I then renamed the release.config to web.config and uploaded the upgrade package to my subdomain / subfolder that was created by GoDaddy.
  5. I then had a working updated instance of DNN 4.9.0.

Now for the big main act.  We all want our DNN installation to work on the root of our domains at GoDaddy.  So it should be as easy as moving over the files right?

  1. I verified the root had the same permissions by going through the GoDaddy hosting control center and file manager permissions
  2. copied all files from /dotnetnuke folder on GoDaddy to the Root

And it threw this error:

 

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

 

 

Continued...

I have deleted the orginal subdirectory that GoDaddy install DNN to.  I have verified I have all the files at the Root as they should be.

Question: Do I have to delete the application pool from IIS that is related to the subdirectory?  Assuming that the Root is by default alwasy an app pool even though I can't see it or change it's settings?

Or, is the issue in the web.config elsewhere?

OK, I just blasted away the application pool setup by GoDaddy under the subdirectory installed for DNN... hope I didn't just really mess up.

and it while I'm waiting for them to do that I was wondering if the original error above might have anything to do with the pipeline setting classic vs. integrated?

Hosting Control Center Help
Integrated pipeline mode

IIS 7's integrated pipeline mode handles all requests through a unified pipeline because of the integration of ASP.NET's runtime with the Web server. IIS 7's classic mode behaves in the same manner as IIS 6, using two pipelines to process requests--one for native-code application components and the other for managed code application components.

To learn more about pipeline mode, click here.
 
New Post
10/2/2008 5:15 PM
 
Chad P. Statham


www.mymaxstore.com
Joined: 7/2/2003
Posts: 100

Could this is the web.config be my problem?

    <validation validateIntegratedModeConfiguration="false" />
 
 
New Post
10/6/2008 3:45 PM
 
jrl

Joined: 5/15/2008
Posts: 44

Chad,

  It's nice to see you taking the initiative here.  I read with interest your efforts above!

I wanted to share the following snip-it from another discussion thread that I read, BUT HAVEN'T ATTEMPTED MYSELF YET:

AndrewZ said: November 25, 2007 5:19 PM

1) Check that the Root and DNN directories have the same permissions

2) Backup both your DNN web installation and your database.
3) Place html file called app_offline.htm into the DNN directory, taking the site offline.
4) Update the database table containing the Portal Alias from mysite.com/DNN to simply mysite.com
5) Move the contents of the current DNN folder into the root
6) Update any references you might have in your web.config file to your old site path.
7) Remove the app_offline.htm file and point a browser at the default.aspx file.
 
 

 

Jack
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error after moving site.Error after moving site.


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