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...Errors Upgrading from 7.0.0 to 7.3.2 - Appears as a 6.x installation via web.configErrors Upgrading from 7.0.0 to 7.3.2 - Appears as a 6.x installation via web.config
Previous
 
Next
New Post
9/8/2014 11:49 PM
 

Over the course of my 10 years or so of using DNN I've performed countless upgrades on many sites, and my current situation has me stuck, so I'm looking for a hand.

 I have a site that is running 7.0.0, and I attempted to upgrade it to 7.3.2 using the routine ftp file method.

 Just to recap exactly what I did:

1. Backed up site files

2. Backed Up DB

3. Downloaded and extracted the 7.3.2 upgrade package.

4. Set the 'AutoUpgrade' to false in the current web.config file on the site

5. Uploaded the Upgrade files to the site with the 'overwrite' option.

6. Lauched the site /Install/Install.aspx?mode=upgrade

 

This is where it started to get a bit hinky.  Usually you see all green success and move on.  In this case a number of the 7.0.x sql provider scripts failed, then some of the 7.1 scripts worked, and then again some failed, and so on through the 7.2 SQL provider scripts until it made it to the module upgrades.  Then some failed, but some passed.  It really seemed to have no rhyme or reason. I also was told by someone from interactive webs who was helping troubleshoot another issue on the site that it looked like my site was still using an outdated web.config file from an old 6.x installation. 

 

Exactly what do I need to be doing during upgrades to ensure that any new items fields etc. are getting updated in the web.config?  Is there a reason that the upgrade process does not handle this?  I cannot attach the web.config file here but if anyone can offer insight please let me know.  Or if you think looking at the actual web.config file will help reach out in response to this thread and I can arrange to get a sanitized copy for you.

 

Thanks!

Dustin


___________________________________________ Make It a Great Day! D-Man
 
New Post
9/9/2014 2:42 AM
 
did you unblock downloaded upgrade zip file prior to unzipping the files in it?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/9/2014 9:56 AM
 

Sebastian,

  No I apparently did not (although I thought I had).  I can't believe after doing this for so long such a simple step tripped me up, and I didn't catch it.  This is why my friend, you have always been an amazing member of the community and I look forward to your advice blogs and forum posts.  

After business hours today I will try to perform the upgrade again this time with the unblocked files. 

 

But can you also enlighten me as to the new items/fields etc. in the web.config file.  If I do a diff on a 7.0.0 web.config file vs 7.3.2 there are different items which are not present in the older version and some things removed. 

As I previously stated this apparently was a problem for the iwebs-Register Module.  What is the method you use to get the latest web.config settings into the file during an upgrade, if the upgrade package has no web.config file present?  Or should that happen during the upgrade process with the files unblocked now?

 

Thanks!

Dustin


___________________________________________ Make It a Great Day! D-Man
 
New Post
9/9/2014 11:58 AM
 
Dustin,
web.config should get modified automatically during Upgrades, however there shouldn't be many changes since DNN 7.0.
Web.config of an upgraded DNN might have a different order for sections and keys (and maybe some outdated sections as well), but as long as the hierarchy is same, this should not be an issue.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Errors Upgrading from 7.0.0 to 7.3.2 - Appears as a 6.x installation via web.configErrors Upgrading from 7.0.0 to 7.3.2 - Appears as a 6.x installation via web.config


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