locked
Getting errors after backup and restore RRS feed

  • Question

  •  

    I backed up and restored a site collection into a new site collection using STSADM operation. Since then I have been getting the following errors. Any suggestions?

     

    Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: User Profiles
    Event ID: 5553
    Date:  4/28/2008
    Time:  4:00:03 PM
    User:  N/A
    Computer: *****

    Description:
    failure trying to synch site 2a918abf-12ce-4819-811d-803f0f87d313 for ContentDB 1c85deaa-d2a2-4f01-90ec-fca3f691dab3 WebApp ada1f800-c105-4970-bca0-c43d699daadc.  Exception message was Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
    The statement has been terminated..

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Monday, April 28, 2008 9:58 PM

Answers

  • Here is excerpt from "Monthly Moss", 9/26/7, which I can't access today for some reason.  Hope it helps you out.

     

    Probable cause is due to backing up our current content DB and restoring it to a different application on the same farm.

    What happened is the GUID for the content DB is the same causing a conflict during the sync process.

    Following steps are a workaround the issue:

    Get a list of the content databases GUIDs that are being affected.
    Stsadm -o sync -listolddatabases 0

    Now run a Select Query on the Config Databases “dbo.Objectstable and look for the GUID that matches the listed GUID.

    Database: Sharepoint_Config, Table dbo.Objects

    SELECT Id, ClassId, ParentId, Name, Status, Version, Properties
    FROM Objects
    WHERE (Id = '5bafe2af-48a7-4043-a36d-29160f3b88e2')


    In our case this is just a development/testing site that will not be around for long so we just excluded it from the sync process.
    Stsadm –o sync –ExcludeWebApps URL of webapplist

    But for those that are not as fortunate as us you will want to do a full detach and rebuild of the content database. This will enable the Content Database to get new GUID and be included in the sync process.

    Detach Content Database. This will not delete your database only break the association.
    stsadm -o preparetomove -contentdb -ContentDB SQLserverBig SmileB_NAME -site http://website
    stsadm -o deletecontentdb -url http://website -databaseserver SQLserver -databasename DB_NAME

    Reattach Content Database.
    stsadm -o addcontentdb -url http://website -databasename DB_NAME -databaseserver SQLserver

     

    Tuesday, April 29, 2008 1:30 PM

All replies

  • Here is excerpt from "Monthly Moss", 9/26/7, which I can't access today for some reason.  Hope it helps you out.

     

    Probable cause is due to backing up our current content DB and restoring it to a different application on the same farm.

    What happened is the GUID for the content DB is the same causing a conflict during the sync process.

    Following steps are a workaround the issue:

    Get a list of the content databases GUIDs that are being affected.
    Stsadm -o sync -listolddatabases 0

    Now run a Select Query on the Config Databases “dbo.Objectstable and look for the GUID that matches the listed GUID.

    Database: Sharepoint_Config, Table dbo.Objects

    SELECT Id, ClassId, ParentId, Name, Status, Version, Properties
    FROM Objects
    WHERE (Id = '5bafe2af-48a7-4043-a36d-29160f3b88e2')


    In our case this is just a development/testing site that will not be around for long so we just excluded it from the sync process.
    Stsadm –o sync –ExcludeWebApps URL of webapplist

    But for those that are not as fortunate as us you will want to do a full detach and rebuild of the content database. This will enable the Content Database to get new GUID and be included in the sync process.

    Detach Content Database. This will not delete your database only break the association.
    stsadm -o preparetomove -contentdb -ContentDB SQLserverBig SmileB_NAME -site http://website
    stsadm -o deletecontentdb -url http://website -databaseserver SQLserver -databasename DB_NAME

    Reattach Content Database.
    stsadm -o addcontentdb -url http://website -databasename DB_NAME -databaseserver SQLserver

     

    Tuesday, April 29, 2008 1:30 PM
  • Thanks Sukie! That worked.

     

    Tuesday, April 29, 2008 10:31 PM
  •  

    Hi Sukie

    i added user profile images into MOSS, by creating new web application on the same application server, paste images there, then i mapped the images to the users from audiences at the SSP site.

    the Log file generated this error:

    Date: 5/26/2008

    Source: Microsof Office SharePoint server

    Time: 8:00:00 AM

    Category: User Profiles

    User: N/A

    Event ID: 5553

    Computer: SRV01

    Description:

    failure trying to synch site a2f20e04-ea0a-4a32-b2c7-0aba30580d82 for ContentDB d0f0117b-a131-4796-be05-fa9ac6c97885 WebApp 6638b673-3190-409d-8e8f-ef539595a09a. Exception message was An entry with the same key already exists..

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    can you please help me at this problem.

    Monday, May 26, 2008 5:37 AM
  • hi i couldnt get results from the select query,

     i have the same problem can you please help me at that, please refer to my question below

    thanks

     

    Sunday, June 1, 2008 6:13 AM
  • Molayyan - are you querying the Content Database or the Config Database? It should be the Config. If you are on the config database, maybe you are using the wrong ID number. Your log file will give you three ID numbers,

    like this:

     

    failure trying to synch site 5201g6e7-c348-05c8-7274-0coi4gh445f6 for ContentDB c8c28f87-5def-4acf-b65b-aerh445f242a WebApp 2e54e8wd-45c1-4t7s-b1ti-40846926g23d

     

     

    Make sure you are using the site and WebApp ones to figure out which item is causing your problem (not the ContentDB ID). At least when I used my ContentDB ID I got no results either.

    Monday, June 2, 2008 4:24 PM
  •  

    Hi Edkrull

    i am sorry because i am new to the administration part of MOSS2007, and thank you for helping me

    Let me understand this

    below are three databases who are cousing the problem on the SSP


    C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
    dm.exe -o sync -listolddatabases 0

    Shared Service Provider XXXXXXX
    ID: 9d874959-de1c-4ee4-b330-4c08c2285011  Synchronized: 6/18/2008 9:00:00 AM
    ID: 47368b73-7581-4635-8b01-d802defae1c5  Synchronized: 6/18/2008 9:00:00 AM
    ID: d0f0117b-a131-4796-be05-fa9ac6c97885  Synchronized: 6/18/2008 9:00:01 AM

     

    after that i should prepare the SSP content database to remove then reattach the conetnt database again ? or should we do those steps to the Site Content database ?

     

     

    Wednesday, June 18, 2008 6:56 AM
  • I was just wondering if when you were doing your query that got no results, which DB you were querying. The fix given above should resolve your issue.

    Wednesday, June 18, 2008 12:37 PM
  • Hi Edkrull

    i used the configuration database and i got the result, the database name that contains the error is the site content database.

     

    Monday, June 23, 2008 6:13 AM