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 ...Upgrade to 4.5.1 ErrorUpgrade to 4.5.1 Error
Previous
 
Next
New Post
5/15/2007 8:50 AM
 
Hi, I'm having major problems upgrading to 4.5.1. I had a working DNN installation, but the upgrade failed. As this was a new site, there wasn't much content, so I thought it would be easier to start from scratch (I had installed a custom skin and XMod so thought there could be a conflict there somewhere).

So, I deleted the entire DNN installation and the SQL2005 db and started a fresh installation of 4.5.0 (CrystalTech automated). This was successful. Before I did anything else, I went through the procedure to upgrade to 4.5.1. Despite following the steps in Mitchel Sellers upgrade guide, I received the following error:

00:00:00.031 - Installing Version: 4.4.0
00:00:00.046 - Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.343 - Executing Script: DotNetNuke.Schema.SqlDataProvider Error! (see DotNetNuke.Schema.log for more information)
00:00:26.047 - Executing Script: DotNetNuke.Data.SqlDataProvider Error! (see DotNetNuke.Data.log for more information)
00:00:26.875 - Installing MemberRole Provider:
00:00:26.875 - Executing Script: InstallCommon.sql
00:00:27.953 - Executing Script: InstallMembership.sql
00:00:28.719 - Executing Script: InstallProfile.sql
00:00:29.031 - Executing Script: InstallRoles.sql
00:00:29.594 - Upgrading to Version: 4.5.1
00:00:29.625 - Executing Script: 04.04.01.SqlDataProvider Success
00:00:29.859 - Executing Script: 04.05.00.SqlDataProvider Success
00:00:31.828 - Executing Script: 04.05.01.SqlDataProvider Success
00:00:32.000 - Performing General Upgrades
00:00:32.953 - Loading Host Settings:
00:00:33.375 - Configuring SuperUser:
00:00:33.672 - Installing Modules:
00:00:33.672 - Executing Additional Scripts:
00:00:33.687 - Creating Portal: My Website
00:00:33.828 - Error: Error creating Profile Definitions
00:00:33.828 - Portal failed to install:Error!
00:00:33.828 - Installing Optional Resources:

Installation Complete

Viewing the Schema log shows the following errors:

System.Data.SqlClient.SqlException: There is already an object named 'PK_EventLogMaster' in the database.
System.Data.SqlClient.SqlException: There is already an object named 'PK_EventLogTypes' in the database.
System.Data.SqlClient.SqlException: There are no primary or candidate keys in the referenced table 'dbo.EventLogTypes' that match the referencing column list in the foreign key 'FK_EventLog_EventLogTypes'.
System.Data.SqlClient.SqlException: There are no primary or candidate keys in the referenced table 'dbo.EventLogTypes' that match the referencing column list in the foreign key 'FK_EventLogConfig_EventLogTypes'.

and the Data log:

System.Data.SqlClient.SqlException: 'FK_EventLogConfig_EventLogTypes' is not a constraint.

This is the error in the browser:
Server Error in '/' Application.
Runtime Error

What have I done wrong? More importantly, how do I correct it? Whilst I could delete everything and start again, I'm going to be confronted with the same problem! All help much appreciated.
 
New Post
5/15/2007 4:05 PM
 

For some reason the upgrade is trying to execute the 4.4.0 scripts, then it is installing the 4.5.1 scripts.  This is giving you the errors because it is trying to create tables that are already created.

In your web.config do you have an installation date appSetting by chance?


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
5/15/2007 4:52 PM
 
mitchel.sellers@gmail.com wrote

In your web.config do you have an installation date appSetting by chance?


Hi there, I meant to say, your [b]excellent[/b] guide :) .

I did actually delete everything and start again. CrystalTech's install is now at 4.5.0, so I thought I'd leave the upgrade for now. But to answer your question, I did have an installation date setting, and I copied that over from the saved web.config.old: into the new web.config.

Is that good or bad that there is one?

(I come in peace from the land of ColdFusion, so am on a bit of a learning curve with ASP.NET :) )
 
New Post
5/16/2007 12:49 AM
 

MetaSolutions wrote
 mitchel.sellers@gmail.com wrote

In your web.config do you have an installation date appSetting by chance?


Hi there, I meant to say, your [b]excellent[/b] guide :) .

I did actually delete everything and start again. CrystalTech's install is now at 4.5.0, so I thought I'd leave the upgrade for now. But to answer your question, I did have an installation date setting, and I copied that over from the saved web.config.old: into the new web.config.

Is that good or bad that there is one?

(I come in peace from the land of ColdFusion, so am on a bit of a learning curve with ASP.NET :) )

Thanks for the kind words.

The installation date item is a good thing to have in if you are doing an upgrade, It prevents machine keys from being changed by the install, and helps identify an upgrade.  I am still very curious as to why the 4.4.0 scripts tried to execute on upgrade, when I did my 4.5.0 -> 4.5.1 upgrades ONLY the 4.5.1 data scripts ran, and that is all that should be run for you....


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
5/16/2007 1:10 AM
 

If it runs the 4.4.0 script again then it is probably because that is what version it thinks the DB is at (Versions table).

The output of that upgrade looks like new install to me.  Maybe the {objectQualifier} or {databaseOwner} were different so it tried to install a fresh copy (still should have worked though).


DotNetNuke Modules from Snapsis.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade to 4.5.1 ErrorUpgrade to 4.5.1 Error


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