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 Upgrading Community versions 5.2.2 to 5.2.3...Error Upgrading Community versions 5.2.2 to 5.2.3...
Previous
 
Next
New Post
2/22/2010 1:45 PM
 

 Any suggestions?  We are on a co-located machine, so I can make any changes necessary.  

Thank You,

John

Upgrading DotNetNuke

Current Assembly Version: 05.02.03

Current Database Version: 05.02.02



Upgrade Status Report

00:00:00.015 - Upgrading to Version: 05.02.03
00:00:00.390 -   Executing Script: 05.02.03.SqlDataProvider Error! (see 05.02.03.log for more information)

 


Server Error in '/new' Application.

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

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.

 
New Post
2/23/2010 9:51 AM
 

 So, the website itself still works for them most part.  However it seems a lot of my admin features are messed up.  If I just hit the Admin or Host link, I get a blank page.  A few of the Custom Modules that I made no longer show the "edit" links.  Has anybody experienced this?  I can't delete the DB since I have thousands of users and a lot of data.

John

p.s. On second review, the site is no longer working.  I am getting an under construction message.

 
New Post
2/25/2010 9:40 PM
 

I had this same error and could not get past it. I determined the error was due to a portal alias that was acceptable in 5.02.02 but was invalid in 5.02.03. The portal alias was www.mywebsite.com\child. It seems aliases of this format are no longer valid. I was unable to get the portal back on line with various other names. I tested the database and it was not affected, so I restored the DNN folder and all subfolders from the most recent backup, reassigned the original portal name and the site worked again.

I see this as a bug in this version.

 

 
New Post
2/26/2010 3:00 PM
 
Thank you for your reply. I too am using a sub-folder for this installation. Perhaps I will try to change that over the weekend. John
 
New Post
2/26/2010 5:54 PM
 

I have tried installing the 5.2.3 upgrade on three of my websites and none of them work at all after copying the upgrade files to the live folder, it doesn't even run the upgrade installation routine.

All I get when I try and access the sites to run the upgrade is the error below.

If I restore the folder all is well again but back to the original 5.2.2  version.

 

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>

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Error Upgrading Community versions 5.2.2 to 5.2.3...Error Upgrading Community versions 5.2.2 to 5.2.3...


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