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...Upgrade gone really really wrong, please helpUpgrade gone really really wrong, please help
Previous
 
Next
New Post
1/16/2013 8:26 AM
 

Hi, I hope someone can help me, my sites have been down now for a week! Here's briefly what happened:

I have about 30 portals (aliases)

All were working fine however in order to install a paid-for customization to the Smith Cart installed on one of our portals, the Smith people said we had to upgrade from 06.0.2 to 06.02.

I downloaded 06.02.06

I downloaded all the files from the httpdocs folder onto my local drive

I asked my hosting people to make a backup of the database - which they did and sent to me

I then followed the steps for the upgrade from http://www.dotnetnuke.com/Resources/Wiki/Page/Upgrading-DotNetNuke.aspx 

The upgrade seeded to go okay but, when I took a look at the sites the skins were all messed up. Most of my sites were using Morpheus, one other was using the Max Skin. On the sites using Morpheus I could not login but on the one site using the Max skin I could actually log in though nothing was where it should have been. Once logged into this site, I tried to change the default skin (for edit and view) to Dark Knight but nothing happened. I could not get into the pages to change individual settings either.

I then downloaded 06.02.05 and tried to install this but then just got an Error when trying to get into any of the sites.

At this stage all I could think to do was to revert to my backup so I uploaded the contents of the httpdocs folder from my local machine and contacted my hosting people to ask them to restore the backup of the database.

A while later I received a message to say they had fixed the sites - but although they now looked okay, I was not able to log in using either host or a user login which I wrote to let them know.

Later I tried again and was surprised that  things had gone back a step and once again just got the Runtime error message

They then cleaned out the contents of the httpdocs folder and asked me to upload the files from my computer again

Following that, they restored the database from the copy they had sent to me on 6th Jan

Now I get a different error - Could not load file or assembly 'Telerik.Web.UI' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

My hosting people are now suggesting that the only thing to do is to do a complete new install of DNN.

Can someone please tell me if we do the new install will I lose all my portals? 

Or can someone please help with an alternative solution.

Please, please HELP, I am going so crazy over this disastrous situation 

Yours Hopefully Glynis

 
New Post
1/16/2013 11:54 AM
 
Glynis,

If you were to set up a new DNN site you would lose everything unless they managed to point the new site to the old database. That may work but I don't know what happens since the versions would be different.

Also, your skins may still be broken due to the newer version of DNN.

My recommendation is to set up a new site locally and test your skins. If they don't work, reach out to the makers of the skins to see if you can get a v7 compatible version, install them and test again.

As for your content, it's possible you could install a fresh copy of DNN and point to the old database but I don't know what would happen since the new site would be from an older version.

Mark
 
New Post
1/16/2013 12:30 PM
 
Thanks for your help Mark. I am a bit lost to the bit about pointing the new site to the old database.i will talk to my hosting people about it.

Meanwhile if anyone has any other ideas, please, please help
 
New Post
1/16/2013 1:30 PM
 
Normally you use a new database when you set up a new instance of DNN. However, you can install DNN using a temporary database and then go back and manually edit the database connection string to point to the old one. We see this done on occasion but it would require some testing to see if it works.

Mark
 
New Post
1/16/2013 1:45 PM
 
okay, thanks again for the help
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade gone really really wrong, please helpUpgrade gone really really wrong, please help


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