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...5.2.2 to 5.3.1 upgrade fails with: Violation of UNIQUE KEY constraint 5.2.2 to 5.3.1 upgrade fails with: Violation of UNIQUE KEY constraint 'IX_Version'
Previous
 
Next
New Post
3/29/2010 9:01 PM
 
check out log files inside /providers/dataproviders/sqldataprovider folder.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/8/2010 9:39 AM
 
Hay there.. we have been tracking this problem too, and unlike most DNN issues that we can solve this one really has us tricked.

We noted your reply, and as I am sure you know, the error log shows the error associated with this failure. Very much the same error information as is displayed in the IIS .net errror message.

So the questions here (and from what we can find everywhere about this issue are)

1. What is going on with the actual cause of the failure. Some people have it at very different update script version numbers (ours is 5.0.0)
2. If the site funks out with this upgrade at this point, but then appears to silently run the other upgrade items and from that points behaves normally, is it safe to continue? (an opinion is fine)
3. Any real suggestions to tackle this for an error free upgrade would be appreciated.

P.S. Checking the logs is not a suggestion... they say there was an error!
 
New Post
6/8/2010 11:17 AM
 
Well the site doesn't see heavy usage, but I've not encountered other issues and certainly did not take further action to resolve it - so am operating under the belief/hope that all is fine.
 
New Post
6/8/2010 12:37 PM
 
Ours funked out and we have rolled back to 4.9.5. This has really got us stumped.
 
New Post
7/6/2010 3:32 AM
 
Hey guys,

I came across this article while troubleshooting the same error going from 5.2.3 to 5.4.4.    For me, my issue was resolved by first upgrading to 5.4.1 - see Will Stroll's article on upgrade paths. http://www.willstrohl.com/Blog/EntryId/102/Suggested-DotNetNuke-Site-Upgrade-Path-s

The upgrade ran fine, except I did get the following error.  However, the installation/portals seemed to work fine

Executing Script: 05.04.00.SqlDataProvider Error! (see 05.04.00.log for more information)


To resolve this new issue, I ran the following script from Timo (http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/365005/scope/posts/Default.aspx) which found 2 "ghost" portals - ones I created then deleted later.  I then ran Sebastian's script to remove those rows.

After all that. I ran the 5.4.4 upgrade, which installed fine without any errors.    Unfortunately, it took me a few hours to dig around and find these solutions.  Hopefully this might help some save a few hours, if it works for them.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...5.2.2 to 5.3.1 upgrade fails with: Violation of UNIQUE KEY constraint 5.2.2 to 5.3.1 upgrade fails with: Violation of UNIQUE KEY constraint 'IX_Version'


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