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...Error upgrading from 5.2.2 to 5.4.1Error upgrading from 5.2.2 to 5.4.1
Previous
 
Next
New Post
5/3/2010 4:07 PM
 

Alex,

I'm actually staging upgrade from 4.9.5 to 5.2.2 and then to 5.4.1.  I did find that after upgrade, the Upgrade.vb file is still the version for 4.9.5.  Also, only in the Source/New install file do these files and the new /library directory structure/content exist.  So ... I asked if the issue is simply that the new Upgrade.vb file can't be found but the old one is and certain path/content updates simply can't happen?  Could it be that easy?

I've taken some very good thorough notes and here they are.  This editor still chops this all up badly.  The format will be readable until I post it and then it's all bolded and underlined -- no way to avoid this, sorry.

I hope this helps you out.  If I follow this, I end up with the errors at the very end of the post, at 5.2.2 and 5.4.1

Mike Durthaler

 

Module Definitions

Error Error: Module Definitions is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/Admin/ModuleDefinitions/ModuleDefinitions.ascx' does not exist. ---> System.Web.HttpException: The file '/Admin/ModuleDefinitions/ModuleDefinitions.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

  

Module Definition Validator

Error Error: Module Definition Validator is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/Admin/ModuleDefinitions/ModuleDefValidator.ascx' does not exist. ---> System.Web.HttpException: The file '/Admin/ModuleDefinitions/ModuleDefValidator.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

29 Apr 2010, REV 2 May 2010:

If you get the error that the database is in use when doing a restore:

Detach the db, selecting the checkbox to drop active connections

Stop the doa.ovionx.com website in IIS

Restart IIS

Close any queries using the db

Close any Visual Studio instances which may be referencing it

Look for any programs that might be referencing it

Stop the SQL Server Agent, this is sometimes trying to act on the databases.

Restart the SQL Server Instance at the root node

See if other users are logged on and ask if they're in the db.

Reattach the db from the appropriate type of mdf file, DOA.mdf in this case.

Retry the restore

If all else fails, bounce the server.

Before starting/restarting an upgrade sequence:

Back up doa.ovionx.com in a new unit of time
 

Back up the database in a new unit of time

 

If restoring to 4.9.5 or 5.2.2 and re-starting an upgrade:

Restore the db to the file: C:\WebFtpShare\mdurthaler\DOA\29 Apr Backup DOA\DOA-Full_Pre_495_Up_Apr_2010_29.bak. If not including Catalook, as this was removed because 5.8.1 won't work with DNN 5.x and above (and 6.0.8 won't work on 4.9.5, making an upgrade impossible), restore from this file: C:\WebFtpShare\mdurthaler\DOA\29 Apr Backup DOA\DOA-Full_Pre_495_Up_Apr_CATRem_2010_29.bak.
Done

Restore the site from C:\WebFtpShare\mdurthaler\DOA\29 Apr Backup DOA\495_doa.ovionx.com.rar; if restoring to 5.2.2, same directory, other zip file.
Done Check this every time a restore is done. Also check to make sure the SQLDataproviders folder has these permissions propagated to it.
Checked
Set Log and Site files to unrestricted.

Security Settings for Website folder can blow -- make sure Network Service privileges are re-set. This may be being caused when the upgrade package is unzipped.

When restoring a database be sure to set the file capacity to unrestricted.

Remove any 5.x dll files if you have to restore back to 4.9.5. In particular are:
DotNetNuke.Modules.Html.dll. Done
DotNetNuke.Modules.Taxonomy.dll Done Added during 522 to 541
DotNetNuke.Modules.Messaging.dll Done Added during 522 to 541

There is a DotNetNuke.HtmlEditor.TelerikEditorProvider.dll in place after upgrading high enough along a 5.x path. Leave it in place because there's an assmbly mismatch error that shows up.

Due to the assembly mismatch, it may be necessary to remove the Telerik.Web.UI.dll file. This is the assembly where the upgrade complains about a mismatch between Telerik dll files. It was removed on one upgrade path and another dll took its place. As the mismatch showed up from 4.9.5 to 5.2.2 I'm guessing it's caused by the new dll file not being in place in the 522 upgrade zip. So I copied it over and we'll see what happens.

