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 6.2.5 to 7.4.0Error Upgrading from 6.2.5 to 7.4.0
Previous
 
Next
New Post
2/10/2015 9:24 AM
 

I'm getting the following error when doing the upgrade:

4:10 Minutes   |   29% ERROR occured - Error: Object reference not set to an instance of an object. at DotNetNuke.Services.Upgrade.Upgrade.ConvertCoreNotificationTypeActionsFor700() at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion700() at DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(String providerPath, Version version, Boolean writeFeedback)

Any thoughts on what's going on and how to get past this?

I rolled it back and tried again, just to see if it was something transient, it failed inthe same place both times.

There are no errors logged to the dnn_eventlog table.

 
New Post
2/10/2015 9:33 AM
 
I'm sure it's not practical for the developers to test every combination of upgrade paths. I would make a guess that the problem is biting you as it goes to 7.00 (based on the name in the message).

I would try a separate upgrade to the last version before 7.00, and then another one on to 7.4.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
2/10/2015 10:20 AM
 

Thanks for the quick suggestion, I agree on the expectation.

I tried your suggestion (as it seemed pretty reasonable to me) and first upgraded to the last 6.x version first (06.02.09).  This went fine.

I then tried 07.04.00 again and it failed with the same error.  :-(

It would not surprise me that there is some knot or scar in my DNN configuration that is causing this issue, as my installation started w/DNN3.x.

Any idea where the log file is so that I can see what it was working on at the time of failure?  Perhaps that might provide a clue as to where things went south.  With that, hopefully, I can unwind / correct whatever is making the upgrader unhappy.

Other suggestions / advise are also welcome.

 

 
New Post
2/10/2015 10:28 AM
 
I found the log.

Here is the failure in context:

02/10/2015 15:10:20 [INFO] DotNetNuke.Services.Upgrade.Internals.Steps.BaseInstallationStep Upgrading Application to 7.0.0
02/10/2015 15:10:20 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start Application Upgrades: 7.0.0
02/10/2015 15:10:20 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddModuleDefinition:AdvancedSettings
02/10/2015 15:10:29 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddModuleControl:177
02/10/2015 15:10:29 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddAdminPages:Advanced Settings
02/10/2015 15:10:29 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddAdminPage:Advanced Settings
02/10/2015 15:10:30 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddPagePermission:View
02/10/2015 15:10:30 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddPagePermission:Edit
02/10/2015 15:10:30 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddPage:Advanced Settings
02/10/2015 15:10:32 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddModuleToPage:177
02/10/2015 15:10:34 [INFO] DotNetNuke.Services.Upgrade.Upgrade End AddModuleToPage:177
.
.
.

02/10/2015 15:11:52 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddPagePermission:Edit
02/10/2015 15:11:52 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddPage:Advanced Settings
02/10/2015 15:11:53 [INFO] DotNetNuke.Services.Upgrade.Upgrade Start AddModuleToPage:177
02/10/2015 15:11:55 [INFO] DotNetNuke.Services.Upgrade.Upgrade End AddModuleToPage:177
02/10/2015 15:11:55 [ERROR] DotNetNuke.Services.Upgrade.Upgrade Error: Object reference not set to an instance of an object. at DotNetNuke.Services.Upgrade.Upgrade.ConvertCoreNotificationTypeActionsFor700()
at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion700()
at DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(String providerPath, Version version, Boolean writeFeedback)


I assume that means tab 177, in my system tab 177 is the Admin/LogViewer for one of my portals.
From the looks of this, it's working it's way through all the portals and fixing up the log viewer.
 
New Post
2/10/2015 10:47 AM
 
did you made sure, your application pool is running ASP.Net 4 in integrated mode, before triggering the upgrade to DNN 7?

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...Error Upgrading from 6.2.5 to 7.4.0Error Upgrading from 6.2.5 to 7.4.0


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