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
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...GoDaddy & Upgrading DNN 5->6GoDaddy & Upgrading DNN 5->6
Previous
 
Next
New Post
5/30/2012 10:19 PM
 
Ryan Ramsey


Joined: 5/25/2012
Posts: 20

Ive had a lot of issues with upgrading my stock installation of DNN to 6.x

 I started out (walking into this environment from another admin) with DNN at 5.6.1 and using GoDaddy's interface to upgrade to 6.1.5. Although the installation succeeded, the outcome was failure.

When I logged into the portal after the upgrade, I got a black framed login box but when I entered my creds, I got a System Exception and that was the end of it. After subsequent attempts to log back in, I got the same issue.

I then rolled back to 5.6.1 and was introduced to the DNN wiki (http://www.dotnetnuke.com/Resources/Wiki/Page/Suggested_Upgrade_Path.aspx) that introduced upgrades and noticed that the first upgrade path to 6.x was through 5.6.4, particularly because of the Telerik library (documented in http://dotnetnuke.codeplex.com/releases/view/75803)

So my questions to the community are this

  1. When i originally upgraded from 5.6.1 to 6.1.5 could the failure I had be due to the issues resolved in 5.6.4?
  2. Has anyone successfully upgraded to 6.x on GoDaddy and how did you do it, from what version to what version.
  3. I currently upgrade via ftp. Is there any benefit or downfall to using the integrated 'critical update
  4. Do i need to upgrade my extensions BEFORE the upgrade? Is there a way to tell what extensions are included in the upgrade vs. ones that i have to do manually?
  5. If I do the upgrade and an extension is not updated, could that cause my whole system to fail or just render that outdated extension inoperable?
  6. My plan was to upgrade from 5.6.4 to 6.0.2 and then to what? 6.2 directly? It is advisable to upgrade from 5.6.4 to 6.2 without the 6.0.2 intermediate step? The wiki (http://www.dotnetnuke.com/Resources/Wiki/Page/Suggested_Upgrade_Path.aspx) seems a little out of date.

My big issue is that I only have ftp access to this site, with no rollback options on the localhost and my only recovery option is recovering from an ftp backup which is very painful. I would like to get as much knowledge as possible before continuing.

 Sorry for the long laundry list of questions but any advise would be very helpful as I have already had my panic moment and don't wish to repeat it.
 
New Post
5/31/2012 2:38 AM
 
Matthias Schlomann


Joined: 8/10/2003
Posts: 3594

A Upgrade from a very old release could be very painfull.  Basicly I would then do this on an test instance with a cloned system to find out the steps I needed.

Then to upgrade a large number of versions, I would try to use the new install package, and make a copy of the old web.config file about the install package have a own web.config included. 

  1. Backup the database and files
  2. create a copy the old web.confg file
  3. Extract the install package
  4. modify the new web.config file and trasfer both connection strings, Install Date,  Maschine Key, ObjectQualifier and databaseOnwer, from the old file to the new web.config.
  5. Check the permissions and be sure the application pool user have full access to the root filesand they are inherit to all subfolders and files!!!!   (On some szenariouses it can be that the IUser must have execute permissions)
  6. Run the upgrade on the test system.
  7. If the Upgrade runs without issues do the same on the production site.  If not, try to upgrade in several version steps. 

Good luck!

Updated:
It could be you have first Upgrade some of the modules you have in use.  On 3rd partity module, be sure they are worked with the new version.  Also check if the Skin supports the new version or change the skin to one of the default skins that shiped with DNN.

Regards
Matthias
DNN MVP
www.aarsys.de
Metro7 Skin
ShoutCastStats Module for DNN
 
New Post
5/31/2012 11:45 AM
 
Ryan Ramsey


Joined: 5/25/2012
Posts: 20
With regard to #3, is this because some upgrades have new web.configs or does it get changed from the install script?
 
New Post
6/1/2012 6:53 AM
 
Matthias Schlomann


Joined: 8/10/2003
Posts: 3594

Install packages are for new installs and they included the web.config file, as well the source package.  Only the upgrade package is minimized and did not habe a web.config file in the package.  Changes on the web.config will made on code side for the upgrade package. 

But on lage different of the version No. it could be that you miss something on the upgrade packages, so I like to use the install package, and must be sure about the web.config file.

 

Regards
Matthias
DNN MVP
www.aarsys.de
Metro7 Skin
ShoutCastStats Module for DNN
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...GoDaddy & Upgrading DNN 5->6GoDaddy & Upgrading DNN 5->6


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