When restoring to 4.9.5, delete the contents of C:\WebShare\newdoa.ovionx.com\Website\Providers\DataProviders\SqlDataProvider folder. This is to remove any scripts from higher versions of DNN before another upgrade attempt is done.
Done

If the site was stopped to restore an earlier db or site version, restart it in IIS.
Done

When starting @ 495 with the db bak file of NEW_DOA-Full-CATRemoved.bak be sure to use the skins file referenced below WITH the script and role functions.

Prevent the url rewriters from acting during the upgrade process:

in the js folder we have a customized /plugins folder so that DNN can't overwrite it. These js files reference Catalook.

Skins - for upgrade from 5.2.2 to 5.4.1, remove the following from the skins file collectors.ascx in the Skins | DOA folder
C:\WebShare\doa.ovionx.com\Website\Portals\_default\Skins\DOA

<

script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.4/jquery.min.js"></script>

<%

If PortalSecurity.IsInRole("Administrators") Then %>

<

script type="text/javascript">jQuery.noConflict();</script>

<%

End If %>

Follow the upgrade sequence below.

 

Upgrade Sequence

Catalook tables/sprocs/views are scripted out.
NB: For this upgrade, since I found out that another person had no issue with Catalook, I will try leaving it in this time.

There already are content scripts for NEW_DOA which is the same as DOA
NB: Disregard for 2 May upgrade first attempt.

Settings table can't be copied probably due to credit card protections in place.

Uninstall Catalook and also uninstall Ad Rotator. OVX Ad Rotator has no db objects of its own, it only uses Catalook objects.
NB: Disregard for 2 May upgrade first attempt.

The uninstall drops all objects but a few. Drop the straggling Catalook tables, sprocs and the view
CAT_OrdersItemsLinks
CAT_Froogle -- view
CAT_SerialNumberOrderDetailsIDUpdate
CAT_SerialNumbersAssign

NB: Disregard for 2 May upgrade first attempt.
 

Make up a CatRem_ backup version of the db. Keep this in the WebFTPShare folder/DOA/ for backups.
NB: Disregard for 2 May upgrade first attempt. The backup does exist.

Manually do the 5.0.0 and 5.0.1 scripts. Delete these from future upgrade scripts
5.0.0 Done
5.0.1 Done

Update the dnn_Version table

Redo the CatRem_ backup above, append to the backup set
NB: Disregard for 2 May upgrade first attempt. This is the backup that exists in db.

Copy over the backup configs contents to Website/
Done

The copied web config files are backups of the 495, 522 and 541 web configs.

Make a DOA_495 copy of web.config Done
Delete web.config Done
Copy and paste the 495_2_522_release.config file. Done
Rename the copy to web.config Done

Remove keys for url rewriters in httphandlers and providers in the web config, use only the dnn url rewriter

Make sure the initial catalog is set from NEW_DOA to DOA.
Done

The HTML is already removed as mentioned above in the skins file section. Rename the collectors.ascx and collectors-copy appropriately. This way you keep a backup.
Not done as part of 4.9.5 to 5.2.2.

495 to 522
Ensure the above sequence is done Done
Unzip the 522 upgrade zip in my webftpshare folder/DNN Versions over the /Website folder Done
Open the C:\WebShare\doa.ovionx.com\Website\Providers\DataProviders\SqlDataProvider folder and remove the scripts for 5.0.0 and 5.0.1
Done
Run the Create script from Lisa Gillespie
Done -- had to edit [dbo].[dnn_].[object] to [dbo].[dnn_object]
There are 2 messages from SQL after this:
The module 'dnn_SaveCoreAuditTypes' depends on the missing object 'dbo.AddEventLogType'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'dnn_SaveCoreAuditTypes' depends on the missing object 'dbo.AddEventLogConfig'. The module will still be created; however, it cannot run successfully until the object exists.
There are 2 EXEC statements using the type without object qualifiers, which is why it failed.
Edited the copy and re-ran the script. Commands completed successfully. Done, but found out later object qualifiers are a serious issue. These files are no good and I'll have to start over.

