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 10:55 AM
 

Hi Sebastian,

Good, question.  The app pool is running .NET CLR Version v4.0.30319, with integrated pipeline mode.

 
New Post
2/10/2015 11:29 AM
 
177 appears earlier in your log. Another possible interpretation of 177 is for it to be the modulecontrol that is being added. Adding modules repeatedly to page 177 could be correct, but feels odd to me.

You may need to try the upgrade with a debugger attached to get enough information to diagnose it.

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

Below is the code of the method that's failing.  It makes the assumption that "NotificationsController.Instance.GetNotificationType(name);"  actually returns an object.  This is probably not a good assumption. 

At least in my database, the following query results in 0 records:  "select * From dnn_CoreMessaging_NotificationTypes where name in ('FriendRequest', 'FollowerRequest', 'FollowBackRequest', 'TranslationSubmitted')"

So, my question at this point is, should I just add the missing records?


private static void ConvertCoreNotificationTypeActionsFor700()
{
var notificationTypeNames = new[] { "FriendRequest", "FollowerRequest", "FollowBackRequest", "TranslationSubmitted" };

foreach (var name in notificationTypeNames)
{
var nt = NotificationsController.Instance.GetNotificationType(name);

var actions = NotificationsController.Instance.GetNotificationTypeActions(nt.NotificationTypeId).ToList();

if (actions.Any())
{

foreach (var action in actions)
{
action.APICall = action.APICall.Replace(".ashx", "");
NotificationsController.Instance.DeleteNotificationTypeAction(action.NotificationTypeActionId);
}

NotificationsController.Instance.SetNotificationTypeActions(actions, nt.NotificationTypeId);
}
}
}

 
New Post
2/10/2015 2:43 PM
 
I ran the following statement:
insert into dnn_CoreMessaging_NotificationTypes (name, [Description], TTL, DesktopModuleID, CreatedByUserID, CreatedOnDate, LastModifiedByUserID, LastModifiedOnDate)
values
( 'FriendRequest','Friend Request',NULL,NULL,-1,'2012-08-04 07:26:40.270', -1, '2012-08-04 07:26:40.270'),
( 'FollowerRequest', 'Follower Request', NULL, NULL, -1, '2012-08-04 07:26:40.463', -1, '2012-08-04 07:26:40.463'),
( 'FollowBackRequest', 'Follow Back Request', NULL, NULL, -1, '2012-08-04 07:26:40.527', -1, '2012-08-04 07:26:40.527'),
( 'TranslationSubmitted', 'Translation Submitted', NULL, NULL, -1, '2012-08-04 07:26:40.657', -1, '2012-08-04 07:26:40.657')

This allowed the upgrade to complete. I did 6.2.5 ->6.2.9->7.4.0 with SUCCESS!
I would call this a bug in the upgrader, it didn't account for the possibility of a NULL return (granted the underlying db was missing things, but that shouldn't kill the upgrade, I have no idea why those entries were missing, it's not a feature that I use)
 
New Post
2/10/2015 2:43 PM
 
-- UGH -- AGAIN -- the forum module isn't giving feedback when I click submit!
 
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