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 ...Compiler error after restoring site from a failed upgradeCompiler error after restoring site from a failed upgrade
Previous
 
Next
New Post
2/24/2011 1:51 AM
 
I tried to upgrade our DNN 4.9.5 site, www.oaklandsymphonychorus.org, to DNN 5.6.1 this afternoon, and install succeeded but I got the error that indicates the absence of ASP.NET 3.5 SP1.  My host techs confirmed that it wasn't on my shared server. 

I asked them to restore my site from yesterday's backup, and move the site to a new server which has the ASP.NET service pack applied; both done. 

I just tried to load my site and now I have a NEW error that I don't understand:

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30560: 'DataProvider' is ambiguous in the namespace 'DotNetNuke.Modules.HTML'.

Source Error:

Line 40: Line 41: ' singleton reference to the instantiated object Line 42: Private Shared objProvider As DataProvider = Nothing Line 43: Line 44: ' constructor

Source File: C:\inetpub\wwwroot\oaklandsymphonychorus.org\wwwroot\App_Code\HTML\DataProvider.vb    Line: 42




It's almost 11 PM my time and I'm beat.  Can someone look at this and tell me what I need to do next?  I can't restore the site myself because I can't get to the SQL database server, the support techs have to do that; but I have a full site backup from yesterday and if there's a file I need to upload, I can do that tomorrow.

hedera
**********
Nature bats last.
 
New Post
2/24/2011 6:47 PM
 
I have more information on this situation.  My ISP tech support told me they'd restored my site, again, so I tried to bring it up and got the compiler error again.  I found a reference to the compiler error that suggests that I should delete one or both of these DLLs. if present:

DotNetNuke.Modules.Html.dll 

DotNetNuke.Modules.Html.SqlDataProvider.dll.

I found the first one and renamed it; that got rid of the compiler error and brought me to the install wizard, which now shows this:

Upgrading DotNetNuke

Current Assembly Version: 04.09.05

Current Database Version: 05.06.01



Upgrade Status Report

00:00:00.015 - Upgrading to Version: 4.9.5
00:00:00.031 - Performing General Upgrades

Upgrade Complete



Click Here To Access Your Portal

When I "click here to access your portal" it loops back around to the Wizard page.  I read this to mean that when they restored the SQL database, they failed to tell it to overwrite the existing database.  Does that sound right to anyone else??  Am I correct to assume that a 5.6.1 database can't really talk to the 4.9.5 code?  Is there a solution I should suggest to them other than restoring the db again, making sure to tell it to "overwrite"??

Am I also right to assume that when I get the 4.9.5 database back, I will need to rename that DLL back to make it active??

hedera
**********
Nature bats last.
 
New Post
2/24/2011 8:47 PM
 
As you suspected, your hosting provider restored the file system to DNN 4.9.5 pre-upgrade attempt but either failed to restore the database or did not do so properly. The assembly version and the database version MUST match except in the case of triggering an upgrade when the assembly version will momentarily be that of the upgrade version and the database that of the current version - never the other way around as in your case.

Regarding the HTML module, if your hosting provider restores only the database to the 4.9.5 version, you should not have to again delete the DotNetNuke.Modules.Html.dll or DotNetNuke.Modules.Html.SqlDataProvider.dll. They were not part of 4.9.5 and did not come into being until DNN 5.1.x or so. HOWEVER, their presence in the /bin folder following the file system restore gives me concern that when doing the file system restore your hosting provider did not first clear all folders and files from the root install folder then and only then restore from the filesystem backup.  There were major changes in folder structure between 4.9.5 and 5.x so if they simply copied the filesystem backup over the files system following the attempted upgrade there may be other folders/files left over from the 5.6.1 upgrade attempt.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
2/24/2011 9:34 PM
 
Wow.  Thanks so much for confirming my suspicions, and for the warning about the file structure changes.  I've learned the hard way to clear the file folder before restoring files.  The support guys FINALLY got the site back up and it seems to be working.  However, given that I had to tell them to overwrite the database when restoring it, I wouldn't bet a plugged nickel that they didn't overwrite the files without clearing the directory.  Is there an easy way to check this?? 

I feel really stupid about this as it all started when I began the upgrade without doublechecking the system requirements - I had successfully upgraded on my local test system, so what's the prob?  My ISP, however, had us on a deliberately backleveled .NET server, and it didn't occur to me to ask the question first.  We've now been moved to a server where the .NET SP1 has been applied.

If they did NOT clear the file system before restoring, would that cause issues when I try to do the upgrade again??  My 4.9.5 site appears to be working normally, and I hoped to do the upgrade tomorrow afternoon (and give myself the weekend to clean it up, as I'm moving to a much more complicated commercial skin).

hedera
**********
Nature bats last.
 
New Post
2/24/2011 9:48 PM
 
I just tried to access my site's Admin and Host menus, logged in as host - and all I get is a 404, file not found.  This seems to me to indicate that they didn't clear the file system before restoring the files.  Does that sound right to you??  I'm going to go back to them and ask the question, assuming the answer is yes...

hedera
**********
Nature bats last.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Compiler error after restoring site from a failed upgradeCompiler error after restoring site from a failed upgrade


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