move WSUS2 to new server and update to WSUS3

Discussion in 'Update Services' started by Heinz, Jan 30, 2009.

  1. Heinz

    Heinz Guest

    Hello,

    I try to move a WSUS 2 to a new server and update the WSUS to Version 3

    What I did :

    Backup WSUS 2 on the "old " server using ntbackup (Content and Database)
    Install WSUS 2 on new Server
    Restored teh backup to new Server
    Result: the restore seems to work: the database starts and in
    "http\\server\wsusAdmin" I see the same data in the new server as in the
    "old" server.

    So far so good.... but when I try to update the WSUS 2 to 3 I get the
    following error:

    The CREATE UNIQUE INDEX statement terminated because a duplicate key was
    found for the object name
    'dbo.tbDeployment' and the index name
    'nc_RevisionID_TargetGroupID_ActionID'.
    The duplicate key value is (31181, cac067a1-9883-40c9-a358-319295b09b91, 4).
    The statement has been terminated.

    The Update fails (and corrupts the WSUS 2 installation although there is a
    "Rollback" running....)


    Now my question is: How could I avoid the "duplicate key" error ?

    thank you
    Heinz
     
    Heinz, Jan 30, 2009
    #1
    1. Advertisements

  2. Crossposting in German Newsgroup too. ;-(

    Winfried
     
    Winfried Sonntag [MVP], Jan 30, 2009
    #2
    1. Advertisements

  3. Heinz

    Heinz Guest

    well... just trying my luck in two languages.. hope that's OK ?

    bye
    Heinz
     
    Heinz, Jan 31, 2009
    #3
  4. You possibly caused the "duplicate key" error by something in your restoring
    of the backup to a new server. Alternatively it may be a defect in your
    source database that's only showing up now as a result of an indexing
    operation being performed by the upgrade. Consider this a successful "test"
    (because you managed to not impact/corrupt your production WSUS 2 server).

    Given the *possibility* that there's an issue with your WSUS 2.0 database,
    my recommended procedure for such a scenario would be to abandon the WSUS
    2.0 server in place. Install WSUS 3.0 on the new server, and configure,
    synchronize, and mark approvals as if this were the first time you'd ever
    installed a WSUS server in your environment.



    --
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin \(MVP\), Jan 31, 2009
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.