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 ...Error with upgrade 04.09.04 to 05.01.00Error with upgrade 04.09.04 to 05.01.00
Previous
 
Next
New Post
6/30/2009 8:25 AM
 

Thank you for the information as it is good to know that the site functionality will not be impacted by the error.

 
New Post
7/1/2009 7:59 AM
 

When you upgrade a 04.09.04 install version with the upgrade script from 05.01.00, the script tries to (an succeeds) in adding a new bigint field (autonumber, not null) called "LogEventID". The script fails however in making this field the primary field.

You can manually remove the primary key from the field LogGUID (but leave the field in the table) and make the LogEventID a primary key. As already stated this error will have no impact on the application, however when it is not the primary key it will slow down performance when doing lookup's in the table with this field because it is not indexed.

 
New Post
7/6/2009 5:51 PM
 

Sebastian Leupold wrote
 

This is a known issue, which will be fixed in next upgrade and shall not affect function of your web site.

 

I had gotten the same error on a 4.6.2 upgrade to 5.01.00, with the same sql logfile contents. I also got an "5.01.00 Application Upgrades: Error" message as well when the upgrade was running. There seems to be no other problems with my sites - things are working well. Is there a way I can find out what the specific error was that it found, or is the message related to the sqldataprovider error? Thanks!

 
New Post
7/7/2009 6:04 PM
 

Piet wrote

You can manually remove the primary key from the field LogGUID (but leave the field in the table) and make the LogEventID a primary key. As already stated this error will have no impact on the application, however when it is not the primary key it will slow down performance when doing lookup's in the table with this field because it is not indexed.

 

Can anyone comment on what performance hits you might get because of this? Or rather, what performance gains one can expect with regards to the new LogEventID over the old LogGUID? This question isnt really installation related but I'm picking up on this thread as it discusses this (and I got the same problem).

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error with upgrade 04.09.04 to 05.01.00Error with upgrade 04.09.04 to 05.01.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