Run the Alter script from Lisa Gillespie
Edited [dbo].[object] to [dbo].[dnn_object]
When I first opened the script, some of the dnn_vw objects were throwing the error of Invalid Object. I had to close and reopen SQL 2008 Mgmt Studio to fix this. The error disappeared, I have no idea why. The objects were also missing from intellisense.
NB: There are errors that show up, such as invalid objects for the HTMLTextLog table. These do exist in databases already upgraded to 5.x and don't for the moment exist. I highlighted and ran a query where there were errors, as this only ALTERS a stored procedure. It does run.
I'm trying the upgrade to see if this doesn't put the objects in place that I expect.

Verify all web.config edits are correct

Upgrade to 522. Do the rest of the upgrade later in the sequence
Reinstall iFinity -- copy over web config entries from 495 copy. Add these to the appropriate sections. make sure iFinity is in the appropriate sections and is the default friendly url provider. REPLACE the key in the <httphandlers> section; ADD the key to the provider section.
Run the SQL Query to reset dnn_tabs | Is Secure to False This is: dnn_Tabs_IsSecure-Set_False.sql
Check that admin and host links work. They will but not all tabs can be browsed to because of a bug supposedly repaired in higher upgrades
Ensure the rest of the site works

Backup the db, backup the site to this point.

522 to 541
Make a DOA_522 copy of the web.config
Delete web.config
Copy and paste the 522_2_541_release.config file -- make sure iFinity is in the appropriate sections and is the default friendly url provider. REPLACE the key in the <httphandlers> section; ADD the key to the provider section.
Rename the copy to web.config

Ensure the above sequence is done
Unzip the 541 upgrade zip in my webftpshare folder/DNN Versions over the /Website folder
Verify all web.config edits are correct

Upgrade to 541
Check that everything works

 

 

 

 

Do the upgrade path on the test site:

Reinstall the modules for Catalook

Backup the CAT folders in /Desktop Modules -- reinstall these file by file from a backup once Cat 6.0.8 is installed. We customized these files.

Script the content back in

Check that it all works Settings table can't be copied probably due to credit card protections in place.


Done
Write these down and otherwise confirm on the live site upgrade that we have these settings to hand.
NB: Disregard for 2 May upgrade first attempt.

Browse to the site once it is back in place so you know you're starting from a good working point. DoneRemove from the web.config | http modules references to the ovionx.httpmodules and ifinity, be sure to use the DNN friendly urls provider; also delete the entry from providers section.

This is already handled by using the saved release config files under BackupConfigs in my WebFTPShare folder. Just change the initial catalog in the connection strings.

 


 

 

 
New Post
5/4/2010 5:24 AM
 
I'd suggest upgrading directly to 5.4.1. But it looks like there are files either missing or the asp.net user doesn't have access to it. make sure, file system permissions are granted and all files are "unblocked", if using Win7 (and maybe Vista as well as Server 2008).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/4/2010 10:49 AM
 
Sebastian, the problem seems to be related to enabled languages in the sites right before 5.3, so there won't be a difference in upgrading directly. The error is in the 5.3 upgrade logic.

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
5/4/2010 10:53 AM
 

>Yes, there is supposed to be 1 Default.page.template file in that folder.

I rolled back the VM, copied a Default.page.template from the default folder and re-ran the upgrade. The error message in the log is gone but it still fails with the following:

00:00:04.984 -   Executing Application Upgrades: 05.03.00 Error!
00:00:06.609 -   Installing Package File HTML_Community_05.02.00_Install:  Error!
00:00:07.015 -   Installing Package File Messaging_01.01.00_Install:  Error!
00:00:07.078 -   Installing Package File Taxonomy_01.01.00_Install:  Error!

Is there a way to get more diagnostics about these as the event log isn't showing anything and "Error!" doesn't give one much to go on.

Also, you say this error is reported in DNN-12154 - is this for all the above errors or just the default page missing? I notice in this issue log it mentions something about default language. This DNN site was built a while back and I'm not a DNN expert (even less so when it was installed) but I'm sure I remember something about installing the right language pack so I did that.

Cheers,Rob.

 
New Post
5/4/2010 10:56 AM
 
Caroig wrote:

 I have a es-ES language pack loaded so my config matches pretty much what Alex is describing.


I'm in the UK so I most likely installed the UK language pack. I'm not a DNN expert so was pretty much following the script when I first installed DNN about a year ago.

Is there a workaround here?

Cheers, Rob.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Error upgrading from 5.2.2 to 5.4.1Error upgrading from 5.2.2 to 5.4.1


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