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 3:34 PM
 

I just tried to upgrade www.VashonSoftware.com from 5.02.02 to 5.03.01 and got the following error. I had just upgraded the XML module to the latest (beta) version as I know that was a known issue due to some namespace issues. Any ideas? I'll put debug info into the web.config and retry...

- John

Upgrading DotNetNuke

 

Current Assembly Version: 05.03.01

Current Database Version: 05.02.02



 

Upgrade Status Report

00:00:00.093 - Upgrading to Version: 05.03.01
00:00:00.125 -   Executing Script: 05.02.03.SqlDataProvider Success
 

 

 


Server Error in '/' Application.

Violation of UNIQUE KEY constraint 'IX_Version'. Cannot insert duplicate key in object 'dbo.Version'.
The statement has been terminated.

 


Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Violation of UNIQUE KEY constraint 'IX_Version'. Cannot insert duplicate key in object 'dbo.Version'.
The statement has been terminated.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:


   
       
   



Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[SqlException (0x80131904): Violation of UNIQUE KEY constraint 'IX_Version'. Cannot insert duplicate key in object 'dbo.Version'.
The statement has been terminated.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +1950890
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4846875
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2392
   System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +204
   System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +954
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162
   System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) +175
   System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +137
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) +168
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +188
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) +247
   DotNetNuke.Data.SqlDataProvider.UpdateDatabaseVersion(Int32 Major, Int32 Minor, Int32 Build, String Name) +218
   DotNetNuke.Common.Globals.UpdateDataBaseVersion(Version version) +69
   DotNetNuke.Services.Upgrade.Upgrade.UpgradeVersion(String strScriptFile, Boolean writeFeedback) +122
   DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, Version dataBaseVersion) +338
   DotNetNuke.Services.Install.Install.UpgradeApplication() +931
   DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +272
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

 
New Post
3/29/2010 4:08 PM
 

Just refreshing the site caused it to load fine and under host it shows it is running at 5.3.1(7). Do I trust this though?! (I do have a backup if others recommend a reinstall...)

 
New Post
3/29/2010 4:49 PM
 
which upgrade skript has this error occured? if all scripts has been passed, the site should run fine

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/29/2010 5:24 PM
 

I had just unzipped the DNN upgrade script for 5.3.1 into wwwroot, then accessed the home page and got the error I reported above. Thereafter I waited a few minutes, then loaded the home page (which took some time to compile or whatever) but it seems to run fine.

I am curious what the source of the error is of course. Well, on to a few of my other sites to try this also then...

Thanks (as always) Sebastian.

 
New Post
3/29/2010 8:10 PM
 

 

Well my next site, skcoad.org had to be upgraded from 5.2.3 to 5.3.1, and that also got an error:

Upgrading DotNetNuke

Current Assembly Version: 05.03.01

Current Database Version: 05.02.03



 

Upgrade Status Report

00:00:00.343 - Upgrading to Version: 05.03.01
00:00:00.453 -   Executing Script: 05.03.00.SqlDataProvider Error! (see 05.03.00.log for more information)
 

 

 

 


Server Error in '/' Application.

Runtime Error

 

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

A subsequent reload of the page worked fine  - and shows the version as 5.3.1. While puzzling, I guess this may be par for the course with this install!

Does anyone know where to find the mentioned: "05.03.00.log"? It's not at wwwroot or the top level directory. Could this be made into a link?!

 
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