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 05.04.04 to 05.06.00Error 05.04.04 to 05.06.00
Previous
 
Next
New Post
11/24/2010 2:32 PM
 
William Severance wrote:
Does your site currently use or at one time had installed the iFinity URL Master extension but later un-installed it?

Not that I know of. We took over admin of this site near the begining of the year. To my knowledge the site is several years old, so it could have had that module before my time. I still consider my DNN abilities as entry level, excuse me if this is a dumb question, is there a log/report I can check to see if this module was previously installed?

 
New Post
11/24/2010 2:43 PM
 
Ken Grierson wrote:
Adam;
Do you have 3rd Party modules installed on your site? I'm asking because Events Module will throw a very similar type of error during upgrade.
I logged it here:
http://dnnevents.codeplex.com/workitem/19061
If you have other 3rd party modules loaded please check that each of them still load and perform correctly

 This may be the issue. I am attempting to work this solution now.

Thank you.

 
New Post
11/24/2010 3:32 PM
 
The easiest way to check for this issue is to open the installation's database using a tool such as MS SQL Server Management Studio. In the tables view, look at the Modules table to see if it has an insert trigger defined and enabled. I can't recall the name of the trigger but recall that its definition referenced iFinity and makes a reference to the 'ModuleTitle' column of the Modules table which was removed in DotNetNuke 5.05.00. As far as I know unless some other third party extension created a trigger on the Modules table, there should be no trigger defined.

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
11/24/2010 8:34 PM
 
William Severance wrote:
The easiest way to check for this issue is to open the installation's database using a tool such as MS SQL Server Management Studio. In the tables view, look at the Modules table to see if it has an insert trigger defined and enabled. I can't recall the name of the trigger but recall that its definition referenced iFinity and makes a reference to the 'ModuleTitle' column of the Modules table which was removed in DotNetNuke 5.05.00. As far as I know unless some other third party extension created a trigger on the Modules table, there should be no trigger defined.

 Success!!

This was the problem. There were 2 tables with triggers defined on them from a module that was previously removed. I have to admit that it took me a while to consider that there might be 2 tables with triggers and go looking. :)

Module (ifty_OnNewModule)
ModuleControls (ifty_OnNewModuleControl)

After deleting both, everything appears to be functioning properly. I did roll back to 05.04.04, then delete the triggers, and finally re-apply the upgrade.

Thank you everyone for your comments and support!!

Adam

 
New Post
11/24/2010 10:01 PM
 
Good going! During the course of troubleshooting a failure to add any module to a client's site which they had unpdated to DNN 5.05.00, I had discovered the insert trigger created by the iFinity URL Master extension on the Modules table and found that even though the extension had been un-installed some time prior to my involvement with the site, the trigger was still active. In that case I  did not find a trigger enabled on the ModuleControls table. Apparently it had successfully un-installed.

Your decision to roll back to 05.04.04 then delete the triggers before re-attempting the upgrade was the correct action to take.

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
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Error 05.04.04 to 05.06.00Error 05.04.04 to 05.06.00


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