Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: V9 to latest upgrade failed

  1. 04-06-2010, 07:41 PM #1
    tommytl is offline Member
    Join Date
    Sep 2008
    Posts
    34

    Default V9 to latest upgrade failed

    I upgraded the db from 8.0.1.2 to 9.0.. that worked.

    Now I'm updating the db script from 9.0 to latest which is 9.0.1.2 and get this error:


    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (1 row(s) affected)

    (0 row(s) affected)
    Msg 2627, Level 14, State 1, Line 3
    Violation of UNIQUE KEY constraint 'UQ_GlobalConfig_Name'. Cannot insert duplicate key in object 'dbo.GlobalConfig'.


    What that is?? Anyone else seeing this?
  2. 04-07-2010, 12:51 AM #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    Just please ignore that error, I believe that was addressed already here in our build. The "Cannot insert duplicate key in object 'dbo.GlobalConfig'" error means, the [UQ_GlobalConfig_Name] CONSTRAINT is existing in the DB already, so you should be fine.